• State
  • Locked Locked
  • Replies 34 replies
  • Subscribers 100 subscribers
  • Views 1117 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SK-AM62B-P1: SK-AM62B-P1

Sai Kiran Y
Prodigy 60 points
Part Number: SK-AM62B-P1
Other Parts Discussed in Thread: SYSCONFIG

Hi,

On the EVK, using main_mcan0 interface, I am able to send and receive CAN data. How do I use the other two interfaces(mcu_mcan0 and mcu_mcan1) for the same?

I have made the following connections:

TX(from external CAN transceiver) to Pin 22 of J9.
RX(from external CAN transceiver) to Pin 16 of J9.

Is there any other setup process needed for this? It would be great if someone can help me with this.

Thanks,
Sai Kiran.

  • 0
    TI__Genius 12330 points

    Sai,

    Hope you have looked at the MCU SDK MCAN Page

    https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/latest/exports/docs/api_guide_am62x/DRIVERS_MCAN_PAGE.html

    I also wanted to check if you are using Sysconfig tool : https://www.ti.com/tool/SYSCONFIG

    Regards

    Anshu

  • 0 in reply to Anshu Choudhary
    Prodigy 60 points

    Hi Anshu,

    I have looked at the MCAN drivers documentation. Unfortunately, that did not help.

    Thanks,
    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    Hello Sai,

    Are you using MCU+ SDK or the Linux processor SDK to run the example?
    Also, is this an internal loopback or external loopback setup?

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    Intellectual 860 points

    Hi Sai Karan,

     Please tell PSDK version and MCU+SDK version. External loopback was also possible how to load bare-metal code please explain.

    Regards,

    Veerapandiyan V

  • 0 in reply to Aparna Patra
    Prodigy 60 points

    Hi,

    I am using Linux Processor SDK. I have flashed the ti-default-image-am62xx-evm.wic.xz to SD Card and booted the EVK with this image. 
    To perform the CAN test, I am using PCAN software to send CAN data. I have interfaced external CAN transceiver to the EVK. I am trying to access the 
    MCU mcans from the SDK(with the default yocto image provided).

    Thanks,
    Sai Kiran.

  • 0 in reply to veerapandiyan v
    Prodigy 60 points

    Hi Veerapandiyan,

    I am using the following Yocto image. The Processor SDK version is 09.02.01.09.

    Thanks,
    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    Intellectual 860 points

    Hi Sai Karan,

      please check below code is working fine. /cfs-file/__key/communityserver-discussions-components-files/791/mcan_5F00_loopback_5F00_polling_5F00_am62x_2D00_sk_5F00_m4fss0_2D00_0_5F00_nortos_5F00_ti_2D00_arm_2D00_clang.zip

    This file was generated for 9.1 u  change it to 9.2.

    Regards,

    Veerapandiyan V.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    Hi Sai,

    Have you applied the k3-am62x-sk-mcan.dtbo on top of default SDK?
    If yes, please share the results of dmesg | grep can command

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    Prodigy 60 points

    Hi Aparna,

    Yes, I have applied the dtbo on top of the SDK. Here is the snap of CAN messages in the dmesg.

    root@am62xx-evm:~# dmesg | grep can
[    0.391186] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[    0.404535] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[    0.417883] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[    0.431229] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[    5.929581] m_can_platform 4e18000.can: m_can device registered (irq=0, version=32)
[    5.983402] m_can_platform 20701000.can: m_can device registered (irq=413, version=32)
[    6.042619] m_can_platform 4e08000.can: m_can device registered (irq=0, version=32)
[    8.849194] m_can_platform 4e18000.can mcu_mcan1: renamed from can0
[    8.918815] m_can_platform 4e08000.can mcu_mcan0: renamed from can2
[    9.131858] m_can_platform 20701000.can main_mcan0: renamed from can1


    Thanks,
    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    Hi Sai,

    Looks like the overlay file is applied and you have access to MCU MCANs.
    Please make the necessary connections, and if there is no hardware fault, MCAN communication should work fine.

    You are right, the following pins correspond to MCU_MCAN0:

    Sai Kiran Y said:
    TX(from external CAN transceiver) to Pin 22 of J9.
    RX(from external CAN transceiver) to Pin 16 of J9.

    From the logs, can2 should drive MCU_MCAN0, could you test the same.

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    Prodigy 60 points

    Hi,

    I have made the connections as per the diagram. Using PCAN-View software, I am sending the data to EVK.
    However, using "candump mcu_mcan0" command, I do not see any CAN messages. 

    Using the same setup, if I connect external CAN transceiver to main_mcan0 pins, I see the CAN messages when I run
    "candump main_mcan0" command.

    Thanks,
    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    Hi Sai,

    Please run the following commands and share the output:

    > dmesg | grep can
