>
> Is there *current* and *correct* documentation about uBoot, uEnv.txt, capemgr,
> and CAN for the Beagle Bone Black? All of the hits I am getting doing web
> searches are for older pages, most of which do not work (or don't seem to
> work) with a current kernel (4.14.108-ti-r106). Or do I need a different
> kernel?
Both implementations read the eeprom the same way and load the
approprate overlay..
Your "written" eeprom is wrong..
Look at the examples *.dump here:
boot-scripts/device/bone/capes at master · RobertCNelson/boot-scripts · GitHub
For debugging connect a usb-serial adapter and look at what u-boot is
reading from your eeprom and trying to load:
This is what I am getting on the serial console:
U-Boot SPL 2015.10-00001-g143c9ee (Nov 06 2015 - 15:27:19)
bad magic
U-Boot 2015.10-00001-g143c9ee (Nov 06 2015 - 15:27:19 -0600), Build: jenkins-github_Bootloader-Builder-274
Watchdog enabled
I2C: ready
DRAM: 512 MiB
Reset Source: Global warm SW reset has occurred.
Reset Source: Power-on reset has occurred.
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment
Net: <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot: 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
2106 bytes read in 31 ms (65.4 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.14.108-ti-r106 ...
9925120 bytes read in 576 ms (16.4 MiB/s)
loading /boot/dtbs/4.14.108-ti-r106/am335x-boneblack.dtb ...
60317 bytes read in 59 ms (998 KiB/s)
loading /boot/initrd.img-4.14.108-ti-r106 ...
4695471 bytes read in 294 ms (15.2 MiB/s)
debug: [console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet] ...
debug: [bootz 0x82000000 0x88080000:47a5af 0x88000000] ...
Kernel image @ 0x82000000 [ 0x000000 - 0x977200 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8fb85000, end 8ffff5af ... OK
Loading Device Tree to 8fb73000, end 8fb84b9c ... OK
Starting kernel ...
[ 0.000775] timer_probe: no matching timers found
[ 0.883249] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 1.126851] omap_voltage_late_init: Voltage driver support not added
[ 1.133957] PM: Cannot get wkup_m3_ipc handle
[ 1.460685] bone_capemgr bone_capemgr: loader: failed to load slot-0 BB-CAN1:00A0 (prio 0)
[ 1.472004] hdmi-audio-codec hdmi-audio-codec.0.auto: ASoC: no source widget found for Playback
[ 1.480985] hdmi-audio-codec hdmi-audio-codec.0.auto: ASoC: Failed to add route Playback -> direct -> TX
rootfs: clean, 102623/1870848 files, 746903/7571456 blocks
My cape's eeprom is now set up to load BB-CAN1-00A0.dtbo, which exists in
/lib/firmware/.
I'm not really sure how to debug this. I can stop the normal boot process in
uboot, but I don't know what I should be doing to debug things at that point.
Where is bone_capemgr? More importantly, where is its configuration files?
How can I get it so spit out more information about what it is doing/not
doing? Find out what file(s) it is actually trying to load (eg where is it
looking for overlays)?
Grab the latest stretch-console, as it has the latest version of
u-boot and the eeprom read/debug information..
https://rcn-ee.net/rootfs/bb.org/testing/2019-06-23/stretch-console/
What do I do with these files? Do I dd one of the .img files to the uSD card?
If so, which one? (Can I in fact do that without trashing the existing root
file system?)