Skip to contentSkip to conversation

DiskOnChip 2000 and Millenium support in GRUB bootloader

DISCUSSION Mark Meade 2 participants 2 messages Mar 11, 2002 – Mar 12, 2002 Memory technology devices (MTD)

lore
Share & tools
lore

Mark Meade

author
#0 lore raw
Quoted 14 lines · Ilguiz Latypov

I was able to test the grub_firmware file produced by the patch on a 64M DoC 2000. Yes, I could get to the GRUB prompt and play with "root (dc0," command. GRUB can access the configuration file and the kernel image stored in ext2 partition. The partition was created on top of NFTL block device layer.

Mark Meade has offered few improvements to the patch. I think there are 2 latest changes that may be of interest to you:

a) New configuration option --enable-diskonchip-biosnetboot will make GRUB firmware to attach itself to INT 18h (BIOS network boot) rather than to INT 19h (BIOS bootstrap loader). If you try that option, enable network boot in BIOS as well.

Quoted 6 lines

b) The DoC SlowIO register is no longer read when fetching the data from the flash memory.

I updated the patch. It is available at

http://savannah.gnu.org/patch/?func=detailpatch&patch_id=164&group_id=68

Ilguiz,

I have been testing your latest patch with the DoC Millennium. I'm able to get a GRUB prompt only after forcing the 512-byte-page code (doc_stage1b.S) to address 0x100.

Normally, it looks like the 256-byte/page code ends up at 0x100, and the 512-byte at 0x200. With the DoC 2000, this insures that the proper code (loaded by the IPL) ends up at 0x100.

Since the Millennium is XIP, jumping to 0x100 ends up running 256-byte-page code, which doesn't work in this case.

You mentioned that there are DoC Millennium parts based on 256-byte-page chips -- so my hack to force the 512-byte code to 0x100 will not work correctly for all Millennium parts.

Any thoughts or ideas?

Thanks,

Mark

#1 lore raw

Mark,

1. Thanks for the latest patch to stage2/bdev_diskonchip.c that rectifies the chip identification.

2. As for the device page size issue in Millennium IPL, the data sheets and application notes at

http://www.m-sys.com/content/Products/ShowInformation.asp?PID=1&Code=1

inform that DoC Millennium and DoC Millennium Plus feature a Download Engine which takes care of copying the flash image into the read-only area available at offset 0 of the window.

The above process takes place when the device is reset.

Apparently, the XIP IPL doesn't need the DoC 2000 trick with duplicating the code for 256-byte and 512-byte page size devices at offsets 0x100 and 0x200 respectively.

3. There is a data sheet on Millennium Plus at the aove link, if anyone is interested. The chip has ID 0x40, its IPL is downloaded from a non-zero flash offset, and there are few data structures in the beginning of the flash memeory.

Ilguiz

Quoted 3 lines · Mark Meade

You mentioned that there are DoC Millennium parts based on 256-byte-page chips -- so my hack to force the 512-byte code to 0x100 will not work correctly for all Millennium parts.