![]() I then write the UBI image to the flash with the following commands (in U-Boot): nand erase 0x140000 0xfec0000 Mkfs.ubifs -e 124KiB -c 132 -m 2KiB -r nfsroot/www/upload/files data.img I added those parameters based on this answer.īoth UBI partitions have been make with the following commands: mkfs.ubifs -e 124KiB -c 132 -m 2KiB -r nfsroot/ root.img The PEB is indeed 128KB ( 0x2000) and the page size is 2048B ( 0x800). The UBI image was created with ubinize and the following configuration: Īnd this command (the sama5-ubinize.cfg is the above configuration) ubinize -o ubi.img -p 128KiB -m 2KiB sama5-ubinize.cfg With printenv mtdparts, I get: mtdparts=mtdparts=atmel_nand:256k(bootstrap)ro,512k(uboot)ro,256k(env)ro,256k(envbackup)ro,128k(dtb),5M(kernel),16M(rootfs),16M(datafs)Īnd printenv mtdids mtdids=nand0=atmel_nand In U-Boot, the partitions are defined by mtdparts: device nand0, # parts = 8Īctive partition: nand0,0 - (bootstrap) 0x00040000 0x00000000 (to see my actual questions, go to the end of the question) ![]() They ask me to put the DTB, the kernel, the root filesystem and a data filesystem in a UBI image to be written to the flash but I cannot access the UBI partitions once I flashed it (the access fails with error code 22, or -22 in an embedded Linux environment). ![]() I am following Bootlin's embedded Linux training which aims to put an embedded Linux system on an Atmel SAMA5D4 Xplained board ( theory slides, practical lab instructions) and I am stuck a putting the whole system on the NAND flash.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |