Dear all,
I explain how I resolved the problem on this post:
http://tech.groups.yahoo.com/group/ts-7000/message/15184
Best regards,
Jeremie
--- In "jeremie.chevalier" <>
wrote:
>
> Dear all,
>
> I've decided to compile my own kernel.
>
> From Technologic Systems FTP, I've downloaded the kernel sources for 2.4.26,
> the RTAI/Adeos patch, a cross compiler for ARM, and the RTAI Magma sources.
>
> First, I tried a kernel with no Adeos/Rtai support. I configured the kernel
> from the TS7400_config configuration that is provided with the kernel
> sources, then I modified that configuration in order to include the NAND
> flash drive support as built-in, not as a module (otherwhise the kernel was
> not able to mount the YAFFS2 filesystem). I compiled the kernel and modules,
> installed everything onto the TS-7400 card, and I've been able to boot that
> kernel with no issue and no error message with the command "bootload -c
> 'console=ttyAM0,115200 root=/dev/mtdblock3 rootfstype=yaffs'
> zImage-2.4.26-custom". So, the 'bootload' utility is working fine with my own
> kernel, as long as it has no adeos/rtai extension.
>
> But secondly, I patched the kernel with the adeos/rtai patch, and rebuilt
> everything. In the configuration of the kernel, I added the "adeos support"
> as built-in. I did exactly the same steps than previously, but that kernel
> won't boot. I can't even see the 'Linux version 2.4.26-custom-rt ...' line at
> the beginning. So my custom kernel works perfectly with no Adeos/Rtai
> extensions, but when I add them to the configuration of the kernel, it makes
> everything freeze... I've even tried to build my kernel with the Adeos/Rtai
> patch applied but not activated through menuconfig, and it works. But every
> time I reactivate the "Adeos support" through menuconfig (as built-in), the
> compiled kernel won't boot and will freeze without a single line to output...
>
> How can that be? For the moment I have no SD card so I cannot try to boot the
> RTAI kernel into such...
>
> Best regards,
> Jérémie.
>
> --- In "jeremie.chevalier" <jeremie.chevalier@>
> wrote:
> >
> > Dear,
> >
> > Thanks for the answer.
> >
> > So far I've managed to boot the "zImage-7400-ts11" kernel, provided on TS's
> > FTP, with the bootload command. I can boot that kernel once my card has
> > booted (FLASHBOOT) and chrooted into the YAFFS2 filesystem located on the
> > NAND flash rom, at /dev/mtdblock/3 (through the linuxrc-mtdroot script).
> > The command I use is:
> >
> > bootload -c "console=ttyAM0,115200 root=/dev/mtdblock/3" zImage-7400-ts11
> >
> > You can notice that I use console=ttyAM0 rather than console=/dev/ttyAM0,
> > and thanks to that little trick I'm able to see the kernel booting.
> > However, it hangs at the VFS part, saying:
> >
> > VFS: Cannot open root device "mtdblock/3" or 1f:00
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on 1f:00
> >
> > So I suppose the root=/dev/mtdblock/3 argument is wrong, but I can't figure
> > out what to put there.
> >
> > Also, this 'bootload' command partly works with the non-rt kernel, but with
> > the realtime kernel, I can't even see it booting, while I use the same
> > command... So that's strange...
> >
> > Any thoughts?
> >
> > Best regards,
> > Jeremie.
> >
> > --- In "dokapra" <nebojsa@> wrote:
> > >
> > > I have very bad experience with bootload and setting console parameters.
> > > I am using 7260, and there is a hardware support for selecting different
> > > serial ports as a console. But, certain combinations of this jumper
> > > together with "console=..." setting made kernel freeze. It did however
> > > answer to ping from my host machine.
> > > Try to remove "console=/dev/ttyAM0,115200" part of parameter and see if
> > > it helps. You can test with ping to see if you have the same problem as I
> > > had. Seems to me that kernel gets stuck writing to console buffer, which
> > > never gets emptied for some reason.
> > >
> > > --- In "jeremie.chevalier" <jeremie.chevalier@>
> > > wrote:
> > > >
> > > > Hi folks,
> > > >
> > > > Any idea on this? Didn't someone encounter this problem in the past?
> > > >
> > > > Best regards,
> > > > Jeremie.
> > > >
> > > > PS: If I find the solution, I'll describe it here so that anyone that
> > > > encounters the problem in the future could be helped.
> > > >
> > > > --- In "jeremie.chevalier"
> > > > <jeremie.chevalier@> wrote:
> > > > >
> > > > > Dear all,
> > > > >
> > > > > I'm currently trying to load a real-time kernel on a TS-7400 and
> > > > > can't manage to have it working.
> > > > >
> > > > > The board computer I use is a stock TS-7400 with 2.4.26-ts11 kernel.
> > > > >
> > > > > I've downloaded the kernel image "vmlinux-7400-ts11-rt.bin" (2.4.26)
> > > > > from TS's FTP and simply put it in the root directory of the YAFFS2
> > > > > NAND filesystem. I also downloaded the kernel modules for
> > > > > 2.4.26-ts11-rt (got from the FTP as well) and put them in
> > > > > /lib/modules/2.4.26-ts11-rt/.
> > > > >
> > > > > I'm trying to load the real-time kernel with the "bootload" command,
> > > > > but every time I try, it freezes. I'm not sure about the parameters
> > > > > to use, for example I tried the following:
> > > > >
> > > > > bootload -c "console=/dev/ttyAM0,115200 root=/dev/mtdblock/3" -r
> > > > > /dev/rd/0 /vmlinux-7400-ts11-rt.bin
> > > > >
> > > > > But this never works. I tried several values for the ramdisk, and for
> > > > > the "root=" parameter as well, but nothing seems to work. I don't
> > > > > want to use a SD card, I would just like to replace the current
> > > > > kernel (non-real-time) by the rt one, got from TS website.
> > > > >
> > > > > Any thoughts on how I could proceed?
> > > > >
> > > > > Best regards,
> > > > > Jeremie.
> > > > >
> > > >
> > >
> >
>
------------------------------------
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/
|