• State Verified Answer
  • Replies 2 replies
  • Subscribers 87 subscribers
  • Views 97 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 360192
Options

Queries Regarding Usage nRFX For Development

Aditya M

Greetings,

I'm considering nRF52840 for a product. My connectivity requirements are BLE 5+ (For GATT-based communication, No requirement for channel sounding, etc), USB Device capabilities & QFN package format (Not aQFN).

nRF52840 fits my requirements but I don't want overhead of RTOS, etc & Unfortunately baremetal SDK is only supported for 54L series & I don't think Nordic would be willing to send out samples of 54LM20A SoC for testing with custom PCB to someone who doesn't even have a company established yet & I cannot wait for the said SoC to hit the market.

Thus I am thinking of using nRFX for development on nRF52840, For which I had a few questions.

  1. Can Nordic provide technical support for projects using nRFX?
  2. Is there chances for nRFX to be depreciated in future?
  3. Can you highlight any potential issues when using nRFX over nRF Connect SDK?
  4. Are there samples/examples for nRFX as there are for nRF Connect SDK?
  5. Are there any plans to add baremetal SDK support to nRF52 series?

Regards,
Aditya M.

Parents
  • +1

    Hi Aditya,

    Can Nordic provide technical support for projects using nRFX?

    Yes, using nrfx as part of a SDK is no problem and supported. But anything you do outside or without an SDK or that we have not provided, it is difficult to provide support on.

    Is there chances for nRFX to be depreciated in future?

    I cannot comment on long term road map questions, but I do not see the concept of low-level drivers (which is primarily what nrfx is) going away any time soon.

    Can you highlight any potential issues when using nRFX over nRF Connect SDK?

    These are different things. nRF Connect SDK is a complete SDK, which involved many different modules, one of which is nrfx. Nrfx is a set of low-level peripheral drivers and hardware abstraction for nordic devices. If the real question is if I see a problem with you using only nrfx and other software you choose, and not an SDK, then yes and no. It will not be supported by us and it will be up to you, and by not using an SDK you will have to do a lot of work that will already be done for you by choosing an SDK.

    Are there samples/examples for nRFX as there are for nRF Connect SDK?

    There are low-level samples for nrfx, which are part of nRF Connect SDK here. These demonstrate usage of nrfx driver APIs (this is as part of nRF Connect SDK / Zephyr projects, but for the most part these samples are generic and will be valid also outside of NCS).

    Are there any plans to add baremetal SDK support to nRF52 series?

    No, for that you have the old nRF5 SDK, though I do not recommend starting with that now as it is old and there are no updates expected.

    Some additional considerations:

    1. I recommend contacting sales regarding availability and timeline for nRF54LM20.
    2. I would consider if using an RTOS is a major problem. Zephyr is quite flexible, and you can implement much of your application in a single thread if you like (though some subsystems will use separate threads).
    3. The only supported USB stack for nRF54L series is the Zephyr USB stack

    Br,

    Einar

Reply
  • +1

    Hi Aditya,

    Can Nordic provide technical support for projects using nRFX?

    Yes, using nrfx as part of a SDK is no problem and supported. But anything you do outside or without an SDK or that we have not provided, it is difficult to provide support on.

    Is there chances for nRFX to be depreciated in future?

    I cannot comment on long term road map questions, but I do not see the concept of low-level drivers (which is primarily what nrfx is) going away any time soon.

    Can you highlight any potential issues when using nRFX over nRF Connect SDK?

    These are different things. nRF Connect SDK is a complete SDK, which involved many different modules, one of which is nrfx. Nrfx is a set of low-level peripheral drivers and hardware abstraction for nordic devices. If the real question is if I see a problem with you using only nrfx and other software you choose, and not an SDK, then yes and no. It will not be supported by us and it will be up to you, and by not using an SDK you will have to do a lot of work that will already be done for you by choosing an SDK.

    Are there samples/examples for nRFX as there are for nRF Connect SDK?

    There are low-level samples for nrfx, which are part of nRF Connect SDK here. These demonstrate usage of nrfx driver APIs (this is as part of nRF Connect SDK / Zephyr projects, but for the most part these samples are generic and will be valid also outside of NCS).

    Are there any plans to add baremetal SDK support to nRF52 series?

    No, for that you have the old nRF5 SDK, though I do not recommend starting with that now as it is old and there are no updates expected.

    Some additional considerations:

    1. I recommend contacting sales regarding availability and timeline for nRF54LM20.
    2. I would consider if using an RTOS is a major problem. Zephyr is quite flexible, and you can implement much of your application in a single thread if you like (though some subsystems will use separate threads).
    3. The only supported USB stack for nRF54L series is the Zephyr USB stack

    Br,

    Einar

Children
Related
Terms of service