Important changes to forums and questions
All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.
5 years, 9 months ago.
nRF51-DK: exported gcc version didn't work
I tested mbed_blinky in developer site. This version is working good.
But same project export gcc version. I compiled this project in my computer. gcc version didn't work.
Let's me know What's wrong form me?
PS mbed_blinky_gcc_arm_nrf51_dk.zip file is export file. /media/uploads/jade74/mbed_blinky_gcc_arm_nrf51_dk.zip
Best Regards. Jade, Lee
Question relating to:
5 years, 7 months ago.
I'm having this issue, even after running make merge. Everything compiles and links without errors, but after drag'n drop the "combined.hex" file, nothing happens. It seems it's not jumping to main(), since I have LED1=1 at the beginning.
Anyone has an idea of what can I do to solve this?
5 years, 8 months ago.
Hi all guys, I'm experiencing the same problem written above.
I've successfully ran the online-compiled version of the blinky test code. I've tweaked it a bit so it is 244836 byte large. I copy it on the FileSystem and it runs as expected.
I've also tried exporting this example for offline working (that is what will be my stable workbench) and it compiles and link nicely.
The first strange thing is that the .bin (which is said to be the right version to flash in the last line of this document https://developer.mbed.org/handbook/Exporting-to-GCC-ARM-Embedded ) executable is only 29988 byte large while the .hex is 84402 byte large.
As I drag'n drop the .bin file onto the drive, it appears a fail.txt reporting "OUT OF MEMORY".
If, otherwise, I drag-n drop the offline-compiled .hex file, it appears the same file reporting "CORRUPT FILE".
Can you please where I'm doing wrong? Have you any hint for a newbye like me? Thank you in advance.
Have a nice Sunday :)