Firmware works on chip rev QFABB0, but not on QFABE0 chip rev

[CurtisHx1]

The firmware is based on the BLE UART example running on an nRF52832 with the S132 softdevice.  The first batch of boards were build with the QFABB0 chip revision of the nRF52832.  These boards were programmed and ran fine.  Some were put out in the field for testing and never had any problems.

The second batch of boards were built with the QFABE0 chip revision, and now the firmware doesn't work. Here's the call stack to where things go wrong:

main

peer_manager_init

pm_init

pds_init

fds_init

pages_init

pds_init returns an error code (bubbled up from pages_init, and the code in pm_init changes the error to NRF_ERROR_INTERAL. 

However, the root failure is pages_init fails to find any pages for the FDS, and throws up with  "NO_PAGES" fds_init_opts_t.

The firmware runs fine on the QFABB0 chip revision, but fails on the QFABE0 chip revision.  Here's the link to the chip revisions.  We even tried pulling firmware off of the working (QFABB0) chips and loading it onto the QFABE0 chips, and the firmware crashes.

I suspect this has something to do with Errata 163 which is present on QFABB0, but was fixed on QFABE0.

Help?

[SteveHx]

I have since discovered that, after downloading the latest SDK last week, two other projects no longer work on known good hardware. Reloading the saved binary images from the prior SDK they run fine.

[Jørgen Holmefjord]

Did you modify the project settings in SDK 16 to match the available RAM and Flash in the chip variant you are using (32 kB and 256 kB)?