Other Parts Discussed in Thread: FLASHTOOL,
Tool/software: Linux
Good afternoon.
I'm expereiencing some troubles with your product.
First of all - I had to install Windows XP x86 (THIS IS IMPORTANT!) on separate PC for being able just properly connect to my DM3730. It turned out, your OMAP Flashtool (v 4.2) works only with WinXP x86 (HELLO, IT'S 2018!!!).
But the main issue is that after full chip erase and downloading:
- MLO (offset 0x0, ECC 1-bit x-loader/u-boot),
- u-boot.bin (offset 0x8000, NAND ECC),
- uImage (offset 0x280000, NAND ECC)
- rootfs.yaffs2 (I was trying different offsets: 0x780000, 0x1b80000 and 1400000, NAND ECC).
So after thouse manipulations I reboted, set some environments (diff my bootargs with bootargs, generated after run makeyaffsboot command):
OMAP Logic # setenv kernel_location nand-part
OMAP Logic # setenv rootfs_location /dev
OMAP Logic # setenv rootfs_type yaffs
OMAP Logic # setenv partition nand0,0
OMAP Logic # setenv mtddevname x-loader
OMAP Logic # setenv mtddevnum 0
OMAP Logic # setenv filesize 8E9BCC0
OMAP Logic # setenv yaffsimage rootfs.yaffs2
OMAP Logic # saveenv
After reboot x-loader starts successfully, u-boot starts successfully, Linux kernel starts successfully, but then I got:
[ 6.520996] devtmpfs: error mounting -2
[ 6.525268] Freeing init memory: 244K
[ 6.529571] Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
So what's going on? I tried erase each region instead of entire chip, but it gives me error about wrong ECC in debug terminal at u-boot loading stage.
