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.

Keystone II Rev 3.0 EVM - fails to get to u-boot prompt

 
   I am trying to setup my Hawking with the latest MCSDK-HPC release (per:  http://processors.wiki.ti.com/index.php/MCSDK_HPC_3.x_Getting_Started_Guide
).
 
   After updating the u-boot-spi-keystone-evm.gph from the newer MCSDK images (using the sf erase, sf write commands from the EVM’s u-boot prompt per the above guide), the EVM now fails to get any console output on the debug COM port, and fails to show the u-boot prompt.
 
   The output from the BMC session looks fine, and is as follows:
 
 
BMC VERSION 1.0.2.5
BUILT May 14 2013 11:46:18
---------------------
[00:00:00]  BMC Init Begin
[00:00:00]  BMC Version 1.0.2.5
[00:00:00]  XTCIEVMK2X
[00:00:00]  3.0
[00:00:00]  S/N: 91402
[00:00:00]  BMC Init Complete
[00:00:00]  Main PWR Start Begin
[00:00:00]  Main PWR Start Complete
[00:00:00]  SOC PWR Start Begin
[00:00:00]  Clock 1
[00:00:00]  Passed
[00:00:00]  Clock 2
[00:00:01]  Passed
[00:00:01]  Clock 3
[00:00:01]  Passed
[00:00:01]  SOC PWR Start Complete
[00:00:02]  SOC RST Begin
[00:00:02]  Current BootMode is set to ARM SPI
[00:00:02]  SOC RST Complete
[00:00:02]  BOOT COMPLETE
 
 
    I was thinking my only option now is to use CCS to flash a new u-boot, but I have a Rev 3.0 EVM, and looking at  http://processors.wiki.ti.com/index.php/Program_EVM_UG I see:
 
“For Rev 2.0 and 3.0 EVM using alternative U-Boot command to program NAND, please follow the steps below:
Set the boot mode to SPI boot mode: Set_SPI_boot
  1. Set up TFTP server
  2. Have Ethernet cable connected to the EVM and verify the connection to the TFTP server
  3. Boot up the EVM to the U-boot prompt and type the following commands:”
 
   Which is a bit of a catch-22, since one cannot get to the u-boot prompt in the first place to install a new u-boot!
 
   Is there an alternate method to reflash the u-boot on a Rev 3.0 EVM which doesn’t already involve already having u-boot working?
 
Thanks,
- Gil 
  • Gil,

    It's been a while since I've done this, but here's something to try:

    If somehow u-boot got erased on your board, you can still load u-boot directly to MSMC memory using CCS. It's tricky --

    Basically,  start by looking here: http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Tools#Loading_U-Boot_with_CCS 

    You want to start by getting u-boot running from MSMC (by loading the .bin file).  Once you get the u-boot prompt, halt. Then, the same way you loaded the.bin file to address 0xc001000, this time you should load the .gph file to the location 0xc300000. Resume, and follow the steps pretending like you downloaded the .gph via tftp:

    setenv serverip 192.168.1.10
    dhcp 0xc300000 u-boot-spi-keystone-evm.gph
    sf probe 
    sf erase 0 <size of u-boot-spi-keystone-evm.gph in hex rounded to
                sector boundary of 0x10000> 
    sf write 0xc300000 0 <size of u-boot-spi-keystone-evm.gph image in
                hex> 

    I crossed out the two lines because you'll be loading the .gph using CCS instead of downloading it over the network.
  • Thanks Dharik!

       I essentially followed the link you provided, and ran the following commands once the first stage u-boot was loaded, which updated to the latest .gph file:

     run get_uboot_net
     run burn_uboot

    I can once again boot Linux :-)

    Many Thanks,
    - Gil