App does not work via DFU

RE: App does not work via DFU

Ken Matsui — Tue, 08 Apr 2014 07:58:21 GMT

Thank you so much for your detail comment, Joe. I understood your workaround to setup UICR.

Actually, I could flash and run my bootloader and app with Nordic Windows tools. So, I will try it with pure-gcc environment in MacOSX.

Thank you.

RE: App does not work via DFU

Joe Merten — Fri, 04 Apr 2014 13:19:26 GMT

Your 10001000 memory dump just shows you the Uicr register. You sould

After "make erase-all" it should be all FF. After "make flash-softdevice" we see the "00 40 01 00" and the "49 00". > mem 10001000 20 > 10001000 = 00 40 01 00 FF FF FF FF FF FF FF FF FF FF FF FF > 10001010 = 49 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF

Now, you have to write the address of your bootloader code to 10001014, so that you got e.g.: > mem 10001000 20 > 10001000 = 00 40 01 00 FF FF FF FF FF FF FF FF FF FF FF FF > 10001010 = 49 00 FF FF 00 A0 03 00 FF FF FF FF FF FF FF FF

My workaround to set up UICR for my needs is a patch in pure-gcc Makefile.posix where I add the following to the target flash-softdevice.jlink: printf "\x00\xA0\x03\x00" >$(OUTPUT_PATH)uicr_bl.bin loadbin "$(OUTPUT_PATH)uicr_bl.bin" 0x10001014\n The "loadbin..." part has to be inserted into the printf line, e.g before "r\ng\nexit\n".

Finally it looks like this:

flash-softdevice.jlink: # UICR of our bootloader located at 0003A000 printf "\x00\xA0\x03\x00" >$(OUTPUT_PATH)uicr_bl.bin # Write to NVMC to enable write. Write mainpart, write UICR. Assumes device is erased. printf "w4 4001e504 1\n loadbin "$(SOFTDEVICE_OUTPUT:.hex=_mainpart.bin)" 0\n loadbin "$(SOFTDEVICE_OUTPUT:.hex=_uicr.bin)" 0x10001000\n loadbin "$(OUTPUT_PATH)uicr_bl.bin" 0x10001014\n r\n g\n exit\n" > flash-softdevice.jlink

Well I know, that it is a little hacky to write the bootloader related UICR part during "make flash-softdevice". This should be better performed when flashing the bootloader itself and should automatically choose the bootloaders address. But that needs a bit more work inside the makefiles.

RE: App does not work via DFU

Ken Matsui — Sun, 30 Mar 2014 21:41:15 GMT

The flash.jlink script seems trying to flash correct address, though.

r loadbin _build/ble_bootloader_s110.bin 0003a000 r g exit

RE: App does not work via DFU

Ken Matsui — Sun, 30 Mar 2014 21:31:47 GMT

Hi Joe,

I was able to connect to the custom board with JLink LITE. And, I'm trying to rewrite soft device/bootloader built with pure-gcc (following your tutorial, thank you)

But the bootloader code did not locate in the flash sector "3A000h". > J-Link>mem 10001000 20 > 10001000 = 00 40 01 00 FF FF FF FF FF FF FF FF FF FF FF FF > 10001010 = 49 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF

I'm using your makefile and "LINKER_SCRIPT := ../gcc_nrf51_s110_bootloader.ld" from BleblGcc-V2. I'd appreciate it if you could give some advice for flashing bootloader with pure-gcc. Thanks in advance.

RE: App does not work via DFU

Ken Matsui — Tue, 25 Mar 2014 12:13:22 GMT

It's a custom hardware with nRF51822. And there is no JTAG adaptor yet...

So, I was not able to DFU-OTA and I'm making JTAG adaptor jig right now. Will try to check "mem 10001000 20" and "mem 3FC00 10".

Thank you.

RE: App does not work via DFU

Joe Merten — Tue, 25 Mar 2014 12:06:23 GMT

What hardware are you working on, is it a Nordic dev-board (which) or a custom hardware with nRF51822? Hoping that you own a Jtag adapter, could you provide a dump of "mem 10001000 20" and "mem 3FC00 10"?

RE: App does not work via DFU

Ken Matsui — Tue, 25 Mar 2014 11:44:08 GMT

Thank you for your advice! Actually, I bought this device from another supplier. I'm not sure how SoftDeivce and bootloader was flashed, but I think it was flashed by nRFgo Studio. (And I'm trying to upload bin file which built with gcc & Mac)

So, the causes of this issues is that the way of flashing/building SoftDevice/bootloader/App was not unified?

RE: App does not work via DFU

Joe Merten — Tue, 25 Mar 2014 11:24:46 GMT

The UICR must be set up correctly. You may check that with your Jtag adapter. If using S110 SoftDevice it looks like this:

$ JLinkExe -Device nrf51822 -If SWD
...
J-Link>mem 10001000 20
10001000= 00 40 01 00 FF FF FF FF FF FF FF FF FF FF FF FF
10001010= 49 00 FF FF 00 A0 03 00 FF FF FF FF FF FF FF FF

"00 40 01 00" is the beginning of your application code = 14000h.
"00 A0 03 00" is the beginning of the bootloader code = 3A000h. (3A000h is not the standard value here, you may see a 3C800h instead)

Normally, the UICR should set up correctly, but it may depend on the way you flashed your SoftDevice and/or your bootloader (did you used Windows nRFgo Studio or Segger JLinkExe from Linux Command line ...?).

The UICR is used by the SoftDevice for e.g.

Starting the bootloader at poweron
Switching the interrupt redirections to the application when the bootloader starts it

You may also check the bootloaders persistent data which is located in the last flash sector (3FC000h):

$ JLinkExe -Device nrf51822 -If SWD
...
J-Link>mem 3FC00 10
0003FC00= 01 00 00 00 F5 61 00 00 FF 00 00 00 DC 0A 00 00

Check bootloader_settings_t (in bootloader_types.h of the bootloader example) for the meaning of the values.

RE: App does not work via DFU

Joe Merten — Tue, 25 Mar 2014 11:11:03 GMT

What means »My app does not run«? Is the bootloader still running (still seeing the "DfuTarg" via Ble)? What bootloader are you using (e.g. bootloader example from Nordic Sdk 5.2, compiled with gcc 4.8 or Keil ...)? If using nRFgo hardware (Starter Kit) which Led's are on? Does your app running right when flashing via Jtag? Startaddress of your app 0x14000?