[Xenomai-help] Re: [Xenomai-core] I-pipe patch for ARM S3C24xx

["Schlägl Manfred jun." <manfred.schlaegl@domain.hid>]

[-- Attachment #1: Type: text/plain, Size: 2024 bytes --]

On Tue, 2006-10-24 at 12:49 +0200, Sebastian Smolorz wrote:
> > Hi all,
> >
> > I'm currently working on porting I-pipe to the ARM S3C24xx. The patch is
> > attached, it must be applied after the shipped
> > adeos-ipipe-2.6.15-arm-1.5-01.patch. Unfortunately, there is still a severe
> > bug somewhere. I built Xenomai as modules. When I try to modprobe
> > xeno_native, the system hangs. No reaction at all, inlcuding serial console
> > and network access. I guess that interrupts are not handled any more. From
> > what I see if I spread some debug printk() into my code, the timer starts
> > working under the control of the Xenomai domain and one or two calls to the
> > Linux timer interrupt handler are made. But after that nothing happens any
> > more.
> >
> > As I try to find the bug for some days now but wasn't successful maybe the
> > experts have any hints where to continue searching. Or perhaps there is
> > someone who can test it and confirm or disprove my observation? It would be
> > great to support one more ARM model.
> 
> Small update with new infos: After Xenomai has (re)started the system timer 
> the Linux timer interrupt handler ist called only once, but 
> xnintr_clock_handler() is called several thousand times. So it seems that the 
> timer interrupt handler of Linux is not properly called or Xenomai is 
> starving Linux.
> 
> Sebastian
> 
> _______________________________________________
> Xenomai-core mailing list
> Xenomai-core@domain.hid
> https://mail.gna.org/listinfo/xenomai-core

Hi. I had the same Problem on my Netsilicon board.

I changed my timer-clock from CPU_CLK/64 to CPU_CLK so Xenomai is able
to use it with a higher granularity (set_dec/get_dec). So my machine has
1769472 ticks per jiffy instead of 27648. (works only with 32bit timers)

Further I had to set CLOCK_TICK_RATE (/include/asm/arch-xxxx/timex.h) to
real cpu frequency (im my case around 176000000).

Now I'm able to run latency with periods > 200us

	- Manfred

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]