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.

There are some errors when using ubifs filesystem on Dm8148.

 Heelo all:

  I use EZSDK 5.05 on DM8148,and making ubifs according to the http://processors.wiki.ti.com/index.php/UBIFS_Support  .But  :

1.When making ubifs:

ubiformat /dev/mtd9 -f ubi.img -s 2048 -O 2048

then turn the followings erros:

ubiformat: mtd9 (nand), size 839385088 bytes (800.5 MiB), 3202 eraseblocks of 262144 bytes

(256.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 3201 -- 100 % complete 
ubiformat: 3202 eraseblocks are supposedly empty
ubiformat: flashing eraseblock 194 -- 21 % complete  libmtd: error!: cannot write 262144

bytes to mtd9 (eraseblock 194, offset 0)
        error 5 (Input/output error)
ubiformat: error!: cannot write eraseblock 194
           error 5 (Input/output error)
libmtd: run torture test for PEB 194
libmtd: PEB 194 passed torture test, do not mark it a bad
ubiformat: mark it as bad? Continue (yes/no) yesd
ubiformat: marking block 194 bad
ubiformat: flashing eraseblock 239 -- 26 % complete  libmtd: error!: cannot write 262144

bytes to mtd9 (eraseblock 239, offset 0)
        error 5 (Input/output error)
ubiformat: error!: cannot write eraseblock 239
           error 5 (Input/output error)
libmtd: run torture test for PEB 239
libmtd: PEB 239 passed torture test, do not mark it a bad
ubiformat: mark it as bad? Continue (yes/no) yes
ubiformat: marking block 239 bad
ubiformat: flashing eraseblock 915 -- 100 % complete  ubiformat: error!: eof reached; 262144

bytes remaining
ubiformat: error!: failed to read eraseblock 913 from "ubi.img"
           error 5 (Input/output error)

 

 

2.After finishing.Reboot the system,the filesystem can run.

But sometimes,will turn out the followings errors when getting into some dir.

UBIFS error (pid 1408): ubifs_read_node: bad node type (255 but expcted 2)
UBIFS error (pid 1408): ubifs_read_node: bad node at LEB 865:204312, LEB mapping status 0
UBIFS error (pid 1408): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 1408): ubifs_read_node: bad node at LEB 865:204312, LEB mapping status 0
UBIFS error (pid 1408): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 1408): ubifs_read_node: bad node at LEB 865:204312, LEB mapping status 0
UBIFS error (pid 1408): ubifs_read_node: bad node type (255 but expected 2)
UBIFS error (pid 1408): ubifs_read_node: bad node at LEB 865:204312, LEB mapping status 0
UBIFS error (pid 1408): ubifs_read_node: bad node type (255 but expected 2)

 

  3.Wheather there exist some bugs about  BHC8 on  mtd driver?and you refer to the followings files:

arch/arm/mach-omap2/board-dm8148evm.c or your corresponding board file. 
arch/arm/mach-omap2/board-flash.c
arch/arm/mach-omap2/gpmc.c
drivers/mtd/nand/nand_base.c
drivers/mtd/nand/omap2.c

I use 5.05.00.11 ,so wheather there some patchs for these files?

Thanks very much.

                                                                    zhichao.