To whom it may concern:
We have a product in production based on the nrf52810 and SD 112 ver 6.1.1, developed with SDK 15.3. Due to our manufacturer having nRF52810 availability issues (shortages), we have recently modified our firmware to accommodate the usage of the nrf52832 in our product [Bluetooth SIG QDID D056539, either nrf52810 or nrf52832 based].
The problem we are running into is the nrf52832 based product is having odd behavior not seen with the nrf52810 such as random BLE disconnects, or unpredictable behavior consistent with RAM corruption.
My concern and questions are:
1) Does the SD 112, ver 6.1.1 handle the more recent nrf52832 errata? If not, are there patches to the 6.1.1 available without updating to a later version, i.e. 8.0?
[Given we have a QDID updating to SD 8.0 is an expensive and lengthy process including the migration from SD 6.1.1. to SD 8.0 requiring another Bluetooth SIG qualification]
2) Do I need to manually implement the more recently developed fixes for the nrf52832 errata since our development is based on SDK 15.3 version? For example, modifying system_nrf52.c to add the additional errata workarounds which might be present in later SDKs or soft devices.
3) Will addressing issues in the system_nrf52.c be sufficient?
Any guidance in this area will be greatly appreciated and is urgently needed!
Thank you.
