• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 432 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.

TMDXICE3359 Rev 1.0 A does not boot from SPI flash after flashing pre-built bootloader and application

Edgar Schroeder
Prodigy 100 points
Other Parts Discussed in Thread: SYSBIOS

Hi All,

I have a similar problem to http://e2e.ti.com/support/dsp/sitara_arm174_microprocessors/f/791/t/179001.aspx.

The AM335x ICE board REV 1.0 A came with the LEDs flashing when power was applied.  I flashed the am335x_sysbios_ind_sdk_prebuilt_01_00_00_03 SPI boot loader according to the instructions in the Getting Started Guide.     After I flashed the the boot loader it didn't boot at all, not from the SD card and not from a newly flashed SPI flash App .  I erased the NOR flash, nothing.  I tried loading the NOR flash bootloader and application, still nothing.  All it does is light the green LED D3. I went through this process several time, no success. 

The first time I tried the GEL file AM335x initialization script, I had to do a HW reset because the ICE board was already running.  Ever since then, after flashing the pre-built bootloader, I have not had to do a HW reset, the script runs every time.  Seems the board is not running.

Is there something different between REV 1.0 A and A2?  Is the bootloader different between these two hardware revisions?

Thanks,

Ed Schroeder

  • 0
    Intellectual 810 points

    1. What is the nature of the app that you are attempting to flash: you mentioned that you (hopefully) flashed the prebuilt bootloader for 01.00.00.03...are you also trying one of the prebuilt apps from 01.00.00.03 or compiling your own?

     

    2. Are you getting any output on your virtual serial port: anything like this?:

    *** StarterWare  Boot Loader. Build -  ***

    Copying application image from MMCSD to RAM

    Unable to open application file from MMCSD

    Copying application image from SPI to RAM

    Image Copy Successful, Executing Application..

    1.0.13

  • 0 in reply to Darrin Hansen
    Expert 2380 points

    Hello Ed Schroeder,

    The bootloader is same for both ICE revisions.

    The board seems to be having no issues as  the LEDs were rolling when it was powered up first time. The only possibility I can think of is flash corruption.

    As the above post suggested, please let us know what is the UART message that you see.

    Regards,

    Shahid

  • 0 in reply to Shahid AC
    Prodigy 100 points

    Thanks Darrin and Shahid,

    I revisited the instructions in the Starting Guide and realized that I hit 0 before loading memory with the .bin file.  I was thrown because you had to give the SPI loader tool the .bin file name and then again in the load memory step. 

    But now you have me curious.  Everything works again,  SD card and SPI boot just fine, but there is no output to the virtual COM port.   From the bootloader source code it seems that the PORT needs to be 115200, 8, n, 1 and no hardware control.  Is this correct?  My PC assigned it to COM15, this should have no bearing on the problem, but just in case I thought I would mention it.

    Thanks again,

    Ed Schroeder

  • 0 in reply to Edgar Schroeder
    Intellectual 810 points

    That sounds like the correct settings for the serial port: it's COM4 on my machine but I wouldn't think it should matter unless the terminal emulator program you are using has some sort of max com port restriction.  The only trouble I have with my terminal emulator program (Terra Term) is that once I'm all connected and powered up, in order to actually get anything to display I first have to select a different COM port in the setup menu, and then go back to COM4.

    Darrin

  • 0 in reply to Darrin Hansen
    Prodigy 100 points

    Thanks Darrin,

    Again it was a misunderstanding on my part.  I should have realized that I needed to hit the reset button to see the virtual COM port output.  Now everything works as expected.

    You have been a great help.

    Ed