NRF52832 fault if not connect JLINK RTT viewer

[mokoysh]

Hi  nordic engineer

      I have a product  use nrf52832. And have two project,project use nrf5 17.0.0 SDK and MDK.

     The project A  choose chip nrf52832  and S132

     The project B choose chip NRF52840 and S140 ,and can adapt product 

     There have two problem:

    1、Use the project A firmware, if device not conn jlink RTT viewer, device will restart about 1 day.But if dev conn JLINK RTT ,device not restart. The problem tested many times and many device.

    2、First use project B firmware,device no problem.Then  flash the project A firmware to device and run a period time . Then flash the project B firmware to device ,some device had problem.  Some device start and ble adv,but if use phone connect the adv,device will restart.But  if device start and ble adv after device connected JLINK RTTviewer ,this adv is connectable.

    Both issues are related to JLINK,How to solve this issue?

[Einar Thorsrud]

Hi,

mokoysh said:

I will modify project A and use new product test and update to SDK17.1.0 test 

That sounds good. I look forward to knowing if that makes a difference.

mokoysh said:

    When reflash project A firmware,chip erase chip by JFLASH  and recover by nrfjprog .

    I guess two problem casued by project A. And the project A modifies the values of certain areas of the chip, such as radio configuration or efuse.  It can explain the problem 2. Is there have method to recover the chip?

"nrfjprog --recover" will erase the entierflash and UICR, and there are no fuses, so this means that there will be no trace of firmware A if that is used. So this is strange - could there be a problem with the testing, and that there pattern described where using firmware A causes problem after subsequently programming firmware B, is a red herring?

Br,

Einar