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

Run u-boot from DRAM on OMAP35X EVM

shauly
Intellectual 315 points

hello,

Question: how to program and run u-boot from DDRAM on OMAPEVM35X?

I have donload the u-boot using DownloadUtility.exe to DDRAM  (the original u-boot is run from flash)

and try to run it with:

go 0x80e80000

## Starting application at 0x80E80000 ...

 

U-Boot 1.1.4 (Jan 18 2009 - 10:19:07)

OMAP3-GP rev 2, CPU-OPP2 L3-165MHz

OMAP3EVM 1.0 Version + mPOP (Boot ONND)

DRAM:  128 MB

OneNAND Manufacturer: Samsung (0xec)

Muxed OneNAND 128MB 1.8V 16-bit (0x30)

OneNAND version = 0x0221


quastion: how to program and run u-boot from DDRAM

note: i can see that u-boot is loaded to DDRAM

thanks

Shaul

OMAP3EVM # ver

U-Boot 1.1.4 (Jan 18 2009 - 10:19:07)

OMAP3EVM # md 0x80e9ec30

80e9ec30: 80e9f89a 80e9f8a2 80e9f8a9 80e9f8b1    ................

80e9ec40: 80e9f8b9 80e9f8c1 6f422d55 3120746f    ........U-Boot 1

80e9ec50: 342e312e 614a2820 3831206e 30303220    .1.4 (Jan 18 200

80e9ec60: 202d2039 313a3031 37303a39 00000029    9 - 10:19:07)...

80e9ec70: 00000000 00000000 4806a000 00000000    ...........H....

80e9ec80: 00000000 00000000 ffffffff ffffffff    ................

80e9ec90: ffffffff ffffffff ffffffff ffffffff    ................

80e9eca0: ffffffff ffffffff ffffffff ffffffff    ................

80e9ecb0: ffffffff ffffffff ffffffff ffffffff    ................

80e9ecc0: ffffffff ffffffff 00000a0a 000000ec    ................

80e9ecd0: 80ea0bf3 00000000 80ea064c 646e616e    ........L...nand

80e9ece0: 00000000 59035655 5a5a0f0c 03590c0f    ....UV.Y..ZZ..Y.

80e9ecf0: 65005556 3c663330 3f3f6a69 663c696a    VU.e03f<ij??ji<f

80e9ed00: 66653033 3f653033 3c3c696a 653f6a69    30ef30e?ji<<ij?e

80e9ed10: 03663330 5a005556 59590c0f 005a0f0c    03f.VU.Z..YY..Z.

80e9ed20: 69035655 306a3f3c 33336665 6a306566    UV.i<?j0ef33fe0j

