This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Custom hardware with MDBT42 module (nRF52832) only works while debugging or RTT viewer connected.

Hi,

We are developing a custom hardware that has MDBT42 module with nRF52832 chip on it. Our project is based on the ble-throughput example and this module is using the peripheral role. We are using zephyr v2.7.99-ncs1-1 and nrf connect sdk v1.9.1. You can also find the changes we have made in the prj.conf file:

# Clock control
CONFIG_CLOCK_CONTROL=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n
CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y

CONFIG_SPI=n
CONFIG_NRFX_SPIM=y
CONFIG_NRFX_SPIM1=y

CONFIG_ADC=y

CONFIG_GPIO=y

As you can see, we are using the internal RC oscillator. The code works perfectly on the nRF52-DK but it only works while debugging or RTT viewer connected with the custom hardware. We have tested several things to overcome this issue but couldn't find a solution yet.

I would very much appreciate if you can suggest a solution to understand the issue. I can also send the schematic through private channels if needed.

Thanks.

Parents
  • Hi,

    Do you have the external inductors needed for the DCDC converter on the custom board?

    If the DCDC converter have been enabled in software and there are no external inductors this behavior can occur. In debug mode the regulator is always operating in LDO mode regardless of what is configured in software.

     

    Best regards,

    Bendik

Reply
  • Hi,

    Do you have the external inductors needed for the DCDC converter on the custom board?

    If the DCDC converter have been enabled in software and there are no external inductors this behavior can occur. In debug mode the regulator is always operating in LDO mode regardless of what is configured in software.

     

    Best regards,

    Bendik

Children
No Data
Related