[okl4-developer] okl4 3.0 for openmoko Neo FreeRunner(s3c2442)

[Sean Chiang]

Josh,

Sorry for late, my internet got broken last weekend. :(

Here is the build argument,

./build.py machine=gta02 project=l4test project=iguana project=examples
example=hello pistachio.TOOLC    HAIN=gnu_arm_toolchain PYFREEZE=False
mutex_type=user enable_fastpaths=False


2009/1/17 Josh Matthews <jmatthews at ok-labs.com>

> Hi Sean,
>
> On Fri, January 16, 2009 1:37 am, Sean Chiang wrote:
>
> > I have a gta02(Neo FreeRunner) on hand and I have been porting the okl4
> > 3.0 to gta02 days ago.
>
> Welcome to OKL4. That sounds like a great project!
>
> > First, I almost copied everything from platform/s3c2410/ to platform
> > /s3c2442/ and did some gta02 specific modifications. Fortunately, it's
> > workable, I mean at least I could see msg[1] from serial console or lcm
> > and no exception happen so far.
> >
> > But the booting process seems to be in trouble, if you look at the
> bootlog
> > you would know what I mean. There's nothing happen after the msg "##
> > Starting application at 0xf0000000 ..." displayed.
> >
> > What's supposed to be displayed, run or happen after the msg
> "Starting..".
>
> The expected output depends on your build. Would you be able to let us
> know the build line that you used to produce this build?
>
> The output in image.elf.bootlog is from U-Boot only, so a first guess at
> the problem would suspect your UART/serial driver. However, the output in
> image.bin.bootlog at least shows the OKL4 hello message (which is printf'd
> from init_hello(), called from startup_system_mmu() in
> arch/arm/pistachio/src/init.cc). My advice would be to track execution


Got it, will give it a try and see what happen. Thanks. ;)


>
> from there using printfs to see how far the kernel actually gets.
>
> Best regards,
>
> Josh
>
>
-Sean Chiang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20090119/18fe265d/attachment.htm