Hi,
I'm done.
I have created DSP app LED project which will not wakeup the ARM and will run DSP app directly and also I have tested the DSP app on OMAPL137 SDI board(DA830).
(Please visit the site to view this file)
Steps:
1) Build DSP LED app project on CCS
2) Convert to binary from *.out through "HexAIS_OMAP-L137.exe" tool
Ex:
C:> HexAIS_OMAP-L137.exe -o OMAPL137-DSP-LED.bin DSP_LED_APP.out
3) Flash DSP LED app binary to SPI flash on OMAPL137 SDI board.
ex:
Set boot switch to UART
i)
root@titus-desktop:/home/titus/workdir/ti-e2e/src/DaVinci-PSP-SDK-03.22.00.06/host-tools/OMAP-L137_FlashAndBootUtils_2_43/OMAP-L137/GNU# ./sfh_OMAP-L137.exe -erase
ii)
root@titus-desktop:/home/titus/workdir/ti-e2e/src/DaVinci-PSP-SDK-03.22.00.06/host-tools/OMAP-L137_FlashAndBootUtils_2_43/OMAP-L137/GNU# ./sfh_OMAP-L137.exe -flash_noubl OMAPL137-DSP-LED.bin
Set boot switch to SPI
You can see the flashing LEDs on OMAPL137 board.
Please test at your end and let me know the status.
Typically,
For running the DSP binary on OMAPL137,
We do not want to wakeup the ARM and will run the DSP app directly through single binary.
For running the ARM binary on OMAPL137,
We should wakeup the ARM through DSP UBL code and we can run ARM app on OMAPL137's ARM core.
Here you need to bind the DSP UBL code and ARM binary.
Note:
TI wiki "Boot images for OMAPL137" seem to be wrong for the DSP LED project attachments,
Sorry for that,