• State Verified Answer
  • Replies 3 replies
  • Subscribers 90 subscribers
  • Views 1494 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 257680
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Where did nrf_serial go in SDK v17?

Glen M

Hi Everyone!

nrf_serial.c and nrf_serial.h are gone in SDK 17.0.2. There are present in 16.0.0. I do not see any mention of this in the release notes.

Was this module intentionally removed? Has it been replaced by something or deemed unnecessary?

I'm porting some code built with an older version of the SDK and I don't know if I should just grab the nrf_serial from version 16 or if I need to rewrite it to use a different interface.

Thanks,

Glen

Parents
  • +1

    Hi Glen,

    The nrf_serial library has been replaced by the libuarte driver in SDK 17, as the latter is a better solution. One problem with nrf_serial is that it doesn't handle UART errors well. If you get a UART error, you will need to uninit and init the driver again. This is, however, not a problem with the libuarte driver. You can still use nrf_serial from SDK 16, but you should be aware of this problem.

    Best regards,

    Marte

Reply
  • +1

    Hi Glen,

    The nrf_serial library has been replaced by the libuarte driver in SDK 17, as the latter is a better solution. One problem with nrf_serial is that it doesn't handle UART errors well. If you get a UART error, you will need to uninit and init the driver again. This is, however, not a problem with the libuarte driver. You can still use nrf_serial from SDK 16, but you should be aware of this problem.

    Best regards,

    Marte

Children
Related