i.mx28 NAND flash问题（已解决）

FSL_TICS_Rita

回复第 7 楼 于2014-04-15 11:43:23发表:
 我看了这两个帖子，他们描述的内容都是linux内核启动后用ubi烧写文件系统。我的问题是我编译完了imx_ivt_linux.sb，如何烧到flash中，用kobs-ng工具行吗？
 

使用kobs-ng应该是可以的，我没有试过。

twn2000

没用过ubi和MFG工具，ltib如何设置呢？

FSL_TICS_Rita

回复第 12 楼 于2014-04-15 15:54:32发表:
没用过ubi和MFG工具，ltib如何设置呢？ 

如果你用的板子是飞思卡尔官网上的开发板，直接可以用就OK了，如果你是自己design的板子的话，你需要根据你的板子编译mfgtool使用的firmware。关于mgtgool的使用你可以到飞思卡尔官网下载一下它，先了解一下。
链接为：[url=https://www.freescale.co
m/zh-Hans/webapp/sps/site/prod_summary.jsp?code=MCIMX28EVKJ&fpsp=1&tab=Design_Tools_Tab]www.freescale.com/zh-Hans/webapp/sps/site/prod_summary.jsp[/url]。
如图中标示处：

twn2000

 
我按照community.freescale.com/message/289582#289582的步骤修改在SD启动时用ubi工具烧写没有用mfg工具，
                 flash_eraseall /dev/mtd0
                kobs-ng init /boot/imx28_ivt_linux.sb /dev/mtd0
            flash_eraseall /dev/mtd2
ubiattach /dev/ubi_ctrl -m 2
 
ubimkvol /dev/ubi0 -N rootfs0 –m
 
mkdir /mnt/ubifs
 
mount -t ubifs ubi0:rootfs0 /mnt/ubifs
 
tar vjxf rootfs.tar.bz2 -C /mnt/ubifs
            
umount /mnt/ubifs
现在用nand可以启动
Kernel command line: noinitrd console=ttyAM0,115200 ubi.mtd=2 root=ubi0:rootfs0 rootfstype=ubifs rw gpmi
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
。。。。。。。。。。。
。。。。。。。。。。。
Creating 2 MTD partitions on "gpmi-nfc-main":
0x000000000000-0x000001400000 : "gpmi-nfc-0-boot"
0x000001400000-0x000200000000 : "gpmi-nfc-general-use"
Creating 4 MTD partitions on "gpmi-nfc-general-use":
0x000000000000-0x000080000000 : "gpmi-nfc-ubi-0"
0x000080000000-0x000100000000 : "gpmi-nfc-ubi-1"
0x000100000000-0x000180000000 : "gpmi-nfc-ubi-2"
0x000180000000-0x0001fec00000 : "gpmi-nfc-ubi-3"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   524288 bytes (512 KiB)
UBI: logical eraseblock size:    516096 bytes
UBI: smallest flash I/O unit:    4096
UBI: VID header offset:          4096 (aligned 4096)
UBI: data offset:                8192
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "gpmi-nfc-ubi-0"
UBI: MTD device size:            2048 MiB
UBI: number of good PEBs:        4096
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 4096
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 3/1
UBI: image sequence number: 0
UBI: background thread "ubi_bgt0d" started, PID 1037
 ubiblka: unknown partition table
mxs-spi mxs-spi.0: Max possible speed 24000 = 24000000/2 kHz
mxs-spi mxs-spi.0: at 0x80014000 mapped to 0xF0014000, irq=84, bus 1, DMA ver_major 4
vcan: Virtual CAN interface driver
其中mtd2为0x000000000000-0x000080000000 : "gpmi-nfc-ubi-0"
root@freescale ~$ cat /proc/mtd 
dev:    size   erasesize  name
mtd0: 01400000 00080000 "gpmi-nfc-0-boot"
mtd1: 1fec00000 00080000 "gpmi-nfc-general-use"
mtd2: 80000000 00080000 "gpmi-nfc-ubi-0"
mtd3: 80000000 00080000 "gpmi-nfc-ubi-1"
mtd4: 80000000 00080000 "gpmi-nfc-ubi-2"
 
mtd5: 7ec00000 00080000 "gpmi-nfc-ubi-3"
 
root@freescale ~$ df -h
Filesystem                Size      Used Available Use% Mounted on
ubi0:rootfs0              1.8G     82.2M      1.7G   4% /
tmpfs                    60.7M     60.0K     60.6M   0% /dev
shm                      60.7M         0     60.7M   0% /dev/shm
rwfs                    512.0K    512.0K         0 100% /mnt/rwfs
rwfs                    512.0K    512.0K         0 100% /tmp
rwfs                    512.0K    512.0K         0 100% /var
我看imx28的代码好像ubi的大小最大为2G，但是如何使用mt3~mtd5呢？不能每次上电都把他们的内容清空。
回复第 13 楼 于2014-04-15 17:20:10发表:
回复第 12 楼 于2014-04-15 15:54:32发表:
没用过ubi和MFG工具，ltib如何设置呢？ 

