Closed nvlsianpu closed 4 years ago
Bug: address range checks don't take into account flash start address, which might be non-zero for new devices. for instance: https://github.com/NordicSemiconductor/nrfx/blob/9136253e271f978a8da735864fc50d60e0ed68c6/drivers/src/nrfx_nvmc.c#L214
affected version: any version since nRF53 support was included master head of time this issue was opened: https://github.com/NordicSemiconductor/nrfx/commit/9136253e271f978a8da735864fc50d60e0ed68c6
consequence: driver will fail on assertion if used on nRF53 network cpu flash controller.
workaround: disable assertions
Looks like was fixed in 2.1.0 release. cc @kl-cruz
Bug: address range checks don't take into account flash start address, which might be non-zero for new devices. for instance: https://github.com/NordicSemiconductor/nrfx/blob/9136253e271f978a8da735864fc50d60e0ed68c6/drivers/src/nrfx_nvmc.c#L214
affected version: any version since nRF53 support was included master head of time this issue was opened: https://github.com/NordicSemiconductor/nrfx/commit/9136253e271f978a8da735864fc50d60e0ed68c6
consequence: driver will fail on assertion if used on nRF53 network cpu flash controller.
workaround: disable assertions