[Xenomai-help] How to Adapt ARM I-pipe patch to S3C6410

[Xenomai-help] How to Adapt ARM I-pipe patch to S3C6410

[陈晓]

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

I want to get the  ARM I-pipe patch  Adapt to S3C6410,but when I start up
the board,it stopped at the head.s,with no warning and notice.I find It
even not go to the start_kernel() function.what can I do??

[-- Attachment #2: Type: text/html, Size: 206 bytes --]

Re: [Xenomai-help] How to Adapt ARM I-pipe patch to S3C6410

[Gilles Chanteperdrix]

On 12/19/2011 02:38 AM, 陈晓 wrote:
> I want to get the  ARM I-pipe patch  Adapt to S3C6410,but when I start up
> the board,it stopped at the head.s,with no warning and notice.I find It
> even not go to the start_kernel() function.what can I do??
> 

What kernel version? What I-pipe version? What kernel configuration?
Have you tried the howto?

http://www.xenomai.org/index.php/I-pipe:ArmPorting

-- 
                                                                Gilles.

Re: [Xenomai-help] How to Adapt ARM I-pipe patch to S3C6410

[Gilles Chanteperdrix]

On 12/22/2011 03:37 AM, 陈晓 wrote:
> The kernel version is 2.6.37.6 I-pipe patch is 2.6.0-rc4,

2.6.0-rc4 is a xenomai version, not an I-pipe version. And xenomai
2.6.0-rc4 is obsolete and superseeded by xenomai 2.6.0.

I tried the
> howto ,but I couldn't find the variables and functions in irq.c ,but
> some of  the  functions and variables in time.c were here because of
> the patch.  I want to know whether all the function need to be add by
> myself ? because some of it exist when I patch the ipipe-patch.
> And the tip "Implementing a high-resolution counter.",I modified the
> CONFIG file and use the second way "Decrementer  See s3c24xx
> implementation."
> The complie work was finished with no error. Is there any patch t
> adpat  to the board?
> Thank you !

As indicated by the howto: "In the rest of this document we will call
these files time.c and irq.c, even though they may have another name for
your board. "

Anyway, irq demuxing is done differently with current versions of the
I-pipe, the howto is out of date. For each irq demux (the callbacks
registered with set_irq_chained_handler), the demux function should call
ipipe_handle_chained_irq instead of generic_handle_irq.

However, if the bug happens before start_kernel, the bug has probably
nothing to do with the modifications you made for the I-pipe. But are
you sure that the bug happens before start_kernel? Have you noted that
printk does not work as early as in start_kernel, you have to enable
early printk or use the printascii trick mentioned in the "tips and
tricks" section of the howto.

Please no private mails.

-- 
					    Gilles.

[Xenomai-help] How to Adapt ARM I-pipe patch to S3C6410

[陈晓]

sorry for the mistake,my ipipe-patch is
adeos-ipipe-2.6.37.6-arm-1.18-03   ,and where can I get the new
"HowTo" as it maybe out of date.
As I said,I add the printascii function in the begin of
start_kernel(),but it didn't print out ,so I believe it didn't go to
the start_kernel. I also add the printascii function to the
arch/arm/kernel/head.S,I found when it run to "enable the mmu" it
stopped. I believe the .config file works well before I patch the
xenomai .I also believe the xenomai has nothing to do with the setup
of hardware before the kernel startup.

Re: [Xenomai-help] How to Adapt ARM I-pipe patch to S3C6410

[Gilles Chanteperdrix]

On 12/24/2011 03:10 AM, 陈晓 wrote:
> sorry for the mistake,my ipipe-patch is
> adeos-ipipe-2.6.37.6-arm-1.18-03   ,and where can I get the new
> "HowTo" as it maybe out of date.
> As I said,I add the printascii function in the begin of
> start_kernel(),but it didn't print out ,so I believe it didn't go to
> the start_kernel. I also add the printascii function to the
> arch/arm/kernel/head.S,I found when it run to "enable the mmu" it
> stopped. I believe the .config file works well before I patch the
> xenomai .I also believe the xenomai has nothing to do with the setup
> of hardware before the kernel startup.
> 

There is no updated version of the howto. But the only wrong thing is
the part about multiplexed interrupts.

You should try printascii with a non-patched kernel to verify that
printascii works for the board you use.

As for using printascii around the place where the mmu is enabled, have
you read the following comment in the kernel sources:

/*
 * Enable the MMU.  This completely changes the structure of the visible
 * memory space.  You will not be able to trace execution through this.
 * If you have an enquiry about this, *please* check the linux-arm-kernel
 * mailing list archives BEFORE sending another post to the list.

Anyway, as early in the boot process the I-pipe patch does not change
anything, so, your problem does not come from the I-pipe patch. Have you
tried the exact same config you use with the patched kernel with an
unpatched kernel?

-- 
                                                                Gilles.