MangOH yellow CAN Iot Bus not working

Antoine · September 18, 2020, 1:47pm

Hello, i’m a beginner in mangOH card developping.

I have a mangOH yellow with this card module to communicate using CAN protocol :

But unfortunately i get a “busheavy” message status when i’m trying to send message trough the CAN (i’m using PCAN-View)

The question is maybe obvious but do i have to install some drivers or are they already setting up on the mangOH yellow ?
If yes do i have to follow this tutorial even if it is for a mangOH green card ? :

Thanks by advance for your replies.

Ps: sorry if my english is bad i’m french.

jyijyi · September 18, 2020, 2:02pm

I never tried before, but i saw the last few line of this file, you need to uncomment the last line to have the CAN driver

github.com

mangOH/mangOH/blob/master/green.sdef

//--------------------------------------------------------------------------------------------------
// mangOH system definition for the mangOH Green board.
//
// Copyright (C) Sierra Wireless Inc.
//--------------------------------------------------------------------------------------------------

buildVars:
{
    MANGOH_BOARD = green
}


#include "shared.sdef"


apps:
{
    $CURDIR/apps/GpioExpander/gpioExpanderService/gpioExpanderServiceGreen
    $CURDIR/apps/MuxControl/muxCtrlService/muxCtrlService
    $CURDIR/apps/MuxControl/tools/muxCtrlTools

This file has been truncated. show original

Antoine · September 24, 2020, 8:15am

Hi @jyijyi, thanks for you response !

I just forget to update the software (it was very old) to 3.0.0.

After the upgrade i see a canpoen app on my mangOH yellow, but unfortunately it doesn’t want to start.
I performed a “logread -f” to see what is happening and i get these errors :

Sep 24 10:08:35 swi-mdm9x28-wp user.err Legato: =ERR= | canopen_dbg[4715] | ifconfig: SIOCGIFFLAGS: No such device
Sep 24 10:08:35 swi-mdm9x28-wp user.debug kernel: [ 1468.329510] gpio_map_name_to_num: find GPIO 38
Sep 24 10:08:35 swi-mdm9x28-wp user.debug kernel: [ 1468.329534] gpio-38 (sysfs): gpiod_request: status -16
Sep 24 10:08:35 swi-mdm9x28-wp user.debug kernel: [ 1468.329544] export_store: status -16
Sep 24 10:08:35 swi-mdm9x28-wp user.err Legato: =ERR= | canopen_dbg[4715]/components T=main | canbus.c WriteToSysfs() 196 | Error writing to sysfs file ‘/sys/class/gpio/export’ (Device or resource busy).
Sep 24 10:08:35 swi-mdm9x28-wp user.err Legato: =ERR= | canopen_dbg[4715]/components T=main | canbus.c WriteToSysfs() 196 | Error writing to sysfs file ‘/sys/class/gpio/export’ (Device or resource busy).
Sep 24 10:08:35 swi-mdm9x28-wp user.err Legato: =ERR= | canopen_dbg[4715]/components T=main | canbus.c insmod() 165 | Unable to load can module /legato/systems/current/modules/can_iot.ko errno: Exec format error

Did anyone has an idea ?

jyijyi · September 24, 2020, 8:44am

GPIO38 in kernel means GPIO2 of the module.

From the script below, I believe it needs to control GPIO2 , but it failed in your log:

github.com

mangOH/mangOH/blob/master/linux_kernel_modules/can_common/start_can.sh

#!/bin/sh

# It seems that taking the IoT card out of reset fails in the core
# mangOH driver - but placing things after user-space has fully started
# and through the SWI gpiolib-sysfs code works - TODO fix and move into
# the core driver so no shell script is needed.
# Thus, we remove the inserted chip driver and bring it back.

usage () {
    echo "\"$0 board [slot]\" where board is \"green\" or \"red\" or \"yellow\" and slot is \"0\" or \"1\""
}

if [ "$#" -lt 1 ]; then
    usage
    exit 1
fi

if [ "$#" -gt 2 ]; then
    usage
    exit 1

This file has been truncated. show original

What is the return of AT+WIOCFG?
Also did you have the mcp251x kernel driver in the module?
( you can find by "find / -name “mcp251x*”)

Antoine · September 24, 2020, 8:55am

What do you mean by “AT+WIOCFG” ?

Is it the expected output ? :

root@swi-mdm9x28-wp:~# find / -name “mcp251x*”
/lib/modules/3.18.140/kernel/drivers/net/can/spi/mcp251x.ko

jyijyi · September 24, 2020, 9:15am

root@swi-mdm9x28-wp:~# microcom /dev/ttyAT
at+wiocfg?
+WIOCFG: 2,16,0,0,1,0,0
+WIOCFG: 4,0,0,0,1,0,0
+WIOCFG: 6,0,0,0,1,0,0
+WIOCFG: 7,16,0,0,1,0,0
+WIOCFG: 8,16,0,0,1,0,0
+WIOCFG: 13,16,0,0,1,0,0
+WIOCFG: 21,16,0,0,1,0,0
+WIOCFG: 22,16,0,0,1,0,0
+WIOCFG: 23,16,0,0,1,0,0
+WIOCFG: 24,16,0,0,1,0,0
+WIOCFG: 25,16,0,0,1,0,0
+WIOCFG: 28,16,0,0,1,0,0
+WIOCFG: 29,16,0,0,1,0,0
+WIOCFG: 30,16,0,0,1,0,0
+WIOCFG: 31,16,0,0,1,0,0
+WIOCFG: 32,16,0,0,1,0,0
+WIOCFG: 33,16,0,0,1,0,0
+WIOCFG: 35,16,0,0,1,0,0
+WIOCFG: 42,16,0,0,1,0,0

OK

(ctrl+x to quit the program)

Antoine · September 24, 2020, 9:23am

When i do the “microcom /dev/ttyAT” command, nothing appears.

jyijyi · September 24, 2020, 9:24am

What do you mean nothing appears?
Do you enter AT command there?

BTW, do you see modem port in device manager in Windows platform?
Or do you see /dev/ttyUSB2 in host linux PC ?

Antoine · September 24, 2020, 9:28am

I performed your command and nothing happend on the terminal :
I did this :

I am on Windows and i have this one on device manager :

jyijyi · September 24, 2020, 9:30am

you need to type AT+WIOCFG? by yourself after “microcom /dev/ttyAT”

Antoine · September 24, 2020, 9:31am

Oh sorry i didn’t undestand that i have to enter “at+wiocfg?”

Here is the output :

Just to know, what is the goal of this program ?

jyijyi · September 24, 2020, 9:38am

this is to check the GPIO2 status.
BTW, can you type following in console:
echo 2 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio2/direction
echo 1 > /sys/class/gpio/gpio2/value
modprobe mcp251x

Antoine · September 24, 2020, 9:40am

I get this :

root@swi-mdm9x28-wp:~# echo 2 > /sys/class/gpio/export
sh: write error: Device or resource busy

For the 2 others command it didn’t output any error message

jyijyi · September 24, 2020, 9:48am

Then seems the GPIO2 is working fine.
How about the following?:
modprobe mcp251x
kmod load can_iot.ko

Antoine · September 24, 2020, 9:52am

Are you sure that another program is not still using the GPIO2 ?

root@swi-mdm9x28-wp:~# modprobe mcp251x
root@swi-mdm9x28-wp:~# kmod load can_iot.ko
Could not load the required module, can_iot.ko. (LE_NOT_FOUND)
See the device log for details.

jyijyi · September 24, 2020, 9:57am

Seems your platform does not have the CAN driver.
You can try to search by:
find / -name “can_iot.ko"

Antoine · September 24, 2020, 9:58am

root@swi-mdm9x28-wp:~# find -name “can_iot.ko”
root@swi-mdm9x28-wp:~#

jyijyi · September 24, 2020, 9:59am

that is why the driver cannot be loaded.
You need to rebuild the mangoh yellow layer and add the following in yellow.sdef:

// Uncomment to include support for the CAN IoT card
#include “sinc/can_iot_card.sinc”

Antoine · September 24, 2020, 10:01am

How can i rebuild mangoh yellow layer ?

Can i do that using Octave ?

jyijyi · September 24, 2020, 10:35am

There are steps here

Here is an example on how to build for mango red

Topic		Replies	Views
CAN IoT Card driver mangOH Red	54	7013	March 5, 2021
MangOH project: how to use	2	569	April 6, 2021
Bootstrap CAN Bus application Open Connected Car Challenge	7	1476	April 16, 2019
Talon CAN bus IoT extender + mangOH green doesn't work?!	0	323	March 11, 2021
Cannot find device Can0 mangOH Green	101	3905	March 22, 2021

MangOH yellow CAN Iot Bus not working

Related topics