Configure CAN0 with buildroot

[Andy Bergh]

Hi,

How can I use the CAN0 device with a Buildroot image?

I have a Beaglebone black rev C and have build an image using Buildroot. I used the standard beaglebone_defconfig and installed can-utils as well as iproute2.

My understanding is that the i2c2 pins should be reconfigured to be able to use the CAN0 device. In order to keep things simple (and avoid overlays) I edit the "am335x-bone-common.dtsi" file in two ways.

1) Comment out the i2c2 and insert the CAN0 pin setup:

//    i2c2_pins: pinmux_i2c2_pins {
//        pinctrl-single,pins = <
//            0x178 (PIN_INPUT_PULLUP | MUX_MODE3)    /* uart1_ctsn.i2c2_sda */
//            0x17c (PIN_INPUT_PULLUP | MUX_MODE3)    /* uart1_rtsn.i2c2_scl */
//        >;
//    };

dcan0_pins: pinmux_dcan0_pins {
        pinctrl-single,pins = <
            0x178 (PIN_OUTPUT_PULLUP | MUX_MODE2)  /* P9.20 (0x178), ddcan0_tx */
            0x17c (PIN_INPUT_PULLUP | MUX_MODE2)   /* P9.19 (0x17c), ddcan0_rx */
        >;
    };

2) Replace i2c2 with

&dcan0 {
    #address-cells = <1>;
    #size-cells = <1>;
    status = "okay";
    pinctrl-names = "default";
    pinctrl-0 = <&dcan0_pins>;
  
};

Once I log in I can not get any CAN device going anywhere:

# ifup can0

Cannot find device "can0"

# ifconfig can0 up

ifconfig: SIOCGIFFLAGS: No such device

And looking at the available networks

# ls -al /sys/class/net/

total 0

drwxr-xr-x    2 root     root             0 Jan  1 00:00 .

drwxr-xr-x   43 root     root             0 Jan  1 00:00 ..

lrwxrwxrwx    1 root     root             0 Jan  1 00:00 eth0 -> ../../devices/platform/ocp/4a100000.ethernet/net/eth0

lrwxrwxrwx    1 root     root             0 Jan  1 00:00 lo -> ../../devices/virtual/net/lo

lrwxrwxrwx    1 root     root             0 Jan  1 00:02 sit0 -> ../../devices/virtual/net/sit0

I have exhausted all resources and am truly stuck. Any information which may help will be greatly appreciated.

Thank you

[John Dammeyer]

I've only used CAN1 since the I2C for Cape ID isn't something I wanted to lose.

 

The Beagle that was running with the CAN cape had its SD card die so I lost the configuration information.  But this site here does a pretty good job of explaining what is needed.

https://www.beyondlogic.org/adding-can-to-the-beaglebone-black/

 

I did not see the same information as the web page when I looked at dmesg.

debian@beaglebone:/dev$ dmesg | grep -i can

[    0.851243] CAN device driver interface

[    0.975646] can: controller area network core (rev 20170425 abi 9)

[    0.982999] PM: Cannot get wkup_m3_ipc handle

debian@beaglebone:/dev$

 

I've got a cape from Logic Supply on this beagle but it's not found at the moment on this new 4.14 installation.  Following the web page…

 

debian@beaglebone:/dev$ config-pin p9.24 can

P9_24 pinmux file not found!

Pin has no cape: P9_24

 

Ever since $SLOTs concept was trashed on the Beagles the Logic Supply user manual for the CBB Cape is useless for installing the device but I've included the dts in case that will help.

 

At the moment I have no idea how to even ask the Beagle if it has seen the cape installed.  I can see it's connected physically.   I put the beagles into their kennel last summer and before that they spent more than a year in isolation.  Now they are out again and I'm working through Derek Molloy's book so at some point I'm sure the cape will be seen.

 

My other Beagle may well have worked with the CAN cape at one point but it doesn't have the cape installed.

 

debian@ebb:~$ dmesg | grep -i can

[    1.015868] CAN device driver interface

[    1.017132] c_can_platform 481cc000.can: c_can_platform device registered (regs=fa1cc000, irq=42)

[    1.018405] c_can_platform 481d0000.can: c_can_platform device registered (regs=fa1d0000, irq=43)

