DOUBT ABOUT FLASH MEMORY IN NRF52832 QFABB0

[NANDHU]

Hi,

• We are developing a mouse . The controller we are using is NRF52832  QFABB0.
• You known that its contain 32KB RAM and 256KB of flash memory.
• Our application contains OTA-DFU feature.So we need to flash softdevice+bootloader+ application hex to the NRF52832.
• our softdevice hex = 135.5 KB
• our bootloader hex= 40.8 KB
• our application  hex =118.7 KB
• Total = 296 KB.
• The total size of softdevice +bootloader+ application is greater than the size of NRF52832 flash memory.
• I flashed all softdevice +bootloader+application hex to the NRF52832 and it successfully done. and the application is working fine too and also we can able to do the OTA-DFU too.

DOUBT

• SOFTDEVICE +BOOTLOADER+APPLICATION HEX FILE ARE STORING  IN WHICH MEMORY OF THE MICROCONTROLLER . I THINK ITS FLASH ,IS IT RIGHT?
• I ALREADY MENTIONED THAT THE SOFTDEVICE +BOOTLOADER+APPLICATION HEX SIZE IS GREATER THAN NRF52832 FLASH MEMORY +RAM. THEN HOW THE PROGRAMME  FLASHING IS SUCESSFULLY TAKEING PLACE? I AM TOTALLY CONFUSED ABOUT IT. 

[NANDHU]

So you are saying i want to use NRF52832  QFAAB0

[Kenneth]

Yes, though build code B (rev 1) I believe is no longer in production. So I assume it will be QFAAE0 (rev 2), ref:
https://infocenter.nordicsemi.com/topic/comp_matrix_nrf52832/COMP/nrf52832/ic_revision_overview.html?cp=3_1_2_0 

[NANDHU]

Kenneth said:

Have you tried to readback the code for instance by using: nrfjprog --readcode dump.hex

 I tried these look the screen short  below a dump.hex file was generated  but i didn't got any information regarding the memory from it.

 

[Kenneth]

I don't need the dump.hex anymore, I think the below explain what you are experiencing.

Kenneth said:

What may be the case here is that during early production of a new variant it may share silicon with a larger variant for a short period of time, for instance to meet production schedule. However, this will only occur for a short period of time, and the RAM and Flash above the specified size is not tested or guaranteed to work in any way. So if you have created firmware that exceed the size of a variant, then you need to use a larger variant.