This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR1642: Maximum meta image size limitation

Part Number: AWR1642
Other Parts Discussed in Thread: UNIFLASH,

Hi,

Any limitation to the maximum meta image size that will be burned into the SFlash? Customer feedbacked when the image size is greater than 1MB, then it would be failed to burn on flash using the uniflash tool.

Andy

  • Hi,

    We are limited by the size of the Memory that can be loaded on the device.

    What type of application is the customer looking at?

    thank you
    cesar
  • Cesar,

    It is for automotive application. Based on my customer feedback, the image size is limited to less than 1MB, it can be burned into flash and boot up well if image size is less than 1MB, else it cannot be burned into flash and report error image size. Pls help confirm why it has such limitation and how to fix it, thanks.
    Andy
  • Anyone can help on it, thanks.
  • Hello Andy,
    As you know MetaImage file contains MSS, BSS and DSS FW/application in it. Further MSS and DSS images size depends on AWR1642 device memory. [DSS: L3, L2] [MSS: TCMA,TCMB].

    If MetImage contains MSS/DSS application which uses more memory than defined for device then flashing or bootup will throw an error.
    Please refer TRM for deailed memory info of individual core.


    Regards,
    Jitendra
  • Jitendra,

    I understand your points that should ensure the code and data size less than the device memory. My question is if there is any limitation on the final generated META IMAGE size, as based on my customer's test the code can be downloaded and run well through ccs, generate META IMAGE with tools in sdk, burn on flash, then if the size is greater than 1MB it would report image size error.
    So would u pls help check if there is any limitation from the uniflash or ROM for the META IMAGE size? Thanks.
    BR,
    Andy

  • Hello Andy,
    Can you check if the application is trying to load to TCMB or HSRAM memory area?
    While over CCS it will able to load the image to above-mentioned memory area but in flashed mode bootloader won't allow to load the content to these memories, hence it may not boot up properly.
    The easiest way to check this to look into MSS map file if TCMB (0x08000000) or HS_RAM (0x52080000) memory address is loaded with some const/code.

    Further, I would suggest going over the AWR1642 bootloader app-note (section-2) which explains the valid memory load options in the device.



    Regards,
    Jitendra