[    1.160062] can: controller area network core (rev 20170425 abi 9)

[    1.167640] PM: Cannot get wkup_m3_ipc handle

debian@ebb:~$ config-pin p9.24 can

debian@ebb:~$ config-pin p9.26 can

debian@ebb:~$ sudo /sbin/ip link set can1 up type can bitrate 250000

[sudo] password for debian:

debian@ebb:~$

 

This one doesn't complain.  Again, I've completely forgotten what I've done.

 

John

 

 

 

--
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 beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/01f7e77d-c061-4ade-954d-94d29dcabf80n%40googlegroups.com.

[Andy Bergh]

Thank you for the reply and info John.

The solution provided (in the link as well) is using the debian distribution for the beaglebone, which has a ton of packages to assist with the configuration of the BBB. My buildroot image does not even have a package manager! It is less than 80MB in total size. I do not have access to modules and features such as cape_mgr, pin-config ect.

My understanding is that I have to edit the default device tree source file to enable the CAN device, which is the part I am not able to do.

Regards

You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/N3XgXZ9NHv4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/0bec01d74899%24dff0dee0%249fd29ca0%24%40autoartisans.com.

[Andy Bergh]

Hi,

For if ever anyone runs into this problem, setting the following in the linux-menuconfig file fixes the problem (to load the can device):

CONFIG_CAN_C_CAN=y
CONFIG_CAN_C_CAN_PLATFORM=y

Cheers

[johnd]

Which OS version?

Sent from my Samsung S10

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAAmck7W2fqq4Ri-jAR%2B8sRjFdoTxqrh7NJjfe6QosX0GNDXaBQ%40mail.gmail.com.

[Andy Bergh]

I am not sure what you mean with OS version? This is a buildroot OS with the Linux kernel version 4.19.63

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/609ebc12.1c69fb81.c6f46.99e1SMTPIN_ADDED_MISSING%40gmr-mx.google.com.

[johnd]

Ah. So it doesn't apply to Debian. Thanks

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAAmck7W-Si0EXK8-O%2B8C%2B0rEJ-KtJdUco0xmwof-GqOcpZZ2%2BA%40mail.gmail.com.

[Robert Nelson]

On Fri, May 14, 2021 at 1:46 PM johnd <jo...@autoartisans.com> wrote:
>
> Ah. So it doesn't apply to Debian. Thanks

For Debian, it's enabled out of the box, just use config-pin to change
it from i2c to can..

If it doesn't work, report back with:

sudo /opt/scripts/tools/version.sh

Regards

--
Robert Nelson
https://rcn-ee.com/

[John Dammeyer]

So here's the results of version.sh from both beagles. The rev 141 doesn't see the cape_CBB_Serial-r01 from Logic Supply as shown in the photo. For convenience I've also included the side by side compare of the two files.

