• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 25 subscribers
  • Views 107 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 290537
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[254] errata

user108266

Hello !

In latest errata,https://infocenter.nordicsemi.com/pdf/nRF52840_Rev_3_Errata_v1.1.pdf is not so clear all details of this anomaly

[254] RADIO: External PAs, FEMs, and LNAs need additional Radio configuration.

1. Can I apply this errata for any revision of nRF52840 with and without FEM ? Or I should track revision of chip and know if it used with or without FEN nRF21540 ?

   Or it safe to use it for any nRF52840 ?

2. Should I apply this code for all radio modes, BLE and IEEE as first step ?

Apply the following code before enabling the RADIO in any radio mode: if (*(volatile uint32_t *) 0x10000330ul != 0xFFFFFFFFul) { *(volatile uint32_t *) 0x4000174Cul = *(volatile uint32_t *) 0x10000330ul; }

or this is for NON IEEE modes only ?

3. And this code "If entering another RADIO mode after mode 802.15.4, apply the following code before enabling the RADIO:" is really no need if RADIO is powered off / on before switching to other radio ?

Please clarify usage of this errata.

Regards,

Eugene

  • 0

    Hi,

    You can find in the errata 254 also says at the end: "This workaround is included in nRF Connect SDK 1.7 and later." So the easiest is to update to 1.7 or later to apply the workaround for errata 254:
    https://infocenter.nordicsemi.com/topic/errata_nRF52840_Rev3/ERR/nRF52840/Rev3/latest/config_840_254.html 

    But to answer your questions:

    1. This must only be done with designs using FEM. The code snippets itself do check if there is a value at certain memory address, and only apply the workaround in those specific cases, so they should be safe to run on all revisions of the nRF52840, since the codes snippets will have no effect on devices with date code prior to 2139.

    2. The first code snippet for all radio modes, the last two code snippets only apply to 802.15.4. Honestly speaking I think applying these workaround to earlier nRF Connect SDK or even nRF5 SDK will be difficult, since typically the radio stacks are precompiled libraries (e.g. softdevice controller) that does not allow direct radio manipulation, but if you are writing your own radio stack, then these lines of codes is something you must implement as described.

    3. 

    is really no need if RADIO is powered off / on before switching to other radio ?

    True.

    Best reards,
    Kenneth

  • 0 in reply to user2111

    Hi Kenneth !

    I have own radio and really should/can program all radio registers with desired values and write own driver for this.

    I have some boards with FEM and some without. Looks like it is not so easy to detect GPIO controlled nRF21540.

    But for have common FW for both designs, I should have runtime detection if FEM present or not.

    How harmful can be case when errata is applied for board where FEM is not present ?

    Regards,

    Eugene

  • +1 in reply to user108266

    From my understanding it may for instance affect sensitivity and blocking. I don't have much more details, since it's not been tested or intended to be used without an FEM.

    Best regards,
    Kenneth

Related
Terms of service