On Sat, 21 Mar 2009, Belisko Marek wrote:
> Hi,
>
> On Fri, Mar 20, 2009 at 10:30 PM, Robert P. J. Day
> <rpjday@xxxxxxxxxxxxxx> wrote:
> >
> > (i posted on this on the ARM mailing list but i'm still waiting to
> > hear if my attempt at subscribing to that list was accepted. so i'll
> > reproduce the problem here and hope for the best.)
> >
> > i have a technologic TS-7250 ARM-system with a homegrown in-flash
> > 2.6.17 kernel and very old busybox-1.2.1 based root filesystem, but it
> > boots and runs just fine via the RedBoot bootloader.
> Could you post redboot configuration?
>
> And also configs for working and not working kernels?
>
> Seems to me that u do not have correct File System support.
i'd thought of that, so here's more of what's happening. i don't
have access to the source tree for the 2.6.17 kernel that works, so
it's possible that the previous developer modified the MTD map file so
that the /dev/mtdblock files don't even match up with what's in flash
with the 2.6.21-ts kernel. so let's do this carefully. start with the
redboot loader:
RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
(reserved) 0x60000000 0x60000000 0x01D04000 0x00000000
RedBoot 0x61D04000 0x61D04000 0x00040000 0x00000000
vmlinux 0x61D44000 0x00218000 0x00160000 0x00218000
RedBoot config 0x61FF8000 0x61FF8000 0x00001000 0x00000000
FIS directory 0x61FFC000 0x61FFC000 0x00004000 0x00000000
RedBoot> fconfig -l
Run script at boot: true
Boot script:
.. fis load vmlinux
.. exec -c "console=ttyAM0,115200 root=/dev/mtdblock2"
... etc etc ...
so that tells me that the root filesystem is in the "(reserved)"
portion. now let the ***working*** kernel boot to see:
...
Using static partition definition
Creating 3 MTD partitions on "ts7250-nand":
0x00000000-0x00004000 : "TS-BOOTROM"
0x00004000-0x01d04000 : "Linux"
0x01d04000-0x02000000 : "RedBoot"
...
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
Reading data from NAND FLASH without ECC is not recommended
Reading data from NAND FLASH without ECC is not recommended
VFS: Mounted root (yaffs filesystem).
Freeing init memory: 76K
Reading data from NAND FLASH without ECC is not recommended
Reading data from NAND FLASH without ECC is not recommended
mounting ramfs at /dev
... etc etc ...
and once the system boots:
$ cat /proc/mtd
dev: size erasesize name
mtd0: 02000000 00020000 "phys_mapped_flash"
mtd1: 00004000 00004000 "TS-BOOTROM"
mtd2: 01d00000 00004000 "Linux"
mtd3: 002fc000 00004000 "RedBoot"
$
i have to admit, i'm a bit confused since the output of "fis list"
doesn't seem to match the MTD partitions, even though this
configuration clearly boots and runs. am i misreading the above?
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================
