Is the peer functionality related to RTC?

Hello Nordic Engineer,

I used nRF52811

nRF5_SDK_17.1.0_ddde560 \ examples \ ble_central_and_peripheral \ experimental \ ble_app_multirole_lesc

After attempting to add NUS, NUS_C, and deleting PEER, and porting to 52811, I encountered an RTC error when running the final RTT.

The following image shows the modifications I made for porting to 52811

<sdk_config.h>
UART_LEGACY_SUPPORT     0
NRF_BLE_LESC_ENABLED    0
NRF_BLE_LESC_GENERATE_NEW_KEYS  0
NRF_CRYPTO_RNG_STATIC_MEMORY_BUFFERS_ENABLED    0
NRF_CRYPTO_RNG_AUTO_INIT_ENABLED    0
PM_LESC_ENABLED 0

<main.c>
delete --->  err_code = nrf_ble_lesc_request_handler()

Since I don't require the LESC functionality, I hope to have the same connection method as the peripheral UART example.

This is probably all the changes I made. How should I solve the RTC issue?

Thanks

  • I installed the new nRF command line tools, and it also asked me if I wanted to install J-Link 7.94e, to which I agreed.

    The test results are divided into two sections, with the yellow text 'connection lost' in the middle. Above that is when 52811 is running. I connected and then disconnected with my phone, then after a short period of time, an 'app: Fatal error' occurred.

    Below the yellow text is when 52811 is running. I didn't do anything, and after a short period of time, an 'app: Fatal error' also occurred.

  • Did this updating the J-link drivers fix the issue with duplicate log messages? 

    tony55723 said:
    Above that is when 52811 is running. I connected and then disconnected with my phone, then after a short period of time, an 'app: Fatal error' occurred.

    In your debugger, can you read the error information passed to the error handler to find out where the error was raised?

  • sorry,

    I give up on the RTT repetitive printing issue. I only have one J-Link in hand, and I lack experience in firmware upgrades. I fear more problems might arise.

    May I ask a question?

    examples \ ble_central_and_peripheral \ experimental \ ble_app_multirole_lesc

    This is the example I've been using. I tried adding NUS and NUS_C, and deleted HRS and PEER. Finally, I ported it to 52811, all of which were successful. Eventually, I added UART functionality, successfully compiled it, and downloaded the program to 52811. However, after scanning with my phone, I couldn't find this device.

    Do you know how much RAM NUS and UART respectively occupy?

    Thank you

  • tony55723 said:
    Do you know how much RAM NUS and UART respectively occupy?

    I don't have any numbers on this. Generally, fitting a multirole application on the 52811 is challenging due to memory constraints. However, all memory is statically allocated, so you should receive an error at build time if there is insufficient memory. Have you checked the return code from your advertising start function?

  • The error I encountered is 'NRF_ERROR_INVALID_LENGTH'.

    I still feel very sorry, because of two things.

    【1】First, I asked about the error. Now I ask about the UART. I don’t know if this will violate the rules.

    【2】Yesterday I submitted a new question, and a few minutes ago the system prompted an engineer to accept it.

    what should i do now....?(What I mean is, will this cause you trouble?)

    Thank you

Related