OAD binary size

RE: OAD binary size

Vidar Berg — Mon, 03 Aug 2020 13:05:34 GMT

Hi Lakshmi,

Yes, but that's why I need you to debug the application to see what happens. It might be a problem with the code size as you say, but there may be other reasons for this as well.

RE: OAD binary size

Lakshmikanth Satyavolu — Mon, 03 Aug 2020 13:01:04 GMT

Hi Vidar,

I got that. But the issue is, the same application working perfectly when it run standalone. Another thing is If i reduce the code size by removing few modules, this works with boot loader service too.

There is something with code size it seems. How can we debug that?

Best

Lakshmi

RE: OAD binary size

Vidar Berg — Mon, 03 Aug 2020 07:26:54 GMT

It appears to be stuck in your application code (around address 0x00026CC8). So you need to debug the application.

RE: OAD binary size

Lakshmikanth Satyavolu — Fri, 31 Jul 2020 12:49:54 GMT

Hi Vidar,

Sorry for late response. Been busy with some other stuff. I have run this command. Below is the output for your reference. Please suggest a fix.

R0: 0x00004001
R1: 0x00004001
R2: 0x0003CB2C
R3: 0x00000001
R4: 0x00001000
R5: 0x200077D4
R6: 0x10001000
R7: 0x0007E000
R8: 0x00000000
R9: 0x00000000
R10: 0x00000000
R11: 0x00000000
R12: 0x20003A11
SP: 0x2000FED0
LR: 0x00026D03
PC: 0x00026CC8
xPSR: 0x21000000
MSP: 0x2000FED0
PSP: 0x00000000

Best

Lakshmi

RE: OAD binary size

Vidar Berg — Tue, 02 Jun 2020 12:28:21 GMT

What do you use to debug, Segger embedded studio? In any case, I would start by running the "nrfjprog --readregs" command after the app has started to hang (nrfjprog is a part of our nRF5x Command Line Tools package). This will return CPU registers such as the Program counter value that may help us figure out exactly where it hangs.

RE: OAD binary size

Lakshmikanth Satyavolu — Mon, 01 Jun 2020 11:42:13 GMT

Hi Vidar,

Please suggest about debugging OAD application.

Best

Lakshmi

RE: OAD binary size

Lakshmikanth Satyavolu — Fri, 29 May 2020 12:07:08 GMT

Hi Vidar,

I have tested my application standalone without DFU programmed. It is working alright.

I have no idea how to debug dfu+appilcation using a JLINK step by step. Can you please help?

-Lakshmi

RE: OAD binary size

Vidar Berg — Fri, 29 May 2020 11:38:38 GMT

Thanks for confirming. I think the next step is to try debugging the application after you have completed the DFU to find out where it hangs.

RE: OAD binary size

Lakshmikanth Satyavolu — Fri, 29 May 2020 11:33:20 GMT

I verified it. FDS_VIRTUAL_PAGES has been set to 3 in my application sdk_config.h. Which is matching NRF_DFU_APP_DATA_AREA_SIE.

What else could be the problem?

RE: OAD binary size

Vidar Berg — Fri, 29 May 2020 09:49:21 GMT

It's going to correspond to the number of FDS_VIRTUAL_PAGES if you are using FDS in your app (either directly or through the Peer manager module). Each page is 4096 bytes by default.

RE: OAD binary size

Lakshmikanth Satyavolu — Fri, 29 May 2020 07:37:01 GMT

Hi Vidar,

I found, NRF_DFU_APP_DATA_AREA_SIE of dfu bootloader, it is 12288.

Where to find application data region to match with?

Regards

Lakshmi

RE: OAD binary size

Vidar Berg — Mon, 25 May 2020 12:07:26 GMT

Hi,

Are you able to debug the application after completing DFU? That should help you determine where the app gets stuck.

A common reason for issues like this is that the bootloader is overwriting parts of the 'application data' region during DFU that leads to initialization problems next time the app is booted (see Memory layout). You may want to verify if the NRF_DFU_APP_DATA_AREA_SIZE config in your bootloader matches the size of the 'application data' region used by the app first as that will prevent the possibility of getting overwrites.

RE: OAD binary size

Lakshmikanth Satyavolu — Mon, 25 May 2020 08:40:00 GMT

Hello Tech support team,

Please look into it.

Regards

Lakshmi

RE: OAD binary size

Lakshmikanth Satyavolu — Fri, 22 May 2020 12:57:59 GMT

Hi Guys,

Can someone please look into it?

Best

Lakshmi