a parasitic character in the input buffer. Which creates those strange errors "Uncaught SyntaxError: Got ?[255] expected EOF"
I have to check UART6 and more details on I/O.
Just a complement about Nucleo boards:
A- port A: the ST-LINK/V2-1 is using some of its pins to debug and program as mbed needs it.
PA2 and PA3 are the USART2 console TX/RX.
"PA13 and PA14 share with SWD signals connected to ST-LINK/V2-1, it is not recommend to
use them as IO pins if ST-LINK part is not cut."
B- power supplied from USB port: there is the negotiation between the host and the Nucleo that happens at boot time. If there is no agreement from the host, the Nucleo will only use 100 mA from the USB port. This happens when the Nucleo is powered from an USB power supply. The jumper JP1 determines that (manual UM1724 page 17/54). This could also be a trap when more power is required at boot time or later.
C- various default solder bridges change a lot of details around the pins potential usage.
Again thank you for supporting an "unofficial board".
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Congratulations: Now BTN1 and setWatch do work!!!
The remaining problems are now:
Just a complement about Nucleo boards:
A- port A: the ST-LINK/V2-1 is using some of its pins to debug and program as mbed needs it.
use them as IO pins if ST-LINK part is not cut."
B- power supplied from USB port: there is the negotiation between the host and the Nucleo that happens at boot time. If there is no agreement from the host, the Nucleo will only use 100 mA from the USB port. This happens when the Nucleo is powered from an USB power supply. The jumper JP1 determines that (manual UM1724 page 17/54). This could also be a trap when more power is required at boot time or later.
C- various default solder bridges change a lot of details around the pins potential usage.
Again thank you for supporting an "unofficial board".