• State
  • Locked Locked
  • Replies 11 replies
  • Subscribers 97 subscribers
  • Views 865 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

How to Program SPI Boot flash..?

Todd Zielinski
Intellectual 455 points
Other Parts Discussed in Thread: OMAP-L137, OMAP-L138

I've read a number of articles, got the idea that you need to use AISgen to make a boot file..

But I don't see where there's a utility - or utility framework - for loading the AISgen created image to the SPI flash device... I have found discussions about using a serial port loader that takes the image, and loads it to the SPI device, but I can't find anything that actually does that.. Unfortunately after spinning my wheels quite a bit, that's all I can seem to get.,,.

To complicate matters (or not), I am trying to load a simple application on to an OMAP-L137 without using DSP BIOS, or Linux, just load a simple control loop app on to the DSP core, boot, and run like hell. I have found CSL (deprecated) CSL support, and I have an app under CCS v4 that I can build run / debug over the JTAG on to an eval board.

So.. where do I find a SPI flash loader app for my soon to be created AISgen image?

Anyone?  :)   .. Thanks in advance..

  • 0
    TI__Mastermind 27585 points

    There are detailed instructions for doing this here on the OMAP-L138: http://processors.wiki.ti.com/index.php/Boot_Images_for_OMAP-L138

    The procedure for OMAP-L137 is almost identical so that should get you started.

    The serial flasher for OMAP-L137 is here: http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L137

    Jeff

  • 0 in reply to jc-ti
    Intellectual 455 points

    Did this, did not produce anything like the directions.

    Downloaded, serial flasher from link previously extracted, set up, checked path, ran make from base directory, said nothing to make, all up to date, yet still can't find a utility that produces a flash loader as described. what am I missing?

    Does it put it somewhere interesting? Where the heck is the utility?

     

  • 0 in reply to Todd Zielinski
    Intellectual 455 points

    I verified that I can access csc, and that the c# tools directory is in the path, along with the code sourcery tools.. verified that they work in cygwin,,

     It still isn't producing the executable sfh_OMAP-L137.exe as described inthe linked directions.. I can't find any utility that is being produced, or an executable of the same name..

    The only interesting thing occuring in the cygwin build attempt is that it seems to want to use CCS timake, which it cannot find - is thios related to only installing CCS4, not 3.3?

    The build attempt follows:

    username/cygdrive/c/Program Files/Texas Instruments/DM647_8_FlashA
    ndBootUtils_1_00/DM647_8
    $ make
    make -C CCS all
    make[1]: Entering directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8
    _FlashAndBootUtils_1_00/DM647_8/CCS'
    make[2]: Entering directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8
    _FlashAndBootUtils_1_00/DM647_8/CCS/NORWriter'
    timake NORWriter.pjt Debug
    make[2]: timake: Command not found
    make[2]: *** [all] Error 127
    make[2]: Leaving directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8_
    FlashAndBootUtils_1_00/DM647_8/CCS/NORWriter'
    make[2]: Entering directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8
    _FlashAndBootUtils_1_00/DM647_8/CCS/UBL'
    timake UBL.pjt Debug -a
    make[2]: timake: Command not found
    make[2]: *** [all] Error 127
    make[2]: Leaving directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8_
    FlashAndBootUtils_1_00/DM647_8/CCS/UBL'
    make[1]: Leaving directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8_
    FlashAndBootUtils_1_00/DM647_8/CCS'
    make -C GNU all
    make[1]: Entering directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8
    _FlashAndBootUtils_1_00/DM647_8/GNU'
    make[2]: Entering directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8
    _FlashAndBootUtils_1_00/DM647_8/GNU/AISUtils'
    make[3]: Entering directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8
    _FlashAndBootUtils_1_00/DM647_8/GNU/AISUtils/AISextra'
    make -C src
    make[4]: Entering directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8
    _FlashAndBootUtils_1_00/DM647_8/GNU/AISUtils/AISextra/src'
    make[4]: Nothing to be done for `all'.
    make[4]: Leaving directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8_
    FlashAndBootUtils_1_00/DM647_8/GNU/AISUtils/AISextra/src'
    make[3]: Leaving directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8_
    FlashAndBootUtils_1_00/DM647_8/GNU/AISUtils/AISextra'
    make[3]: Entering directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8
    _FlashAndBootUtils_1_00/DM647_8/GNU/AISUtils/HexAIS'
    make[3]: Nothing to be done for `all'.
    make[3]: Leaving directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8_
    FlashAndBootUtils_1_00/DM647_8/GNU/AISUtils/HexAIS'
    make[2]: Leaving directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8_
    FlashAndBootUtils_1_00/DM647_8/GNU/AISUtils'
    make[1]: Leaving directory `/cygdrive/c/Program Files/Texas Instruments/DM647_8_
    FlashAndBootUtils_1_00/DM647_8/GNU'

     I can't find a reference to timake.

  • 0 in reply to Todd Zielinski
    TI__Mastermind 27585 points

    I think you have the wrong package. You should have downloaded OMAP-L137_FlashAndBootUtils_2_15.tar.gz from the wiki site, and you'll find the exe in the OMAP-L137/GNu directory.

    Running 'make' from the base OMAP-L137 directory will rebuild the CCS based tools, which requires CCS installed and the correct paths set up. If you just want to rebuild the serial flasher, run 'make clean' then 'make' from the GNU directory.

    Jeff

  • 0 in reply to jc-ti
    Intellectual 455 points

    Go figure, I downloaded the file that is linked to in the wiki for the OMAP L137, and that  is not the file that you say I should be looking for.. Odd how I might be confused, or get the wrong file, eh..?

    The download link is connected to the DaVinci series, which it lists as a collection to support the OMAP and DaVinci processors. There is a link to another download area there that goes to the OMAP-L137 specific variant, but that isn't clear anywhere in the wiki, the instructions, or the docs. I have been doing the process described from before you gave me the links the first time - I already had found and installed everything you linked to, and as I have indicated several times, I have CCS installed, but it is CCS 4, not 3.3.. I have all the paths correctly set up, and as indicated in the wiki..they work, and are tested.

    I am trying to point out that the docs are unclear, and the link to the file is unclear / incorrect. I have had allt he tools installed and working properly. If you need CCS 3.3 to do a build, please indicate so. If you need to download a linked file that is not the download link's target, please specifiy that as well. It would help.

    Got the utility now, will give it a spin. Thanks.

  • 0 in reply to Todd Zielinski
    Intellectual 455 points

    Well, Got flash loader working.. which is good.. but still can't get the release build running from loading off of SPI..

    Used AISgen to create an image using the EVM defaults, using a simple pin toggling app that loads and runs properly using JTAG in the IDE..

    Erased the flash and loaded the flash successfully using sfh_OMAP-L137.exe..

    Still not booting on the EVM.. any thoughts as to the last piece I'm missing?

    Is there a potential issue since I'm not using ARM to boot and run? The flash loader only seem to have ARM / uboot options..

     

     

     

     

  • 0 in reply to Todd Zielinski
    TI__Mastermind 27585 points

    The link in the wiki was pointing to https://sourceforge.net/projects/dvflashutils/files/OMAP-L137/ which has separate folders for each version of the OMAP-L137 tool. It looks like theres a new link SourceForge puts at the top that says: "Looking for the latest version? Download DM647_8_FlashAndBootUtils_1_00.tar.gz (666.6 KB) " so I can see how that would be confusing. I changed the link on the wiki to point directly to the download site of the latest release to prevent future confusion.

    The section for compiling the tools has been updated as well with your suggestions in mind. Thanks

    Jeff


  • 0 in reply to Todd Zielinski
    TI__Mastermind 27585 points

    Can you paste the command line arguments you used for the SFH tool?

    Also can you zip up the bin file you are using as well as the AIS configuration file and attach them to your reply so I can try it myself? Thanks

    In the meantime you can use this GEL file to see if there are any ROM error messages: http://processors.wiki.ti.com/index.php/OMAP-L1x_Debug_Gel_Files

    Jeff

  • 0 in reply to jc-ti
    Intellectual 455 points

    OK - Found it was a release target build issue, not the load procedure. Got it loaded, so it works.

    One remaining question: are there any other supported methods for loading applications into SPI flash?

    UART is a bit unwieldy, is there a JTAG or other executable option to load an into SPI for Boot? Having to switch boot modes to load the app seems a bit problematic, and uses a UART in the process.

    Thanks again..

  • 0 in reply to Todd Zielinski
    TI__Mastermind 27585 points

    Yes there are CCS 3.3 projects in the serial flashing tools you downloaded (in the CCS directory) which will load the SPI flash.

    Also the PSP package comes with a CCS based flashing tool as well, which does the same thing.

    Jeff

  • 0 in reply to jc-ti
    Intellectual 455 points

    Are there CCS 4.x flash tools coming? Is there a migration for those tools?

    Or should I be going backwards, and get a copy of 3.3? It doesn't seem like you are supporting / migrating tools for 4.x.?

    What PSP package are you talking about?