i.MX ProcessorsのトピックRe: Mfg-tools burning nandflash failure

Mfg-tools burning nandflash failure

zhangbin_eos — Fri, 08 Mar 2019 06:28:38 GMT

I refer to How-To use NAND boot on i.MX6UL EVK board and solder U302 NAND FLASH on EVK board.

NAND FLASH is MT29F32G08CBADBWP-12IT:D (Same as on the schematic )

I downloaded L4.1.15_2.0.0-ga_mfg-tools.tar.gz,and run the `mfgtool2-yocto-mx-evk-nand.vbs`,

Result:

U-Boot 2016.03-imx_v2016.03_4.1.15_2.0.0_ga+g0ec2a01 (Sep 16 2016 - 18:36:22 -0500)
CPU: Freescale i.MX6UL rev1.1 528 MHz (running at 396 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 43C
Reset cause: POR
Board: MX6UL 14x14 EVK
I2C: ready
DRAM: 512 MiB
force_idle_bus: sda=1 scl=0 sda.gp=0x1d scl.gp=0x1c
MMC: FSL_SDHC: 0, FSL_SDHC: 1
SF: Unsupported flash IDs: manuf ff, jedec ffff, ext_jedec ffff
*** Warning - spi_flash_probe() failed, using default environment
Display: TFT43AB (480x272)
Video: 480x272x24
In: serial
Out: serial
Err: serial
Net: FEC1
Boot from USB for mfgtools
Use default environment for mfgtools
Run bootcmd_mfg: run mfgtool_args;bootz ${loadaddr} ${initrd_addr} ${fdt_addr};
Hit any key to stop autoboot: 0
Kernel image @ 0x80800000 [ 0x000000 - 0x554130 ]
## Loading init Ramdisk from Legacy Image at 83800000 ...
Image Name: fsl-image-mfgtool-initramfs-imx6
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 8591032 Bytes = 8.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8300beef
Modify /soc/aips-bus@02000000/bee@02044000:status disabled
ft_system_setup for mx6
.........
brd: module loaded
loop: module loaded
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0x44
nand: Micron MT29F32G08CBADBWP
nand: 4096 MiB, MLC, erase size: 2048 KiB, page size: 8192, OOB size: 744
gpmi-nand 1806000.gpmi-nand: enable the asynchronous EDO mode 5
Bad block table found at page 524032, version 0x01
Bad block table found at page 523776, version 0x01
nand_read_bbt: bad block at 0x00000b400000
nand_read_bbt: bad block at 0x00000b600000
gpmi-nand 1806000.gpmi-nand: driver registered.
20b4000.ethernet supply phy not found, using dummy regulator
....
UTP: received command '$ mount -t debugfs debugfs /sys/kernel/debug'
UTP: executing "mount -t debugfs debugfs /sys/kernel/debug"
UTP: sending Success to kernel for command $ mount -t debugfs debugfs /sys/kernel/debug.
utp_poll: pass returned.
UTP: received command '$ flash_erase /dev/mtd0 0 0'
UTP: executing "flash_erase /dev/mtd0 0 0"
Erasing 2048 Kibyte @ b200000 -- 4 % complete flash_erase: Skipping bad block at 0b400000
flash_erase: Skipping bad block at 0b600000
Erasing 2048 Kibyte @ 65800000 -- 39 % random: nonblocking pool is initialized
Erasing 2048 Kibyte @ ff600000 -- 99 % complete flash_erase: Skipping bad block at ff800000
flash_erase: Skipping bad block at ffa00000
flash_erase: Skipping bad block at ffc00000
flash_erase: Skipping bad block at ffe00000
Erasing 2048 Kibyte @ ffe00000 -- 100 % complete
UTP: sending Success to kernel for command $ flash_erase /dev/mtd0 0 0.
utp_poll: pass returned.
UTP: received command 'send'
UTP: sending Success to kernel for command send.
UTP: received command '$ kobs-ng init -x -v --chip_0_device_path=/dev/mtd0 $FILE'
UTP: executing "kobs-ng init -x -v --chip_0_device_path=/dev/mtd0 $FILE"
MTD CONFIG:
chip_0_device_path = "/dev/mtd0"
chip_1_device_path = "(null)"
search_exponent = 2
data_setup_time = 80
data_hold_time = 60
address_setup_time = 25
data_sample_time = 6
row_address_size = 3
column_address_size = 2
read_command_code1 = 0
read_command_code2 = 48
boot_stream_major_version = 1
boot_stream_minor_version = 0
boot_stream_sub_version = 0
ncb_version = 3
boot_stream_1_address = 0
boot_stream_2_address = 0
-- We add the 1k-padding to the uboot.
.tmp_kobs_ng: verifying using key '00000000000000000000000000000000'
.tmp_kobs_ng: is a valid bootstream for key '00000000000000000000000000000000'
mtd: use new bch layout raw access mode
mtd: opening: "/dev/mtd0"
NFC geometry :
ECC Strength : 40
Page Size in Bytes : 8762
Metadata size : 10
ECC Chunk Size in byte : 1024
ECC Chunk count : 8
Block Mark Byte Offset : 7692
Block Mark Bit Offset : 0
====================================================
mtd: opened '/dev/mtd0' - '(null)'
mtd: mtd size too small
mtd_init failed!
UTP: sending Non-success to kernel for command $ kobs-ng init -x -v --chip_0_device_path=/dev/mtd0 $FILE.
utp_poll: exit with status 1280

Can't mfgtool2-yocto-mx-evk-nand.vbs in L4.1.15_2.0.0-ga_mfg-tools be used directly?

Re: Mfg-tools burning nandflash failure

igorpadykov — Fri, 08 Mar 2019 10:09:35 GMT

Hi 斌张

seems mentioned link produced files for L3.14.38

linux-2.6-imx.git - Freescale i.MX Linux Tree

uboot-imx.git - Freescale i.MX u-boot Tree

so one can compare mx6ul_14x14_evk_nand_defconfig, mx6ul_14x14_evk.h

with original ones and make the same changes for L4.1.15_2.0

mx6ul_14x14_evk.h\configs\include - uboot-imx - i.MX U-Boot

linux-imx - i.MX Linux kernel

Then perform steps described as "Software Modification" for L4.1.15_2.0,

so new u-boot-imx6ulevk_nand.imx, zImage-imx6ul-14x14-evk-gpmi-weim.dtb

(for L4.1.15_2.0) were generated and copied to MFGTOOL\Profiles..

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: Mfg-tools burning nandflash failure

zhangbin_eos — Fri, 08 Mar 2019 10:09:43 GMT

I replace the Profiles\Linux\OS Firmware\firmware\u-boot-imx6ul14x14evk_nand.imx, then mfg-tools can burn the uboot and kernel.

But burnning the rootfs to NAND is faile

UTP: received command '$ flash_erase /dev/mtd3 0 0'
UTP: executing "flash_erase /dev/mtd3 0 0"
flash_erase: error!: /dev/mtd3
error 13 (Permission denied)
UTP: sending Non-success to kernel for command $ flash_erase /dev/mtd3 0 0.
utp_poll: exit with status 65280

and I change the mfgtool2-yocto-mx-evk-nand.vbs : ""part_rootfs=4"" , no better

Re: Mfg-tools burning nandflash failure

zhangbin_eos — Fri, 08 Mar 2019 10:16:19 GMT

Bad block table found at page 524032, version 0x01
Bad block table found at page 523776, version 0x01
nand_read_bbt: bad block at 0x00000b400000
nand_read_bbt: bad block at 0x00000b600000
5 cmdlinepart partitions found on MTD device gpmi-nand
Creating 5 MTD partitions on "gpmi-nand":
0x000000000000-0x000004000000 : "boot"
0x000004000000-0x000005000000 : "kernel"
0x000005000000-0x000006000000 : "dtb"
0x000006000000-0x000006100000 : "misc"
mtd: partition "misc" doesn't end on an erase block -- force read-only
0x000006100000-0x000100000000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
gpmi-nand 1806000.gpmi-nand: driver registered.

I found these msg. and in the uboot env :

mtdparts=gpmi-nand:64m(boot),16m(kernel),16m(dtb),1m(misc),-(rootfs)

Partitions should be integers of erasable block size(分区应该是可擦出块大小的整数倍)

Re: Mfg-tools burning nandflash failure

zhangbin_eos — Fri, 08 Mar 2019 10:19:40 GMT

Hi,igor

Thank you very much. I'm going to screenshot to make sure I don't forget it.

Best regards