• State Verified Answer
  • Replies 9 replies
  • Subscribers 68 subscribers
  • Views 1489 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 234931
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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. 
Parents
  • +1

    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.
Reply
  • +1

    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.
Children
No Data
Related