IAR and DFU problem

[Will_008700]

Hi 

I'd like to debug my code from IAR with nrf52840dk.

I'm using nrf5_SDK_thread_zigbee_v4.1.0.

I got this error after uploading the code inside the nf52840 dk

==>ELF/DWARF Error: Unsupported .debug_info format version: 4

I've checked the makefile, it's aligned with forum comment "-gdwarf-3"

If I remove "include debug information in output" in linker=>output, I can't debug the code, could you help me?

thanks 

[Vidar Berg]

Hi,

Is it a custom library or a SDK library that uses this debug format? Also, which one of the SDK examples are you testing with? I tried the Thread bootloader (\thread\dfu\bootloader) which uses the uECC library, but did not get this error.

[Will_008700]

Hi

I use nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8

I can't compile \thread\dfu\bootloader, I got this error " Fatal Error[Pe1696]: cannot open source file "uECC.h" 

I'm interested in coap example and I have tested simple coap client in thread\simple coap client, I can compile project with IAR 7.80 using the following mdk "nRF_MDK_8_27_0_IAR_NordicLicense.msi" provided by the sdk, but if I want debugging the firmware through the segger chip included in the nrf52840dk , I can't because I have these issues

Tue Jun 30, 2020 13:21:41: ELF/DWARF Error: Unsupported .debug_info format version: 4

Tue Jun 30, 2020 13:21:42: Failed to load debugee: Nordic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\simple_coap_client\pca10056\blank\iar\_build\ thread_simple_coap_client_pca10056.out

[Vidar Berg]

Hi,

I'm a bit surprised this hasn't been reported before, but the problem is that the 'nrf_security' libraries introduced in T&Z SDK v4.0.0  are built with .debug_info format version 4, which isn't compatible with IAR 7. Maybe you can try IAR 8 if you have that installed?

I have reported this issue internally.

Will_008700 said:

I can't compile \thread\dfu\bootloader, I got this error " Fatal Error[Pe1696]: cannot open source file "uECC.h" 

 I assumed you were testing with this project because "DFU" was mentioned. This particular project has a dependency on the uECC library that must beforehand (build scripts located in /external/micro-ecc)

[Will_008700]

Hi,

I can't use IAR 8 because I have some problems with it, I saw several topics in this forum, I'm using 7.80 for that.

I use thread/cli, I can compile, but I can't debug, I use temporarily .out in segger ozone that works "correctly". My goal is to use IAR debugging

[Vidar Berg]

I understand. I'll update the ticket as soon as I hear back from the SDK team.

[Jørgen Holmefjord]

Hi,

The problem seems to come from the nrf_security/crypto libraries being built with the wrong debug symbol configuration. The simple solution to this is to strip the debug information from the lib-files. Normally there is no need to debug these libraries and the debug symbols can be stripped out. I verified that this works on my Win10 setup with a fresh copy of the SDK:

cd nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\external\nrf_security\lib
arm-none-eabi-strip -g *.a

Best regards,
Jørgen

[Farhang]

Magic, thanks!

I wish things just worked out of the box.. Started with IAR 8.x.x, that doesn't work, OK, then to 7.80.x which is supposed to work (Release notes), oops V_ARGS_ error..compile error. OK put brackets around double Macro calls with Macro args.. OK. then this "ELF/DWARF Error"... how many hours do we embedded developers waste on getting the setup right?!
 
I still appreciate Noridc's team support but it would be nice if things "work out-the-box"

Thanks!