Hi,
Today, I installed Mbed Studio (on Windows 10) and connected an Mbed LPC1768 target. I downloaded the mbed-os-example-blinky, build and compiled, using the debug icon. I folowed the instructions from the ARM Mbed Studio manual. Mbed Studio however does not flash the target, and I get two notifications:
Timeout waiting for gdb server to start;
Build of mbed-os-example-blinky completed: Program compliled;
‘dragging and dropping’ the binary from the Build directory however works.
I do not have this target so I can not test it but the Build and Deploy must work. If not then try to update mbed Interface Firmware.
Also for deploy without debug just use the Play button.
Jan, thanks. I tried several combinations of build profile (‘Develop’ or ‘Release’), and Build (‘Hammer’) and Build & Run (‘Play’), but none of them flashes the target… Just continue my investigations
All, just got a message from the MBed Studio team, stating:
‘LPC1768 is not yet fully supported in Mbed Studio. Studio uses python tool called pyOCD for binary flashing and debugging a program on the board. Unfortunately, pyOCD fails to work correctly with that target. We are working with pyOCD maintainers to resolve this issue’
After struggling for a while with similar issue(s), I came to the conclusion, that the best is to forget the Mbed Studio (tested both Win and Mac) and use Eclipse for the development. Not so fancy, but it works.
Besides that, forget the pyOCD and invest into a real HW JTAG debugger, if you want to do some serious development. I recommend Segger J-Link. Although it is not cheap, the time you will invest in making the things work outweighs the costs of it.
The low cost alternative to start with less pain is, to switch to a Mbed compatible board with an integrated JTAG debugger. E.g. STM-Fxx-DISCO boards , with detachable ST-Link.
In latter case avoid low-power CPU boards as this also does not work entirely well with Mbed Studio (e.g. STM-Lxx series, can be flashed but not debugged).