The result was that receiving msgs stopped working. Our Apalis standard image provide a kernel and if applicable a device tree configured for CAN. Eric G 1 3. By using this configurations, the platform data for the SPI resp. The drivers have to be enabled and configured in the device tree. On Colibri modules, CAN is not a standard pin mux and therefore not supported by our default image.
|Date Added:||16 May 2005|
|File Size:||70.59 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
I understand that it might be convenient that messages that is sent is filtered, but I should be possible to choose.
Refer to this hardware related article. Alright, I have been at this issue many times but given up.
I want to Use flexcan interface of IMX6, | NXP Community
Email Required, but never shown. The can-utils package requires SocketCAN, which was integrated into the stock kernel 2. Beside that, the interface needs to started using the up command:. If not enable it and recompile the kernel. By using this configurations, the platform data lfexcan the SPI resp.
The reason I want to do this is for creating a service tool on the same device which can log all CAN frames. With the Colibri Evalution board V3. The second component, the CAN transceiver, is external and makes sure electrical specification the physical layer is met.
The following shows the bring-up of a Colibri EvalBoard V3. This not device tree enabled kernel must be recompiled with the following kernel configurations enabled:.
[PATCH 2/3] can: flexcan: Use a regulator to control the CAN transceiver
I have a custom build linux 2. On Colibri modules, CAN is not a standard pin mux and therefore not supported by our default ijx.
iMX FlexCAN Driver | GuruCE
Any clues are welcome. The former is supported by all Colibri modules. Kernel versions prior to 4. For older images the required ipk packages can be built with OpenEmbedded or can be found on http: Eric G 1 3.
The drivers have to be enabled and configured in the device tree. The syntax of the cansend command is different between the two. Use the latest kernel sources as we had to backport the following commits: Both can be built with openembedded, the former with ‘bitbake canutils’ and the later with ‘bitbake can-utils’.
But know I stumbled on the solution: The most important configuration is fleexcan bitrate.