One other thing.  Adding a second cape.  
First with Jessie where the Logic Supply cape-CBB-Serial cape CAN device 
worked but the newest uboot version doesn't.
The questions are:
Why doesn't it?
What can I do to troubleshoot this problem?

I suspect it's because the CAN hardware and can utils are now part of the 
BBB image.  Some sort of conflict with the cape-BBB-Serial and the cape's 
eeprom dtbo file linkage that wants the CAN bus pins.

Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l 
GNU/Linux
debian@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-11-06
debian@beaglebone:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 8.7 (jessie)
Release:        8.7
Codename:       jessie

debian@beaglebone:~$ cat $SLOTS
 0: P---L-   0 cape-CBB-Serial,r01,Logic Supply,cape-CBB-Serial
 1: PF----  -1
 2: PF----  -1
 3: P---L-   1 OneWire plus CANbus,00A0,AutoArtisans Inc,BB-W1-P8.11

debian@beaglebone:~$ sudo modprobe can
debian@beaglebone:~$ sudo modprobe can-dev
debian@beaglebone:~$ sudo modprobe can-raw
debian@beaglebone:~$ sudo ip link set can0 up type can bitrate 250000
debian@beaglebone:~$ sudo ifconfig can0 up

And dump the MilCAN messages on the bus.

debian@beaglebone:~$ candump can0
  can0  0200800C   [2]  85 03
  can0  0200800C   [2]  86 03
  can0  0200800C   [2]  87 03
  can0  1E601B01   [6]  00 00 00 FF FF FF


===================================================================================
And here's the latest with uboot...

debian@ebb:~$ uname -a
Linux ebb 4.14.94-ti-r94 #1 SMP PREEMPT Thu Feb 21 23:29:48 UTC 2019 armv7l 
GNU/Linux
debian@ebb:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2018-10-07

*** This version doesn't have an lsb_release nor $SLOTS



*debian@ebb:~/bb.org-overlays/src/arm$ cat 
/proc/cmdlineconsole=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait 
uboot_detected_capes=cape-CBB-Serial,BB-W1-P8.11, coherent_pool=1M 
net.ifnames=0 quiet*


Same set of steps
debian@ebb:~$ sudo modprobe can
debian@ebb:~$ sudo modprobe can-dev
debian@ebb:~$ sudo modprobe can-raw
debian@ebb:~$ sudo ip link set can0 up type can bitrate 250000
debian@ebb:~$ sudo ifconfig can0 up
debian@ebb:~$ candump can0

Nothing so ^C to get out.
^Cdebian@ebb:~$

The CAN device shows up in ifconfig. 


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/9aac50a5-630c-4904-96eb-f34d07afd79d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to