What Zephyr version is required for nrf52840 rev 3 HW

We are currently running v1.4.1 but want to move to the new revision (R3) to gain the RF immunity and security features.

Do we need to move to a new version of Zephyr to gain support for the R3 silicon?

Is there a way to continue with v1.4.1 and use the R3?  If yes, what are the ramifications of doing this?

If we have to move to a new Zephyr version to gain support for R3, has it been qualified (host and controller)?

Parents
  • Hi,

    Do we need to move to a new version of Zephyr to gain support for the R3 silicon?

    Support for nRF52840 revision 3 was introduced in nRF Connect SDK 1.7.0, so you can use that or any later version.

    Is there a way to continue with v1.4.1 and use the R3?  If yes, what are the ramifications of doing this?

    It is technically possible to update just the MDK files to at least version 8.40.2, but then you would have to do the effort of porting that to the old SDK release yourself. See IN-141.

    If we have to move to a new Zephyr version to gain support for R3, has it been qualified (host and controller)?

    In general, yes. Refer to Bluetooth QDIDs to see relevant qualifications for various components and SDK releases.

Reply
  • Hi,

    Do we need to move to a new version of Zephyr to gain support for the R3 silicon?

    Support for nRF52840 revision 3 was introduced in nRF Connect SDK 1.7.0, so you can use that or any later version.

    Is there a way to continue with v1.4.1 and use the R3?  If yes, what are the ramifications of doing this?

    It is technically possible to update just the MDK files to at least version 8.40.2, but then you would have to do the effort of porting that to the old SDK release yourself. See IN-141.

    If we have to move to a new Zephyr version to gain support for R3, has it been qualified (host and controller)?

    In general, yes. Refer to Bluetooth QDIDs to see relevant qualifications for various components and SDK releases.

Children
No Data
Related