"integration/nrfx/legacy" directory in SDK 15.0

[Rob Philip]

I am porting software built with SDK 14.2 to SDK 15.0

It looks like some files have been moved from "components/drivers_nrf" to "integration/nrfx/legacy". The first one I've encountered is nrf_drv_clock.c but I see that there are others. 

Have these files/apis/whatever been deprecated? Are there "new" ways to do the things provided in these legacy files? I notice that (for example) many of the examples still use these "legacy" functions...

Any insights would be helpful. 

[Jørgen Holmefjord]

Hi,

This is described in the release notes for SDK 15.0.0:

** Drivers and libraries **
 - The way peripheral drivers are handled in the SDK has been reorganized:
     - Replaced existing drivers with the "external" drivers from nrfx project. See github.com/.../README.md for more information on nrfx.
     - New drivers from nrfx are located in "..\modules\nrfx".
     - Drivers replaced by nrfx are removed from "..\components\driver_nrf".
     - A glue layer is added to make the nrfx driver compatible with SDK and the SoftDevice.

Best regards,
Jørgen

[Jørgen Holmefjord]

Yes, you can read more about this in the SDK 15.0.0 migration guide as well.

There will be more examples migrated to using the new drivers in future SDK releases. In most cases, it should be sufficient to change the names of function calls and configurations as described in the migration guide.

If you are facing any issues, please post your question in a devzone question and we will help you resolve it!

[Jørgen Holmefjord]

There is no UART1 peripheral available, only UARTE1. Please make sure you set UART_LEGACY_SUPPORT 0 in sdk_config.h.

[Rob Philip]

Right - but it's a Nordic macro that is generating the error (i copied it to remove the "static")

Do you mean I should set UART_LEGACY_SUPPORT to zero or one? 

[Rob Philip]

I wonder if somebody there can build me an example for using UARTE1 on with SDK 15.0? The "legacy" shim layer doesn't compile/work for UARTE1, and there is no apparent documentation that I can find. I can figure it out, but an example would speed things up immensely.

[Nguyen Hoan Hoang]

It would probably better to use drivers from this library.  It is independent of the SDK and more importantly, it doesn't require 3000 defines to enable it.

example use case can be found on this blog. other UART example codes

[Jørgen Holmefjord]

Yes, it is caused by nordic macro. The issue is that nRF52840 support legacy UART for UART instance 0 (support both UART and UARTE), but not for instance 1 (UARTE only). When you enable lagacy UART support in the legacy UART driver and enable UART1 in the config, it will try to define both UART1 and UARTE1 instance. 

These configs work fine for me when using UARTE1 with the legacy driver layer:

The new nrfx driver solve these issues, as there are separate drivers for UART and UARTE.

[Rob Philip]

I have no idea where you got that lovely configuration screen.

Can you tell me what #defines it generates into sdk_config.h? 

[gnf]

I am using a separate tool for working with the sdk_config.h. It is called "CMSIS Configuration wizard" and can be downloaded from here http://helmpcb.com/software/cmsis-configuration-wizard:

[Rob Philip]

Thanks.