Not sure why this install doesn't see the cape.
============================================================================
Last login: Fri May 14 00:16:10 2021 from 192.168.0.137
debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian:
git:/opt/scripts/:[81709cddd6994c0c6895b5d31a73ac459f252fa0]
eeprom:[A335BNLT00C02814BBBK0472]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 2018.09-00002-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500)]:[location: dd MBR]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.09-00002-g0b54a51eee]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06)]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2015.01-00001-gb2412df]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack.dts]
kernel:[4.14.108-ti-r141]
nodejs:[v6.17.0]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
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.14.20210416.0-0~stretch+20210416]
pkg:[bb-customizations]:[1.20210225.0-0~stretch+20210225]
pkg:[bb-usb-gadgets]:[1.20200504.0-0~stretch+20200504]
pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~stretch+20200813]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~stretch+20200716]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~stretch+20200305]
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 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait fixrtc coherent_pool=1M net.ifnames=0 quiet]
dmesg | grep remote
[ 0.960861] remoteproc remoteproc0: wkup_m3 is available
[ 1.303024] remoteproc remoteproc0: powering up wkup_m3
[ 1.303049] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148
[ 1.303304] remoteproc remoteproc0: remote processor wkup_m3 is now up
dmesg | grep pru
dmesg | grep pinctrl-single
[ 0.728816] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
dmesg | grep gpio-of-helper
[ 0.730005] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 005: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 001 Device 004: ID 04d9:048e Holtek Semiconductor, Inc. Optical Mouse
Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END
debian@beaglebone:~$
============================================================================================
I then moved the SD card from the other BBB over to this one and the results are below. Should probably bring it up to the same revision 141 from 136.
============================================================================================
Last login: Fri May 14 01:14:14 2021 from 192.168.0.137
debian@ebb:~$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian:
git:/opt/scripts/:[f495239e456d8ec99554a35ae04b33ddce5c26cc]
eeprom:[A335BNLT00C02814BBBK0472]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.09-00002-g0b54a51eee]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2015.01-00001-gb2412df]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack.dts]
kernel:[4.14.108-ti-r136]
nodejs:[v6.17.0]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
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.14.20210416.0-0~stretch+20210416]
pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~stretch+20200813]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~stretch+20200716]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~stretch+20200305]
groups:[debian : debian adm kmem dialout cdrom floppy sudo audio dip video plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep admin spi tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait fixrtc coherent_pool=1M net.ifnames=0 quiet]
dmesg | grep remote
[ 0.997836] remoteproc remoteproc0: wkup_m3 is available
[ 1.334504] remoteproc remoteproc0: powering up wkup_m3
[ 1.334528] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168
[ 1.334783] remoteproc remoteproc0: remote processor wkup_m3 is now up
dmesg | grep pru
dmesg | grep pinctrl-single
[ 0.765028] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
dmesg | grep gpio-of-helper
[ 0.766227] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END
========================================================================


Also why the rev 141 SD Card when installed into the beagle that had the rev 136 hangs with:
[ 0.957781] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
[ 1.050633] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0xb00
[ 1.065255] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
[ 1.074698] print_req_error: I/O error, dev mmcblk0, sector 0
[ 1.107216] mmcblk0: error -84 transferring data, sector 1, nr 7, cmd response 0x900, card status 0x0
Till it lands in BusyBox. It's like it has trouble with the sd card. Swap them back and both systems boot.



Thanks for looking
John

> -----Original Message-----
> From: Robert Nelson [mailto:robert...@gmail.com]
> Sent: May-14-21 11:50 AM
> To: Beagle Board
> Cc: John Dammeyer
> Subject: Re: [beagleboard] Configure CAN0 with buildroot
>

[Robert Nelson]

On Fri, May 14, 2021 at 4:58 PM John Dammeyer <jo...@autoartisans.com> wrote:
>
> So here's the results of version.sh from both beagles. The rev 141 doesn't see the cape_CBB_Serial-r01 from Logic Supply as shown in the photo. For convenience I've also included the side by side compare of the two files.
>
> Not sure why this install doesn't see the cape.
> ============================================================================
> Last login: Fri May 14 00:16:10 2021 from 192.168.0.137
> debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
> [sudo] password for debian:
> git:/opt/scripts/:[81709cddd6994c0c6895b5d31a73ac459f252fa0]
> eeprom:[A335BNLT00C02814BBBK0472]
> model:[TI_AM335x_BeagleBone_Black]
> dogtag:[BeagleBoard.org Debian Image 2018-10-07]
> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 2018.09-00002-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500)]:[location: dd MBR]
> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.09-00002-g0b54a51eee]:[location: dd MBR]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 2015.01-00001-gb2412df (Jan 29 2015 - 15:01:06)]:[location: dd MBR]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2015.01-00001-gb2412df]:[location: dd MBR]

Oh fun, 2018 wth 2015 causing issues..

how set in stone are your for "2018-10-07" Release?

Regards,

[Robert Nelson]

If you want to keep: "2018-10-07" here's what i would do:

#Good bye 2015 bootloader:

sudo apt update
sudo apt install bb-u-boot-am335x-evm
cd /opt/u-boot/bb-u-boot-am335x-evm/
sudo ./install.sh

#Latest v4.14.x-ti:

cd /opt/scripts/tools/
sudo ./update_kernel.sh

# and reboot..

now run:

sudo /opt/scripts/tools/version.sh

We should see a more friendly setup. ;)

[John Dammeyer]

