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
Uncaught InternalError: setDeviceClockCmd: Unknown Device 816 with 1v80, not 1v79 #559
Comments
Changing Serial4 in Serial3 with the same pins did not show any error. However Serial3 doesn't receive any data. |
Changing to Serial2 worked with A2 and A3 pins...
Which means that is is a problem linked with the pins definitions... |
Thanks - Sorry about that. Just fixed this (so it'll work in the build from http://www.espruino.com/binaries/git/commits/594759be79485dc9ace2b8459fb99117f8c6407c) but there are still issues with Serial3 on C10/C11 (it works on B10/11) so leaving this bug open for now. |
Ok, thanks for beeing so fast. |
Strange - looks like I messed up with git :) This one will have a build in an hour or so: http://www.espruino.com/binaries/git/commits/22398e5f3007f4faae7cca59cce7bdc59ac38acf I did try a previous build from today and it works - are you sure you chose the correct binary? |
Still the same problem on
|
Argh, sorry - embarassing. Got it working, then did a quick code tidyup before commit and broke it again :) http://www.espruino.com/binaries/git/commits/286fed3ea0006fa7dd3f10ddc9a8c65023972a22 will be another hour before that's built though |
Ok 👍 that one runned correctly with
Should we wait that you solve the Serial3 problem to close this one? |
Actually, lets close this. I just found there is a bug for Serial3 already :( #409 |
I just updated my Espruino board 1v4 to interpreter 1.80.
I tried to run a Serial4 logger and I received this error message from the very first line of code:
Interestingly it show C11 as
And furthermore, not copy / pastable, I had to type a Carriage return on the left console to get the '>' prompt immediatly after the error happened.
Version 1v79 was working perfectly just a few seconds before...
Removing the pin's defintions does give the same error's message.
And removing only rx's pin definition does not show the
after a dump() but the error remains.
The text was updated successfully, but these errors were encountered: