This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF51822 reset during BLE connection/transfer

Hello,

in our application I can see, that sometimes the nRF51822 completely resets, during a BLE transmission. I am using S120 as peripheral. The peripheral is connected to a peer (smartphone). Now the central (smartphone) tries to send some data. Sometimes, this operation works and sometimes, a reset on the peripheral side occures. At the moment I try to debug the connection with the sniffer. Maybe there is something wrong with the UUIDs or the data length. But is there an opportunity to debug such an error on nRF51 side? I think I have to implement some kind of error handling on the peripheral side, so that the nRF51 doesn`t run into reset. Which options do I have?

Regards, BTprogrammer

Parents
  • Hello run_ar, thanks for your reply. I am using the S120 version 2.0.0. This is what KEIL "manage runtime environment" says... Maybe your hint with the error handler brings me a step forward. I had to add dbg_printf("%d, %d, %s\r",error_code, line_num, p_file_name); nrf_delay_ms(10); to the error handler. This gives me err_code 18 at function twi_master_init() in my file i2c.c, if an error occurs. Is there any known issue when using SPI, I2C and Softdevice at the same time?

Reply
  • Hello run_ar, thanks for your reply. I am using the S120 version 2.0.0. This is what KEIL "manage runtime environment" says... Maybe your hint with the error handler brings me a step forward. I had to add dbg_printf("%d, %d, %s\r",error_code, line_num, p_file_name); nrf_delay_ms(10); to the error handler. This gives me err_code 18 at function twi_master_init() in my file i2c.c, if an error occurs. Is there any known issue when using SPI, I2C and Softdevice at the same time?

Children
No Data
Related