HardFault after GPIO PIN set to High on Custom Board

[Buli]

Hi,

on my Custom Board I'am setting P0.12 to High triggered by a BLE notification (NUS). I'am here using the BLE Uart Example (S112, pca10040). The Custom Board's nrf52832 DCDC Pin is not connected

The Problem is, that on my Custom Board the System goes direct in the Hard Fault on the nrf52 DK not. Is there something in for P0.12 in use somewhere else?

P0.12 is bounded to an STM32 MCU's boot0 Pin with a external 10k pulldown.

if (p_evt->type == BLE_CTRL)
{

if (p_evt->params.rx_data.p_data[0]==0xFA)
{ // Bootloader Pattern1
m_ctrl=1;
nrf_gpio_pin_write(12, 1);
nrf_gpio_pin_write(11, 0);
for (uint16_t ts=0;ts<4000;ts++){}
nrf_gpio_pin_write(11, 1);

}


if (p_evt->params.rx_data.p_data[0]==0xFB)
{ // Reset
m_ctrl=0;
nrf_gpio_pin_write(12, 0);
nrf_gpio_pin_write(11, 0);
for (uint16_t ts=0;ts<4000;ts++){}
nrf_gpio_pin_write(11, 1);

}

[Buli]

The section for 0xFB works on both..custom and DK board

The section for 0xFA not it goes to the hard fault direct after nrf_gpio_pin_write(12, 1) on the custom board. On the scope I can see, that the GPIO is set on high. It seems, that something else are triggered by setting P0.12 to high, but what and why is it different to the DK board, where P0.12 aren't in use.

This is the init snipped for the GPIO's

nrf_gpio_cfg_output(11);
nrf_gpio_cfg_output(12);
nrf_gpio_pin_set(11);
nrf_gpio_pin_clear(12);

[Vidar Berg]

Hello,

I can't think of any obvious reasons for the hardfault based on the information given here. I also think it's strange that you only see it on your custom board but not on the DK.

As a start, can you post a screenshot of the call stack window after the program has entered the fault handler. Alternatively, if you can enable the HardFault handling library and post the log output here.

Best regards,

Vidar

[Buli]

Hi Vidar

here the screenshot from the call stack

[Vidar Berg]

Hi,

Please disable NRF_LOG_ENABLED in sdk_config.h to see if that changes anything. The call stack shows that it is processing logs when the fault exception was raised.

[Buli]

Hi Vidar,

now it's jumping the app_error_fault_handler to the NRF_BREAKPOINT_COND

[Vidar Berg]

Hi,

So the error is triggered in uart_event_handle, and the error code appears to be NRF_ERROR_DATA_SIZE.

You can get the exact line number of where the error occurred if you build with the 'DEBUG' flag enabled.