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.

DM8168 U-Boot flashing problem

8875.pdf and u-boot.rarI flashed builted U-Boot to Nand flash according to <DM8168_DVR_RDK_Install_Guide.pdf -- section 1.4.3.2.2> and the board doesn't work now,

and I want to use sd card to reboot it and flash TI offered /bin/u-boot.bin back to Nand flash according to <section 1.4.3.2.1>, It doesn't work either.

I use 2G*4G * fat32*fat16 sd cards, none of them works, no serial output found. 

so, any other restrain to sd card, or any other suggestions ?

Attchment pls find the pdf and u-boot both for sd card and nand flash.

 

Besides, Is there any detailed instructions for flashing it using CCS?

Thank you! 

  • I have successfully flashed the DM8168 EVM NAND using CCS and also using u-boot.  Using u-boot is quicker and easier in my opinion, but the instructions for CCS are here:

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

  • Hi, Jeffray

    Thanks for reply.

    Could you boot the board from SD card U-Boot but not the Nand Flash U-Boot, and how about using my attchment files MOL and u-boot.bin for SD card? and what's you SD Card formation?

    I've also used CCS, but it was stuck on "launch Selected Configuration"

    I used CCS v4.1 v4.2 and v5, and SEED-XDS560PLUS Jtag, what's you CCS version?

  • I used the SD card supplied with the EVM, but I've also created my own setup on a fresh SD card as per the instructions on the wiki:

    http://processors.wiki.ti.com/index.php?title=How_to_Make_3_Partition_SD_Card

    Boot U-Boot from SD card, then use it to fetch the new u-boot and write it the Nand;

    mw.b 0x81000000 0xFF 0x20000 ; tftp 0x81000000 u-boot.min.nand ; nand erase 0x0 0x60000 ; nandecc hw 2 ; nand write.i 0x81000000 0x0 0x20000 ; nandecc hw 0 ; mw.b 0x81000000 0xFF 0x40000 ; tftp 0x81000000 u-boot.bin ; nand write.i 0x81000000 0x20000 0x40000

    More info here; http://processors.wiki.ti.com/index.php/DM816x_AM389x_PSP_U-Boot

    I also used CCSv5 as supplied with the EVM, and the XDS100v3 as supplied with the EVM, and the instructions on the wiki.   It's really slow, though (maybe your XDS560 would be nice and fast!), so flipping the boot mode switches and using u-boot to write a new u-boot to NAND is much faster.   Fortunately this isn't required very often - only when I completely screw up U-boot nand builds and need to 'unbrick' the board :-)

  • Oops. The commands I pasted above are actually for DM814x.  For DM816x the boot.min is not required:

    mw.b 0x81000000 0xFF 0x260000 ; tftp 0x81000000 u-boot.noxip.bin ; nand erase 0x0 0x260000 ; nandecc hw 2 ; nand write.i 0x81000000 0x0 0x260000 ; nandecc hw 0

  • Hi,Jeffray

    I havn't got a supplied SD card, and my SD card setup creating goes not smooth, so does a fresh SD card + offered files(MLO, u-boot.bin) works on your board?

    or How Can I get a special purpose SD card TI supplied?

    Thanks,

    Jacky.

  • what's the difference between the comman "nand write" and "nand write.i"?

    BTW, CCS flashing works now, it's driver problem before; and my sd card works too.

  • Hi,


    I'm using DM810x_DVR_RDK_Install_Guide for flashing NAND Flash on TI 8107 DVR RDK HW. While using TFTP for flashing, we give the following command,
                    
                 UBOOT# mw.b 0x81000000 0xFF 0x20000;
                   tftp 0x81000000 u-boot_ud810x_dvr.min.nand;
                   nand erase 0x0 0x20000;
                   nand write 0x81000000 0x0 0x20000;

    I wanted to know why 0xFF is used here. Also it is used in SD card support.

  • Aparna,

    The 1st step is setting the memory range with "0xFF" where we wanted to load the nand image. (This is an optional step)

    The default erase bit state of the NAND flash memory is 1( that means "0xFF" for a byte).

    We are not passing the actual images size to the nand write command but it is aligned to the next page boundary.  The NAND write command will try to write entire page boundary area which can be avoided if it is set to the default erase state which is "0xFF"