• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Subscribers 97 subscribers
  • Views 1259 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.

OMAP-L138 Experimenter board - Flash Utility Problem

Andres Gomez
Intellectual 270 points
Other Parts Discussed in Thread: OMAP-L138, TMS320C6748, AM1808

I'm trying to erase SPI Flash on Experimenter board.

On the  cmd line I'm trying "sfh_OMAP-L138.exe -erase"

"Waiting for SFT on the OMAP-L138..."    and nothing happens. It hangs.... Any suggestions?

Are there other ways to load an image into flash for the experimenter?

Thanks for your help!

 

  • 0
    TI__Mastermind 27585 points

    Are you using the latest version of the serial flasher? And are you using the OMAP-L138 or C6748?

    The SPI flash is directly on the SOM so there are rarely issues with flashing this. Are you able to use the CCS flasher to test if the SPI is working?

    Jeff

  • 0 in reply to jc-ti
    Intellectual 270 points

    Hi Jeff,

    Thanks for your response. I have used the following versions of the serial flasher without any luck: 4/29/2010 (196 KB) and  2/10/2011 (224 KB)

    Is there a newer version?

    Yes, the SPI Flash is directly on the SOM. To test the SPI Flash I have used the test under c6748\tests\experimenter\spiflash and the test passed (tested with CCS).

    Any ideas?

    Thanks!

     

  • 0 in reply to Andres Gomez
    TI__Mastermind 27585 points

    Maybe there is an issue with the UART connection to your host. Is your host running Windows or Linux? Are you using a NULL modem cable, or a USB adapter?

    Jeff

  • 0 in reply to jc-ti
    Intellectual 270 points

    My host is running Windows. I'm using a NULL Modem cable.

    Andres

  • 0 in reply to Andres Gomez
    Intellectual 270 points

    My issue is similar to the following posting:

    http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/p/100815/354758.aspx

    But mine hangs here "Waiting for SFT on the OMAP-L138..."

    I'm running XP and checked the Ports on "Device Manager" and COM1 says "This device is working properly."

    Thanks,

    Andres

  • 0 in reply to Andres Gomez
    Intellectual 270 points

    Jeff,

    I found another similar issue to mine: http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/p/72532/380906.aspx#380906

    The fix mentioned changing the DDR timing which is set by the AISgen tool provided by TI. Colman got it working by reducint the DDR2 clock rate.  Is this correct? Can you guys provide a fix?

    Thanks,

    Andres

  • 0 in reply to Andres Gomez
    TI__Mastermind 27585 points

    If you are using the LogicPD EVM with the SOM, the mDDR timings are already set correctly, so it should just work without any changes.

    I have tested the latest files on my own EVM and it worked. What is the serial number of the SOM (101xxxx)?

    Jeff

  • 0 in reply to jc-ti
    Intellectual 270 points

    Jeff,

    Thanks again for your response. It is good to know I dont have to change the mDDR timings as suggested on another post.

    I tested my COM1 port with a terminal emulator and it seems to be working.  I connected the terminal to COM1, turned the power on and saw the message "BOOTME"

    I am using LogicPD "ZOOM OMAP-L138 eXperimenter Kit". The serial number of the SOM is 1016660

    Thanks,

    Andres

  • 0 in reply to Andres Gomez
    TI__Mastermind 27585 points

    That is the latest SOM which we have not seen any problems with.

    Can you try using the CCS flashing tools? Either the one that comes with the SFH or the one that comes in the PSP.

    Jeff

  • 0 in reply to jc-ti
    Intellectual 270 points

    Jeff,

    Can you point me to the CCS flashing tools (path, articles, documents, links or anything that talks about it) ?

    I have read other posts about using CCS Flashing tools and people suggest it took a long time to load small bin file into flash.  Why does it take a while?

    I mentioned I'm using the OMAP-138 eXperimenter Kit but did not explicitly mention I'm using the TMS320C6748 SOM-M1 instead of the OMAP-L138 SOM-M1.

    My cmd line to run the flash utility is: "sfh_OMAP-L138.exe -flash arm-spi-ais.bin u-boot.bin". when I switch SOMs and run the same cmd line, it works fine on the OMAP-L138 SOM-M1. Then I switched S7 pin 7 and 8 to off (all default to boot from SPI) and power cycled the board. It tried to boot from SPI Flash but it did not work correctly as there was a CRC issue.

    Is there an ais.bin for the "TMS320C6748 SOM-M1" ? This is the one I'm trying to get up and running.

    Thanks for your help!

    Andres

  • 0 in reply to Andres Gomez
    Intellectual 270 points

    Hi,

    Any suggestions on my questions from the previous message?

    I have tried a few other things and got further along.

    Using the Serial Boot and Flash Loading Utility for OMAP-L138 I erased the SPI flash typing the following in the cmd line:

    sfh_OMAP-L138.exe - erase - targetType C6748 -flashType SPI_MEM

    I tried to load the UBL and application image to SPI flash typing the following in the cmd line:

    sfh_OMAP-L138.exe -flash ubl_C6748_SPI_MEM.bin mytest.bin -targetType C6748 -flashType SPI_MEM

    *mytest.bin is my application

    It seemed to have worked as the Flashing operation for UBL and application was completed.

    I started putty (terminal) and connected to COM1. I resetted all S7 pins to OFF to boot from SPI Flash and restarted the board. I got the following:

    " C6748 initialization passed!

    Booting TI User Boot Loader  UBL Version 1.65, UBL Flashtype: SPI, Starting SPI Memory Copy...

    Valid magicnum, 0x55424CBB, found at offset 0x00010000.

          DONE

    Jumping to entry point at 0xC1080000 "

    Questions:

    1. Why is it jumping to 0xC1080000 ? This is address is in external_ram according to my linker file. Why is it jumping to external ram?

    2. Why is my Application in Flash not running?

    3. How do I make sure that my Application runs from Flash and does not get copied to RAM ( I really just need to run it from Flash) ?

    Thanks,

    Andres

  • 0 in reply to Andres Gomez
    Intellectual 270 points

    I got it working...

    I was able to load the LED example test to SPI Flash as an AIS bin, boot from SPI Flash and verify that it was working correctly

    I would like to share with others what I have done:

    There are two options for flashing SPI Flash on the OMAP-L138 eXperimenter Kit. My development tools/environment are:

    CCS Version: 4.2.0.10018

    C6748 Device type: d800k002

    OS: Windows XP SP2

    Option #1 Using the Boot and Flash Loading Utility for OMAP-L138

    http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138

    Using the AISgen:

    1. Under General tab I chose Device Type d800k002, DSP, set Boot Mode to SPI1 Flash, set Clock Source to Crystal and 24MHZ. Checked "Specify Entrypoint" and set it to  0x00000000 and then unchecked it so that it was grayed out.

    2. Under Peripheral tab I set Module Clock at 150 MHz, SPI Clock to 1, and 1.00MHz

    3. Checked "Configure PLL0" and under the PLL0 tab set Pre-Divisor to 1, Multiplier to 25, Post-Divisor to 2, DIV1 to 1, DIV3 to 3, DIV7 to 6, CPU to 300 MHz, SDRAM to 100 MHz and EMAC to 50.00 MHz

    4. Under DSP Application File I added:  <path of ubl file>\ubl_C6748_SPI_MEM.bin;<path of led test. out file>\test_led_dip.out

    5. Under AIS Ouput File I chose: C:\flash\ais.test.bin

    6. In the windows cmd line, I typed sfh_OMAP-L138.exe -flash_noubl ais.test.bin -targetType C6748 -flashType SPI_MEM (S7 pins 7 and 8 were ON). It flashed the application. The images was transmitted over UART. The Flashing process was quick.

    7. Turned board off, set all S7 pins to OFF. Turned board on to boot from SPI Flash, LED1 and LED2 started blinking.

    Option #2 Using the CCS Flashing Tools

    1. Downloaded the C6748_setupwin32_1_00_00_11.exe from TI's website

    2. Opened the spiflash_writer in CCS and built it.

    3. Generated the AIS file using the same steps as mentioned in Option#1. Used the UBL.bin and led.out and generated the ais.test.bin

    4. Ran the spiflash_writer in CCS and in the Console it prompted for some information. "Enter the image type (one of "dspais", "armubl", "uboot", "other")". In my case I entered dspais. Then it prompted to enter the file that shall be read into memory. I entered C:\flash\ais.test.bin

    5. It ran, erased flash and verified the file. The Flashing process was quick. I used a JTAG.

    6. Turned the board off and back on, and the LED1 and LED2 started blinking.

    The OMAP-L138/AM1808 SOM-M1 U-Boot Labs (Bootloader Documentation) provides detailed information about option #1 but These labs also assume that the OMAP-L138 EVM has the OMAP-L138 SOM-M1 (not the TMS320C6748 SOM-M1) connected to the baseboard.

    I hope this information helps others trying to load a Binary/App/Image into SPI Flash.

    Thanks,

    Andres 

  • 0 in reply to Andres Gomez
    TI__Mastermind 27585 points

    Thanks we updated the documentation to be more clear on the point that the device type must be selected for the serial flasher if the C6748 or AM1808 SOM are used. That was the root cause of your problems.

    Jeff