problem with RDB1768 secondary USB bootloader

lpcware · ‎06-15-2016

Content originally posted in LPCWare by navman on Wed Feb 22 04:13:24 MST 2012
Hi,
I've been trying to get the RDB1768 USB bootloader example to work. So far, I've done the following:
1) Loaded the USB bootloader to the RDB board.
2) It enumerates as USB drive when the joystick button is pressed and board is reset (or if no valid user app is found).
3) I delete the firmware.bin already on the USB drive, rename the application code to firmware.bin and copy it to USB drive. Then safely remove the drive from windows.
4) Disconnect and re-connect USB cable (which also carries power)to the RDB board.
5) The LCD displays "Running user app from flash".
6) The user app doesn't do what it is supposed to do (blink LED). However, when it is loaded to the RDB board as a standalone app, it works just fine.

I've modified the linker scripts of the user app and made sure that the app starts from memory location 0x10000 instead of 0x00 as mentioned in the readme.txt accompanying the USB bootloader example.

I'm attaching the app code (led_blink) as well as the USB bootloader codes.

Please can somebody tell me what I'm doing wrong?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by navman on Wed Feb 22 23:48:48 MST 2012
Thanks, changing the path of the .ld files in the INCLUDEs did the trick. I had somehow missed them completely from the readme.txt file. I must be reading the instructions more carefully henceforth :)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Ex-Zero on Wed Feb 22 09:00:40 MST 2012

Quote: navman

...
I've modified the linker scripts of the user app and made sure that the app starts from memory location 0x10000 instead of 0x00 as mentioned in the readme.txt accompanying the USB bootloader example.

No, exactly that's what you didn't :eek:

What Memory Configuration is your map-file reporting?

Quote:

Memory Configuration

Name             Origin             Length             Attributes
MFlash512        0x00010000         0x00070000         xr
RamLoc32         0x10000000         0x00008000         xrw
RamAHB32         0x2007c000         0x00008000         xrw
*default*        0x00000000         0xffffffff

If it's still reporting:

Quote:

MFlash512 0x00000000 0x00080000 xr

you've includes a wrong mem-file or forgotten to add the correct path :rolleyes:

Quote:

INCLUDE "[COLOR=Red]../linkscripts/[/COLOR]Blink_led_Debug_lib.ld"
INCLUDE "[COLOR=Red]../linkscripts/[/COLOR]Blink_led_Debug_mem.ld"

Notes:

#1 You don't have to change the name of your bin-file to firmware.bin before you copy it.

#2 You are still using CMSISV1.3

#3 It's useless to read CLR / SET register so just use

LPC_GPIO1->FIOCLR [B][COLOR=Red]=[/COLOR][/B] (1<<24);
....
LPC_GPIO1->FIOSET [B][COLOR=Red]= [/COLOR][/B](1<<24);