Hi,
I have a TS-7250 which has Linux 2.4.26-ts11 installed on it. The board has 128
MB NAND Flash and 64MB RAM. I ran into this issue of insufficient time
resolution (10 ms on gettimeofday() calls) while doing code execution delay
measurements on the current Linux 2.4 kernel. I read one of the posts in this
group that said the time resolution bug has been fixed in the Linux 2.6 kernel.
So now I am trying to install 2.6 on the board. But I have been running into
issues while booting. Here is what I did:
* Dowloaded the Linux 2.6.21-ts kernel and compiled it successfully with
arm-none-linux-gnueabi(compiler crosstool-linux26-3.4.4-2005q3-2.tar.gz). I set
the CONFIG_HZ to be 1000 instead of 100 before compiling. (I also tried
applying the high resolution timer patch but I ran into compilation issues and
since I am compiling/loading a kernel for the first time, I decided to first
learn how to load the kernel image with default settings so that I can try
compiling again with relevant patches and settings later on)
* I put the 'zImage', 'bootloader.o' and 'bootload' files onto a directory on
the flash - /root/Linux_2_6
* I ran the command 'insmod -f bootloader.o' from /root/Linux_2_6 and it worked.
* To load the kernel, from the /root/Linux_2_6 directory, I ran:
'bootload -c "console=ttyAM0,115200 root=/dev/mtdblock/1" zImage'
The bootloader finds the kernel zImage and loads it, but while the kernel
loads, it hangs forever with following messages:
mice: PS/2 mouse device common for all mice
rtc-m48t86 rtc-m48t86: rtc core: registered m48t86 as rtc0
rtc-m48t86 rtc-m48t86: battery exhausted
ep93xx-rtc ep93xx-rtc: rtc core: registered ep93xx as rtc1
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <>
rtc-m48t86 rtc-m48t86: hctosys: invalid date/time
Sending DHCP requests ...<3>DHCP/BOOTP: Ignoring fragmented reply.
DHCP/BOOTP: Ignoring fragmented reply.
DHCP/BOOTP: Ignoring fragmented reply.
DHCP/BOOTP: Ignoring fragmented reply.
DHCP/BOOTP: Ignoring fragmented reply.
DHCP/BOOTP: Ignoring fragmented reply.
DHCP/BOOTP: Ignoring fragmented reply.
DHCP/BOOTP: Ignoring fragmented reply.
DHCP/BOOTP: Ignoring fragmented reply.
DHCP/BOOTP: Ignoring fragmented reply.
printk: 2226 messages suppressed.
DHCP/BOOTP: Ignoring fragmented reply.
.<4>printk: 2230 messages suppressed.
DHCP/BOOTP: Ignoring fragmented reply.
.<4>printk: 3759 messages suppressed.
DHCP/BOOTP: Ignoring fragmented reply.
.<4>printk: 3739 messages suppressed.
DHCP/BOOTP: Ignoring fragmented reply.
The above pattern keeps repeating and the kernel does not boot further.
I must be going wrong somewhere, but not able to figure out where. Please guide
me in case you have seen this before. I am new to loading kernels. I can
provide the complete kernel log if required.
If I need to use Redboot, what changes do I need to make in my approach?
Also, is there any other way to obtain a better time resolution, like in the
order of 1 microsec?
Thank you
------------------------------------
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/
|