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.
7 years, 10 months ago.
on-line complier produces binaries that will run mbed platform but not on custom PCB
I am using the mbed for the LPC-1768. Are there some type of settings or configuration for the on-line complier to provide consistent binaries. Several times I have complied and flash program the binary (using a Segger arm flash programmer) to my custom PCB. Sometimes the binary will work and as soon as power is cycled on custom pcb, it begins running as indicated by the changes in different DigitalOuts pins. Other times, the binary does not "work" even tough the flash procedure was successful and there were no errors; and yes, the start application was performed. The DigitalOuts remained in the off state even though they were hard coded to turn on. The same non-working binary will run on the MBED platform for LPC1768 with no problem. What am I doing wrong?
1 Answer
7 years, 10 months ago.
Hi. If the non-working binary works on the MBED upon each RESET and/or power cycle of the MBED board then have to assume the binary is fine.
Focus on your custom PCB. What are the details ? Perhaps there is a power on RESET issue ? Do you have a manual push button on the custom PCB ? Can you post a schematic of your custom PCB ?
What is your clock source for the custom PCB ? Is it a crystal or a fixed oscillator ? If crystal, are the loading caps the proper value ? Monitor the crystal leg to confirm the crystal is oscillating during each power up of the PCB. No clock = no code run.
When you flash your version of the PCB, review the clock speed of the arm flash programming tool and slow it down to the bare minimum till the issue is resolved. If you have a LED onboard, create a simple blinky and confirm the code to work each and every time you reflash your design.