This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
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

ble_app_uart crashes with error 4 NRF_ERROR_NO_MEM

Hi all

I have developed my own hardware very similar to adafruit feather nrf52.

I am using the example ble_app_uart from sdk_14.2.0. The example is running fine on pca100040 and feather nrf52 but not on my own hardware:

pca100040 says:

<info> app: JoWi: log started... 
<info> app: JoWi: leds init... 
<info> clock: Function: nrf_drv_clock_init, error code: NRF_SUCCESS.
<warning> nrf_sdh_ble: RAM starts at 0x20002A68, can be adjusted to 0x20002760.
<warning> nrf_sdh_ble: RAM size can be adjusted to 0xD8A0.
<info> app: JoWi: ble init... 
<info> app: JoWi: gap init... 
<info> app: JoWi: gat init... 
<info> app: JoWi: service init... 
<info> app: JoWi: service init... 
<info> app: JoWi Modul_1 started...!

mbn modul vom murata says: (seems to be perfect)...
 0> <info> app: JoWi: log started... 
 0> <info> app: JoWi: leds init... 
 0> <info> clock: Function: nrf_drv_clock_init, error code: NRF_SUCCESS.
 0> <info> app: JoWi: ble init... 
 0> <info> app: JoWi: gap init... 
 0> <info> app: JoWi: gat init... 
 0> <info> app: JoWi: service init... 
 0> <info> app: JoWi: service init... 
 0> <info> app: JoWi Modul_1 started...!

my hardware says:

<info> app: JoWi: log started... 
<error> app: ERROR 4 [NRF_ERROR_NO_MEM] at ..\..\..\main.c:571

this line ist in

/**@snippet [Handling the data received over UART] */
void uart_event_handle(app_uart_evt_t * p_event)
....
        case APP_UART_COMMUNICATION_ERROR:
            APP_ERROR_HANDLER(p_event->data.error_communication);
            break;
...

I can't find any differences in the hardware. Clock ist oscillating fine. Power supply fine. Memory should be the same.

Does anyone have an idea how to debug... ?

br j

Parents
  • I found the problem. we connected another controller to the rxd pin. for some reason this output was high-z and the input was left floating. i would suggest to pull up the rxd-pin in your examples, if that is possible. a colleque found the same problem some times ago ...

Reply
  • I found the problem. we connected another controller to the rxd pin. for some reason this output was high-z and the input was left floating. i would suggest to pull up the rxd-pin in your examples, if that is possible. a colleque found the same problem some times ago ...

Children
No Data
Related