LPC MicrocontrollersのトピックRe: user code doesn't always start after FW load from USB

user code doesn't always start after FW load from USB

lpcware — Wed, 15 Jun 2016 19:37:58 GMT

Content originally posted in LPCWare by mspahr on Mon Apr 14 16:52:01 MST 2014
LPC11U35

I plug in the USB, makes connection into MSC disk emulation.
I hold down ISP pin then reset.
USB reconnects and shows firmware.bin file.
I delete firmware.bin and copy my user.bin file to it.
When I unplug the USB cable, sometimes my user code starts up, sometimes it does not.
Is there anything I can do to guarantee that my code starts up.

Re: user code doesn't always start after FW load from USB

lpcware — Wed, 15 Jun 2016 19:37:59 GMT

Content originally posted in LPCWare by embd02161991 on Mon Apr 14 22:25:30 MST 2014
Hi,

Please refer to the Application note AN11305: USB In-System Programming with the LPC11U3X/LPC11U2X for details.

http://www.lpcware.com/content/nxpfile/an11305-usb-system-programming-lpc11u3xlpc11u2x

Thanks,

NXP Technical Support

Re: user code doesn't always start after FW load from USB

lpcware — Wed, 15 Jun 2016 19:37:59 GMT

Content originally posted in LPCWare by mspahr on Wed Apr 16 13:13:25 MST 2014
After programming, half the time, the user code starts up when the USB connector is unplugged.
Can you explain? Is there a way to make this work every time?

I have read the app note. It says to cycle the power. I cannot because it is powered by rechargable batteries and are not accessible.
I have entered ISP mode with 2 capacitive sense buttons which are not available once in ISP mode.
How can I use the watchdog idea when I don't know how long it will take the user to delete firmware.bin and copy the new file?

Mike

Re: user code doesn't always start after FW load from USB

lpcware — Wed, 15 Jun 2016 19:38:00 GMT

Content originally posted in LPCWare by serge on Thu Apr 17 02:24:32 MST 2014
My two cents for what they are worth:
A resetbutton may be of any help?
Or writing your own bootloader which does a reset after programming the device? If this is an option of course.