如果你用的板子是飞思卡尔官网上的开发板，直接可以用就OK了，如果你是自己design的板子的话，你需要根据你的板子编译mfgtool使用的firmware。关于mgtgool的使用你可以到飞思卡尔官网下载一下它，先了解一下。
链接为：[url=https://www.freescale.co
m/zh-Hans/webapp/sps/site/prod_summary.jsp?code=MCIMX28EVKJ&fpsp=1&tab=Design_Tools_Tab]www.freescale.com/zh-Hans/webapp/sps/site/prod_summary.jsp[/url]。
如图中标示处：

 

 

twn2000

用SD卡启动搞不定，决定用mfg试试，能给我一个用mfg烧写成功时的log文件吗？

FSL_TICS_Rita

回复第 15 楼 于2014-04-22 14:42:52发表:
用SD卡启动搞不定，决定用mfg试试，能给我一个用mfg烧写成功时的log文件吗？ 

你好，我手上现在没有这块板子，所以也没有烧写成功的mfgtool log文件，你先自己烧写一下，如果有问题联系我。

twn2000

如果用mfg烧写的话，只需要把原目录下的updater_ivt.sb替换成我自己编译出来的updater_ivt.sb就可以烧写了吧

FSL_TICS_Rita

回复第 17 楼 于2014-04-22 15:41:16发表:
如果用mfg烧写的话，只需要把原目录下的updater_ivt.sb替换成我自己编译出来的updater_ivt.sb就可以烧写了吧 

你好，updater_ivt.sb为MFGTool使用的firmware你可以替换，也可以不替换。你要烧写你自己编译的images的话，你需要替换files下面的内容。
关于mfgtool的使用，建议你先什么都不用改，使用mfgtool上自带的images，先烧写一下，并通过串口观察烧写过程，了解了解。然后再烧写你自己编译的。

twn2000

1 mfg下载后，不修改任何文件直接烧
  串口显示：
MXS RTC driver v1.0 hardware v2.3.0
mxs-rtc mxs-rtc.0: rtc core: registered mxs-rtc as rtc0
mxs-mmc: MXS SSP Controller MMC Interface driver
mxs-kbd mxs-kbd.0: Invalid button: raw = 1395, normalized = 1424, vddio = 3675
mxs-kbd mxs-kbd.0: Invalid button: raw = 1415, normalized = 1452, vddio = 3657
__mxs_reset_block(f0010000): timeout when resetting
mxs-mmc mxs-mmc.0: mmc0: MXS SSP MMC DMAIRQ 82 ERRIRQ 96
mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 00:00:10 UTC (10)
mxs-kbd mxs-kbd.0: Invalid button: raw = 1437, normalized = 1464, vddio = 3683
Freeing init memory: 124K
Starting UTP
disable turn off display
uuc 0.4 [built Dec 26 2010 23:10:08]
UTP: Waiting for device to appear
utp_mk_devnode: creating node '/dev/utp' with 10+222
cpu_id is 28
mmc0: new high speed SDHC card at address aaaa
mmcblk0: mmc0:aaaa SU04G 3.69 GiB
mmcblk0: p1 p2 p3
g_file_storage gadget: high speed config #1
UTP: received command 'mknod clautp_exec: exit with status -22
ss/mtd,mtd0,/dev/mtd0'
class = 'class/mtd'
item = 'mtd0'
node = /dev/mtd0
type = (null)
UTP: running utp_mk_devnode(class/mtd,mtd0,/dev/mtd0,0x2000)
UTP: sending Non-success
mfglog 文件显示：
Tuesday, April 22, 2014 16:00:35
1 - Panel A Start processing Singlechip NAND .
Panel A Start  type="boot" body="Recovery" file="updater_ivt.sb" timeout="60" onError="" text="Booting Update Firmware.".
1 - Panel A Finished  type="boot" body="Recovery" file="updater_ivt.sb" timeout="60" onError="" text="Booting Update Firmware." SUCCESS code=0x0.
Panel A Start  type="find" body="Updater" file="" timeout="180" onError="" text="".
Panel A UtpUpdate Event: DeviceRemoval Msg: (null) DevState: Disconnected OpState: WAITING_FOR_DEVICE
Panel A UtpUpdate Event: VolumeArrival Msg: (null) DevState: Updater OpState: WAITING_FOR_DEVICE
1 - Panel A Finished  type="find" body="Updater" file="" timeout="180" onError="" text="" SUCCESS code=0x0.
Panel A Start  type="push" body="mknod class/mtd,mtd0,/dev/mtd0" file="" timeout="10" onError="" text="".
1 - Panel A Finished  type="push" body="mknod class/mtd,mtd0,/dev/mtd0" file="" timeout="10" onError="" text="" FAIL code=0xffffffea.
Panel A: Command is not supported by device.,failed to run command: type="push" body="mknod class/mtd,mtd0,/dev/mtd0" file="" timeout="10" onError="" text=""  
2 - Panel A Finished processing Singlechip NAND  : FAIL code=-22.
Panel A: Reason is unknown,

