Content originally posted in LPCWare by CodeRedSupport on Tue Apr 27 05:09:48 MST 2010
Ok, thanks for the confirmation.
I've just tried merging code from the RDB1768cmsis_UART_print example into the RDB1768cmsis_usb_bootloader, so that I get an initial printf displaying to the terminal on my PC when the bootloader begins running. And deleting firmware.bin still works fine.
If you are getting a hard fault, then you can tell where in your sources this is being caused by looking at the VECTPC pseudo-register that is displayed in the Core Register view when the hard fault is trapped. If you hover your mouse over VECTPC, it will do a lookup on the address and the tooltip will show you where in your code that is.
Hopefully from there, you should be able to find and fix the cause of the fault.
Regards,
CodeRedSupport