Debugging DFU in IAR - SDK12.3.0!!!

RE: Debugging DFU in IAR - SDK12.3.0!!!

Vidar Berg — Mon, 20 May 2019 12:12:31 GMT

Hi,

Please post a new question since this is unrelated to the original issue you had. The problem may be that you have not increased the NRF_SDH_BLE_VS_UUID_COUNT in your sdk_config.h file and adjusted the APP RAM base address.

RE: Debugging DFU in IAR - SDK12.3.0!!!

Urvisha Andani — Mon, 20 May 2019 12:01:14 GMT

Hi,

I add initialization of DFU in my program and then upload program in device. Program runs successfully and starts advertising.

When I add custom service in my program and then upload program in device at that time program is getting stuck somewhere. so please give suggestion.

RE: Debugging DFU in IAR - SDK12.3.0!!!

Vidar Berg — Mon, 13 May 2019 11:04:57 GMT

Thanks for the update. Note that the mdBT40 comes two memory variants so I think you may have the 16K RAM one since you had to change the linker settings to make it work.

RE: Debugging DFU in IAR - SDK12.3.0!!!

Urvisha Andani — Mon, 13 May 2019 10:18:55 GMT

Thanks for the input by following them my problem got resolved.

RE: Debugging DFU in IAR - SDK12.3.0!!!

Vidar Berg — Mon, 13 May 2019 09:19:41 GMT

The APP RAM base must be 0x200025e0. Can you try this and see if you get the same result?

RE: Debugging DFU in IAR - SDK12.3.0!!!

Urvisha Andani — Fri, 10 May 2019 10:29:33 GMT

I also change of RAM address as you told but not run show like below,

RE: Debugging DFU in IAR - SDK12.3.0!!!

Urvisha Andani — Fri, 10 May 2019 10:21:29 GMT

Actually I am using mdbt40 custom board in which nRF51822 use.And in this module 32K RAM is available showing in specification of mdBT40 and link is given below,

https://www.seeedstudio.com/MDBT40-256RV3-nRF51822-based-BLE-module.html

RE: Debugging DFU in IAR - SDK12.3.0!!!

Vidar Berg — Fri, 10 May 2019 10:12:22 GMT

The memory settings are for the 32K RAM variant, while your chip has 16K. Try to change the RAM end address to 0x20004000 and start address to 0x20002500.

Edit: RAM base must be at least 0x200025e0 for the bootloader in SDK 12.3.0

RE: Debugging DFU in IAR - SDK12.3.0!!!

Urvisha Andani — Fri, 10 May 2019 10:06:53 GMT

Memory setting is as like below,

And use nRF51822 QFAA.

RE: Debugging DFU in IAR - SDK12.3.0!!!

Vidar Berg — Fri, 10 May 2019 09:57:33 GMT

Which memory variant of the 51 are you using? And does the bootloader work if you just program it nrfjprog, etc.?

RE: Debugging DFU in IAR - SDK12.3.0!!!

Urvisha Andani — Fri, 10 May 2019 09:52:58 GMT

Hi,

Thanks for reply.

I haven't got this error but still advertisement is not start and debug window show like below,

And I have also try to scan my device in nRF connect application but not show in my device.

RE: Debugging DFU in IAR - SDK12.3.0!!!

Vidar Berg — Fri, 10 May 2019 08:53:56 GMT

Hi,

You need to change the compile flag in the Makefile as well: "CFLAGS += -Wall -Werror -Os -g3" --> "CFLAGS += -Wall -Werror -Os -gdwarf-3"

RE: Debugging DFU in IAR - SDK12.3.0!!!

Urvisha Andani — Thu, 09 May 2019 13:22:21 GMT

Hi,

I have run this script and output is shown below,

But still having the same error.

RE: Debugging DFU in IAR - SDK12.3.0!!!

Vidar Berg — Thu, 09 May 2019 13:03:02 GMT

Try to run the script below in \nRF5_SDK_12.3.0_d7731ad\external\micro-ecc. You need to have Make, Git, and the GCC toolchain installed (4.9 2015q3 release)

devzone.nordicsemi.com/.../build_5F00_all.bat

RE: Debugging DFU in IAR - SDK12.3.0!!!

Urvisha Andani — Thu, 09 May 2019 12:58:14 GMT

hi,

Thanks for reply.

Can you please share step to compile uECC? I have downloaded uECC library from github but haven't compile it.

RE: Debugging DFU in IAR - SDK12.3.0!!!

Vidar Berg — Thu, 09 May 2019 11:58:07 GMT

Hi,

It because of the uECC library. The debug information generated by GCC is not compatible with IAR. Try to compile the library without '-g' or compile with '-gdwarf-3' to override the default DWARF version.