twn2000

用我编译出来的updater_ivt.sb
串口显示：
g_file_storage gadget: Number of LUNs=1
fsl-usb2-udc: bind to driver g_file_storage
mice: PS/2 mouse device common for all mice
input: mxs-kbd as /devices/platform/mxs-kbd.0/input/input0
input: MXS touchscreen as /devices/virtual/input/input1
MXS RTC driver v1.0 hardware v2.3.0
mxs-rtc mxs-rtc.0: rtc core: registered mxs-rtc as rtc0
mxs-mmc: MXS SSP Controller MMC Interface driver
mxs-mmc mxs-mmc.0: mmc0: MXS SSP MMC DMAIRQ 82 ERRIRQ 96
regulator_init_complete: incomplete constraints, leaving vbus5v on
mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 00:00:19 UTC (19)
Freeing init memory: 124K
init started: BusyBox v1.15.0 ()
starting pid 941, tty '': '/etc/rc.d/rcS'
Mounting /proc and /sys
Setting the hostname to freescale
Mounting filesystems
mount: mounting shm on /dev/shm failed: No such file or directory
mount: mounting rwfs on /mnt/rwfs failed: Invalid argument
mmc0: new high speed SDHC card at address aaaa
mmcblk0: mmc0:aaaa SU04G 3.69 GiB
mmcblk0: p1 p2 p3
mount: mounting usbfs on /proc/bus/usb failed: No such file or directory
Starting inetd:
starting pid 976, tty '': '/sbin/getty -L ttyAM0 115200 vt100'
g_file_storage gadget: high speed config #1
process '/sbin/getty -L ttyAM0 115200 vt100' (pid 976) exited. Scheduling for restart.
starting pid 977, tty '': '/sbin/getty -L ttyAM0 115200 vt100'
process '/sbin/getty -L ttyAM0 115200 vt100' (pid 977) exited. Scheduling for restart.
starting pid 978, tty '': '/sbin/getty -L ttyAM0 115200 vt100'
process '/sbin/getty -L ttyAM0 115200 vt100' (pid 978) exited. Scheduling for restart.
starting pid 979, tty '': '/sbin/getty -L ttyAM0 115200 vt100'
process '/sbin/getty -L ttyAM0 115200 vt100' (pid 979) exited. Scheduling for restart.
starting pid 980, tty '': '/sbin/getty -L ttyAM0 115200 vt100'
process '/sbin/getty -L ttyAM0 115200 vt100' (pid 980) exited. Scheduling for restart.
starting pid 981, tty '': '/sbin/getty -L ttyAM0 115200 vt100'
process '/sbin/getty -L ttyAM0 115200 vt100' (pid 981) exited. Scheduling for restart.
starting pid 982, tty '': '/sbin/getty -L ttyAM0 115200 vt100'
process '/sbin/getty -L ttyAM0 115200 vt100' (pid 982) exited. Scheduling for restart.
starting pid 983, tty '': '/sbin/getty -L ttyAM0 115200 vt100'

MTGTOOL log显示
Tuesday, April 22, 2014 16:06:21
2 - Panel A Start processing Singlechip NAND .
Panel A Start  type="boot" body="Recovery" file="updater_ivt.sb" timeout="60" onError="" text="Booting Update Firmware.".
2 - Panel A Finished  type="boot" body="Recovery" file="updater_ivt.sb" timeout="60" onError="" text="Booting Update Firmware." SUCCESS code=0x0.
Panel A Start  type="find" body="Updater" file="" timeout="180" onError="" text="".
Panel A UtpUpdate Event: DeviceRemoval Msg: (null) DevState: Disconnected OpState: WAITING_FOR_DEVICE
Panel A UtpUpdate Event: VolumeArrival Msg: (null) DevState: Updater OpState: WAITING_FOR_DEVICE
2 - Panel A Finished  type="find" body="Updater" file="" timeout="180" onError="" text="" SUCCESS code=0x0.
Panel A Start  type="push" body="$ flash_eraseall /dev/mtd0" file="" timeout="10" onError="" text="Erasing rootfs partition 0".