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.
Hello
i programmed my filesytem.tar.gz in NAND but when i boot from NAND AM3352:
U-Boot# fatload mmc 0 0x84000000 targetNFS74M140623.tar.gz
U-Boot# nand write 0x84000000 0x00600000 0x20D1494
But i can't mount the filesystem :
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
[ 2.631317] Please append a correct "root=" boot option; here are the available partitions:
[ 2.639892] Kernel panic - not syncing: VFS: Unable to mount root fs on unkno
wn-block(0,0)
[ 2.648315] Backtrace:
[ 2.650848] [<c0017978>] (dump_backtrace+0x0/0x110) from [<c0421438>] (dump_s
tack+0x18/0x1c)
1)Have you any idea where the problem is ?
2)is there in linux configuration to change ?
My env variable ubi is : (NAND of 2048 bytes / page) : nandroot=ubi0:rootfs rw ubi.mtd=7,2048
regards
Hi,
You have to write a NAND flash file system (most commonly UBIFS) to the NAND flash, not a tar.gz archive as this won't work.
You can read all about it here: http://processors.wiki.ti.com/index.php/UBIFS_Support
Best regards,
Miroslav
Hello
thanks for the link
I have the MT29F1G08ABAEAW NAND, with 2048 page size so i did :
mkfs.ubifs /home/pengwyn/ti-sdk-am335x-evm-05.06.00.00/targetNFS –F -m 2048 -e 129024 -c 2047 -o ubifs.img
the result is a file of 1.7Mb for a file system of 74,6Mb.
1° Is it normal ?
2° I don't understand what i should put in the -e and -c parameters, can you help me ?
regards
Hello
when i do the mtdinfo on linux i got the following answer
mtdinfo -a
Count of MTD devices: 0
is it normal ? can i have a ubifs system however ?
regards
Hello
I still have trouble !!! can you help me please?
For the MT29F1G08ABAEAW NAND :
page=2048b
block erase=128K
total size=1G
I did on linux :
sudo mkfs.ubifs /home/pengwyn/ti-sdk-am335x-evm-05.06.00.00/targetNFS –F –v -m 2048 -e 126976 -c 8406 -o ubifs.img
sudo ubinize -o ubi.img -m 2048 -p 128KiB -s 2048 ubinize.cfg
I did on target :
mw.b 0x84000000 0xFF 0x500000
mmc rescan
fatload mmc 0 0x84000000 ubi.img
nand erase 0x00600000 0x500000
nand write 0x84000000 0x00600000 0x200000
setenv bootargs 'console=ttyO0,115200n8 noinitrd ip=off mem=1024M rootwait=1 rw ubi.mtd=7,2048 rootfstype=ubifs root=ubi0:rootfs init=/init'
boot
It still can't be mounted :
2.623931] VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
[ 2.631134] Please append a correct "root=" boot option; here are the availab
le partitions:
[ 2.639709] Kernel panic - not syncing: VFS: Unable to mount root fs on unkno
wn-block(0,0)
[ 2.648132] Backtrace:
[ 2.650665] [<c0017978>] (dump_backtrace+0x0/0x110) from [<c0421438>] (dump_s
regards
Hello
can my problem be related to this error ?
root@am335x-evm:~# ubiattach /dev/ubi_ctrl -m 7 -O 2048
ubiattach: error!: cannot attach mtd7
error 19 (No such device)
regards
Trichet,
I have provided an answer to some of your questions in your Linux forum threads.
Regarding the missing mtd devices - Please check if you have enabled MTD support in the linux kernel. Also if you have the appropriate mtd_partitions table inside your board config file.
Best regards,
Miroslav
Hi,
I am also facing the error in my am335x custom board. But i am using 1GB RAM. I got the below error.
root@am335x-evm:/media/card# ubiattach /dev/ubi_ctrl -m 7 -O 4096
ubiattach: error!: cannot attach mtd7
error 28 (No space left on device)
Did you solve the issue, Please help me what is the problem?. I am referring ti sdk6 with Linux 3.2.
Regards,
Lofna