> ip link set can2 down
> ip link set can2 type can bitrate 125000
> ip link set can2 up
   [   40.940389] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
> candump can2

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    Prodigy 60 points

    Hi Aparna,

    There is no can2 interface. It is named as mcu_mcan0. I have tried the commands you have mentioned.

    root@am62xx-evm:~# ip link set can2 down
Cannot find device "can2"
root@am62xx-evm:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 1c:63:49:22:5f:e5 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 70:ff:76:1e:d0:cf brd ff:ff:ff:ff:ff:ff
4: mcu_mcan1: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qlen 10
    link/can
5: main_mcan0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qlen 10
    link/can
6: mcu_mcan0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qlen 10
    link/can
root@am62xx-evm:~# ip link set mcu_mcan0 down
root@am62xx-evm:~#  ip link set mcu_mcan0 up type can bitrate 125000
[ 3380.921528] IPv6: ADDRCONF(NETDEV_CHANGE): mcu_mcan0: link becomes ready
root@am62xx-evm:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 1c:63:49:22:5f:e5 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 70:ff:76:1e:d0:cf brd ff:ff:ff:ff:ff:ff
4: mcu_mcan1: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qlen 10
    link/can
5: main_mcan0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qlen 10
    link/can
6: mcu_mcan0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP group default qlen 10
    link/can
root@am62xx-evm:~# candump can2
[ 3407.213132] can: controller area network core
[ 3407.217696] NET: Registered PF_CAN protocol family
[ 3407.232553] can: raw protocol
SIOCGIFINDEX: No such device
root@am62xx-evm:~# candump mcu_mcan0

^Croot@am62xx-evm:~#

    "candump mcu_mcan0" does not receive any data, even though the CAN messages are being sent.

    Thanks,
    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    Hello Sai Kiran,

    Could you check for any hardware connection issues associated with MCU MCAN setup?
    The behavior you have reported is currently not seen on TI's setup.
    I will get back to you with more information.

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    Prodigy 60 points

    Hi Aparna,

    I have checked the hardware connections. I do not see any issues. If there are any specific PINS you want me to check(for connectivity and voltage measurement), do let me know.

    Thanks,
    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    Hello Sai Kiran,

    Could you try sending out data from MCU MCAN to your PCAN module, and check if the data is received by PCAN-view ?

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    Prodigy 60 points

    Hello Aparna,

    I have tried that as well. There is no data received by PCAN-view.

    Thanks,
    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    Hello,

    Allow me some time to reproduce this test on my setup. I will be able to get back early next week.

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    TI__Genius 12980 points

    Hi Sai,

    Could you help me with the MCAN parameters(Bitrates, clock frequency and mode: ISO CAN FD or CAN) that are being set in PCAN-view software and the bitrate set in the ip link command?

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    Prodigy 60 points

    Hi Aparna,

    I am using the following settings on PCAN-view software.

    Bitrate: 125000
    Mode: CAN FD
    Clock frequency: 8MHz

    Using ip link command, the bitrate was set to 125000. I have also tried with 500000 bitrate.

    Thanks,
    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    Hello Sai,

    I could receive data from PCAN-view on MCU MCAN instance as well:

    [2024-05-23 13:56:14.228] root@am62xx-evm:~# dmesg | grep can                                        
