topic Re: IMX6ULL 挂载spi-norflash w25q128失败 in i.MX Processors

IMX6ULL 挂载spi-norflash w25q128失败

牛康 — Tue, 02 Jul 2024 03:52:57 GMT

1.驱动匹配成功
[ 1.510560] m25p80 spi0.0: found w25q128, expected m25p80
[ 1.516150] m25p80 spi0.0: w25q128 (16384 Kbytes)
[ 1.523668] spi_imx 2008000.ecspi: probed

2.在/dev能找到mtd设备
ls /dev/mtd*
/dev/mtd0 /dev/mtd0ro /dev/mtdblock0
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk1rpmb 179:24 0 512K 0 disk
mmcblk1boot0 179:8 0 4M 1 disk
mmcblk1boot1 179:16 0 4M 1 disk
mmcblk1 179:0 0 7.3G 0 disk
├─mmcblk1p1 179:1 0 128M 0 part /run/media/mmcblk1p1
└─mmcblk1p2 179:2 0 7.2G 0 part /
mtdblock0 31:0 0 16M 0 disk

3.在挂载的时候，提示以下错误信息

[ 765.604895] FAT-fs (mtdblock0): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[ 765.619877] FAT-fs (mtdblock0): invalid media value (0x06)
[ 765.626234] FAT-fs (mtdblock0): Can't find a valid FAT filesystem
mount: wrong fs type, bad option, bad superblock on /dev/mtdblock0,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.

Re: IMX6ULL 挂载spi-norflash w25q128失败

JorgeCas — Fri, 05 Jul 2024 15:05:46 GMT

Hello,

It seems that the problem is because you are trying to mount a device with a file system other than fat32.

Could you please share the command you used to mount the device?

Best regards.

回复： IMX6ULL 挂载spi-norflash w25q128失败

牛康 — Tue, 09 Jul 2024 10:06:18 GMT

1.格式化spi-norflash w25q128
mkfs.vfat /dev/mtdblock0
mkfs.fat 3.0.28 (2015-05-16)
unable to get drive geometry, using default 255/63

2.挂载flash模块
mount -t vfat /dev/mtdblock0 /home/root/w25q128

[ 161.569958] FAT-fs (mtdblock0): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[ 161.582601] FAT-fs (mtdblock0): bogus logical sector size 65535
[ 161.591027] FAT-fs (mtdblock0): Can't find a valid FAT filesystem
mount: wrong fs type, bad option, bad superblock on /dev/mtdblock0,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.