On 05/04/2013 10:38 PM, Michael Haberler wrote: > > Am 04.05.2013 um 20:07 schrieb Gilles Chanteperdrix > <[email protected]>: > >> On 05/04/2013 04:30 PM, Michael Haberler wrote: >> >>> >>> Am 04.05.2013 um 15:39 schrieb Gilles Chanteperdrix >>> <[email protected]>: >>> >>>> On 05/04/2013 08:04 AM, Michael Haberler wrote: >>>> >>>>> Xenomai: native skin or CONFIG_XENO_OPT_PERVASIVE disabled. >>>>> (modprobe xeno_native?) >>>> >>>> >>>> See: >>>> http://www.xenomai.org/documentation/xenomai-2.6/html/TROUBLESHOOTING/#_xenomai_native_skin_or_config_xeno_opt_pervasive_disabled >>> >>> I went through that before posting, and found no clue hinting to the >>> above, see below; >>> >>> on my first attempt, I managed to start from branch am33x-v3.2 instead from >>> tag 3.8.10-bone15, so failure was obvious but thats fixed >>> >>> is there a requirement the patch files need to reside in >>> xenomai-2.6/arch/arm/patches/* before doing scripts/prepare-kernel.sh ? >>> >>> still dead sure it's a 'duh' build goof >> >> >> One possible reason would be that something changed in 3.8.10, for >> instance in the system calls handling. But to know that, you would have >> to answer the questions I asked you, which you seem not willing to do. > > I'm prepared to confess but the clue is low ;)
The main question was: could you try 3.8.0 without any patches? Since it seems to have support for the beaglebone processor. > > I build the userspace support natively on the BB; the configure log is > http://static.mah.priv.at/public/config.log > > I cross-build only the kernel - following Stephans instructions I concluded > it is sufficient to apply those steps, i.e. apply the two patches like so, > after the inital kernel build which succeeds: > > ../xenomai-2.6/scripts/prepare-kernel.sh --linux=KERNEL --arch=arm > --ipipe=../ipipe-kernel-3.8.10.patch # fuzz here on what files? If there is fuzz on arch/arm/kernel/entry-armv.S for instance, this may be bad. Where did you get this ipipe-kernel-3.8.10.patch from? Please try to simply apply the "post" patch on git://git.xenomai.org/ipipe-gch.git branch for-core-3.8. > cd KERNEL > patch -p1 <../../post.patch # no fuzz > cd .. > tools/rebuild.sh > > I'd be unsure what to configure in the xenomai tree here beforehand when > cross-building? > > --- > > with CONFIG_IPIPE_DEBUG_CONTEXT and CONFIG_IPIPE_DEBUG_INTERNAL enabled, > /proc/interrupts looks so: > > root@arm:/usr/xenomai/bin# cat /proc/interrupts > CPU0 > 28: 1486 INTC edma > 30: 0 INTC edma_error > 34: 0 INTC musb-hdrc.0.auto > 35: 1 INTC musb-hdrc.1.auto > 46: 96 INTC 4819c000.i2c > 56: 0 INTC 4a100000.ethernet > 57: 735 INTC 4a100000.ethernet > 58: 625 INTC 4a100000.ethernet > 59: 0 INTC 4a100000.ethernet > 80: 4748 INTC mmc0 > 83: 18092 INTC gp_timer > 86: 162 INTC 44e0b000.i2c > 88: 363 INTC OMAP UART0 > 91: 0 INTC rtc0 > 92: 0 INTC rtc0 > 125: 0 INTC 53100000.sham So, you only have one interrupt controller, and it is "INTC", you do not need to check this one, it is already adapted. -- Gilles. _______________________________________________ Xenomai mailing list [email protected] http://www.xenomai.org/mailman/listinfo/xenomai
