On Mon, Mar 4, 2019 at 5:54 AM <[email protected]> wrote:
>
>
>
> On Sunday, March 3, 2019 at 6:05:51 PM UTC-8, RobertCNelson wrote:
>>
>> On Sun, Mar 3, 2019 at 7:00 PM <[email protected]> wrote:
>> >
>> >
>> > 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?
>>
>> troubleshoot: first let's look at your serial boot log with both
>> cape's plugged in..
>>
>> That cape's can port is defined by:
>>
>> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/cape-CBB-Serial-r01.dts#L92-L96
>>
>> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/cape-CBB-Serial-r01.dts#L120-L125
>>
>> I'd expect to see a "can" node just by running
>>
>> sudo ifconfig -a
>
>
> Yes. I had done that. That's why I was a bit confused. It appears to be
> there. I can reboot the Jessie 8.7 and grab the ifconfig from it if that
> will help.
>
> can0: flags=128<NOARP> mtu 16
> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10
> (UNSPEC)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device interrupt 42
>
> can1: flags=128<NOARP> mtu 16
> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10
> (UNSPEC)
> RX packets 0 bytes 0 (0.0 B)
> RX errors 0 dropped 0 overruns 0 frame 0
> TX packets 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
> device interrupt 43
>
>>
>> I have two of those Logic Supply cape's so i'll take a look at them tomorrow.
>>
> One point that may or not be important. Derek Malloy's second edition uses
> config-pin -q P1.28 to ask for the P1_28 Mode.
> All I get back is
>
> Pin is not modifiable: P1_28
>
> Which suggests his section on CAN (pages 388-394) does not agree with the
> current BBB Linux version. I did try that with the CAN board not plugged in
> and got the same result.
P1_x/P2_x = PocketBeagle
P8_x/P9_x = BeagleBone, Black, Green, Wireless, Blue...
So with 4.14.94-ti-r94 I'm seeing this:
sudo depmod -a
sudo update-initramfs -uk `uname -r`
debug: process_cape_part_number:[cape-CBB-Serial]
debug: process_cape_part_number:[636170652D4342422D53657269616C]
BeagleBone: cape eeprom: i2c_probe: 0x54:
/lib/firmware/cape-CBB-Serial-r01.dtbo [0x296d72f]
debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[36a476c67f707ba2698bfb30452ebd2951162ce2]
eeprom:[A335BNLT000C1830BBBG0785]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2019-03-03]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
2018.09-00002-g08ae12f051]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2018.09-00002-g0b54a51eee]:[location: dd MBR]
kernel:[4.14.94-ti-r94]
nodejs:[v6.17.0]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.4.20190227.0-0rcnee0~stretch+20190227]
pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.4-git20190107.0-0rcnee0~stretch+20190108]
pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm
eqep admin spi tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait
uboot_detected_capes=cape-CBB-Serial, coherent_pool=1M net.ifnames=0]
dmesg | grep pinctrl-single
[ 0.923512] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
dmesg | grep gpio-of-helper
[ 0.935203] gpio-of-helper ocp:cape-universal: ready
debian@beaglebone:~$ dmesg | grep can
[ 2.178645] c_can_platform 481cc000.can: c_can_platform device
registered (regs=fa1cc000, irq=42)
[ 2.188942] c_can_platform 481d0000.can: c_can_platform device
registered (regs=fa1d0000, irq=43)
[ 2.779238] can: controller area network core (rev 20170425 abi 9)
debian@beaglebone:~$ sudo ifconfig -a
can0: flags=128<NOARP> mtu 16
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
txqueuelen 10 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 42
can1: flags=128<NOARP> mtu 16
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
txqueuelen 10 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 43
Regards,
--
Robert Nelson
https://rcn-ee.com/
--
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/CAOCHtYj1c4dFxuAKTxbh9vb%3Djj15nZ711ZFCiZ%3DR_n%2BDo1CpvA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