[2024-05-23 13:56:19.220] [    0.391231] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[2024-05-23 13:56:19.236] [    0.404581] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[2024-05-23 13:56:19.236] [    0.417930] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[2024-05-23 13:56:19.236] [    0.431277] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[2024-05-23 13:56:19.252] [    6.212035] m_can_platform 4e18000.can: m_can device registered (irq=0,)
[2024-05-23 13:56:19.252] [    6.246735] m_can_platform 4e08000.can: m_can device registered (irq=0,)
[2024-05-23 13:56:19.268] [    6.402926] m_can_platform 20701000.can: m_can device registered (irq=4)
[2024-05-23 13:56:19.268] [    9.022228] m_can_platform 4e18000.can mcu_mcan1: renamed from can0
[2024-05-23 13:56:19.284] [    9.102189] m_can_platform 4e08000.can mcu_mcan0: renamed from can1
[2024-05-23 13:56:19.284] [    9.234537] m_can_platform 20701000.can main_mcan0: renamed from can2
[2024-05-23 13:56:19.300] root@am62xx-evm:~# ip link set mcu_mcan0 down                              
[2024-05-23 13:57:12.160] root@am62xx-evm:~# ip link set mcu_mcan0 type can bitrate 250000
[2024-05-23 13:57:30.206] root@am62xx-evm:~# ip link set mcu_mcan0 up  
[2024-05-23 13:57:35.710] [  106.523708] IPv6: ADDRCONF(NETDEV_CHANGE): mcu_mcan0: link becomes ready
[2024-05-23 13:57:35.710] root@am62xx-evm:~# candump mcu_mcan0
[2024-05-23 13:57:43.549] [  114.360124] can: controller area network core
[2024-05-23 13:57:43.549] [  114.364650] NET: Registered PF_CAN protocol family
[2024-05-23 13:57:43.565] [  114.382747] can: raw protocol
[2024-05-23 13:57:53.053]   mcu_mcan0  0C0   [8]  D1 22 33 44 55 66 77 88
[2024-05-23 13:57:54.061]   mcu_mcan0  0C0   [8]  D1 22 33 44 55 66 77 88
[2024-05-23 13:57:54.365]   mcu_mcan0  0C0   [8]  D1 22 33 44 55 66 77 88
[2024-05-23 13:57:54.541]   mcu_mcan0  0C0   [8]  D1 22 33 44 55 66 77 88
[2024-05-23 13:57:55.165]   mcu_mcan0  0C0   [8]  D1 22 33 44 55 66 77 88
[2024-05-23 13:57:55.357]   mcu_mcan0  0C0   [8]  D1 22 33 44 55 66 77 88
[2024-05-23 13:57:55.501]   mcu_mcan0  0C0   [8]  D1 22 33 44 55 66 77 88
[2024-05-23 13:57:55.661]   mcu_mcan0  0C0   [8]  D1 22 33 44 55 66 77 88
[2024-05-23 13:57:55.949]   mcu_mcan0  0C0   [8]  D1 22 33 44 55 66 77 88
[2024-05-23 13:57:56.141]   mcu_mcan0  0C0   [8]  D1 22 33 44 55 66 77 88
[2024-05-23 13:57:56.333]   mcu_mcan0  0C0   [8]  D1 22 33 44 55 66 77 88
[2024-05-23 13:57:56.525]   mcu_mcan0  0C0   [8]  D1 22 33 44 55 66 77 88

    My PCAN-view had the following settings:

    Mode: CAN
    Clock Freq: 60 MHz
    Bitrate: 250 kbit/s

    Please try the same and let me know if it works?

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    Prodigy 60 points

    Hi Aparna,

    I have checked with 250kbit/s. I do not see any data being received on TI.

    root@am62xx-evm:~# ip ad
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 1c:63:49:22:5f:e5 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 70:ff:76:1e:d0:cf brd ff:ff:ff:ff:ff:ff
4: mcu_mcan0: <NO-CARRIER,NOARP,UP,ECHO> mtu 16 qdisc pfifo_fast state DOWN group default qlen 10
    link/can
5: mcu_mcan1: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qlen 10
    link/can
6: main_mcan0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP group default qlen 10
    link/can
root@am62xx-evm:~# dmesg | grep can
[    0.391158] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page
[    0.404507] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page
[    0.417854] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[    0.431201] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[    5.601234] m_can_platform 4e08000.can: m_can device registered (irq=0, version=32)
[    5.667218] m_can_platform 4e18000.can: m_can device registered (irq=0, version=32)
[    5.686595] m_can_platform 20701000.can: m_can device registered (irq=412, version=32)
[    8.415230] m_can_platform 4e08000.can mcu_mcan0: renamed from can0
[    8.509033] m_can_platform 20701000.can main_mcan0: renamed from can2
[    8.557080] m_can_platform 4e18000.can mcu_mcan1: renamed from can1
[   67.395839] IPv6: ADDRCONF(NETDEV_CHANGE): mcu_mcan0: link becomes ready
[  184.367464] can: controller area network core
[  184.387292] can: raw protocol
[  357.478565] m_can_platform 4e08000.can mcu_mcan0: bus-off
[  543.911025] IPv6: ADDRCONF(NETDEV_CHANGE): main_mcan0: link becomes ready

    Notice that the state of mcu_mcan0 is DOWN, whereas main_mcan0 is UP. I am not sure if that has anything to do with our experiment.
    Could you verify if it's the same on your end as well.

    Thanks,
    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    Hello,

    The state of CANs depend on the what is set using the ip link command. Please refer below:

    [2024-05-23 14:46:59.269] root@am62xx-evm:~# ip ad
