• State Not Answered
  • Replies 10 replies
  • Subscribers 63 subscribers
  • Views 1640 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 236258
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrf52832 hangs in non-debug mode

DevenE

We have custom developed board using nrf52832. When I run the example program developed in SDK15.0.0 with Soft device S132 V6.1.1, no issue noticed in running debug mode (with J-link Debugger) or non-debug mode.

 If we run the already developed code in SDK14.2.0 with soft device S132 V5.0.0, I didn’t see any issue on debug mode. As expected, peripherals are working and BLE communication started and sending data. Same setup, run in non-debug mode, noticed that it hangs on the while loop. Please advise any reason for this issue

  • 0
    DevenE said:
    hangs on the while loop

    What "while loop" ?

    When you say "debug mode" and "non-debug mode" are you talking about different build configurations? or whether the J-Link is connected or not? or whether a debug session is active or not?

  • 0 in reply to awneil

    infinite "While loop" in the main () routine. After initialization, it’s enter into the infinite while loop. Basically it checks the key press interrupt, if key pressed start advertising before go to low power mode in the  while loop.

    “ Debug Mode” : J-link is connected to Segger Embedded Studio IDE and run the program in debug mode.

    “Non Debug mode”: With out J-link connection. I tried different build configuration (release  & debug) as well. Also, checked with 32.768kHz external Xtal on the board and with out external Xtal (Configured internal RC). 

    Example program developed in SDK15.0.0 with Soft device S132 V6.1.1, no issue noticed in debug & non- debug mode. I am able to scan the BLE device from "nrfConnect" apps from my phone establish connection.

  • 0 in reply to DevenE

    Are you enabling the DCDC regulator in your old code by any chance? This could potentially explain the difference between debug and non-debug mode in your case. The chip will always use the LDO regulator when in debug mode, while it's FW dependent when you exit it.  In that case, maybe you are missing the two extra inductors required for DCDC operation?

  • 0 in reply to Vidar Berg

    Thank you Vidar Beng for your response.

    DCDC regulator is not enabled in our code: Only noticed in "sdk_Congif.h"  but it's not enabled.

    // <q> POWER_CONFIG_DEFAULT_DCDCEN  - The default configuration of main DCDC regulator
     
    // <i> This settings means only that components for DCDC regulator are installed and it can be enabled.
    #ifndef POWER_CONFIG_DEFAULT_DCDCEN
    #define POWER_CONFIG_DEFAULT_DCDCEN 0
    #endif
    // <q> POWER_CONFIG_DEFAULT_DCDCENHV  - The default configuration of High Voltage DCDC regulator
     
    // <i> This settings means only that components for DCDC regulator are installed and it can be enabled.
    #ifndef POWER_CONFIG_DEFAULT_DCDCENHV
    #define POWER_CONFIG_DEFAULT_DCDCENHV 0
    #endif
    2 extra inductors (15uH & 15nH) are used in our board as Raytac's MDBT42 V P 512K V2 reference design.
    Our input power is 3V and well stable from the measurement.The firmware examples that we followed, I didn't notice that DCDC is enabled in the firmware. Please advise what circumference, DCDC is need to enable?
  • 0 in reply to DevenE

    I enable the  DCDC in "sdk_config.h" and noticed that 1.265V @ DCC4 pin. 

Related