nrF52840 get disassembled code from hex file

[Shreya J B]

Hi, 

I am using nrf52840, nrf SDK16.0.
we have created hex file using embuild. whenever hard fault occurs, we are storing had fault stack details in non-initialized memory. After reset i.e on por we are sending hard fault stack details through Ble.
so we need to extract PC, PSR, and other hard fault details from the hex file generated using embuild. can we get this details?

Thank you

Shreya

[Vidar Berg]

Hi Shreya,

It depends if this information is stored in the hex file. Does your application store exception info to FLASH?

Best regards,

Vidar

[Shreya J B]

Hi Vidar,

sorry before seeing your reply, I have edited my question and updated more info regarding what we are looking for.
we are storing Hardfault info in non initialsed memory.

[Vidar Berg]

The hex files does not contain debug symbols. Instead, you should be looking at the *.elf and *.map file from your build folder. 

[Shreya J B]

Hardfault details has the program conter value & complete stack details. Since we have generated the hex file using the embuild tool we need some tool which converts this hex file to code, to know which code caused the hardfault. We tried loading emuild generated hex file into segger tool to get code, but we did not get.

 

Is there way to map program counter value to code?, using some tool.

[Vidar Berg]

embuild should also output the *.elf file and *.map file. If it doesn't, you need to go over the build configurations. It doesn't make sense to spend time disassembling and reverse-engineering the hex file.

[Shreya J B]

Thank you. we are getting *.elf and  *.map file.