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.

Linux/66AK2L06: Ease the original linux kernel , cannot boot by uboot

Part Number: 66AK2L06


Tool/software: Linux

I follow this link processors.wiki.ti.com/.../Program_EVM_UG

and format the nand by the command

$DSS_SCRIPT_DIR/dss.sh program_evm.js evmk2l-le format-nand

and when I do the following command
$DSS_SCRIPT_DIR/dss.sh program_evm.js evmk2l-le nand

it stuck and cannot flash the nand successfully.

I use the following command to load the uboot to the nor,
$DSS_SCRIPT_DIR/dss.sh program_evm.js evmk2l-le nand

and when I switch to spi bootmode, i can type uboot command. I try to use tftpboot, but the dhcp doesnot work.

Someone has the similar experience on the 66AK2L06 EVM, please let me know how you boot the linux kernel with uboot.

Thanks!


  • There is damaged block in the nand flash.

    Here is the output after I run the following commands
    $DSS_SCRIPT_DIR/dss.sh program_evm.js evmk2l-le nand
    It takes about tens of minutes to load the nand.bin file, and takes another half hour to flash the blocks. Because there is a damage block (block 6), the procedure try to flash the nand server times.

    Flashing block 1870 (488636416 bytes of 490995712)
    Flashing block 1871 (488898560 bytes of 490995712)
    Flashing block 1872 (489160704 bytes of 490995712)
    Flashing block 1873 (489422848 bytes of 490995712)
    Flashing block 1874 (489684992 bytes of 490995712)
    Flashing block 1875 (489947136 bytes of 490995712)
    Flashing block 1876 (490209280 bytes of 490995712)
    Flashing block 1877 (490471424 bytes of 490995712)
    Flashing block 1878 (490733568 bytes of 490995712)
    Reading and verifying block 6 (0 bytes of 490995712)
    Failure in reading block 6
    Returned platform error number is 2
    Flashing block 6 (0 bytes of 490995712)
    Flashing block 7 (262144 bytes of 490995712)
    Flashing block 8 (524288 bytes of 490995712)
    Flashing block 9 (786432 bytes of 490995712)
    Flashing block 10 (1048576 bytes of 490995712)
    Flashing block 11 (1310720 bytes of 490995712)
    Flashing block 12 (1572864 bytes of 490995712)
    Flashing block 13 (1835008 bytes of 490995712)
    Flashing block 14 (2097152 bytes of 490995712)
    Flashing block 15 (2359296 bytes of 490995712)
    Flashing block 16 (2621440 bytes of 490995712)
    Flashing block 17 (2883584 bytes of 490995712)
    Flashing block 18 (3145728 bytes of 490995712)
    Flashing block 19 (3407872 bytes of 490995712)
    Flashing block 20 (3670016 bytes of 490995712)
    Flashing block 21 (3932160 bytes of 490995712)
    Flashing block 22 (4194304 bytes of 490995712)
    Flashing block 23 (4456448 bytes of 490995712)
    Flashing block 24 (4718592 bytes of 490995712)
    Flashing block 25 (4980736 bytes of 490995712)
    Flashing block 26 (5242880 bytes of 490995712)
    Flashing block 27 (5505024 bytes of 490995712)
    Flashing block 28 (5767168 bytes of 490995712)
    Flashing block 29 (6029312 bytes of 490995712)
    Flashing block 30 (6291456 bytes of 490995712)
  • Hi,

    I've notified the sw team. Their feedback will be posted here.

    Best Regards,
    Yordan
  • Hi, Thxin,

    In your first post, you mentioned :
    [I use the following command to load the uboot to the nor,
    $DSS_SCRIPT_DIR/dss.sh program_evm.js evmk2l-le nand]
    You really meant the command being $DSS_SCRIPT_DIR/dss.sh program_evm.js evmk2l-le "nor", right?

    Let's clarify a few things first. Programming NAND is to program an image of Kernel and filesystem to the NAND, but programming NOR is to program the uboot image to NOR. The U-boot is always booted from SPI NOR, but booting kernel can be one of the following: net (tftp/nfs), ubi (nand), and ramfs(tftp/ramfs). It is controlled by "setenv boot net/ubi/ramfs ".

    To burn the NAND, there are equivalent uboot commands to do it, You may want to "pri env" and understand how it is done. The commands are "run get_ubi_net" and "run burn_ubi". Please note that there is a size limit of NAND. We noticed that the tisdk ubi file is way too large to fit in the NAND. The arago ubi should fit. Therefore, name_ubi in the u-boot environment variable should reflect which file to get.

    Using the u-boot commands to program the NAND, or boot kernel using net or ramfs, you will need to have dhcp and tftp setup. In ProcSDK bin directory, there are scripts provided to help you set up. You may also refer to information on internet for linux tftp server and dhcp server set up. Using net boot, you will also need to set up NFS server.

    Rex