[okl4-developer] Problem with running 'l4test'

Prince Riley wmarketing3 at gmail.com
Fri Dec 5 06:26:23 EST 2008 

Yeonju

Yes that your board is similar is very helpful.

If you can then e-mail me your current scripts I can use the board that I
have to try and find your problem and correct it so your board runs.

It is very important that you tell me in what way your board is not like
mine so that I don't send you code which tries to use hardware not to be
found on your board.


Prince

On Thu, Dec 4, 2008 at 12:57 PM, Yeonju <xelis at hufs.ac.kr> wrote:

>
> Hi, Prince.
>
> Yes. My board spec is similar to this spec.
>
> Regards,
>  -Yeonju
>
>
> PrinceR wrote:
> >
> > Yeonju,
> >
> > Can you confirm that your board is similar to the board spec listed here
> > below:
> >
> > • 3 x 4 inch Single Board Computer
> >   • 8 channel 10 bit ADC (Max 500K SPS)
> >    • 400 MHz Samsung S3C2440A Processor
> >   • 130 bit GPIO and 24 channel external interrupt
> >    • ARM 920T core with Cache (16K+16K) and MMU
> >      source
> >    • 64MB SDRAM
> >   • Camera interface
> >    • 32 NAND Flash memory
> >   • 10Mbps Ethernet
> >    • AC'97 CODEC interface
> >   • PWM timers, Real Time Clock and Watch Dog
> >    • Touch Screen Interface
> >      Timer
> >    • LCD Controller (TFT)
> >   • Built-in Speaker
> >    • CF/MMC/SD Host
> >   • JTAG Debug port
> >    • USB Host(OHCI) and Device
> >   • Screen size up to 640 x 480
> >    • UART, IrDA, DMA, I2C, I2S interface
> > Prince Riley
> >
> >
> > On Wed, Dec 3, 2008 at 9:09 PM, Yeonju <xelis at hufs.ac.kr> wrote:
> >
> >>
> >> Hi-.
> >>
> >> I misunderstand your message.
> >> I think that you suggest me to repost dumped physical memory using KDB.
> >>
> >> This is my build command line,
> >>
> >> [root at localhost okl4_2.1]# ./tools/build.py machine=gta01
> project=l4test
> >>
> >> and I also used command option "mutex_type=user".
> >>
> >> [root at localhost okl4_2.1]# ./tools/build.py machine=gta01
> project=l4test
> >> mutex_type=user
> >>
> >> I use okl4 2.1 (not fixed.7) and Fedora6.
> >> My target board is MBA2440 based on s3C2440.
> >>
> >> I wonder I understand your message correctly.
> >>
> >> Regards,
> >>
> >>
> >>
> >>
> >> Geoffrey Lee wrote:
> >> >
> >> > On Tue, Dec 02, 2008 at 07:50:20PM -0800, Yeonju wrote:
> >> >>
> >> >> Hi-.
> >> >>
> >> >> I'm sorry to confuse you. And thank you for your help.
> >> >> I'm not so good at English....T-T
> >> >>
> >> >> I built without "mutex_type=user" at first, but it didn't work. So I
> >> >> searched this forum for clue.
> >> >> And I found a topic "S3C2440A and okl4". In that topic, you advised
> to
> >> >> buid
> >> >> with "mutex_type=user".
> >> >> After I read that, I built with "muetex_type=user". But it also
> didn't
> >> >> work.
> >> >>
> >> >> I still find a soultion. Please help me.
> >> >
> >> >
> >> > Just so that I understand your problem correctly, could you please
> >> > re-post the exact build command line that you used to build your
> >> > image, as well as the resulting output?  In addition, are you
> >> > running this on hardware or simulator?
> >> >
> >> >
> >> >>
> >> >> Regards,
> >> >>
> >> >
> >> >       -gl
> >> >
> >> >>
> >> >>
> >> >> Geoffrey Lee wrote:
> >> >> >
> >> >> > On Tue, Dec 02, 2008 at 05:34:35PM -0800, Yeonju wrote:
> >> >> >>
> >> >> >> Hi~.
> >> >> >
> >> >> >
> >> >> > Hi - to make sure I understand correctly, do you mean that
> >> >> > if you build with mutex_type=user, then l4test will run
> >> >> > successfully to completion?  Please note that l4test
> >> >> > must be run with mutex_type=user, if you run it under
> >> >> > a different configuration it may not work.
> >> >> >
> >> >> >    -gl
> >> >> >
> >> >> >>
> >> >> >> I have a question about 'l4test'.
> >> >> >> I succeeded to run example in okl4_2.1/iguana on s3c2440
> (ARM920T).
> >> >> >> So, I've tried running 'l4test'(in okl4_2.1/l4test), but I failed.
> >> >> >>
> >> >> >> I buit 'l4test' like this.
> >> >> >>
> >> >> >> &gt;./tools/build.py machine=gta01 project=l4test
> >> >> >> Binary image was made successful.
> >> >> >> But, after load that image on board, I&nbsp; saw &nbsp;fourth
> case.
> >> >> >> Fisrt case is "Nothing happen".
> >> >> >> There is only one message.
> >> >> >>
> >> >> >> OKL4 - (provider: Open Kernel Labs) built on Dec 4 2008 07:55:18
> >> using
> >> >> >> gcc
> >> >> >> ver.
> >> >> >> Second case is "L4_Rootserver abort".
> >> >> >>
> >> >> >> OKL4 - (provider: Open Kernel Labs) built on Dec 4 2008 07:55:18
> >> using
> >> >> >> gcc
> >> >> >> ver.
> >> >> >> bootinfo: max space = 256, mac mutex = 256, phys [0x30700000,
> >> >> 0x33ffffff)
> >> >> >> Thread Delete failed, ErrorCode = 2
> >> >> >> Assertion failed: r ==1, function deleteThread, file
> >> >> >> l4test/src/utility.c,
> >> >> >> lin.
> >> >> >> -KD# User: L4_Rootserver abort()ed-
> >> >> >> &gt;
> >> >> >> Third case is "Roottask pagefault"
> >> >> >>
> >> >> >> OKL4 - (provider: Open Kernel Labs) built on Dec 4 2008 07:55:18
> >> using
> >> >> >> gcc
> >> >> >> ver.
> >> >> >> bootinfo: max space = 256, mac mutex = 256, phys [0x30700000,
> >> >> 0x33ffffff)
> >> >> >> roottask read pagefault at 00bae664, ip=0012a5a0 - deny
> >> >> >> -KD# roottask pagefault-
> >> >> >> &gt;
> >> >> >> Fourth case is "success".
> >> >> >> All l4test suite was success.
> >> >> >> I fixed console.cc(in platform/s3c2410/pistachip/kdb),
> traps.spp(in
> >> >> >> /arch/arm/pistachio/v5/src) and machine.py(in /arch/arm/tools) for
> >> >> >> s3c2440.
> >> >> >> And also I tried to build 'l4test' like this.
> >> >> >>
> >> >> >> &gt;./tools/build.py machine=gta01 project=l4test mutex_type=user
> >> >> >> How can I run 'l4test' successful?
> >> >> >> Regards,
> >> >> >> --
> >> >> >> View this message in context:
> >> >> >>
> >> >>
> >>
> http://n2.nabble.com/Problem-with-running-%27l4test%27-tp1607028p1607028.html
> >> >> >> Sent from the OKL4 Community Forum mailing list archive at
> >> Nabble.com.
> >> >> >
> >> >> >> _______________________________________________
> >> >> >> Developer mailing list
> >> >> >> Developer at okl4.org
> >> >> >> https://lists.okl4.org/mailman/listinfo/developer
> >> >> >
> >> >> >
> >> >> > --
> >> >> >
> >> >> >
> >> >> > _______________________________________________
> >> >> > Developer mailing list
> >> >> > Developer at okl4.org
> >> >> > https://lists.okl4.org/mailman/listinfo/developer
> >> >> >
> >> >> >
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://n2.nabble.com/Problem-with-running-%27l4test%27-tp1607028p1607438.html
> >> >> Sent from the OKL4 Community Forum mailing list archive at
> Nabble.com.
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> Developer mailing list
> >> >> Developer at okl4.org
> >> >> https://lists.okl4.org/mailman/listinfo/developer
> >> >>
> >> >
> >> > --
> >> >
> >> >
> >> > _______________________________________________
> >> > Developer mailing list
> >> > Developer at okl4.org
> >> > https://lists.okl4.org/mailman/listinfo/developer
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://n2.nabble.com/Problem-with-running-%27l4test%27-tp1607028p1611958.html
> >> Sent from the OKL4 Community Forum mailing list archive at Nabble.com.
> >>
> >>
> >> _______________________________________________
> >> Developer mailing list
> >> Developer at okl4.org
> >> https://lists.okl4.org/mailman/listinfo/developer
> >>
> >
> > _______________________________________________
> > Developer mailing list
> > Developer at okl4.org
> > https://lists.okl4.org/mailman/listinfo/developer
> >
> >
>
> --
> View this message in context:
> http://n2.nabble.com/Problem-with-running-%27l4test%27-tp1607028p1614822.html
> Sent from the OKL4 Community Forum mailing list archive at Nabble.com.
>
>
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20081204/9c2f2aea/attachment-0001.htm

More information about the Developer mailing list