How to use more than 16MB flash on AMB82 Mini

FreeRTOS SDK
1

Hi,

Currently 16MB flash available on AMB82 Mini board. But, for my application more than 16MB is required. Can anyone provide me the details to upgrade it to 32MB(I have Winbond one)?

I think one change is flash partitions json file for new sizes.

Is there any other changes required apart from this like flashing tool settings, etc.

Thanks,

Yuagndhar

2

Modifying the current flash partitions is not recommended, as the starting addresses for each partition are already fixed for the 16 MB flash layout. Changing them may lead to boot-up or compilation issues.

If 32 MB flash is required, we suggest you can append your own parameters after the existing flash partition table and use that area for data storage.

3

Hi @Pammy ,

Why changing amebapro2_partitiontable.json file is not allowed?

My binary file increased few more KBs than fw1/fw2 partition size. I got partition overlap error while building the flash image.

I found that the isp iq files are less than iq partition size, so I increased fw1/fw2 partitions and reduced iq partition, now no obverlap error and able to flash the app and working wothout any issues.

As you said changing amebapro2_partitiontable.json is not allowed and partition addresses are fixed, how it worked for me?

4

Hi @yugandhar

What I meant was that modifying the partition structure is not recommended, as it might affect the application logic; however, it is allowed if you only intend to increase the length of each block. In that case, you may modify starting from fw1 onwards.

FlashLayout
FlashLayout726×892 81.6 KB

5

Hi @Pammy ,

So, if I give any address which exceeds 16MB for firmware, ISP_IQ or NN_Model_Data partitions, will flashing tool writes to it or not?

6

Hi @yugandhar,

Theoretically, flashing and writing should work if you are using a 32 MB flash.
flash_ntz.bin file is generated according to the partition layout defined in amebapro2_partitiontable.json. However, we have not tested this setup with a 32 MB flash on our side.

Do note that start addresses and sizes of all partitions need to be configured correctly.

Understand that your application may exceed 16 MB in size, which means you will need to increase the allocation for fw1. Depending on your partition configuration, OTA updates may no longer be usable, as OTA typically relies on fw2. For example, if your application requires 16 MB and only 8 MB remains available for fw2 after all allocations, that space would be insufficient to support OTA firmware updates for your application.