• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 376 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.

U-Boot image : Reflash broken in OMAP35x-PSP-SDK-02.01.01.07

IsaacLeung
Intellectual 395 points

Just a note:

The U-Boot image is slightly broken in this version of the PSP. The command for programming the OneNAND is broken, I rebuilt the image and same problem. I'm not going to bother delving into it just now, but suffice to say, if you follow the instructions in the Getting Started Guide and you use the current U-Boot image, you won't be able to reflash anything with Samsung memory.

Also, I should note that the Getting Started Guide has since omitted some important fixes that need to be made to the re-flash scripts, but the scripts themselves in the package have not been updated, so you need to refer back to some older documentation on how to do this.

Good luck...

  • 0
    TI__Expert 5000 points

    Hi,

    There are some problems with the flashing scripts. They will be fixed in the next release 02.01.01.09. For instance see below-

    Micron Nand scripts:

    Change is required in the syntax of the nand  ecc command to nandecc
    Change in size of the uImage from 0x200000 to 0x 220000 is required.

    After doing the above mentioned changes Micron scripts execute fine

    Samsung oneNand scripts:
    Change in size of the uImage from 0x200000 to 0x 220000  is required.

    Thanks,

    Prathap.

  • 0 in reply to Prathap Srinivas
    Intellectual 395 points

    No, that doesn't do it. I have the OMAP EVM from Mistral with the Samsung memory, so I'm using those scripts.

     

    First of all, the U-Boot.BIN image file that is included has a flaw, it doesn't support the "onenand unlock" operation. Before I send "reflash-samsung.txt", I tried the following:

    help onenand

    (unlock doesn't show up)

    and manually typing:

    onenand unlock 0x0 0x8000000

    which produces an error about wrong number of arguments. If you run the reflash script with "run rf_all_fs", you will see this error pop up all the time as it goes through all the commands.

    Secondly, I'm not sure if that is a typo, you can't change from 0x200000 to 0x 220000, that will produce an error. Don't use the space.

    If I ignore all the errors and proceed anyones, Linux, of course, doesn't boot. Basically I get the following:

     ----------------------------------------------------------------------------------------------

    Texas Instruments X-Loader 1.41
    Detected Samsung MuxOneNAND1G Flash
    Starting OS Bootloader...
    No OOB scheme defined for oobsize 0
    Scanning device for bad blocks
    onenand_read_oob_nolock: read failed = 0xfffffff5
    Bad eraseblock 501 at 0x03ea0000
    OneNAND: 128 MB
    No NAND device found!!!
    0 MiB


    U-Boot 2008.10 (Jun 15 2009 - 11:34:44)

    OMAP35X-Family-GP rev 2, CPU-OPP2 L3-165MHz
    OMAP3 EVM board + LPDDR/ONENAND
    In: serial
    Out: serial
    Err: serial
    OMAP3_EVM #
     ----------------------------------------------------------------------------------------------

    Something wrong with my procedure? I hope not, as I follow the same procedure with the 1.0.2 PSP version and I can get it going every time. Different scripts (which have to be edited), different image whatever comes with the package.