Open xolott opened 7 years ago
Hopefully it's still in the log:
cat /var/log/dpkg.log | grep overlays
and can you show:
dmesg | grep bone
Regards,
Hi,
The log dont have info about "overlays". The dmesg output is:
[ 0.000000] Kernel command line: console=ttyO0,115200n8 bone_capemgr.enable_partno=cape-universalh root=UUID=46c2a594-8423-44c5-8b3f-373ab153b973 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet cape_universal=enable
[ 2.280426] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,000C,1633BBBG0497'
[ 2.280536] bone_capemgr bone_capemgr: compatible-baseboard=ti,beaglebone-black - #slots=4
[ 2.320486] bone_capemgr bone_capemgr: slot #0: No cape found
[ 2.360480] bone_capemgr bone_capemgr: slot #1: No cape found
[ 2.400474] bone_capemgr bone_capemgr: slot #2: No cape found
[ 2.440476] bone_capemgr bone_capemgr: slot #3: No cape found
[ 2.440505] bone_capemgr bone_capemgr: enabled_partno PARTNO 'cape-universalh' VER 'N/A' PR '0'
[ 2.440516] bone_capemgr bone_capemgr: slot #4: override
[ 2.440530] bone_capemgr bone_capemgr: Using override eeprom data at slot 4
[ 2.440544] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,cape-universalh'
[ 2.440877] bone_capemgr bone_capemgr: initialized OK.
[ 2.858573] bone_capemgr bone_capemgr: slot #4: dtbo 'cape-universalh-00A0.dtbo' loaded; overlay id #0
[ 13.735805] systemd[1]: Set hostname to <beaglebone>.
[ 23.380544] pinctrl-single 44e10800.pinmux: could not request pin 40 (44e108a0.0) from group nxp_hdmi_bonelt_pins on device pinctrl-single
I made a patch to fix my problem, doing a 50ms delay after the change on the GPIO output value. If I use another value, less than 50ms, I experiment the same problem.
Regards
Hi,
I had a program on my beaglebone that communicate with another one throught Modbus via RS485 (with a Serial to RS485 chip). Before upgrade the bb-cape-overlays package, it run fine. But soon I upgrade it, the program became unable to communicate. I know that the UART works, but the GPIO that drive the chip doesn't
I manage to reduce the issue to this specific upgrade. My /boot/uEnv.txt file have: