• State Not Answered
  • Replies 7 replies
  • Subscribers 94 subscribers
  • Views 1921 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 292501
Options

Initialization problem and bricked nrf52833 with nrf connect sdk

Dan_Y

Hi,

I'm working on a custom board based on PCA10100, nrf52833 but it seems to be stuck at the function "lfclk_spinwait".

my custom board does not have an external LFCLK.

The crazy thing is, after exiting debug mode my nrf52833 is bricked, I cannot recover, erase or flash anything on device.

I followed this issue:  Initialization problem

and added the CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y" to your prj.conf which solved the problem.

Some additional data:

  • SDK:  NCS v2.0.0
  • FW: blinky sample.

The full call stack in the image below:

The custom boards are in production ready level, passed QA and work perfectly fine with my application using nrf5 SDK.  In nrf5 SDK if I were to configure my LFCLK incorrect, i would not brick devices to a level were i cannot recover.

Appreciate you look into this.

thanks

Dan

Parents
  • 0

    You need to set the correct lfclk source (that is available for the design) in the project, else the code will freeze/hang during initialization (waiting for a lfclk source to start), however this does not explain the below issue:

    The crazy thing is, after exiting debug mode my nrf52833 is bricked, I cannot recover, erase or flash anything on device.

    Are you sure you have not enabled pin reset by some mean, and that the pin reset is pulled low? This could explain this issue. Try to connect the pin reset pin to VDD to see if the boards can allow reprogramming then. If that didn't help, it could be interesting to measure VDD on the board, to check the voltage.

    Best regards
    Kenneth

  • 0 in reply to Kenneth

    Hi,

    I am using the nrf52833 overlay / I also tried a new board

    1. HW: p.0.18 is not connected to anything. see design below.

    2. i did not add defines in prj.conf like CONFIG_GPIO_AS_PINRESET

    3. I did not touch PSELRESET[n] registers that are in default set to p0.18

    4. this is all done on a clean blinky example, the only thing i had to add to the prj.conff is the CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

    here is a similar schematics from nrf52833 product specification document:

    you can see that design does not have external pull up / down resistor.

    our design is the same.

    VDD is 3v connected directly to SoC as suppose to be, there is nothing much to see here.

    reset pin we have no access, no test point. on this 0,3mm pitch BGA so that's not an option either.

    never had issues on nrf5 SDK.

    Thanks

    Dan

Reply
  • 0 in reply to Kenneth

    Hi,

    I am using the nrf52833 overlay / I also tried a new board

    1. HW: p.0.18 is not connected to anything. see design below.

    2. i did not add defines in prj.conf like CONFIG_GPIO_AS_PINRESET

    3. I did not touch PSELRESET[n] registers that are in default set to p0.18

    4. this is all done on a clean blinky example, the only thing i had to add to the prj.conff is the CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

    here is a similar schematics from nrf52833 product specification document:

    you can see that design does not have external pull up / down resistor.

    our design is the same.

    VDD is 3v connected directly to SoC as suppose to be, there is nothing much to see here.

    reset pin we have no access, no test point. on this 0,3mm pitch BGA so that's not an option either.

    never had issues on nrf5 SDK.

    Thanks

    Dan

Children
Related
Terms of service