Hello,
Multi-Core Communication functionnalities will be supported in 4.1 kernel?
Regards,
Emmanuel
Solved! Go to Solution.
Dear timesyssupport,
I've been trying to execute a previously working MQX 4.1.1 application on the M4 core of a VF61 module. This application was using MCC v1 and worked properly on a system running linux kernel 3.0.15.
Now I'm using a system running linux kernel 4.1.15 and MCC v1, and trying to run the same MQX 4.1.1 application, but it is not running.
From what I've read above, isn't it possible to run this MQX application the way I'm trying? Do I need to use MCC v2 with linux kernel 4.1?
Thanks in advance.
Hi Julen,
What is the source for your Linux v4.1.15 kernel? Please share and we can determine if MCC support is present in it.
Thanks,
Timesys Support
Hi,
I already solved the problem.
The sources were taken from Toradex and MCC support is present in it. The thing was that some initializations for some peripherals that were properly done with the previous kernel/u-boot, weren't done in this kernel/u-boot.
After changing u-boot sources in order to enable clocks and initialize those peripherals code wasn't getting stuck anymore and the execution went through.
Thanks for your interest,
Julen.
Dear Timesys Support,
some dependencies are missing, for example vf610-mscm.h. I'm unable to find it in any known sources. Is there some public accessible 4.1 repository, which is the right kernel source for compiling your mcc-kmod-2.1.0.1.tar.bz2 ?
Thanks
Edward
Hi Timesys Support,
Is there an mcc implementation for i.MX6sx processor and linux kernel v4.1?
Timesys Support,
thanks for these files and sorry for delay. Now it compiles with linker warning for missing symbols from irq-vf610-mscm-ir.c If I replace this irq*.c driver in kernel sources, compiling kernel I get complain about missing #include "irqchip.h". If I replace this include with existing "Linux/irqchip.h", then I get more errors :-(
CC drivers/irqchip/irq-vf610-mscm-ir.o
drivers/irqchip/irq-vf610-mscm-ir.c: In function 'vf610_mscm_ir_domain_alloc':
drivers/irqchip/irq-vf610-mscm-ir.c:170:30: error: 'struct irq_domain' has no member named 'of_node'
gic_data.np = domain->parent->of_node;
^
drivers/irqchip/irq-vf610-mscm-ir.c: In function 'vf610_mscm_ir_of_init':
drivers/irqchip/irq-vf610-mscm-ir.c:318:44: error: 'struct irq_domain' has no member named 'of_node'
if (of_device_is_compatible(domain->parent->of_node, "arm,armv7m-nvic"))
^
make[2]: *** [drivers/irqchip/irq-vf610-mscm-ir.o] Error 1
make[1]: *** [drivers/irqchip] Error 2
make: *** [drivers] Error 2
Thank timesyssupport for let us know. Waiting for your comments
timesyssupport do you have an update of this case?
Hi Karina,
It is looking like official support for MCC for mainline Linux will be pushed to Q3, in the meantime, we will share MCC v2.x Linux kernel module sources as-is in the next two weeks that we have tested on a Vybrid platform with Linux v4.1.
Thanks,
Timesys Support
timesyssupport do you have an estimated due date?
Hi Karina,
We are still targeting end of Q2 for this work.
Thanks,
Timesys Support
timesyssupport do you have an update?
Hi Karina,
The patches are not yet available, we will update the thread once the work has been completed.
Thanks,
Timesys Support
timesyssupport do you have an estimated due date?
Hi Karina,
We are roughly targeting end of Q2, we will provide patches should they be available sooner.
Thanks,
Timesys Support
timesyssupport please continue with the follow up.
Hi Emmanuel,
We are planning to make a release of the MCC v2.x kernel modules targeting mainline Linux kernel and linux-fslc v4.4 from meta-fsl-arm, roughly by end of Q2. Let me know if you have any questions.
Thanks,
Timesys Support