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.

Question about bootloader behaviour and burning flash utility

Hello, I would like to go into bootloader in depth to understand it better, and I am already wondering a few things about how burning flash works. If I have understood well, bootloader use ais image to load code from flash to memory, and the address where the program code will be loaded is into the ais image, isn't it? So I would like to know, where exactly flashburning is loading and how could I change if I wanted? I have seen that flashBurn use and .ini file with some code, but no mention to load point. I wonder too, if flashburn is really using an ais file... and how the flash look like after burn it: ais file + code, or it would be "ais begin" + code + "ais end"? I mean, is the code in the middle of the ais file, or the ais file is like a header of code?

Could someone give some tips about this?

Thanks in advance

  • What platform is this for?  Depending on the platform (DM644x, DM6467, DM355...) you may have one or ways to flash bootloader. 

  • Ooops... sorry I forget to mention it. I am using dm6437

  • Hello again, nobody can help about this subject? I will rewrite my main questions:

    -In dm6437 I am using EMIFA fast boot loader, and I burn my program using flashburn utility. Is the bootloader loading the code from flash to ram of dsp? or the code is executed directed from flash?
    -If the code is really loaded from flash to ram, where I can modified the addres where is loaded? My suppositions are that flashburn use AIS file in someway, and inside of this AIS file is the address where the code will be load... is this righ?

     

    Thanks in advance

  • James Thorton said:
    In dm6437 I am using EMIFA fast boot loader, and I burn my program using flashburn utility. Is the bootloader loading the code from flash to ram of dsp? or the code is executed directed from flash?

    It could be either way, though a typical AIS application image will have all the code and data copied out of flash and into RAM/DDR.

    James Thorton said:
    If the code is really loaded from flash to ram, where I can modified the addres where is loaded? My suppositions are that flashburn use AIS file in someway, and inside of this AIS file is the address where the code will be load... is this righ?

    This is actually defined by your linker command file which is typically generated by your DSP/BIOS configuration, so you can edit where your code/data ultimately ends up from within the DSP/BIOS configuration GUI, this assumes that you are using the genAIS to convert your .out file into a AIS image that will be burned into the flash.

    It is true that the AIS image contains the final locations of your code/data, however these locations are determined by the AIS conversion based on the locations used within your .out file which are determined by your linker command file which is determined by your DSP/BIOS configuration file. Theoretically you can change this anywhere along the line, however it is easiest just to work with the BIOS configuration.