* [Xenomai-core] Question on uITRON Skin development and porting to iMX27/ARM926EJ-S
@ 2009-06-22 2:50 Ravikiran Saralaya
2009-06-22 7:45 ` Gilles Chanteperdrix
2009-06-22 8:27 ` [Xenomai-help] " Philippe Gerum
0 siblings, 2 replies; 3+ messages in thread
From: Ravikiran Saralaya @ 2009-06-22 2:50 UTC (permalink / raw)
To: rpm, gilles.chanteperdrix, xenomai
Dear Philippe, Gilles,
First of all apologies for mailing you directly as our company mail rules
don't allow e-mailing to mail lists.
I am using Xenomai 2.4.7 and upgrading uITRON skin to be compliant to
uITRON specification 4.0 on iMX27/ARM926EJ-S. I have few related
questions. Sorry for the lengthy error logs..
1. The uITRON specification requires task creation to accept base
address of task stack to be allocated. The xnarch_alloc_stack() currently
accepts only stack size but not the base address.
Can anyone please suggest a work around for allocating task stack from a
base address?
2. I am planning to use iMX27 board from iWave (Rainbow-G3) with
ARM926EJ-S and Linux kernel 2.6.19.2 to develop Xenomai application. Is
Adeos ported on this platform? I get following error while building kernel
with ?adeos-ipipe-2.6.19-arm-1.7-00.patch?.
[root@domain.hid linux-2.6.19.2]# make
CHK include/linux/version.h
make[1]: `include/asm-arm/mach-types.h' is up to date.
CHK include/linux/utsrelease.h
CC arch/arm/kernel/asm-offsets.s
In file included from include/linux/sched.h:57,
from arch/arm/kernel/asm-offsets.c:13:
include/linux/ipipe.h:30:23: error: asm/ipipe.h: No such file or directory
In file included from include/linux/sched.h:57,
from arch/arm/kernel/asm-offsets.c:13:
include/linux/ipipe.h:141: warning: 'struct ipipe_domain' declared inside
parameter list
include/linux/ipipe.h:141: warning: its scope is only this definition or
declaration, which is probably not what you want
include/linux/ipipe.h:149: error: 'IPIPE_NR_XIRQS' undeclared here (not in
a function)
include/linux/ipipe.h:164: error: 'IPIPE_NR_EVENTS' undeclared here (not
in a function)
include/linux/ipipe.h: In function 'ipipe_init_notify':
include/linux/ipipe.h:438: error: 'IPIPE_EVENT_INIT' undeclared (first use
in this function)
include/linux/ipipe.h:438: error: (Each undeclared identifier is reported
only once
include/linux/ipipe.h:438: error: for each function it appears in.)
include/linux/ipipe.h: In function 'ipipe_cleanup_notify':
include/linux/ipipe.h:444: error: 'IPIPE_EVENT_CLEANUP' undeclared (first
use in this function)
...
Bla bla bla..
...
make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2
I got rid of the errors by changing include path of ipipe.h to
/asm-arm/ipipe.h. Similarly I got rid of subsequent errors by changing
paths of other header files as above. Now I get following linker errors:
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
arch/arm/kernel/built-in.o: In function `__ipipe_init_platform':
arch/arm/kernel/ipipe.c:123: undefined reference to
`__ipipe_mach_ticks_per_jiffy'
arch/arm/kernel/built-in.o: In function `ipipe_get_sysinfo':
arch/arm/kernel/ipipe.c:133: undefined reference to
`__ipipe_mach_ticks_per_jiffy'
arch/arm/kernel/ipipe.c:133: undefined reference to
`__ipipe_mach_timerint'
arch/arm/kernel/built-in.o: In function `__ipipe_set_decr':
arch/arm/kernel/ipipe.c:141: undefined reference to `__ipipe_mach_get_tsc'
arch/arm/kernel/ipipe.c:142: undefined reference to `__ipipe_mach_set_dec'
arch/arm/kernel/built-in.o: In function `__ipipe_grab_irq':
arch/arm/kernel/ipipe.c:482: undefined reference to `__ipipe_mach_get_tsc'
...
Bla bla bla..
...
arch/arm/xenomai/built-in.o: In function `rthal_timer_request':
arch/arm/xenomai/hal.c:128: undefined reference to
`__ipipe_mach_ticks_per_jiffy'
arch/arm/xenomai/hal.c:128: undefined reference to
`__ipipe_mach_timerstolen'
arch/arm/xenomai/hal.c:128: undefined reference to `__ipipe_mach_timerint'
make: *** [.tmp_vmlinux1] Error 1
Is my approach correct? I tried building with all patches
?adeos-ipipe-2.6.19-arm-1.x-yy.patch? but no success. Does that mean I
have to port Adeos on to this platform?
I also tried to get different Linux kernel version ported to iMX27, such
as 2.6.20, but I don?t have any option here other than 2.6.19 :(
Please advice if there is any alternative.
Thanks
Ravikiran
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Xenomai-core] Question on uITRON Skin development and porting to iMX27/ARM926EJ-S
2009-06-22 2:50 [Xenomai-core] Question on uITRON Skin development and porting to iMX27/ARM926EJ-S Ravikiran Saralaya
@ 2009-06-22 7:45 ` Gilles Chanteperdrix
2009-06-22 8:27 ` [Xenomai-help] " Philippe Gerum
1 sibling, 0 replies; 3+ messages in thread
From: Gilles Chanteperdrix @ 2009-06-22 7:45 UTC (permalink / raw)
To: Ravikiran Saralaya; +Cc: xenomai
Ravikiran Saralaya wrote:
> 1. The uITRON specification requires task creation to accept base
> address of task stack to be allocated. The xnarch_alloc_stack() currently
> accepts only stack size but not the base address.
The solution is simple: let the system allocate the stack, or implement
the missing functionality.
> I also tried to get different Linux kernel version ported to iMX27, such
> as 2.6.20, but I don?t have any option here other than 2.6.19 :(
Then I am afraid there is nothing we can do for you. You are on your
own. Sorry.
--
Gilles.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Xenomai-help] Question on uITRON Skin development and porting to iMX27/ARM926EJ-S
2009-06-22 2:50 [Xenomai-core] Question on uITRON Skin development and porting to iMX27/ARM926EJ-S Ravikiran Saralaya
2009-06-22 7:45 ` Gilles Chanteperdrix
@ 2009-06-22 8:27 ` Philippe Gerum
1 sibling, 0 replies; 3+ messages in thread
From: Philippe Gerum @ 2009-06-22 8:27 UTC (permalink / raw)
To: Ravikiran Saralaya, Vandana Sasidharan; +Cc: xenomai
On Mon, 2009-06-22 at 08:20 +0530, Ravikiran Saralaya wrote:
On Mon, 2009-06-22 at 08:58 +0530, Vandana Sasidharan wrote:
<...>
Could everyone working on this very same project at TCS talk to each
other, so that we don't get the annoying feeling of being spammed? TIA,
Could everyone involved in this project at TCS refrain from sending
private information requests to maintainers, so that we don't get the
annoying feeling of being spammed? TIA,
Could everyone involved in this project at TCS who may wish to get
information from free software contributors/users read this short blog
entry, just to get the basics?
http://opensourcestrategies.blogspot.com/2005/09/how-to-get-support-from-open-source.html
As far as the uITRON issue is concerned, I seem to remember having
indicated what follows at least once already, but I'm going to do it
once more, just in case you do read answers and not just bury people
alive in questions:
there will be no incentive to help you as long as nobody sees any code
from your end on this list. Among other things, the Xenomai project did
write the uITRON emulator in the first place, so I don't see any reason
why anyone would want to help you upgrading it for your own exclusive
benefit, really. If you don't have any code to share yet, then please
start here:
http://www.xenomai.org/documentation/branches/v2.4.x/html/api/group__nucleus.html
Good luck.
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
Abiding by the above rules, I have immediately and permanently deleted
your message. Thank you.
--
Philippe.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-06-22 8:27 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-22 2:50 [Xenomai-core] Question on uITRON Skin development and porting to iMX27/ARM926EJ-S Ravikiran Saralaya
2009-06-22 7:45 ` Gilles Chanteperdrix
2009-06-22 8:27 ` [Xenomai-help] " Philippe Gerum
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.