Program not run on NRF52832 QFAAB0

[ANSH]

Dear Sir,

 I am working on NRF52 and I have DK of PCA10040 / V1.2.1 / 2017.36 / 682236729. I have done program advertising with scanning both in one program. then I used custom board which used N52832 QFAAB0. some due to reason IC has been heat and unplaced. then new IC mounted and then burn program. program run only 1 time and generate following error,

1. <debug> ble_scan: Added filter on UUID 1

2. <debug> ble_scan: Scanning

3. <error> app: SOFTDEVICE: ASSERTION FAILED.

                               How to resolved this and this issue coming in new IC after mount.

Regards

 Ansh

[Jared]

Hi,

How many samples are you seeing this issue on? Only on the one that you replaced the IC on?

3. <error> app: SOFTDEVICE: ASSERTION FAILED.

 The error message should also include where in the softdevice the assert is happening. Did you get any more info?

regards

Jared 

[ANSH]

Dear,

I am working on NRF52 and I have DK of PCA10040 / V1.2.1 / 2017.36 / 682236729. I have done program advertising with scanning both in one program. then I used custom board which used N52832 QFAAB0. some due to reason IC has been heat and unplaced. then new IC mounted and then burn program. program run only 1 time and generated following error,

<error> app: SOFTDEVICE: ASSERTION FAILED.

                               After Flash and RAM segment changes, this following segment,

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x80000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x10000

FLASH_START=0x26000

FLASH_SIZE=0x52000

RAM_START=0x200038D8

RAM_SIZE=0xC728


Now program burnt in UC and verified also, but program counter not found . now new mounted Controller is N52832 / QFAAB0 / 1649ER . this is on place of N52832 / QFAAB0 / 1748kj. i have used new controller and examples of SDK16. will boot loader or memory segment or any other files required? means will be do initial setting on SEGGER Embedded Studio 5.10a and I used s132_nrf52_7.0.1_softdevice. please give me suggestion.

Regards

Ansh

[Jared]

Hi,

Please address this question from my previous reply: 

Jared said:

How many samples are you seeing this issue on? Only on the one that you replaced the IC on?

The first step would be to figure out if the issue is linked to your specific custom board or if it's SW related issue. Could you try to upload a SDK for example ble_app_blinky and see if it advertises successfully on the custom board.

If it does, then the issue is probably a SW issue. Could you proceed with sharing the full error message that is outputted in SES. Preferably a screenshot of the debug console in SES. 

regards

Jared