UART pin should not use AIN pin

[vernon]

Hi, 

I init the UART pin with the AIN pin such as P0.05, but the program will run into __WEAK void app_error_fault_handler(uint32_t id, uint32_t pc, uint32_t info) every time. Is there anyone experience this problem, any suggestion or response is appreciated.

following is the uart init funciton.

static void uart_init(void)
{
uint32_t err_code;
app_uart_comm_params_t const comm_params =
{
.rx_pin_no = RX_PIN_NUMBER,
.tx_pin_no = TX_PIN_NUMBER,
.rts_pin_no = RTS_PIN_NUMBER,
.cts_pin_no = CTS_PIN_NUMBER,
.flow_control = APP_UART_FLOW_CONTROL_DISABLED,
.use_parity = false,
#if defined (UART_PRESENT)
.baud_rate = NRF_UART_BAUDRATE_115200
#else
.baud_rate = NRF_UARTE_BAUDRATE_115200
#endif
};

APP_UART_FIFO_INIT(&comm_params,
UART_RX_BUF_SIZE,
UART_TX_BUF_SIZE,
uart_event_handle,
APP_IRQ_PRIORITY_LOWEST,
err_code);
APP_ERROR_CHECK(err_code);
}

[Martin Lesund]

Hi Vernon,

Are you sure that you are not using the p0.05 pin for anything else?

How is your defines set in BOARD_PCA10056.h ?

Are you able to get out some more information through debugging?

 

Best Regards,

Martin L.

[vernon]

Hi Martin,

Thank you very much for the reply, it seems that it is OK when RX connect to  P0.06 and TX connect to P0.05, but it will run into __WEAK void app_error_fault_handler(uint32_t id, uint32_t pc, uint32_t info) when RX connect to P0.05 and TX connect to P0.06. and for your information,  I am trying to use uart0 and uart1 at the same time and caused that problem.

 

int main(void)
{
bool erase_bonds;

bg96_at_app_init();

// Initialize.
uart_init();
uart1_init();
log_init();
timers_init();
buttons_leds_init(&erase_bonds);

.....

}

Best Regards,

Vernon

[Martin Lesund]

Hi Vernon,

Please keep in mind nrf52840 has only 1 UART so as a second peripheral you can use UARTE.

See this thread for more information.

 

(could also be interesting)

[vernon]

Hi Martin,

I have tried to use the low-frequency-IO as the UART PIN, when configuring all of these IO, the program also ran into the  __WEAK void app_error_fault_handler(uint32_t id, uint32_t pc, uint32_t info), P0.00 and P0.01 also does.  

[Martin Lesund]

Hi Vernon,

Could you try to debug the application, and see what information the app_error_fault_handler gives out.

Debugging in Segger IDE.

Are you running this on the nrf52840 DK?

Which SDK version are you using?