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

Full boot from NAND on LogicPD OMAP-L138 EVM with AM1808

Carmelo Garcia
Prodigy 105 points
Other Parts Discussed in Thread: OMAP-L138, AM1808, OMAPL138

Hello everyone.

My purpose it to flash UBL, u-Boot, Kernel and Rootfs in a NAND flash, so I can boot from there and use the SD just for recovery and updates.

I have been trying with the NANDWriter (loading it with CCSv5 and a XDS100v2) and been almost successful on the basic boot.

My first problem comes when I load and try running the NANDwriter directly.

After connecting, I execute the script "EMIFA_NAND_PINMUX", load the program and when running, it gives no response and hangs on "Starting OMAP-L138 NANDWriter".

However, if I load and run the RAM Test example before doing all this, it works. What am I missing?

The second and main problem appears when running wht NANDWriter. It flashes UBL, but when flashing u-Boot, it asks to enter:

1) the app image load address (in hex)

2) the app image entry point address (in hex)

What are these parameters?

I have tried some values, but of course don't work.

Furthermore, I would like to configure uboot to load kernel and rootfs from the same NAND flash. Is this possible?

Any help?

Thank you very much.

 

  • 0
    TI__Genius 17355 points

    Carmelo Garcia said:

    The second and main problem appears when running wht NANDWriter. It flashes UBL, but when flashing u-Boot, it asks to enter:

    1) the app image load address (in hex)

    2) the app image entry point address (in hex)

    What are these parameters?

    These values are both 0xC1080000.  They specify to what address the UBL should load the application image (in this case u-boot) and to what address the UBL should jump to start executing that loaded image.  The u-boot image provided for this platform is linked to have the address 0xC1080000 as both it's load address and entry point.

    Carmelo Garcia said:
    Furthermore, I would like to configure uboot to load kernel and rootfs from the same NAND flash. Is this possible?

    This is possible, but you will have to create MTD partitions on the NAND flash so that Linux can manage them (or at least the one with the filesystem).  A quick google search turns up a number of different things to consider (using mtdparts from u-boot, static mtd partitioning in the kernel). I've never done this myself, but maybe these articles will help:

    http://processors.wiki.ti.com/index.php/Writing_Kernel_Image_to_NAND_Flash

    http://processors.wiki.ti.com/index.php/Put_JFFS2_Image_to_Flash

     

    Hopefully, some of the above will get you pointed in the right direction.

    Regards, Daniel

  • 0 in reply to Daniel Allred
    Expert 2280 points

    Daniel Allred said:

    The second and main problem appears when running wht NANDWriter. It flashes UBL, but when flashing u-Boot, it asks to enter:

    1) the app image load address (in hex)

    2) the app image entry point address (in hex)

    What are these parameters?

    These values are both 0xC1080000.  They specify to what address the UBL should load the application image (in this case u-boot) and to what address the UBL should jump to start executing that loaded image.  The u-boot image provided for this platform is linked to have the address 0xC1080000 as both it's load address and entry point.

    [/quote]

    Hi Daniel, I have a question about this topic.

    I use that address, 0xC1080000, in AIS-gen tool to generate an ais image from an u-boot binary. Then I write the ais file to SPI Flash to boot the system without UBL (I'm working with LogicPD ZOOM AM1808 Experimenter Kit). If I use the u-boot binary provided with TI SDK 4.01 the system boot successfully, but it doesn't work with u-boot binary pre-built in SDK 5.02. Any suggestion about this issue?

    Thanks.

    Regards,
    Max

     

  • 0 in reply to Qmax
    TI__Genius 17355 points

    I haven't used that SDK with that u-boot, but if I get I chance I'll try it.

    Regards, Daniel

  • 0 in reply to Qmax
    TI__Mastermind 40080 points

    What tool are you using to program the SPI? The OMAPL138 Tool? If you are using that tool you do not need to run the AIS tool on the u-boot binary.

  • 0 in reply to Schuyler Patton
    Expert 2280 points

    I'm using the sfh_OMAP-L138.exe application within OMAP-L138_FlashAndBootUtils_2_31 tools package.

    mono ./sfh_OMAP-L138.exe -flash_noubl -targetType AM1808 -flashType SPI_MEM -v -p /dev/ttyUSB0 <u-boot.bin.ais>

    Please note that I'm not using UBL, so in my understanding AIS scrtipting is required to initialise PLL, DDR, etc...

    Am I wrong or am I missing something?

    Thanks. Regards,
    Max

     

  • 0 in reply to Qmax
    TI__Genius 17355 points

    I think the answer I posted in the other thread should help.  I tried doing exactly what I think you are doing, and I was able to get it to work as described there.

    http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/151906.aspx#552578

    Regards, Daniel

  • 0 in reply to Daniel Allred
    Expert 2280 points

    Yes, thanks. Regards, Max