Hi Robert,
Not that set in stone really. Just that the last time I did one of those "you must upgrade to get support" I ended up buying a new edition of Derek Molloy's book because the $SLOTs stuff vanished which also made 5 other books I have on the Beagle pointless for the most part.

Between editions and versions my 4DCape LCD display also no longer worked so it's in the box of useless LCD displays along with the Manga 1 (never worked right) and Manga2.

How much of the step by step instructions in Derke Molloy's (c) 2019 2nd edition are voided and how will I know what is supposed to work and not.

I've done the following.

cd /opt/scripts/tools/
sudo ./update_kernel.sh
# and reboot..
now run:
sudo /opt/scripts/tools/version.sh

>We should see a more friendly setup. ;)

=============================================================

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian:
git:/opt/scripts/:[81709cddd6994c0c6895b5d31a73ac459f252fa0]
eeprom:[A335BNLT00C02814BBBK0472]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]

bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 2019.04-g10968f0 (Feb 19 2021 - 21:40:51 +0000)]:[location: dd MBR]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-g10968f0]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 2019.04-g10968f0 (Feb 19 2021 - 21:40:51 +0000)]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-g10968f0]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-14-TI-00A0]
UBOOT: Loaded Overlay:[BB-ADC-00A0]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0]
UBOOT: Loaded Overlay:[cape-CBB-Serial-r01]

kernel:[4.14.108-ti-r141]
nodejs:[v6.17.0]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
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.14.20210416.0-0~stretch+20210416]
pkg:[bb-customizations]:[1.20210225.0-0~stretch+20210225]
pkg:[bb-usb-gadgets]:[1.20200504.0-0~stretch+20200504]
pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~stretch+20200813]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~stretch+20200716]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~stretch+20200305]
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 quiet]
dmesg | grep remote
[ 1.096197] remoteproc remoteproc0: wkup_m3 is available
[ 1.440935] remoteproc remoteproc0: powering up wkup_m3
[ 1.441056] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148
[ 1.445403] remoteproc remoteproc0: remote processor wkup_m3 is now up

dmesg | grep pru
dmesg | grep pinctrl-single

[ 0.796756] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
dmesg | grep gpio-of-helper
[ 0.809620] gpio-of-helper ocp:cape-universal: ready
lsusb

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END
debian@beaglebone:~$
==================================================================

Sees the cape now. Mouse and keyboard no longer work. In fact USB doesn't work at all.
John

[Robert Nelson]

Does USB work after 30-45 seconds? If so, still trying to debug that..

[John Dammeyer]

I moved the MicroSD card over to the other Beagle.  Booted and USB mouse and keyboard (Logitech wireless) work.  The Logitech wireless was not discovered on the other Beagle. 

 

I think it may be sick. 

 

 

Last login: Fri May 14 18:11:06 2021 from 192.168.0.137

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh

[sudo] password for debian:

git:/opt/scripts/:[81709cddd6994c0c6895b5d31a73ac459f252fa0]

eeprom:[A335BNLT00C02716BBBK0E8D]

model:[TI_AM335x_BeagleBone_Black]

dogtag:[BeagleBoard.org Debian Image 2018-10-07]

bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 2019.04-g10968f0 (Feb 19 2021 - 21:40:51 +0000)]:[location: dd MBR]

bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-g10968f0]:[location: dd MBR]

bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 2019.04-00002-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)]:[location: dd MBR]

bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-00002-gbb4af0f50f]:[location: dd MBR]

UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]

UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-14-TI-00A0]

UBOOT: Loaded Overlay:[BB-ADC-00A0]

UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]

UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0]

kernel:[4.14.108-ti-r141]

nodejs:[v6.17.0]

/boot/uEnv.txt Settings:

uboot_overlay_options:[enable_uboot_overlays=1]

uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]

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.14.20210416.0-0~stretch+20210416]

pkg:[bb-customizations]:[1.20210225.0-0~stretch+20210225]

pkg:[bb-usb-gadgets]:[1.20200504.0-0~stretch+20200504]

pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~stretch+20200813]

pkg:[kmod]:[23-2rcnee1~stretch+20171005]

pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~stretch+20200716]

pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~stretch+20200305]

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 coherent_pool=1M net.ifnames=0 quiet]

dmesg | grep remote

