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.

[OMAP35x] first time startup, DownloadUtility, and purpose of files in peripheral-boot-images dir



A few questions relating to first time bring up of an OMAP35xx based board.

1.  Apparently the source code for DownloadUtility.exe is not available so it's difficult to figure this out on my own.  The utility automatically sends "OMAP35x_SDK_1.0.0/board_utilities/windows_host/peripheral-boot-images/dnld_startup_omap3_evm.bin" to the target prior to sending the selected u-boot.bin file.  Is there anyway to select an alternate file to download first, similar to what was supported in the SDK-0.9.5 version of the DownloadUtility.exe?

2.  What is "OMAP35x_SDK_1.0.0/board_utilities/windows_host/peripheral-boot-images/peripheral_u-boot.bin" used for?

3.  What are the available LogLevels for DownloadUtility.ini?

4.  Are there plans to release a DownloadUtility.exe and dnld_startup_omap3_evm.bin that support peripheral booting via USB?  It certainly would make sense instead of individual developers having to write these utilities.  Might they be available in the open source community somewhere?

Thanks.

 

 

  • burchmere said:
    Is there anyway to select an alternate file to download first, similar to what was supported in the SDK-0.9.5 version of the DownloadUtility.exe?

    I don't believe that option is available in the current DownloadUtility.exe, though you could just replace that file with the alternative file of your choice, however I doubt it is widely tested for varying initial binaries to download.

    burchmere said:
    What is "OMAP35x_SDK_1.0.0/board_utilities/windows_host/peripheral-boot-images/peripheral_u-boot.bin" used for?

    That is a U-Boot binary, you could use that with the serial loader to get U-Boot running on the board.

    burchmere said:
    What are the available LogLevels for DownloadUtility.ini?

    This is not documented, note that since this is a Mistral utility, I do not have the source, so I could not say for sure. Aside from asking Mistral you could try a few values and see what it lets you do and what ends up in the log, I assume this is just a debugging mechanism for the utility.

    burchmere said:
    Are there plans to release a DownloadUtility.exe and dnld_startup_omap3_evm.bin that support peripheral booting via USB?

    I do not know of any plans for the release of a USB based peripheral booting utility from TI.

    burchmere said:
    Might they be available in the open source community somewhere?

    There is a utility for Beagle Board that looks to do a USB based boot (see pusb at http://elinux.org/BeagleBoard#OMAP_U-Boot_Utils), though I have never used it myself and I could not say if it would function with boards other than Beagle, I have typically used a bootable SD card for my Beagle.

     

  • burchmere said:
    What is "OMAP35x_SDK_1.0.0/board_utilities/windows_host/peripheral-boot-images/peripheral_u-boot.bin" used for?

    Bernie Thompson said:
    That is a U-Boot binary, you could use that with the serial loader to get U-Boot running on the board.

    But what's the difference between peripheral-_u-boot.bin and OMAP35x_SDK_1.0.0/board_utilities/OMAP35x/u-boot.bin?  They are different sizes so apparently are not functionally equivalent.

     

  • It looks like they are different builds of U-Boot, unfortunately I am not sure what makes the peripheral version special, I suspect it is a vestigial file as I have never seen it used in any of the documentation so it is likely just an older version of U-Boot that has not been removed, this is something I would have to verify.

    EDIT: Additional research leads me to believe this is just a U-Boot binary that is built by Mistral, though not definitive I believe this is just what they use to test the serial loading utility.