• State Verified Answer
  • Replies 6 replies
  • Subscribers 63 subscribers
  • Views 6085 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 110669
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

UART SDK migration 8.1.0 -> 10.0.0

Eliot Stock

I have two UART devices on a custom board with an nRF51822. I've just upgraded the SDK I use from 8.1.0 to 10.0.0 and one of the UART connections has stopped working, but not the other.

Both use the same connection params: no hardware flow control, same baud rate, no parity, same buffer sizes, same IRQ priority. I've checked that power is getting to the module that's not responding. For the module that's not working, the UART event handler function is never called. Calls to app_uart_put() and app_uart_get() don't return any errors.

What changed between SDK 8.1.0 and SDK 10.0.0 that could possibly have caused this? I can see nothing in the release notes.

Parents
  • 0

    Ah, ok, so you have one board, with one nRF51 and two peer devices mounted on it? And you lost com to only one of them?

    Then I guess you have routed the UART traces from the peer devices to two separate set of pins on the nRF51, and then you are dynamically reconfiguring the UART to talk to one or the other? Are you using flow control? Do you mind uploading the code? You can submit a support ticket on myPage if your prefer some confidentiality.

Reply
  • 0

    Ah, ok, so you have one board, with one nRF51 and two peer devices mounted on it? And you lost com to only one of them?

    Then I guess you have routed the UART traces from the peer devices to two separate set of pins on the nRF51, and then you are dynamically reconfiguring the UART to talk to one or the other? Are you using flow control? Do you mind uploading the code? You can submit a support ticket on myPage if your prefer some confidentiality.

Children
No Data
Related