[    1.108680] remoteproc remoteproc0: wkup_m3 is available

[    1.453877] remoteproc remoteproc0: powering up wkup_m3

[    1.453993] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148

[    1.458014] remoteproc remoteproc0: remote processor wkup_m3 is now up

[  165.380047] remoteproc remoteproc1: 4a334000.pru is available

[  165.395267] remoteproc remoteproc2: 4a338000.pru is available

dmesg | grep pru

[  163.347677] pruss 4a300000.pruss: creating PRU cores and other child platform devices

[  165.380047] remoteproc remoteproc1: 4a334000.pru is available

[  165.380228] pru-rproc 4a334000.pru: PRU rproc node /ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed successfully

[  165.395267] remoteproc remoteproc2: 4a338000.pru is available

[  165.395389] pru-rproc 4a338000.pru: PRU rproc node /ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfully

dmesg | grep pinctrl-single

[    0.796710] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568

dmesg | grep gpio-of-helper

[    0.809442] gpio-of-helper ocp:cape-universal: ready

lsusb

Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver

Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

END

debian@beaglebone:~$

 

I then created an sd card with this

bone-debian-10.3-console-armhf-2020-04-06-1gb.img.xz

Login prompt on screen with USB keyboard functioning. 

This is without the CAN Cape.  I've attached the serial port terminal log.

 

Next I'll shut it down and put the cape back.

 

From the descriptions on https://beagleboard.org/latest-images I can't figure out what the latest graphical desktop image is for the BBB.

 

Thanks

John

 

From: Robert Nelson [mailto:robert...@gmail.com]
Sent: May-14-21 6:45 PM
To: John Dammeyer
Cc: Beagle Board
Subject: Re: [beagleboard] Configure CAN0 with buildroot

 

Does USB work after 30-45 seconds? If so, still trying to debug that..

[Robert Nelson]

There really isn't an official lxqt release, it just was too un-useful:

https://rcn-ee.net/rootfs/bb.org/testing/2021-04-27/

[John Dammeyer]

With the Cape plugged into the console version it gets to a certain point and then shuts off.

 

 

U-Boot SPL 2019.04-g10968f0 (Feb 19 2021 - 21:40:51 +0000)

Trying to boot from MMC2

Loading Environment from EXT4... ** File not found /boot/uboot.env **

 

** Unable to read "/boot/uboot.env" from mmc0:1 **

 

 

U-Boot 2019.04-g10968f0 (Feb 19 2021 - 21:40:51 +0000)

 

CPU  : AM335X-GP rev 2.1

I2C:   ready

DRAM:  512 MiB

No match for driver 'omap_hsmmc'

No match for driver 'omap_hsmmc'

Some drivers were not found

Reset Source: Power-on reset has occurred.

RTC 32KCLK Source: External.

MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1

Loading Environment from EXT4... ** File not found /boot/uboot.env **

 

** Unable to read "/boot/uboot.env" from mmc0:1 **

Board: BeagleBone Black

<ethaddr> not set. Validating first E-fuse MAC

BeagleBone Black:

BeagleBone Cape EEPROM: found EEPROM at address: 0x54

BeagleBone Cape EEPROM: debug part_number field:[cape-CBB-Serial]

BeagleBone Cape EEPROM: debug part_number field HEX:[636170652d4342422d53657269616c]

BeagleBone Cape EEPROM: debug version field HEX:[7230310]

BeagleBone Cape EEPROM: 0x54: cape-CBB-Serial-r01.dtbo [0x296d72f]

BeagleBone Cape EEPROM: no EEPROM at address: 0x55

BeagleBone Cape EEPROM: no EEPROM at address: 0x56

BeagleBone Cape EEPROM: no EEPROM at address: 0x57

Net:   eth0: MII MODE

cpsw, usb_ether

Press SPACE to abort autoboot in 0 seconds

board_name=[A335BNLT] ...

board_rev=[00C0] ...

switch to partitions #0, OK

mmc0 is current device

SD/MMC found on device 0

switch to partitions #0, OK

mmc0 is current device

Scanning mmc 0:1...

gpio: pin 56 (gpio 56) value is 0

gpio: pin 55 (gpio 55) value is 0