OMAP3EVM #

  • 0
    TI__Mastermind 37340 points

    I am not sure I understand the question 100%, but I would refer you to the Getting Started Guide; it describes how to use the download utility and download u-boot and simply pressing "enter" to get a u-boot prompt (meaning u-boot is running).  It also describes how you can upate flash contents using u-boot.  Let us know if this helps and if there is anything else we can assist you with.

  • 0 in reply to Juan Gonzales
    Intellectual 315 points
    Thanks So The download utility locate the u-boot at DDRAM start address 0x80000000. Can I tell the download utility to load application to other address? how I can run the loaded u-boot from his start address? now its show the u-boot cursor and skip the initialization process Shaul
  • 0 in reply to shauly
    TI__Mastermind 41665 points

    The download utility appears to be hardwired for 0x80000000, there is no option to change it even in the .ini file (at least nothing I can see or have come across), and since the source is not available currently it is not possible to change the address.

    I am curious why you want to use another address? What are you trying to accomplish by loading U-boot with the serial download utility as opposed to the U-boot in flash? Usually you would only use the download utility if your existing U-boot has become corrupted, or as a way of updating the U-boot on the flash.

  • 0 in reply to Bernie Thompson TI
    Intellectual 315 points
    You are right ,I can use the u-boot to load my application Thanks for your answers Shaul
  • 0 in reply to shauly
    Intellectual 315 points
    I have load the reflash-samsung.txt script, then I "run rf_all_fs" . at the end I reset the board and it stack,and show this message:. Texas Instruments X-Loader 1.41 Detected Samsung MuxOneNAND1G Flash Starting OS Bootloader... What is wrong here? is this the procedure to flash new /x-load/u-boot/kernel/FS? Here is the process after run the reflash-samsung.txt script. OMAP3EVM # printenv bootargs=mem=128M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2 bootcmd=echo bootcmd is not configured bootkernel=onenand read 0x80000000 0x280000 0x400000 ; run bootkernel_1 bootkernel_1=bootm 0x80000000 bootdelay=0 baudrate=115200 preboot= gatewayip=192.168.1.1 netmask=255.255.255.0 bootfile="uImage" stdin=serial stdout=serial stderr=serial mmcboot=mmcinit;fatload mmc 0 0x80000000 uImage;fatload mmc 0 0x81600000 ramdisk.gz;bootm 0x80000000 rf_unlock=onenand unlock 0x0 0x8000000 rf_blank_ram=mw.b 0x81600000 0xff 0x1400000 rf_er_xloader=onenand erase block 0-3 rf_er_uboot=onenand erase block 4-18 rf_er_env=onenand erase block 19-19 rf_er_kernel=onenand erase block 20-59 rf_er_ramdisk=onenand erase block 60-1023 rf_er_fs=onenand erase block 60-1023 rf_get_xloader=tftpboot 0x81600000 board_utilities/OMAP35x/x-load.bin.ift rf_get_uboot=tftpboot 0x81600000 board_utilities/OMAP35x/u-boot.bin rf_get_kernel=tftpboot 0x81600000 bin/OMAP35x/uImage rf_get_ramdisk=tftpboot 0x81600000 bin/ramdisk-full.gz rf_get_min_rd=tftpboot 0x81600000 bin/ramdisk-min.gz rf_get_fs=tftpboot 0x81600000 bin/rootfs.jffs2 rf_wr_xloader=onenand write 0x81600000 0x000000 0x0020000 rf_wr_uboot=onenand write 0x81600000 0x080000 0x0040000 rf_wr_kernel=onenand write 0x81600000 0x280000 0x0200000 rf_wr_ramdisk=onenand write 0x81600000 0x780000 0x1000000 rf_wr_fs=onenand write 0x81600000 0x780000 0x1400000 rf_ev=run rf_unlock; run rf_er_env rf_xl=run rf_unlock; run rf_blank_ram; run rf_er_xloader; run rf_get_xloader; run rf_wr_xloader rf_ub=run rf_unlock; run rf_blank_ram; run rf_er_uboot; run rf_get_uboot; run rf_wr_uboot rf_kn=run rf_unlock; run rf_blank_ram; run rf_er_kernel; run rf_get_kernel; run rf_wr_kernel rf_rd=run rf_unlock; run rf_blank_ram; run rf_er_ramdisk; run rf_get_ramdisk; run rf_wr_ramdisk rf_min_rd=run rf_unlock; run rf_blank_ram; run rf_er_ramdisk; run rf_get_min_rd; run rf_wr_ramdisk rf_fs=run rf_unlock; run rf_blank_ram; run rf_er_fs; run rf_get_fs; run rf_wr_fs rf_all_rd=run rf_xl; run rf_ub; run rf_kn; run rf_rd rf_all_min_rd=run rf_xl; run rf_ub; run rf_kn; run rf_min_rd rf_all_fs=run rf_xl; run rf_ub; run rf_kn; run rf_fs ethaddr=00:50:c2:7e:86:91 ipaddr=150.60.9.8 serverip=150.60.9.9 Environment size: 2237/131068 bytes OMAP3EVM # run rf_all_fs start = 0x00000000, ofs = 0x08000000 Erase block from 0 to 3 Reseting CHIP... Done LAN9x18 (0x01150002) detected. Setting mac address: 00:50:c2:7e:86:91 start Auto negotiation... (take ~2sec) Auto negotiation complete, 100BaseTX, full duplex TFTP from server 150.60.9.9; our IP address is 150.60.9.8 Filename 'board_utilities/OMAP35x/x-load.bin.ift'. Load address: 0x81600000 Loading: #### done Bytes transferred = 16908 (420c hex) onenadwrite: addr = 0x81600000, ofs = 0x0, len = 0x20000 Done. ret = 0 start = 0x00000000, ofs = 0x08000000 Erase block from 4 to 18 Reseting CHIP... Done LAN9x18 (0x01150002) detected. Setting mac address: 00:50:c2:7e:86:91 start Auto negotiation... (take ~2sec) Auto negotiation complete, 100BaseTX, full duplex TFTP from server 150.60.9.9; our IP address is 150.60.9.8 Filename 'board_utilities/OMAP35x/u-boot.bin'. Load address: 0x81600000 Loading: ################################ done Bytes transferred = 160984 (274d8 hex) onenadwrite: addr = 0x81600000, ofs = 0x80000, len = 0x40000 Done. ret = 0 start = 0x00000000, ofs = 0x08000000 Erase block from 20 to 59 Reseting CHIP... Done LAN9x18 (0x01150002) detected. Setting mac address: 00:50:c2:7e:86:91 start Auto negotiation... (take ~2sec) Auto negotiation complete, 100BaseTX, full duplex TFTP from server 150.60.9.9; our IP address is 150.60.9.8 Filename 'bin/OMAP35x/uImage'. Load address: 0x81600000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ###################################################### done Bytes transferred = 1935908 (1d8a24 hex) onenadwrite: addr = 0x81600000, ofs = 0x280000, len = 0x200000 Done. ret = 0 start = 0x00000000, ofs = 0x08000000 Erase block from 60 to 1023 onenand_erase: not erasing bad block @0x1f40000 onenand_erase: not erasing bad block @0x4f00000 Reseting CHIP... Done LAN9x18 (0x01150002) detected. Setting mac address: 00:50:c2:7e:86:91 start Auto negotiation... (take ~2sec) Auto negotiation complete, 100BaseTX, full duplex TFTP from server 150.60.9.9; our IP address is 150.60.9.8 Filename 'bin/rootfs.jffs2'. Load address: 0x81600000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ############################################################# done Bytes transferred = 18612224 (11c0000 hex) onenadwrite: addr = 0x81600000, ofs = 0x780000, len = 0x1400000 Done. ret = 0 �MAP3EVM # reset Texas Instruments X-Loader 1.41 Detected Samsung MuxOneNAND1G Flash Starting OS Bootloader... ��
  • 0 in reply to shauly
    TI__Mastermind 41665 points

    It seems that your post somehow lost all carriage returns so it is kind of hard to read, but it looks like the flashing procedure shown there was successfull. Are you saying that it hangs after 'Starting OS Bootloader'?

  • 0 in reply to Bernie Thompson TI
    Intellectual 315 points

    sorry for that...

    Exactly

    I have load the reflash-samsung.txt script,

    then I "run rf_all_fs" .

    at the end I reset the board and it stack,and show this message:.

    Texas Instruments X-Loader 1.41 Detected Samsung MuxOneNAND1G Flash Starting OS Bootloader...

    I'm using the original image

    Shaul

     

     

     

  • 0 in reply to shauly
    TI__Mastermind 41665 points

    If the X-Loader is running but the U-Boot is not than I would suspect that somehow the U-Boot on the flash is corrupted in which case I would try using the serial boot utility and reflashing it again and perhaps rebuilding U-Boot and using a freshly built image. Have you tried reflashing it since it failed?

  • 0 in reply to Bernie Thompson TI
    Intellectual 315 points

    When I run the "run rf_all_fs" its include the u-boot reflash ...

    Unless I mistake and its not do so.

    I'll try to reflash the u-boot only with:rf_ub

  • 0 in reply to shauly
    TI__Mastermind 41665 points

    You are correct that the rf_all_fs does include reflashing U-Boot, I just wanted to make sure you tried doing that more than once to ensure it was not a fluke failure in the reflashing process. If that is the case I would suggest trying a rebuilt U-Boot as it could be that your original U-Boot binary file got corrupted somehow.

  • 0 in reply to shauly
    Intellectual 315 points

    You right the u-boot was corrupted

    I have tried to load and reflash compile u-boot and now I can see it :)

     

    I will try all the process with "run rf_all_fs"

     

    Thanks

     

    Shaul

     

     

  • 0 in reply to shauly
    Intellectual 315 points

    Now all works

     

    Thanks

     

    Shaul