nrf52832 custom board power on question

[ytpark]

onkey_full_20170814.hex onkey_0000.hex onkey_boot_s132.hex This time 14.0 sdk was updated.

There was a problem after the update

Problems when uploading bootloader

1. custom board : remove 32.76khz cyristal

• Power on -> do not run -> hw reset -> run

• power on -> do not run -> power off -> power on -> do not run -> hw reset -> run

2. custom board : No remove 32.76khz cyrisal

• power on -> run -> power off -> power on -> run -> hw reset -> run

Why does not runing the board remove 32.76khz cyristal?

The code changes below : (nrf_sdh.c) 168 line

nrf_clock_lf_cfg_t const clock_lf_cfg =
{
    .source        = 0,
    .rc_ctiv       = 16,
    .rc_temp_ctiv  = 2,
#ifdef S132
    .accuracy      = 7
#else
    .xtal_accuracy = NRF_SDH_CLOCK_LF_XTAL_ACCURACY
#endif
};

[bjorn-spockeli]

log continued ...

<debug> nrf_sdh_soc: In nrf_dfu_transports_init
<debug> nrf_sdh_soc: num transports: 1
<debug> nrf_sdh_soc: Initializing BLE DFU transport
<debug> nrf_sdh_soc: vector table: 0x00073000
<debug> nrf_sdh_soc: vector table: 0x00073000
<debug> nrf_sdh_soc: Error code - sd_softdevice_vector_table_base_set: 0x00000000
<debug> nrf_sdh_soc: Enabling SoftDevice.
<warning> nrf_sdh: RAM start should be adjusted to 0x20002180.
<warning> nrf_sdh: RAM size should be adjusted to 0xDE80.
<debug> nrf_sdh_soc: SoftDevice enabled.
<debug> nrf_sdh_soc: nrf_dfu_settings_adv_name_is_valid FALSE
<debug> nrf_sdh_soc: Regular adv name
<debug> nrf_sdh_soc: #### Advertising NO BONDING ####
<debug> nrf_sdh_soc: Finished initializing BLE DFU transport
<debug> nrf_sdh_soc: After nrf_dfu_transports_init
<debug> nrf_sdh_ble: Calling nrf_dfu_flash_init(sd_irq_initialized=true)...
<debug> nrf_sdh_ble: Initializing nrf_fstorage_sd backend.
<debug> nrf_sdh_soc: Waiting for events

[bjorn-spockeli]

What firmware is present on the nRF52832 before you update the bootloader, i.e. which SDK is the bootloader based on and which SoftDevice version is present? Does the new bootloader.hex file run on the custom board if you flash it with a programmer( not perform a DFU)?

[ytpark]

Please refer to the video.

softdevice : s132_nrf52_5.0.0 , bootloader based(SDK 13) -> power on -> working

softdevice : s132_nrf52_5.0.0 , bootloader based(SDK14) -> power on -> not working(Operation at reset)

link text

[bjorn-spockeli]

Can you check if the new bootloader.hex file( with the RC OSC config) runs on the custom board with no 32kHz crystal, i.e. advertises DfuTarg if you flash with the nRF52DK to the custom board together with the SoftDevice? Do the same for the application, i.e.e only flash the application and SoftDevice to the custom board without the 32kHz crystal. If both of them runs, i.e. advertises, then this is not a clock issue and it must be something else.

[ytpark]

If I do not modify the bootloader(RC OSC), it will not work.

After reset, not working

Send me

32khz removed boot loader file(with the RC OSC config) on sdk 14 base