I have to port Linux-xenomai on target Phytec PhyCARD-M iMx35 (ARM 11 core) and 
I need your help.

I reconfigured the kernel from the configuration provided by Phytec :

    - CONFIG_MX3_IPU = n
    - CONFIG_FB_MX3 = n
    - CONFIG_USB_ISP1760 = n

So, Linux-xenomai runs on the target, but I can't have pictures on the display 
(the configuration of the framebuffer is not set : CONFIG_MX3_IPU and 

I would like to enable xenomai and the framebuffer.

When I patch Linux with adeos-ipipe, disable xenomai and enable ipu (image 
processing unit), the kernel doesn't start :

        booting kernel of type uimage from /dev/ram0.kernel
           Verifying Checksum ... OK
           Image Name:   Linux-
           Created:      2011-04-20   7:14:44 UTC
           Image Type:   ARM Linux Kernel Image (uncompressed)
           Data Size:    2446512 Bytes =  2.3 MB
           Load Address: 80008000
           Entry Point:  80008000
        commandline: console=ttymxc0,115200 video=mx3fb:Primeview-PD050VL1 
ip= root=/dev/nfs   
        arch_number: 2595

        Starting kernel ...

        Linux version (francois@francois-desktop) (gcc version 4.3.2 
(OSELAS.Toolchain-1.99.3) ) #2 PREEMPT Wed Apr 20 09:14:32 CEST 2011
        CPU: ARMv6-compatible processor [4117b363] revision 3 (ARMv6TEJ), 
        CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction c

I think there is a conflict between ipipe and ipu but I don't know why.

IPU depends on dma engine.

When I read the /proc files, I can't see IRQ conflicts nor memory conflicts.

The ipu driver consists of two C files : ipu_idmac.c and ipu_irq.c. 
When I disable ipu_idma.c, I have 4 more IRQs (CONFIG_MX3_IPU_IRQS = 4) and 
Linux-ipipe (and xenomai) starts but I can't have pictures on the display.

I can't debug with printk because the printk calls modify the behaviour.

Do you have any idea ?

Thank you.                                        
Xenomai-core mailing list

Reply via email to