On Fri, 2 Feb 2001, Ronald G Minnich wrote:
> I do not think that the DoC is being written. You can test this.
> First, make sure that /dev/mtd0 is really a device node, and not just a
> file at this point.
>
/dev/mtd0 seems to be a device node :
[root@localhost mtd]# ll /dev/mtd0
crw-r--r-- 1 root root 90, 0 fév 2 23:27 /dev/mtd0
> Next, if you are sure that /dev/mtd0 is a device node, you need to insmod
> docecc.o, doc2001.0, and docprobe.o for your kernel.
>
what is quite strange is that when I boot with original bios, if I insert
the DoC and do the modprobe's, the DoC isnot recognized, here is what I
get from dmesg :
M-Systems DiskOnChip driver. (C) 1999 Machine Vision Holdings, Inc.
Possible DiskOnChip with unknown ChipID FF found at 0xfffc8000
Possible DiskOnChip with unknown ChipID FF found at 0xfffca000
Possible DiskOnChip with unknown ChipID FF found at 0xfffcc000
Possible DiskOnChip with unknown ChipID FF found at 0xfffce000
Possible DiskOnChip with unknown ChipID FF found at 0xfffd0000
Possible DiskOnChip with unknown ChipID FF found at 0xfffd2000
Possible DiskOnChip with unknown ChipID FF found at 0xfffd4000
Possible DiskOnChip with unknown ChipID FF found at 0xfffd6000
Possible DiskOnChip with unknown ChipID FF found at 0xfffd8000
Possible DiskOnChip with unknown ChipID FF found at 0xfffda000
Possible DiskOnChip with unknown ChipID FF found at 0xfffdc000
Possible DiskOnChip with unknown ChipID FF found at 0xfffde000
Possible DiskOnChip with unknown ChipID 86 found at 0xfffe0000
Possible DiskOnChip with unknown ChipID C5 found at 0xfffe2000
Possible DiskOnChip with unknown ChipID 2E found at 0xfffe4000
Possible DiskOnChip with unknown ChipID 03 found at 0xfffe6000
Possible DiskOnChip with unknown ChipID 3E found at 0xfffe8000
Possible DiskOnChip with unknown ChipID 2F found at 0xfffea000
Possible DiskOnChip with unknown ChipID 4C found at 0xfffec000
Possible DiskOnChip with unknown ChipID 44 found at 0xfffee000
then i can burn_mtd in the matsonic directory.
Here is the end of the dmesg :
MTD_write
_DoC_WaitReady called for out-of-line wait
MTD_write
_DoC_WaitReady called for out-of-line wait
MTD_close
then if I insert the modules , here is thenew dmesg :
M-Systems DiskOnChip driver. (C) 1999 Machine Vision Holdings, Inc.
DiskOnChip Millennium found at address 0xFFFC8000
Flash chip found: Manufacturer ID: 98, Chip ID: E6 (Toshiba
TC58V64AFT/DC)
1 flash chips found. Total DiskOnChip size: 8 Mbytes
mtd: Giving out device 0 to DiskOnChip Millennium
Ignoring DiskOnChip Millennium at 0xFFFCA000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFCC000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFCE000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFD0000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFD2000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFD4000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFD6000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFD8000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFDA000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFDC000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFDE000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFE0000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFE2000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFE4000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFE6000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFE8000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFEA000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFEC000 - already configured
Ignoring DiskOnChip Millennium at 0xFFFEE000 - already configured
> The
>
> dd if=/dev/mtdo of=/tmp/test count=1
>
> See if this file has data in it. It should match the docipl file.
>
ok, it match the docipl file, I'm sending it to you in a separate mail
with linuxbios.strip .
Here is the log of the python sequence :
python ~/linuxbios/freebios/util/config/NLBConfig.py
~/linuxbios/freebios/util/config/matsonic.config ~/linuxbios/freebios/
Will place Makefile, crt0.S, ldscript.ld in matsonic
Process config
file: /root/linuxbios/freebios/src/mainboard/matsonic/ms7308e/Config
Process config
file: /root/linuxbios/freebios/src/northsouthbridge/sis/630/Config
Added ram init file: northsouthbridge/sis/630/raminit.inc
Process config file: /root/linuxbios/freebios/src/cpu/p5/Config
Process config file: /root/linuxbios/freebios/src/cpu/p6/Config
Process config file: /root/linuxbios/freebios//src/lib/Config
Now Process the base files
Makebase is : /root/linuxbios/freebios/util/config/make.base :
Trying to create matsonic/Makefile
Trying to create matsonic/ldscript.ld
Trying to create matsonic/crt0.S
Check for crt0.S param
file: /root/linuxbios/freebios/src/include/northsouthbridge/sis/630/param.h
Adding include to crt0.S for this parameter file:
#include <northsouthbridge/sis/630/param.h>
Here is thematsonic.Config file :
# This will make a target directory of ./matsonic
target matsonic
# Matsonic MS7308E mainboard
mainboard matsonic/ms7308e
# Enable Serial Console for debugging
option SERIAL_CONSOLE
# Enable MicroCode update and L2 Cache init for PII and PIII
option UPDATE_MICROCODE
option CONFIGURE_L2_CACHE
# Use the internal VGA frame buffer device
option HAVE_FRAMEBUFFER
# Path to your kernel (vmlinux)
linux /usr/src/linux
# Kernel command line parameters
#commandline root=/dev/nftla1 single
commandline root=/dev/hda7 console=ttyS0,115200
docipl northsouthbridge/sis/630/ipl.S
...
and still nothing...
thank you
eric
