Thank you for all your suggestions.. I went with Linux 2.6.21 earlier because
on the embeddedArm website, it was listed to support the TS7250.. and I also
read in earlier posts that recompiling the 2.4 kernel by just setting HZ=1000
may not work. So I did not try that....
Anyways.. I decided to switch back to Linux 2.4.26-ts11 by adding the hrt
patches as suggested by dokorpa.
I downloaded the source for tskernel-2.4.26-ts11 along with the following three
patches listed under the 'Files' link on this yahoo group (I guess they are all
dependent on one another, so I had to download all three patches):
linux-2.4-ts11-hrt.patch.gz
linux-2.4-ts11-lck1.patch.gz
linux-2.4-ts11-vhz.patch.gz
I compiled the new Linux 2.4 kernel source files after adding all the three
patches and it was succesful.
However, I run into issues while loading the kernel on the board again. I am
using 'Bootloader' and trying to set the root as '/dev/mtdblock/1' which points
to a section on the NAND Flash. Here is the proceedure I follow to load the
kernel:
* Put 'bootloader.o' and 'zImage' files onto a directory '/root/RT_Linux_2_4'
using ftp.
* Connect to the board and get into '/root/RT_Linux_2_4' folder.
* Enter - 'insmod -f bootloader.o' to install the bootloader
* Enter - 'bootload -c "console=ttyAM0,115200 root=/dev/mtdblock/1
rootfstype=yaffs" zImage' to load the kernel from '/root/RT_Linux_2_4' folder.
* The initial portion loads fine until the board hangs with these messages in
the end:
Searching for NAND flash...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bi
t)
Scanning device for bad blocks
Bad eraseblock 0 at 0x00000000
Bad eraseblock 1 at 0x00020000
Bad eraseblock 96 at 0x00c00000
Using static partition definition
Creating 3 MTD partitions on "NAND 128MiB 3,3V 8-bit":
0x00000000-0x00004000 : "TS-BOOTROM"
mtd: partition "TS-BOOTROM" doesn't end on an erase block -- force read-only
0x00004000-0x07d04000 : "Linux"
mtd: partition "Linux" doesn't start on an erase block boundary -- force read-on
ly
0x07d04000-0x08000000 : "RedBoot"
mtd: partition "RedBoot" doesn't start on an erase block boundary -- force read-
only
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NetWinder Floating Point Emulator V0.97 (double precision)
VFS: Cannot open root device "mtdblock/1" or 1f:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 1f:00
I have a few questions here:
* Are my proceedure and the bootload command parameters to load the kernel,
proper?
* Do I need to place the zImage/bootloader in a particular location or is it
okay to be put in the current location?
* The BOOTROM section is between '0x00000000-0x00020000' during normal boot
instead of '0x00000000-0x00004000' ( Please see kernel logs above) as is the
case while booting the new kernel. I am not sure why this is happening. This
problem never occured while loading the 2.6 kernel earlier.
Please let me know about this. Also, if I am not following the correct boot
proceedure please do post the proper steps. (I saw a few posts regarding NFS
boot but I did not come across many that talked about using bootloader to boot
from the Flash).
Thanks so much
--- In "dokapra" <> wrote:
>
> >
> > Also, is there any other way to obtain a better time resolution, like in
> > the order of 1 microsec?
> >
> > Thank you
> >
> You can patch your 2.4-ts11 kernel with a linux-2.4-ts11-hrt.patch.gz from
> Files section. It improves gettimeofday resolution to the microsecond level,
> and fixes a bug (yes a BUG) with real time sliding away some 15 seconds a day
> because of wrong calculation.
> Patch works very well, and time keeping comes back to maximum slide of 5
> sec/day which is what is possible with a given hardware.
> Make note that this is not the same as having kernel scheduler working at
> 1021Hz - your task scheduling still happens with 10ms resolution.
> Anyway this patch does not affect performance as a 1021 clock does and is
> safe to apply.
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|