Greetings!
This is about the errata published by Nordic, i.e., software workarounds from Nordic for a given hardware revision.
Example: nRF52840 Errata
ID Module Description
[20] RTC: Register values are invalid
This anomaly applies to IC Rev. Revision 2, build codes CKAA-Dx0, QIAA-Dx0.
In ID [20], there is a software workaround recommended by Nordic. To apply this workaround for our nRF52840 devices in the field, we need to know the build codes QIAA-Dx0 either in the Bill of Materials (BOM) or in the Non-Volatile Memory (NVM) register such as INFO.VARIANT in the chip.
The problem:
- BOM only captures the order code: nRF52840-QIAA-R.
- It is not clear which NVM register captures the QIAA-Dx0 in the nRF52840 Product Specification v1.1.
- Based on my understanding, QIAA-Dx0, seems only to be available in a factory environment and the hardware/software engineers have no information about this unless we look at what is printed on the chip. So, how to DFU these Nordic Software Errata/Workaround?
Questions:
- Typically, the software workarounds are available in the SDK. When it is not in the SDK, are these patches available in an easy to integrate way of importing or compiling these patches? For example, are the workarounds available module-wise in a .c file for a given QIAA-Dx0?
- Is there any NVM register that I could look up QIAA-Dx0 to apply the patch?
- Currently, there appears to be no way for a developer to know the hardware revision number (like QIAA-Dx0) being used in the factory. Is there any Nordic recommended way of patching our devices in the field for such hardware revisions? Especially when DFU or Firmware Over the Air is performed.
Kindly let me know your thoughts on this each of the above bullets. Looking forward to your response.
Cheers,
Tilak
