[okl4-developer] okl4 in qemu emulated gumstix environment

[Geoffrey Lee]

On Tue, Aug 26, 2008 at 05:43:51AM -0400, Ashish Bijlani wrote:
> Thanks for your quick reply. However, I'm using okl4-1.4 and I didn't
> change anything in it. I get shell using skyeye but no network as
> skyeye does not emulate smc91x network card. I don't get shell in
> qemu. The face that it runs fine on skyeye, indicates that ig_serial
> has been configured properly, isn't it?

Not necessarily, the simulator may sometimes behave differently
to how the hardware really behaves.  Please have a look around
the system to see if there are any clues of misbehavior, for
example, are you actually receiving any interrupts at all when
you hit a key on the serial?  Is the serial driver initialized
properly, or if vserial is present on the system at all?  Is there
any interaction between the vserial and OK Linux?  The KDB should be 
quite helpful here.


	-gl
> 
> -Ashish
> 
> On Tue, Aug 26, 2008 at 5:39 AM, Geoffrey Lee <glee at ok-labs.com> wrote:
> > On Tue, Aug 26, 2008 at 05:04:57AM -0400, Ashish Bijlani wrote:
> >> Hi,
> >>
> >> I'm able to boot OKL4 in QEMU emulated gumstix environment. However,
> >> I'm not able to get "Linux user startup!" and following messages on
> >> the qemu serial console. Any ideas why?
> >>
> >> This is what I did:
> >>
> >> cp build/image.boot /tftpboot/.
> >> ../qemu-gumstix/arm-softmmu/qemu-system-arm -M gumstix -hda
> >> ../connex-gumstix/flash -net nic -net tap,ifname=qtap0  -m 256
> >> -monitor null -serial stdio -m 289 -nographic
> >>
> >> GUM>
> >> GUM> setenv ipaddr 10.0.0.231
> >> GUM> setenv serverip 10.0.0.29
> >> GUM> tftpboot a2000000 image.boot
> >> GUM> bootelf a2000000
> >>
> >> The OKL4 kernel, wombat, iguana everything is loaded and booted
> >> properly. However, I don't see any messages after :
> >>
> >> NET: Registered protocol family 15
> >> VFS: Mounted root (ext2 filesystem) readonly.
> >
> > This probably means ig_serial.c or the user-level serial driver
> > in drivers/ is misconfigured.  The kernel bootup messages get
> > shown via the KDB console, which gets routed to the driver
> > in the OKL4 kernel.  Once you get to Linux user startup
> > output gets routed through /dev/ttyS0, which is backed by
> > ig_serial.
> >
> >        -gl
> >
> >>
> >> Am I missing something?
> >>
> >> Thanks,
> >> Ashish
> >>
> >> _______________________________________________
> >> Developer mailing list
> >> Developer at okl4.org
> >> https://lists.okl4.org/mailman/listinfo/developer
> >>
> >
> > --
> >
> >
> 

--