• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 98 subscribers
  • Views 2767 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.

AISGen Tool

Brian Boru
Expert 1030 points

Other Parts Discussed in Thread: OMAPL138

Hi,

I am trying to generate an SPI1 bootloader for my OMAP L138 Logic PD Experimenter kit. I want to generate a bootloader for the C6748 only as I am not using the ARM. I am using the serial flasher utility to flash the board. I was able to flash an example image (OMAPL138-DSP-LED-NAND-SPI-UART.bin) which I downloaded and it booted up in SPI1 master boot mode and flashed LEDs. When I try to generate my own boot image using the .out file, it will not boot. I've attached my AISGen cfg file.. could you tell me what I have missed in this cfg file?

Thanks

Brian

C6748_SPI1_Master_Boot.cfg

  • 0
    TI__Guru** 116100 points
    Dear Brian,

    When I try to generate my own boot image using the .out file, it will not boot. I've attached my AISGen cfg file..

    What type of project you are using ?
    LED toggling or UART echo etc.,
    Based on that we may need to change the *.cfg file.

    If you wish to boot DSP app on OMAPL138, you need bootloader to wake up the DSP to run the code on it as ARM is the master in OMAPL138.
    We have to convert bootloader to AIS format and DSP app into BIN format using RPRC tool.
    If you look into the given *.cfg fil, it has both ARM bootloader and DSP app.

    OMAPL138-DSP-LED-v4\OMAPL138-DSP-LED\OMAPL138-DSP-LED-NAND-SPI-UART.cfg
    App File String=C:\boot_examples\OMAPL138-DSP-LED\ARM\Debug\OMAPL138-DSP-LED-ARM.out;C:\boot_examples\OMAPL138-DSP-LED\DSP\Debug\OMAPL138-DSP-LED-DSP.out;

    Like this, we can also combine the bootloader code and DSP app into single AIS binary.

    But in your *.cfg file, just it has DSP app alone.
    App File String=C:\ti\biospsp_03_00_01_00\bootloaderUtils\OMAPL138-DSP-LED\DSP\Debug\OMAPL138-DSP-LED-DSP.out

    If you wish to boot AR app alone then you no need to use bootloader and just have ARM app and convert into AIS format.

    Please refer to this wiki page.
    processors.wiki.ti.com/.../Boot_Images_for_OMAP-L138

    I hope this helps.
  • 0
    TI__Guru** 116100 points

    Please try the attached *.cfg file and tell me whether it works for you. You will get the output file named as "OMAPL138-DSP-LED-DSP_Brian.bin"

    5852.C6748_SPI1_Master_Boot.cfg

  • 0 in reply to Titusrathinaraj Stalin
    Expert 1030 points
    Hi Titus,

    Thanks for your detailed response. I am using the LED-Blinking project, but this is not my goal. Ultimately, I want to generate an SPI1 master boot image for custom hardware running a C6746, and no ARM I believe. I am using the OMAP EVM to try to verify a C674x bootloader as I do not have my custom hardware yet.
    What is the procedure for creating a bootloader for just a C674x DSP? Also, my DSP application files are in .xe674 format and not .out format.. will the tools mentioned above treat these the same as .out files?

    Thanks
    Brian
  • 0 in reply to Brian Boru
    TI__Guru** 116100 points
    Dear Brian,


    What is the procedure for creating a bootloader for just a C674x DSP?


    The following code will act as a ARM bootloader (just wake up the DSP)
    OMAPL138-DSP-LED-v4\OMAPL138-DSP-LED\ARM\src\main.c

    Have you tried given *.cfg file which I have attached in above post ?


    lso, my DSP application files are in .xe674 format and not .out format.. will the tools mentioned above treat these the same as .out files?

    File extension seems to be encoder/decoder output files (library).
    I hope it would treat as *.out file (but it should be either COFF or ELF)
  • 0 in reply to Titusrathinaraj Stalin
    Expert 1030 points
    Hi Titus,

    I see. I am not in the office, so I will try this tomorrow and let you know how I get on.

    Many thanks

    Brian
  • 0 in reply to Brian Boru
    Expert 1030 points

    Hi Titus,

    I was able to generate a boot image using the two blinking LED .out files (ARM and DSP) in the one cfg file. I have a couple of curiosities with this..

    1. I wish to create a C6748 bootloader, but the cfg project still has ARM selected as the device type.. is this correct? If I am generating a bootloader for a C674x chip only on custom hardware, would I still configure the AISGen tool as device type = ARM?

    2. I am now trying to generate a boot image using one of my own applications. Should I be able to use the ARM LED .out file combined with any DSP .out file to generate a DSP bootloader? The idea would be that the ARM LED .out file just wakes up the DSP as you mentioned. 

    3. I have not been able to verify whether the AISGen tool will treat .xe674 files as .out files yet and can't find this info anywhere. Could you inquire if the AISGen tool will treat .xe674 files as .out files?

    Many thanks

    Brian

  • 0 in reply to Brian Boru
    TI__Guru** 116100 points
    Dear Brian,

    2. I am now trying to generate a boot image using one of my own applications. Should I be able to use the ARM LED .out file combined with any DSP .out file to generate a DSP bootloader? The idea would be that the ARM LED .out file just wakes up the DSP as you mentioned.

    Yes, you are right, it will act as bootloader.


    3. I have not been able to verify whether the AISGen tool will treat .xe674 files as .out files yet and can't find this info anywhere. Could you inquire if the AISGen tool will treat .xe674 files as .out files?

    Actually, tool won't check the *.out file, just it appends the AIS formatted code on the given binary.

    You can do HEX dump or OBJ dump the actual *.out and after *.AIS generated.
    You can find some of code is appended in header (very initial stage).
    So, you can rename *.out to any name, now also you can convert it, then you would get the same behavior with the tool.

    I hope this helps.
  • 0 in reply to Titusrathinaraj Stalin
    Expert 1030 points

    Hi Titus,

    Thanks for that. 

    Is the ARM .out file required in the AISGen tool just for OMAP (ARM + DSP) chips, or is this also the procedure for generating bootloader images for standalone C674x chips? Seems unusual that an ARM .out file is required to wake up a standalone C674x chip?

    Thanks

    Brian

  • 0 in reply to Brian Boru
    TI__Guru** 116100 points
    Dear Brian,

    Is the ARM .out file required in the AISGen tool just for OMAP (ARM + DSP) chips,

    Yes, it is applicable only for OMAPL138 (not for C6748 which has DSP alone)

    If you are using C6748, you don't want any bootloader, you can run the DSP application directly.
    You can also configure DDR in AISgen settings if you want to boot your DSP app on C6748.