[2024-05-23 14:47:02.709] 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group 0
[2024-05-23 14:47:02.725]     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
[2024-05-23 14:47:02.725]     inet 127.0.0.1/8 scope host lo
[2024-05-23 14:47:02.741]        valid_lft forever preferred_lft forever
[2024-05-23 14:47:02.741]     inet6 ::1/128 scope host 
[2024-05-23 14:47:02.741]        valid_lft forever preferred_lft forever
[2024-05-23 14:47:02.741] 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN 0
[2024-05-23 14:47:02.757]     link/ether 68:e7:4a:08:b3:c2 brd ff:ff:ff:ff:ff:ff
[2024-05-23 14:47:02.757] 3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN 0
[2024-05-23 14:47:02.773]     link/ether 70:ff:76:1e:a4:7f brd ff:ff:ff:ff:ff:ff
[2024-05-23 14:47:02.773] 4: mcu_mcan1: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qlen0
[2024-05-23 14:47:02.773]     link/can 
[2024-05-23 14:47:02.773] 5: mcu_mcan0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP gr0
[2024-05-23 14:47:02.789]     link/can 
[2024-05-23 14:47:02.789] 6: main_mcan0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qle0
[2024-05-23 14:47:02.789]     link/can 
[2024-05-23 14:47:02.805] 7: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN0
[2024-05-23 14:47:02.805]     link/ether 20:d7:78:b6:29:d5 brd ff:ff:ff:ff:ff:ff
[2024-05-23 14:47:02.821] root@am62xx-evm:~# ip link set mcu_mcan0 down
[2024-05-23 14:48:06.240] root@am62xx-evm:~# ip ad
[2024-05-23 14:48:08.560] 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group 0
[2024-05-23 14:48:08.560]     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
[2024-05-23 14:48:08.576]     inet 127.0.0.1/8 scope host lo
[2024-05-23 14:48:08.576]        valid_lft forever preferred_lft forever
[2024-05-23 14:48:08.576]     inet6 ::1/128 scope host 
[2024-05-23 14:48:08.576]        valid_lft forever preferred_lft forever
[2024-05-23 14:48:08.576] 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN 0
[2024-05-23 14:48:08.592]     link/ether 68:e7:4a:08:b3:c2 brd ff:ff:ff:ff:ff:ff
[2024-05-23 14:48:08.592] 3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN 0
[2024-05-23 14:48:08.608]     link/ether 70:ff:76:1e:a4:7f brd ff:ff:ff:ff:ff:ff
[2024-05-23 14:48:08.608] 4: mcu_mcan1: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qlen0
[2024-05-23 14:48:08.624]     link/can 
[2024-05-23 14:48:08.624] 5: mcu_mcan0: <NOARP,ECHO> mtu 16 qdisc pfifo_fast state DOWN group defaul0
[2024-05-23 14:48:08.624]     link/can 
[2024-05-23 14:48:08.624] 6: main_mcan0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qle0
[2024-05-23 14:48:08.640]     link/can 
[2024-05-23 14:48:08.640] 7: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN0
[2024-05-23 14:48:08.640]     link/ether 20:d7:78:b6:29:d5 brd ff:ff:ff:ff:ff:ff
[2024-05-23 14:48:08.656] root@am62xx-evm:~# ip link set mcu_mcan0 up  
[2024-05-23 14:53:51.863] root@am62xx-evm:~# ip ad
[2024-05-23 14:53:58.631] 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group 0
[2024-05-23 14:53:58.631]     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
[2024-05-23 14:53:58.647]     inet 127.0.0.1/8 scope host lo
[2024-05-23 14:53:58.647]        valid_lft forever preferred_lft forever
[2024-05-23 14:53:58.647]     inet6 ::1/128 scope host 
[2024-05-23 14:53:58.647]        valid_lft forever preferred_lft forever
[2024-05-23 14:53:58.663] 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN 0
[2024-05-23 14:53:58.663]     link/ether 68:e7:4a:08:b3:c2 brd ff:ff:ff:ff:ff:ff
[2024-05-23 14:53:58.679] 3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN 0
[2024-05-23 14:53:58.679]     link/ether 70:ff:76:1e:a4:7f brd ff:ff:ff:ff:ff:ff
[2024-05-23 14:53:58.679] 4: mcu_mcan1: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qlen0
[2024-05-23 14:53:58.695]     link/can 
[2024-05-23 14:53:58.695] 5: mcu_mcan0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP gr0
[2024-05-23 14:53:58.695]     link/can 
[2024-05-23 14:53:58.695] 6: main_mcan0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qle0
[2024-05-23 14:53:58.711]     link/can 
[2024-05-23 14:53:58.711] 7: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN0
[2024-05-23 14:53:58.727]     link/ether 20:d7:78:b6:29:d5 brd ff:ff:ff:ff:ff:ff
[2024-05-23 14:53:58.727] root@am62xx-evm:~#

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    Prodigy 60 points

    Hi,

    The state is UP now. But still there is no data.

    Thanks,
    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    If you are using the latest SDK image, and applying the dtbo correctly, you don't need any other software changes. MCU MCANs should directly work.

    Please share the snapshop of your hardware connections.

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    Prodigy 60 points

    Thanks,

    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    Hello Sai,

    You are trying to power the CAN transceiver with the AM62x SK, but power rails on AM62x MCU header are not enabled by default.

    Could you try giving out 3.3 V supply from an alternate source?

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    Prodigy 60 points

    Hi Aparna,

    In the existing setup, I have measures the voltage across CAN transceiver PINS. It is 3.3V.

    However as per your suggestion, I have provided external power supply of 3.3V. I have verified it with multimeter.
    I do not see any CAN messages. 

    Thanks,
    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    Hello Sai,

    Could you check if the MCU_MCAN0(TX) pin is active when data is being sent out ?
    Other parts of the setup looks correct to me. Make sure to use the latest SDK, as the support for MCU MCAN was added recently.

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    Prodigy 60 points

    Hi Aparna,

    Apologies for the delayed response. I am using the latest SDK. I have set "name_overlays" in the device tree. Here are my observations:

    1. When no CAN transceiver is connected, mcu_mcan0_tx is at 3.3V and mcu_mcan0_rx is at 1.1V.
    2. When CAN transceiver is connected, mcu_mcan0_tx is at 3.3V while sending the data and mcu_mcan0_rx is at 3.3V while receiving the data. Note that the CAN transceiver is powered externally as suggested. 
    3. When transceiver is connected, mcu_mcan0_rx is at 0.6V while receiving the data and when USB-UART cable is removed.
    4. Also, the ground of 42-pin User expansion header module is not proper. When ground from another circuit is connected to the ground of this header, the data transfer through main_mcan happens.

    I am not able to figure out what is causing these issues. There could be some hardware issue with the EVK. Let me know what can be done for this.

    Thanks,
    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    Hello Sai Kiran,

    Thanks for sharing. I will verify internally if the above observation is expected.

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    TI__Genius 12980 points

    Hello Sai Kiran,

    What is the current status of this thread?

    Sai Kiran Y said:
    When no CAN transceiver is connected, mcu_mcan0_tx is at 3.3V and mcu_mcan0_rx is at 1.1V.

    Without the transceiver, the CAN module will immediately flag a bit-error and communication would cease.

    Sai Kiran Y said:
    When CAN transceiver is connected, mcu_mcan0_tx is at 3.3V while sending the data and mcu_mcan0_rx is at 3.3V while receiving the data. Note that the CAN transceiver is powered externally as suggested. 

    This is correct.

    Sai Kiran Y said:
    Also, the ground of 42-pin User expansion header module is not proper. When ground from another circuit is connected to the ground of this header, the data transfer through main_mcan happens.

    Please connect to a different gnd pin. Not sure why this is seen.

    Refer here for more debug tips: www.ti.com/.../spracu9.pdf

    Regards,
    Aparna

  • 0 in reply to Aparna Patra
    Prodigy 60 points

    Hi Aparna,

    I have connected to a different ground also. I still do not see any CAN data on mcu_mcan.

    Thanks,
    Sai Kiran.

  • 0 in reply to Sai Kiran Y
    TI__Genius 12980 points

    It would be better to connect to a different EVM, looks like a hardware issue with the MCAN port.