build from source issue
Posted: Mon Jul 08, 2019 8:03 am
Hi,
I have build the nRF52 version with BOARD=microbit. I have a very recent version, 1.11.
The build does create a hex file. I can flash this onto the board (using the "mount", I don't use PyOCD).
However, the serial output only gives a single 'M'. At first I thought it could be a baudrate issue, but the M is also the first character of the MicroPython prompt.
In main.c I added do_str with a print("ABCD") and rebuilt the project. After flashing, the serial output only gives a single 'A'. So, I think it is something different than a baudrate issue.
I have used a gcc-7 and a gcc-8 version. Could it be related to the compiler?
When downloading a MicroPython project from the MicroBit website and online editor, the hex file does work (although it is much larger), so the board is OK.
I do remember, though I am not sure, that I had the same issue when building for STM32 for a NUCLEO board.
Any ideas? Is this a known issue?
I have build the nRF52 version with BOARD=microbit. I have a very recent version, 1.11.
The build does create a hex file. I can flash this onto the board (using the "mount", I don't use PyOCD).
However, the serial output only gives a single 'M'. At first I thought it could be a baudrate issue, but the M is also the first character of the MicroPython prompt.
In main.c I added do_str with a print("ABCD") and rebuilt the project. After flashing, the serial output only gives a single 'A'. So, I think it is something different than a baudrate issue.
I have used a gcc-7 and a gcc-8 version. Could it be related to the compiler?
When downloading a MicroPython project from the MicroBit website and online editor, the hex file does work (although it is much larger), so the board is OK.
I do remember, though I am not sure, that I had the same issue when building for STM32 for a NUCLEO board.
Any ideas? Is this a known issue?