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.

MCSDK: Linux did not boot

Guru 24520 points

Hi community member.

Please provide your advice for my problem.

[Problem]

Linux did not boot when using ubifs on NAND by using the following board and command.

* I would like to boot by using the ubifs and Kernel which put on NAND.

[Evaluation board]

   XTCIEVMK2X Rev2.0

[Command.1]

env default –f –a
setenv boot ubi
setenv mtdparts 'mtdparts=davinci_nand.0:1024k(bootloader),512k(params)ro,522752k(ubifs)'
boot

Before booting, I had done the following command in order to program the fs and kernel to NAND flash.

[Command.2]

export DSS_SCRIPT_DIR=~/ti/ccsv5/ccs_base/scripting/bin
export PROGRAM_EVM_TARGET_CONFIG_FILE =configs/evm667xl/my_evm667xl.ccxml
[MCSDK]/tools/program_evm>$DSS_SCRIPT_DIR/dss.sh program_evm.js evmk2h-le format-nand
/program_evm>$DSS_SCRIPT_DIR/dss.sh program_evm.js evmk2h-le

And I burned the latest F/W of BMC and USC to K2H board.

If  I tried the DHCP or tftpboot boot, I could boot the linux.

So, there is not any problem for  the network setting.

If you have any questions, please let me know.

Best regards,

Kaka

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

Log:

TCI6638 EVM # boot
Unmounting UBIFS volume boot!
UBI: mtd1 is detached from ubi0
Creating 1 MTD partitions on "nand0":
0x000000180000-0x000020000000 : "mtd=2"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=2"
UBI: MTD device size:            510 MiB
UBI: number of good PEBs:        4079
UBI: number of bad PEBs:         5
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     3
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 4079
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 1/0
UBIFS: mounted UBI device 0, volume 0, name "boot"
UBIFS: mounted read-only
UBIFS: file system size:   5713920 bytes (5580 KiB, 5 MiB, 45 LEBs)
UBIFS: journal size:       1142785 bytes (1116 KiB, 1 MiB, 9 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: LZO
UBIFS: reserved for root:  0 bytes (0 KiB)
Loading file 'uImage-k2hk-evm.dtb' to addr 0x87000000 with size 57857 (0x0000e201)...
Done
Loading file 'skern-keystone-evm.bin' to addr 0x0c5f0000 with size 45056 (0x0000b000)...
Done
Loading file 'uImage-keystone-evm.bin' to addr 0x88000000 with size 3990416 (0x003ce390)...
UBI error: ubi_io_read: error -74 while reading 4144 bytes from PEB 21:82832, read 4144 bytes
UBIFS error (pid 0): try_read_node: cannot read node type 1 from LEB 19:78736, error -74
UBI error: ubi_io_read: error -74 while reading 4144 bytes from PEB 21:82832, read 4144 bytes
UBIFS error (pid 0): ubifs_read_node: bad node type (248 but expected 1)
UBIFS error (pid 0): ubifs_read_node: bad node at LEB 19:78736
UBIFS error (pid 0): do_readpage: cannot read page 287 of inode 67, error -22
Error reading file 'uImage-keystone-evm.bin'
uImage-keystone-evm.bin not found!

  • Hi, Kato,

    Did you notice if the NAND programming was successful? Please note the difference for programming the NAND between Rev 2.0 and Rev 1.0 EVM. Try the alternative way to program the NAND, and see if it works.

    Rex

  • Hi Rex,


    Thank you for response.

    In compliance with your advice, I re-performed the NAND programming by using u-boot command.

    As a result, I could confirm that Linux can boot by using ubifs.

    Best regards.

    Kaka