• State Verified Answer
  • Replies 23 replies
  • Subscribers 69 subscribers
  • Views 8119 views
  • Users 0 members are here
Attachments (3) Download All
Nordic Case Info
  • Case ID: 230507
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Using LIBUARTE during flash operations

oguzcan oguz

Hi, 

We are using a NRF52840 chip (SDK 15.3) in an application where we use the softdevice (S140) in combination with 2 UARTS: one for sending out debug output (UART0 - nrfx_uart), and another one for communication with another MCU.

During (internal) flash writes when doing bonding or garbage collection, the CPU stalls for quite a long time (~85 ms during flash erase). In order to make sure we do not lose data from the other CPU we have been looking into the 'nrf_libuarte_async' functionality.

It is constructed by using:

NRF_LIBUARTE_ASYNC_DEFINE(libuarte, 1, 1, NRF_LIBUARTE_PERIPHERAL_NOT_USED, 2, 512, 3);

(UARTE1, TIMER1 for byte counting, TIMER2 for timeout, buffer size of 512).

During normal operation it works fine, but after the CPU stall, we ofter end it in an error in 'nrf_libuarte_async_rx_free', stating "Unexpected RX free input parameter.". In this case the 'rx_free_cnt' is bigger than the 'chunck_size'. We are following the example of examples\peripheral\experimental_libuarte and free the buffer in the NRF_LIBUARTE_ASYNC_EVT_RX_DATA event.

Could you give any indication what can be the issue here? We couldn't find much documentation wrt to this driver. 

Thank you.

Parents
  • 0

    Hi

    What baudrate is the UART1 running at?

    How large is the UART utilization from the connected MCU? Do you think there is a risk that the UART RX buffer could fill up during those ~85 milliseconds?

    Are you using hardware flow control or not?

    Best regards
    Torbjørn

  • 0 in reply to ovrebekk

    Response on behalf of my collegue: The baudrate is 115200. There is no risk that the UART Rx buffer could fill up. The connected MCU can only send one single message (which is less <400 bytes),then it waits for a response. Unfortunately there is no possibility that to use hardware flow control

  • 0 in reply to RoyCreemers

    Hi Roy

    When you say 0x16e5a or close, do you mean this changes from time to time, or you're not sure the exact address?

    The exact address can be important when reporting this to the stack developers. 

    To summarize, you confirm that this can happen with or without flash erase running?

    You confirm that this will only happen when using the libuarte_async library?

    How do you process UART events in the application? 
    Are you running a lot of event processing in the events directly, or do you process it later in main/thread context?

    Do you know what interrupt priority the UART events are returned in?

    Best regards
    Torbjørn

  • 0 in reply to ovrebekk

    Hi Torbjørn,

    I was preparing all your questions with answers, till I reached the final question about the interrupt priority. When searching through our code, I realized that we did not specificy the 'int_prio' field (it was added in the patch we received). It was undefined and pointed out to '112' (or some other high value). Once I changed it to  irq priority 5, the issue is gone!! Thanks!

    Unfortunately I still see that data gets corrupted some times. I will dive into this first to see if I can get a reproducable scenario. For now, it reproduces more often in case I reduce the timeout.

  • 0 in reply to RoyCreemers

    Hi Roy

    That is good to hear Slight smile

    One of the SoftDevice developers confirmed that the assert was related to a delayed interrupt in the SoftDevice, which happens if you configure interrupts to run at the highest priorities (should be reserved for the SoftDevice only). 

    As soon as you have more information on the corruption issue just let me know. 

    I assume you are talking about UART corruption?

    Does it happen both on RX and TX?

    Does it happen with or without flash access enabled?

    And any more details you think might be relevant. 

    Best regards
    Torbjørn

  • 0 in reply to ovrebekk

    Let me start with answering some of your previous questions:

    Q:To summarize, you confirm that this can happen with or without flash erase running?
    A:This happens without flash erase.

    Q:You confirm that this will only happen when using the libuarte_async library?
    A: Yes. When using the nrfx_uarte driver directly, we did not have this issue.

    Q:How do you process UART events in the application? Are you running a lot of event processing in the events directly, or do you process it later in main/thread context?
    A: Data is put in a buffer, and processed in the main thread. No processing is handled in IRQ context. Same for BLE events: everything is queued for processing outside of interrupt context.

    Q: Do you know what interrupt priority the UART events are returned in
    A: The "irq_prio" is filled in with 5

    The corruption only happens on the receive action. I looks like the problem occurs in case I receive new data during the timeout. What I see only the logic analyzer is that we often have a UART sequence looking llike the following

    <~200 bytes on UART Rx>  <no communication for ~5 ms>  <~200 bytes on UART Rx> <no communication for ~X ms)

    Initialily, I had the timeout set to 5 ms. I noticed the error very often. It looked like the data from the first and second burst where mixed.

    Once I set the timeout to 15 ms, I see it very rarely: actually only when my "no communication" window is equal to X.

    Now I reduced it to 2 ms, it works without issues (in the 15 minutes I tried this), probably because this "no communication" window is very unlikely to happen.

  • 0 in reply to RoyCreemers

    Hi Roy

    RoyCreemers said:
    A: The "irq_prio" is filled in with 5

    That's a bit odd. Legal values when using the SoftDevice are 2, 3, 6 and 7. 

    Defines for setting IRQ priority can be found in app_util_platform.h in the SDK:

    #define _PRIO_SD_HIGH 0
    #define _PRIO_SD_MID 1
    #define _PRIO_APP_HIGH 2
    #define _PRIO_APP_MID 3
    #define _PRIO_SD_LOW 4
    #define _PRIO_SD_LOWEST 5
    #define _PRIO_APP_LOW 6
    #define _PRIO_APP_LOWEST 7
    #define _PRIO_THREAD 15

    If the problem seems to be solved when the timeout is shorter than the time between bursts I expect the issue to be triggered when the DMA buffer fills up in the middle of a burst, but the hardware should handle this if you set up two buffers and configure the DMA to switch to the second buffer automatically once the first fills up. 

    I can double check with the designers if the driver is set up to do this. 

    Have you done more testing at 2ms to see if this setting seems reliable?

    Best regards
    Torbjørn

Reply
  • 0 in reply to RoyCreemers

    Hi Roy

    RoyCreemers said:
    A: The "irq_prio" is filled in with 5

    That's a bit odd. Legal values when using the SoftDevice are 2, 3, 6 and 7. 

    Defines for setting IRQ priority can be found in app_util_platform.h in the SDK:

    #define _PRIO_SD_HIGH 0
    #define _PRIO_SD_MID 1
    #define _PRIO_APP_HIGH 2
    #define _PRIO_APP_MID 3
    #define _PRIO_SD_LOW 4
    #define _PRIO_SD_LOWEST 5
    #define _PRIO_APP_LOW 6
    #define _PRIO_APP_LOWEST 7
    #define _PRIO_THREAD 15

    If the problem seems to be solved when the timeout is shorter than the time between bursts I expect the issue to be triggered when the DMA buffer fills up in the middle of a burst, but the hardware should handle this if you set up two buffers and configure the DMA to switch to the second buffer automatically once the first fills up. 

    I can double check with the designers if the driver is set up to do this. 

    Have you done more testing at 2ms to see if this setting seems reliable?

    Best regards
    Torbjørn

Children
Related