-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avr8js does not to run grbl firmware completely accurately. #55
Comments
Thanks @yiivon! Can you give more details about your setup? What simulated hardware did you use? How did you test if you get correct result from the GRBL firmware? |
I've just released a fix for issue #41. If the original issue was related to timers, the fix may help. |
Thank you for your great work, it is very useful for everyone who loves avr programming. I have been working on solving some mechanical problems these days, so I didn’t reply to your message in time. I’m so sorry and so grateful. |
Hi @yiivon, I'm closing the issue for now, but if this is still a problem, feel free to add more details (about how you tested for correct results) and reopen. |
I think it is still a problem-- See #122 |
In fact, I am very eager for avr8js to run grbl firmware completely and accurately.
GRBL is a firmware implemented in pure C language running on arduino uno (ATmega328P).
I use the latest version of Proteus to run grbl for arduino simulation, and I can get the correct result. But the current avr8js does not seem to be able to achieve the same, I guess it may be that some implementations of timer are not perfect.
If you also want to make avr8js run like real chips, you can try to run grbl firmware in emulation, which may solve this problem and make avr8js close to real chips again. At the same time, it also helped me a lot.
Ask for your help and thank you sincerely!
Originally posted by @yiivon in #11 (comment)
The text was updated successfully, but these errors were encountered: