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

nRF52832: Setting NRF_SDH_BLE_GATT_MAX_MTU_SIZE to more than 30 cause boot failure

Hello,

I'm trying to write BLE app that talks to Android phone. sometimes I need to set MTU more than 23 bytes so I decided to increase NRF_SDH_BLE_GATT_MAX_MTU_SIZE.

But as soon as I strt debugging app stucks in the middle of nowhere:

and do not run further.

I have feeling that ihas something to do with RAM, but may be I'm wrong.

Does anybody have experience with that?

Parents Reply
  • If you couldn't see the log with Segger, enable UART log in sdk_config. 

    // <e> NRF_LOG_BACKEND_UART_ENABLED - nrf_log_backend_uart - Log UART backend
    //==========================================================
    #ifndef NRF_LOG_BACKEND_UART_ENABLED
    #define NRF_LOG_BACKEND_UART_ENABLED 1
    #endif

    Start a terminal emulator like PuTTY and connect to the used COM port with the following UART settings:

    • Baud rate: 115.200
    • 8 data bits
    • 1 stop bit
    • No parity
    • HW flow control: None

    If you still cannot see the log, please upload your project. 

    -Amanda H.

Children
No Data
Related