I’m thinking that it might be some filtering in the driver that causes this. Refer to this hardware related article. When extended CAN frames are sent they show up using candump. Use the latest kernel sources as we had to backport the following commits: The following shows the bring-up of a Colibri EvalBoard V2.
|Date Added:||6 December 2005|
|File Size:||63.57 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Once the device tree is setup to use a CAN device, the modules will get loaded automatically. Refer to this hardware related article. The following shows the bring-up of a Colibri EvalBoard V3.
All Boards FlexCAN | NXP Community
If you are using SocketCAN, you should be able to turn on loopback to receive messages that are being transmitted from your interface and they must actually be transmitted on the wires to be received via loopback. The syntax of the cansend command is different between the two. The following changes are needed for the device tree: Contents [ hide ]. Email Required, but never shown. If not enable it and recompile the imc.
Our Apalis standard image provide a kernel and if applicable a device tree configured for CAN. Alright, I have been at this flexcwn many times but given up. For older images the required ipk packages can be built with OpenEmbedded or can be found imd http: The can-utils package requires SocketCAN, which was integrated into the stock kernel 2.
But know I stumbled on the solution: Sign up using Facebook.
I want to Use flexcan interface of IMX6, | NXP Community
It is FlexCAN that is used. With the Colibri Evaluation board V3.
[PATCH 2/3] can: flexcan: Use a regulator to control the CAN transceiver
CAN communication with external nodes works like a charm, but the frames that I send to the nodes from my app is not printed when using “candump can0” in the terminal when I run the flexcah app on my host using a usb-CAN dongle this problem does not occur. When extended CAN frames are sent they show up using candump.
I’m thinking that it might be some filtering in the driver that causes this. Flecxan as a guest Name. On Colibri modules, CAN is not a standard pin mux and therefore not supported by our default image. The Apalis modules have two on-module CAN controllers.
Any clues are welcome. I understand that it might be convenient that messages that is sent is filtered, but I should be possible to choose.
Sign up or log in Sign up using Google.
Flexcab the latest kernel sources as we had to backport the following commits: By using this configurations, the platform data for the SPI resp. The drivers have to be enabled and configured in the device tree.
Kernel versions prior to 4. This not device tree enabled kernel must be recompiled with the following kernel configurations enabled:. I have a custom build linux 2. Both can be built with openembedded, the former with ‘bitbake canutils’ and the later with ‘bitbake can-utils’.