i.MX ProcessorsのトピックRe: NAND, flashing bootloader(u-boot.bin) with kobs-ng tool error.

NAND, flashing bootloader(u-boot.bin) with kobs-ng tool error.

YamilGarcia — Tue, 17 Sep 2013 14:13:10 GMT

I'm working with a custom board based in sabrelite platform, basically it is a sabrelite with NAND support.

When I try to flash the bootloader(u-boot.bin) with kobs-ng tool, it always prompt me an error.

The kernel GPMI driver find the NAND device successfully and partitions are created correctly as shown below:

Kernel GPMI driver output:

ONFI flash detected

ONFI param page 0 valid

NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron MT29F8G08ADADAH4)

gpmi-nand imx6q-gpmi-nand.0: enable asynchronous EDO mode 5

3 cmdlinepart partitions found on MTD device gpmi-nand

Creating 3 MTD partitions on "gpmi-nand":

0x000000000000-0x000000100000 : "boot"

0x000000100000-0x000000500000 : "kernel"

0x000000500000-0x000040000000 : "rootfs"

GPMI NAND driver registered. (IMX)

mtd partitions:

root@freescale /$ cat /proc/mtd

dev: size erasesize name

mtd0: 00100000 00020000 "boot"

mtd1: 00400000 00020000 "kernel"

mtd2: 3fb00000 00020000 "rootfs"

kobs-ng output:

root@freescale /$ kobs-ng init -v u-boot.bin

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

u-boot.bin: verifying using key '00000000000000000000000000000000'

u-boot.bin: is a valid bootstream for key '00000000000000000000000000000000'

mtd: opening: "/dev/mtd0"

NFC geometry :

ECC Strength : 8

Page Size in Bytes : 2112

Metadata size : 10

ECC Chunk Size in byte : 512

ECC Chunk count : 4

Block Mark Byte Offset : 1999

Block Mark Bit Offset : 0

====================================================

mtd: opened '/dev/mtd0' - '(null)'

mtd: bootstream too large

mtd_init failed!

Can someone give a hint on this, please?

Thanks in advance.

Re: NAND, flashing bootloader(u-boot.bin) with kobs-ng tool error.

GraceH — Thu, 26 Sep 2013 03:39:41 GMT

Hi Yamil Garcia,

What is the size of your u-boot.bin? mtd0 size is small and your u-boot.bin can't fit in.

The boot area will contain both search areas and two copies of the boot stream.

Grace

Re: NAND, flashing bootloader(u-boot.bin) with kobs-ng tool error.

YixingKong — Mon, 30 Sep 2013 02:52:16 GMT

Yamil, please respond Grace's question. Yur discussion may be closed if no repy in next two days.

Thanks,

Yixing

Re: NAND, flashing bootloader(u-boot.bin) with kobs-ng tool error.

YamilGarcia — Sat, 30 Nov 2013 16:37:14 GMT

Yes, you were right, the problem was the size of partition.

I already fixed it and it is working fine. I was able to flash u-boot in NAND.

Thanks to all in the community for their support.

Re: NAND, flashing bootloader(u-boot.bin) with kobs-ng tool error.

Raana — Mon, 14 Apr 2014 11:48:49 GMT

Hi Yixing,

I am also facing the same issue but some what different.

Mine is,

/mnt/mmcblk1p1/u-boot.bin: verifying using key '00000000000000000000000000000000'

/mnt/mmcblk1p1/u-boot.bin: is a valid bootstream for key '00000000000000000000000000000000'

mtd: opening: "/dev/mtd0"

mtd: device /dev/mtd0 can't ioctl MEMGETOOBSEL: -1

Unable to open mtd device(s)

But at the same time I am able to save the environment and boot the uImage from NAND.

Herewith, I attached the full log file of this issue.