gpio: pin 54 (gpio 54) value is 0

gpio: pin 53 (gpio 53) value is 1

switch to partitions #0, OK

mmc0 is current device

gpio: pin 54 (gpio 54) value is 1

Checking for: /uEnv.txt ...

Checking for: /boot.scr ...

Checking for: /boot/boot.scr ...

Checking for: /boot/uEnv.txt ...

gpio: pin 55 (gpio 55) value is 1

2062 bytes read in 47 ms (42 KiB/s)

Loaded environment from /boot/uEnv.txt

Checking if uname_r is set in /boot/uEnv.txt...

gpio: pin 56 (gpio 56) value is 1

Running uname_boot ...

loading /boot/vmlinuz-4.19.94-ti-r42 ...

10095592 bytes read in 674 ms (14.3 MiB/s)

debug: [enable_uboot_overlays=1] ...

debug: [enable_uboot_cape_universal=1] ...

debug: [uboot_base_dtb_univ=am335x-boneblack-uboot-univ.dtb] ...

uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot-univ.dtb] ...

uboot_overlays: Switching too: dtb=am335x-boneblack-uboot-univ.dtb ...

loading /boot/dtbs/4.19.94-ti-r42/am335x-boneblack-uboot-univ.dtb ...

162266 bytes read in 152 ms (1 MiB/s)

uboot_overlays: [fdt_buffer=0x60000] ...

uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...

867 bytes read in 44 ms (18.6 KiB/s)

uboot_overlays: loading /lib/firmware/cape-CBB-Serial-r01.dtbo ...

2245 bytes read in 88 ms (24.4 KiB/s)

uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...

1584 bytes read in 315 ms (4.9 KiB/s)

uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...

4915 bytes read in 338 ms (13.7 KiB/s)

uboot_overlays: loading /lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo ...

3801 bytes read in 278 ms (12.7 KiB/s)

uboot_overlays: [uboot_detected_capes=cape-CBB-Serial,] ...

loading /boot/initrd.img-4.19.94-ti-r42 ...

6585227 bytes read in 460 ms (13.7 MiB/s)

debug: [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 lpj=1990656 rng_core.default_quality=100 quiet] ...

debug: [bootz 0x82000000 0x88080000:647b8b 88000000] ...

## Flattened Device Tree blob at 88000000

   Booting using the fdt blob at 0x88000000

   Loading Ramdisk to 8f9b8000, end 8ffffb8b ... OK

   Loading Device Tree to 8f92c000, end 8f9b7fff ... OK

 

Starting kernel ...

 

[    0.002172] timer_probe: no matching timers found

[    0.196489] l4_wkup_cm:clk:0010:0: failed to disable

 

 

 

 

 

[John Dammeyer]

> -----Original Message-----
> From: Robert Nelson [mailto:robert...@gmail.com]

> > I moved the MicroSD card over to the other Beagle. Booted and USB mouse and keyboard (Logitech wireless) work. The Logitech
> wireless was not discovered on the other Beagle.
> >
> > I think it may be sick.
> >

> > From the descriptions on https://beagleboard.org/latest-images I can't figure out what the latest graphical desktop image is for the
> BBB.
>
> There really isn't an official lxqt release, it just was too un-useful:
>
> https://rcn-ee.net/rootfs/bb.org/testing/2021-04-27/
>
> Regards,
>
> --
> Robert Nelson

Been an interesting weekend with many different versions flashed (or sometimes not) into the eMMC.
I have this currently running well from the 32MB SD card from the img link above.
debian@beaglebone:~$ uname -a
Linux beaglebone 4.19.94-ti-r63 #1buster SMP PREEMPT Fri May 14 16:42:32 UTC 2021 armv7l GNU/Linux

There is on issue I've run into that has caused a lot of grief and retries. That's the behavior of the USB port on and after boot.
I have two monitors and an IOGEAR GUS402 USB 2.0 peripheral sharing device. Press a button and it switches the keyboard and mouse between my main workstation and whatever module I'm currently working on; BBB, Pi3, Pi4, PiZeroW.
Between that and the BBB I've been using a 4 port USB hub. One from ANKER which is a USB 3.0 hub and one from INSIGNIA a 4 port USB 2.0 hub with separate power adaptor. The BBB doesn't like the 3.0 hub very much.

