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.

TMS320C6748: Flash programming using sfh_OMAP-L138.exe

Part Number: TMS320C6748
Other Parts Discussed in Thread: OMAP-L138

Hi,

I am wondering is there a way to use sfh_OMAP-L138.exe to program three firmware images at a time. What I want to do is to program a secondary bootloader and two different application images. The secondary bootloader will decide which firmware image to load base on some logic. Do you have a tool that allows me to do that? When I look at the sfh_OMAP-L138.exe document, it does not seem like there is an option for that.

Thanks,

Charles

  • The team is notified. They will post their feedback directly here.

    BR
    Tsvetolin Shulev
  • Charles,

    From the description of the utility on the TI Wiki, it looks like both the "'flash_noubl' and 'flash' options will automatically erase the necessary amount of memory in order to fit the UBL and/or application image." I assume it is implied that this means it will erase *only* the amount needed. You can test it to see if it works, and then please report back to us.

    If that works, you can build three separate images that are all linked to different physical address areas and then execute the utility three times. Each time, it should write one of your three images and not disturb the others. That would be the way to test it.

    If you need help creating an image at a specific address, that would need to be a different thread to get the tools team to help with suggestions.

    Or you could build your three images into one large application image, being careful to use different entry-point labels for each. Then you would only have one combo-image to burn into flash using the utility.

    Regards,
    RandyP
  • Thanks for the info. If the utility only erases the affected areas, then I may be able to make it works with the -appFlashBlock option. I will give it a try.

    Another question while I was looking at adding firmware update ability to the project. I was playing with the nandReadWrite example in the starterware. What I found is that after a page write, that particular page will fail the bad block check after. Do you have any idea why this is happening? I am using LCDK6748 and C6748_startware_01_20_04_01.
  • I do not know, no. Since it is a completely different question, you may get the best results by posting your new question as a new thread.

    Please let us know how the test with sfh_OMAP-L138 goes.

    Regards,
    RandyP