[UPDATE] DOCBoot support for NFTL-based DOC2000
zerivirgo at infocell-its.com
Tue Apr 5 08:00:21 EDT 2005
Dan Brown wrote:
> A recent modification to support variable-sized
> ecc_calc and ecc_code arrays didn't take into account the possibility of
> NULL oobsel. Fixed in CVS.
> Let me know if DOCBoot finally works for you, please!
OK... diskonchip probing was fine with a fresh chip. Here's what I've
Built a kernel with MTD etc linked in (temporarily including hard-disk
stuff) and verified booting it from the hard-disk (obviously the
diskonchip driver doesn't show the firmware partition, but that's ok).
Used M-Systems dformat (from tffs_5.1.4_DOS_TOOLS.zip) to resize the
A:\> DFORMAT /WIN:D000 /BDKL0:2M
Rebooted into a kernel with modules and ran
# modprobe diskonchip show_firmware_partition=1
# cat /proc/mtd
dev: size erasesize name
mtd0: 04000000 00004000 "DiskOnChip 2000 (NFTL Model)"
mtd1: 00208000 00004000 " DiskOnChip Firmware / Media Header partition"
mtd2: 03df8000 00004000 " DiskOnChip BDTL partition"
Edited docboot/cmdline to
root=/dev/mtdblock1 rootfstype=jffs2 ro
Uncommented "#define OLD_DOC2K" in doc_bootstub.h
Copied in the bzImage I'd tested booting from hard-disk.
# flash_eraseall /dev/mtd1
# nandwrite -o /dev/mtd1 doc_spl
# flash_eraseall -j /dev/mtd2
Tested mounting and unmounting /dev/mtdblock2 which seemed OK. (My
cmdline above assumes that this will show as /dev/mtdblock1 when the
linked-in driver is loaded.)
Rebooted and disabled/removed all other boot devices. As the BIOS gets
going, I see "Installing DOCBoot." then a "System Configurations" page with
Verifying DMI Pool Data .........
Loading kernel... _
where the "_" is a flashing cursor. The keyboard is unresponsive and
nothing further happens :(
By the way, I have not yet copied any files to the jffs2 filesystem on
/dev/mtdblock1 except a small text file to test the filesystem.
Any ideas? I'd really like to get this going.
More information about the linux-mtd