Using the 4 port USB 2.0 hub if the IOGEAR isn't switched to present the keyboard and mouse to the Beagle during boot after that, although the screen shows the desktop, the mouse pointer remains in the middle of the screen and mouse and keyboard don't work.

If I've booted with the switch set so the keyboard and mouse are visible to the BBB then after that I can switch back and forth between the workstation and the beagle.

I've attached the serial port boot log and also the dmesg log that shows usb isn't ready. What's missing so that it will find a usb device when it's plugged in?

Thanks
John

[John Dammeyer]

Oh and just for interest. Boot a Pi3 with Linux raspberrypi 5.10.17-v7+ and nothing in the USB port and screen shows up as expected. Plug same 4 port hub with the connect the the USB switch and a 4GB USB drive. Then press the button to change from workstation to Pi and about 5 seconds later the mouse and keyboard work nd in the /media/pi/Transcend are the files on the USB drive.

On the Beagle the little blue LED on the USB drive doesn't even light up.

I kind of think the BBB should be able to do this too.

Thanks
John

> --
> 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 beagleboard...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/beagleboard/0e6201d74abe%2486225e80%2492671b80%24%40autoartisans.com.

[Robert Nelson]

On Sun, May 16, 2021 at 8:55 PM John Dammeyer <jo...@autoartisans.com> wrote:
>
> Oh and just for interest. Boot a Pi3 with Linux raspberrypi 5.10.17-v7+ and nothing in the USB port and screen shows up as expected. Plug same 4 port hub with the connect the the USB switch and a 4GB USB drive. Then press the button to change from workstation to Pi and about 5 seconds later the mouse and keyboard work nd in the /media/pi/Transcend are the files on the USB drive.
>
> On the Beagle the little blue LED on the USB drive doesn't even light up.
>
> I kind of think the BBB should be able to do this too.

Is the USB hub powered externally? How are you powering the Beagle?

[John Dammeyer]

With a 2A 5V supply. No capes installed. Only Ethernet connected and the 4 port USB 2.0 hub is also powered with a 2A supply
John

> -----Original Message-----
> From: Robert Nelson [mailto:robert...@gmail.com]

> Sent: May-16-21 7:05 PM
> To: John Dammeyer
> Cc: Beagle Board

[John Dammeyer]

Oh and HDMI to LG 1080P IPS LED monitor.

The Pi displays the desktop and menu bar in 45 seconds from power on. The hub shows it's powered with a small blue LED but the Transcend USB drive is not lit up. About 5 seconds later the blue LED inside the Transcend blips and then turns on. And the file explorer shows up on the desktop. All about 5 to 8 seconds.

After that, I can switch back and forth between systems. As can the Beagle if the keyboard/mouse switch was plugged into the USB port.

I'll try it with just the Transcend USB drive. Maybe then it will realize the USB port is active.

John


> -----Original Message-----
> From: beagl...@googlegroups.com [mailto:beagl...@googlegroups.com] On Behalf Of John Dammeyer

> --
> 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 beagleboard...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/beagleboard/0e7901d74aca%24d8d90730%248a8b1590%24%40autoartisans.com.

[John Dammeyer]

So the trick is to also have a USB 4GB drive plugged into the 4 port hub. At just under 3 minutes (compared to 42 seconds for the Pi3) the little blue light on the Transcend blinks and the menu bar shows up on the HDMI display and up pops the little list of what removable drives are available.

Then, press the button on the USB switch to move the keyboard and mouse over to the BBB and bingo! Mouse motion.

So this test version of the LXQT 2021 Debian Buster (as do pretty well all the older versions) have an issue with throwing out the USB port if nothing was found while booting.

This time we have:
starting USB...
USB0: scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

Compared to before where there's only the 4 port USB 2.0 Hub:
starting USB...
USB0: scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

Hopefully the reason for this will be easy to fix.

Meanwhile I can now get back to trying to get the CAN1 bus stuff running. I have a fairly long document I'm putting together that explains how to get all this working.

> https://groups.google.com/d/msgid/beagleboard/0e7a01d74acc%24477e6ad0%24d67b4070%24%40autoartisans.com.