Matthieu Crapet wrote:
Hi Andrew,
No reply, but I'm sure that Lennert with reply soon ;)
There are two major things:
- The machine ID provided with TS's Redboot is wrong 0x163 instead of 0x2A1
see messages "TS-7250 booting 2.6-git" (dated from 2006.04.26/27)
Note: If you are using Redboot.bin from ts7200-8MBflash-update.zip, you
can patch the Machine ID (dword) at offset 0xAF0.
- Memory parameters, should be fixed by Redboot (with ATAG list) but you
can try using mem= option
(see messages "didn't take long for me to crash the thing" (dated from
2006.04.28)
Your 2.6 kernel should be able to start booting at least. After that's
only "make menuconfig" customization
Including must of the debug kernel features will help you diagnosticing
problems.
Matthieu
Andrew Gaylard wrote:
Hi Matthieu,
Did you get a reply to this?
I'm unable to boot off the on-board flash with the derevo18 patches...
Andrew.
On 6/9/06, Matthieu Crapet m("gmail.com","mcrapet");"><> wrote:
Is derevo19 path on the way (Lennert) ?
Yes -- I've just got it from http://www.wantstofly.org/~buytenh/ep93xx/derevo19.diff
and it applies cleanly against 2.6.17. Thanks, Lennert!
2.6.17 + derevo19.patch works very well on my TS-7200, with one problem:
I cannot mount the on-board flash filesystem at boot time. I get this:
...[snip]...
physmap flash device: 1000000 at
60000000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit
bank
Intel/Sharp Extended Query Table at
0x0031
Using buffer write
method
cfi_cmdset_0001: Erase suspend on write
enabled
cmdlinepart partition parsing not
available
Searching for RedBoot partition table in phys_mapped_flash at
offset 0xfe0000
6 RedBoot partitions found on MTD device
phys_mapped_flash
Creating 6 MTD partitions on
"phys_mapped_flash":
0x00000000-0x00e20000 :
"(reserved)"
mtd: Giving out device 0 to
(reserved)
0x00e20000-0x00e60000 :
"RedBoot"
mtd: Giving out device 1 to
RedBoot
0x00e60000-0x00fa0000 :
"zImage"
mtd: Giving out device 2 to
zImage
0x00fa0000-0x00fc0000 :
"unallocated"
mtd: Giving out device 3 to
unallocated
0x00fc0000-0x00fc1000 : "RedBoot
config"
mtd: Giving out device 4 to RedBoot
config
0x00fe0000-0x01000000 : "FIS
directory"
mtd: Giving out device 5 to FIS
directory
Generic platform RAM MTD, (c) 2004 Simtec
Electronics
Initializing USB Mass Storage
driver...
usbcore: registered new driver
usb-storage
USB Mass Storage support
registered.
drivers/usb/net/rtl8150.c: rtl8150 based usb-ethernet driver
v0.6.2 (2004/08/27)
usbcore: registered new driver
rtl8150
usbcore: registered new driver
usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver
core
drivers/usb/serial/usb-serial.c: USB Serial support registered
for pl2303
usbcore: registered new driver
pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial
adaptor driver
rtc-m48t86 rtc-m48t86: rtc intf:
sysfs
rtc-m48t86 rtc-m48t86: rtc intf:
proc
rtc-m48t86 rtc-m48t86: rtc intf: dev
(254:0)
rtc-m48t86 rtc-m48t86: rtc core: registered m48t86 as
rtc0
rtc-m48t86 rtc-m48t86: battery
exhausted
ep93xx-rtc ep93xx-rtc: rtc intf:
sysfs
ep93xx-rtc ep93xx-rtc: rtc intf: dev
(254:1)
ep93xx-rtc ep93xx-rtc: rtc core: registered ep93xx as
rtc1
i2c /dev entries
driver
TCP bic
registered
NET: Registered protocol family
1
NET: Registered protocol family
17
NET: Registered protocol family
15
rtc-m48t86 rtc-m48t86: hctosys: invalid
date/time
mtdblock_open
ok
mtdblock: read on "(reserved)" at 0x0, size
0x200
mtdblock: read on "(reserved)" at 0x200, size
0x200
mtdblock_release
ok
No filesystem could mount root, tried:
romfs
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(31,0)
However, if I use a NFS-root, I can manually mount the partition:
...[snip]...
rtc-m48t86 rtc-m48t86: hctosys: invalid date/time
eth0: link up, 100Mbps, full-duplex, lpa
0xFFFF
Sending DHCP requests .,
OK
IP-Config: Got DHCP answer from 0.0.0.0, my address is
192.168.1.7
IP-Config:
Complete:
device=eth0, addr=192.168.1.7, mask=255.255.255.0,
gw=192.168.1.4,
host=192.168.1.7, domain=homeip.net,
nis-domain=(none),
bootserver=0.0.0.0, rootserver=192.168.1.4,
rootpath=
Looking up port of RPC 100003/2 on
192.168.1.4
Looking up port of RPC 100005/1 on
192.168.1.4
VFS: Mounted root (nfs
filesystem).
Freeing init memory:
80K
INIT: version 2.85-ts1.00
booting
...[snip]...
-bash-3.1# mount -t jffs2 -o ro /dev/mtdblock/0
/mnt
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at
0x00000000: 0x5243 in
stead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at
0x00000004: 0x0001 in
stead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at
0x0000000c: 0x1e5a in
stead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at
0x00000010: 0xd00c in
stead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at
0x00000014: 0x00d3 in
stead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at
0x00000018: 0xf000 in
stead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at
0x0000001c: 0xf000 in
stead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at
0x00000024: 0x5100 in
stead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at
0x00000028: 0xe004 in
stead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at
0x0000002c: 0x0054 in
stead
Further such events for this erase block will not be
printed
bash-3.1#
... and all my data's available under /mnt, as it should be.
One thing puzzles me and that's the fact that under 2.4.26-ts9
I used to mount /dev/mtdblock/1; now it has to be /dev/mtdblock/0
or jffs2 complains and does nothing.
What am I doing wrong? I'm sure it's something simple.
Andrew.
__._,_.___
![]()
SPONSORED LINKS
YAHOO! GROUPS LINKS
- Visit your group "ts-7000" on the web.
- To unsubscribe from this group, send an email to:
=Unsubscribe
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
__,_._,___
|
|