Debian login problem after loading PRUCookbook

General Discussion
1

I am running BBB stand alone with LCD touch screen via HDMI port, keyboard etc., all was working, my code working, able to log into the BBB as root with password and get the Debian GUI. Now when it starts up i enter the password but instead of going to the GUI it waits a second then the screen goes black for a second then back to the login screen. I noticed this happening after I added the PRUCookbook " git clone GitHub - MarkAYoder/PRUCookbook: This is a cookbook of the Programmable Realtime Unit on the BeagleBoard" . Some examples from the cookbook run, I can get the hello.pru0.c program to work and blink the user LED so the cookbook code is working. Is there any known issue of the PRUCookbook that interferes with Debian login? I can ssh from a pc into the BBB as root and run startx and debian comes up and logs in properly on the touchscreen and keyboard on the BBB. Any ideas on where to look for the problem?

Running beaglebone 4.19.94-ti-r42 #1buster

Have a Blessed day!
Don

1 Like
2

https://docs.beagleboard.org/latest/books/pru-cookbook/index.html#

Here is what I found!

Seth

3

Hello,

Sorry. Maybe you updated/upgraded since the reboot? I am in no way trying to make you update your image but…

  1. There is a newer image or newer Bullseye images from beagleboard.org on this forum.
  2. Also…w/ your kernel and Debian Distro, I think version.sh was still in the works.

Will you please reply w/ the output of:

  1. cat /boot/uEnv.txt

and…

  1. /opt/scripts/tools/version.sh

Seth

P.S. Sorry to bounce you around like I was doing w/ the newer PRU Cookbook mentioning. I think other people that are more knowledgeable can find what is going on w/ your system easier w/ the above two commands being posted…

4

Sounds like your X is crashing and going back to the login manager. Might be worth having a look at the xorg log file for some clue as to what is happening.

I wouldn’t have thought the PRU stuff would be causing that. It might be adding an extra dts overlay at boot, but the fact you can get X by running startx would indicate that any extra overlays are not interfering with X.

1 Like
5

Thank you for the link silver2row, and here are the two outputs you requested. No I have not updated/upgraded since a reboot or after installing PRU Cookbook. Also here is the Xorg log for benedict.hewson. Thanks for your help.

Have a Blessed day!
Don

uEnv.txt:
root@beaglebone:/# cat /boot/uEnv.txt
#Docs: Beagleboard:U-boot partitioning layout 2.0 - eLinux.org

uname_r=4.19.94-ti-r42
#uuid=
#dtb=

###U-Boot Overlays###
###Documentation: Beagleboard:BeagleBoneBlack Debian - eLinux.org
###Master Enable
enable_uboot_overlays=1

###Overide capes with eeprom
#uboot_overlay_addr0=/lib/firmware/.dtbo
#uboot_overlay_addr1=/lib/firmware/.dtbo
#uboot_overlay_addr2=/lib/firmware/.dtbo
#uboot_overlay_addr3=/lib/firmware/.dtbo

###Additional custom capes
#uboot_overlay_addr4=/lib/firmware/.dtbo
#uboot_overlay_addr5=/lib/firmware/.dtbo
#uboot_overlay_addr6=/lib/firmware/.dtbo
#uboot_overlay_addr7=/lib/firmware/.dtbo

###Custom Cape
#dtb_overlay=/lib/firmware/.dtbo

###Disable auto loading of virtual capes (emmc/video/wireless/adc)
#disable_uboot_overlay_emmc=1
#disable_uboot_overlay_video=1
#disable_uboot_overlay_audio=1
#disable_uboot_overlay_wireless=1
#disable_uboot_overlay_adc=1

###PRUSS OPTIONS
###pru_rproc (4.14.x-ti kernel)
#uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo
###pru_rproc (4.19.x-ti kernel)
uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo
###pru_uio (4.14.x-ti, 4.19.x-ti & mainline/bone kernel)
#uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo

###Cape Universal Enable
enable_uboot_cape_universal=1

###Debug: disable uboot autoload of Cape
#disable_uboot_overlay_addr0=1
#disable_uboot_overlay_addr1=1
#disable_uboot_overlay_addr2=1
#disable_uboot_overlay_addr3=1

###U-Boot fdt tweaks… (60000 = 384KB)
#uboot_fdt_buffer=0x60000
###U-Boot Overlays###

cmdline=coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet

#In the event of edid real failures, uncomment this next line:
#cmdline=coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet video=HDMI-A-1:1024x768@60e

##enable Generic eMMC Flasher:
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

root@beaglebone:/# /opt/scripts/tools/version.sh
git:/opt/scripts/:[b39ec679648a6be8f25f48bd1c9784c1fc5a0c46]
eeprom:[A335BNLT00C02151SBB36780]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-00002-g07d5700e21]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-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.19.94-ti-r42]
nodejs:[v10.15.2]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade ]
pkg:[bb-cape-overlays]:[4.14.20200403.0-0rcnee0~buster+20200403]
pkg:[bb-wl18xx-firmware]:[1.20200322.0-0rcnee0~buster+20200322]
pkg:[kmod]:[26-1]
pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~buster+20190327]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep remoteproc admin spi iio docker tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet]
dmesg | grep remote
[ 71.383717] remoteproc remoteproc0: wkup_m3 is available
[ 71.403722] remoteproc remoteproc0: powering up wkup_m3
[ 71.403756] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168
[ 71.404037] remoteproc remoteproc0: remote processor wkup_m3 is now up
[ 74.307660] remoteproc remoteproc1: 4a334000.pru is available
[ 74.323979] remoteproc remoteproc2: 4a338000.pru is available
dmesg | grep pru
[ 74.307660] remoteproc remoteproc1: 4a334000.pru is available
[ 74.307861] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 probed successfully
[ 74.323979] remoteproc remoteproc2: 4a338000.pru is available
[ 74.324127] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 probed successfully
dmesg | grep pinctrl-single
[ 1.203095] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
[ 1.216963] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 005: ID 04d8:0c02 Microchip Technology, Inc.
Bus 001 Device 004: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 001 Device 003: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 001 Device 002: ID 2109:2812 VIA Labs, Inc. VL812 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END

root@beaglebone:/# cat /var/log/Xorg.0.log
[ 133.590]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[ 133.591] Build Operating System: Linux 4.19.0-18-armmp-lpae armv7l Debian
[ 133.591] Current Operating System: Linux beaglebone 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020 armv7l
[ 133.591] Kernel command line: console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet
[ 133.592] Build Date: 18 December 2021 09:05:36AM
[ 133.592] xorg-server 2:1.20.4-1+deb10u4 (Debian -- User Support)
[ 133.592] Current version of pixman: 0.36.0
[ 133.592] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 133.592] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 133.593] (==) Log file: “/var/log/Xorg.0.log”, Time: Wed Dec 7 11:09:20 2022
[ 133.594] (==) Using config file: “/etc/X11/xorg.conf”
[ 133.594] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
[ 133.596] (==) ServerLayout “Builtin Default Layout”
[ 133.596] () |–>Screen “Builtin Default fbdev Screen 0” (0)
[ 133.596] () | |–>Monitor “Builtin Default Monitor”
[ 133.598] () | |–>Device “Builtin Default fbdev Device 0”
[ 133.598] (==) Automatically adding devices
[ 133.598] (==) Automatically enabling devices
[ 133.598] (==) Automatically adding GPU devices
[ 133.598] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 133.599] (WW) The directory “/usr/share/fonts/X11/cyrillic” does not exist.
[ 133.599] Entry deleted from font path.
[ 133.599] (WW) The directory “/usr/share/fonts/X11/100dpi/” does not exist.
[ 133.599] Entry deleted from font path.
[ 133.599] (WW) The directory “/usr/share/fonts/X11/75dpi/” does not exist.
[ 133.599] Entry deleted from font path.
[ 133.599] (WW) The directory “/usr/share/fonts/X11/Type1” does not exist.
[ 133.599] Entry deleted from font path.
[ 133.599] (WW) The directory “/usr/share/fonts/X11/100dpi” does not exist.
[ 133.599] Entry deleted from font path.
[ 133.599] (WW) The directory “/usr/share/fonts/X11/75dpi” does not exist.
[ 133.599] Entry deleted from font path.
[ 133.599] (==) FontPath set to:
/usr/share/fonts/X11/misc,
built-ins
[ 133.599] (==) ModulePath set to “/usr/lib/xorg/modules”
[ 133.599] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 133.599] (II) Loader magic: 0x649f98
[ 133.599] (II) Module ABI versions:
[ 133.600] X.Org ANSI C Emulation: 0.4
[ 133.600] X.Org Video Driver: 24.0
[ 133.600] X.Org XInput driver : 24.1
[ 133.600] X.Org Server Extension : 10.0
[ 133.607] (++) using VT number 7

[ 133.608] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 133.612] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 133.627] (II) no primary bus or device found
[ 133.627] falling back to /sys/devices/platform/ocp/4830e000.lcdc/drm/card0
[ 133.627] (II) LoadModule: “glx”
[ 133.629] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 133.669] (II) Module glx: vendor=“X.Org Foundation”
[ 133.669] compiled for 1.20.4, module version = 1.0.0
[ 133.670] ABI class: X.Org Server Extension, version 10.0
[ 133.670] (II) LoadModule: “fbdev”
[ 133.670] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 133.671] (II) Module fbdev: vendor=“X.Org Foundation”
[ 133.671] compiled for 1.20.0, module version = 0.5.0
[ 133.672] Module class: X.Org Video Driver
[ 133.672] ABI class: X.Org Video Driver, version 24.0
[ 133.672] (II) FBDEV: driver for framebuffer: fbdev
[ 133.673] (WW) Falling back to old probe method for fbdev
[ 133.673] (II) Loading sub module “fbdevhw”
[ 133.673] (II) LoadModule: “fbdevhw”
[ 133.674] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 133.675] (II) Module fbdevhw: vendor=“X.Org Foundation”
[ 133.675] compiled for 1.20.4, module version = 0.0.2
[ 133.675] ABI class: X.Org Video Driver, version 24.0
[ 133.676] (II) FBDEV(0): using default device
[ 133.676] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 133.677] (II) FBDEV(0): Creating default Display subsection in Screen section
“Builtin Default fbdev Screen 0” for depth/fbbpp 16/16
[ 133.677] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16
[ 133.677] (==) FBDEV(0): RGB weight 565
[ 133.677] (==) FBDEV(0): Default visual is TrueColor
[ 133.677] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[ 133.677] (II) FBDEV(0): hardware: DRM emulated (video memory: 1200kB)
[ 133.677] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[ 133.677] (II) FBDEV(0): checking modes against framebuffer device…
[ 133.677] (II) FBDEV(0): checking modes against monitor…
[ 133.678] (II) FBDEV(0): Virtual size is 1024x600 (pitch 1024)
[ 133.678] () FBDEV(0): Built-in mode “current”
[ 133.678] (==) FBDEV(0): DPI set to (96, 96)
[ 133.678] (II) Loading sub module “fb”
[ 133.678] (II) LoadModule: “fb”
[ 133.679] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 133.680] (II) Module fb: vendor=“X.Org Foundation”
[ 133.680] compiled for 1.20.4, module version = 1.0.0
[ 133.680] ABI class: X.Org ANSI C Emulation, version 0.4
[ 133.681] () FBDEV(0): using shadow framebuffer
[ 133.681] (II) Loading sub module “shadow”
[ 133.681] (II) LoadModule: “shadow”
[ 133.681] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 133.682] (II) Module shadow: vendor=“X.Org Foundation”
[ 133.682] compiled for 1.20.4, module version = 1.1.0
[ 133.682] ABI class: X.Org ANSI C Emulation, version 0.4
[ 133.712] (==) FBDEV(0): Backing store enabled
[ 133.713] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.713] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.713] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.713] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.713] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.713] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.713] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.713] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.713] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.713] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.713] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.714] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.715] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.715] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.715] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.715] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.715] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.715] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.715] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.715] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.715] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.715] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.715] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.715] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.715] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.716] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.716] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.716] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.716] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.716] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.716] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.716] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.716] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.716] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
[ 133.716] (==) FBDEV(0): DPMS enabled
[ 133.716] (II) Initializing extension Generic Event Extension
[ 133.718] (II) Initializing extension SHAPE
[ 133.719] (II) Initializing extension MIT-SHM
[ 133.720] (II) Initializing extension XInputExtension
[ 133.721] (II) Initializing extension XTEST
[ 133.723] (II) Initializing extension BIG-REQUESTS
[ 133.724] (II) Initializing extension SYNC
[ 133.725] (II) Initializing extension XKEYBOARD
[ 133.726] (II) Initializing extension XC-MISC
[ 133.727] (II) Initializing extension SECURITY
[ 133.728] (II) Initializing extension XFIXES
[ 133.729] (II) Initializing extension RENDER
[ 133.730] (II) Initializing extension RANDR
[ 133.733] (II) Initializing extension COMPOSITE
[ 133.734] (II) Initializing extension DAMAGE
[ 133.735] (II) Initializing extension MIT-SCREEN-SAVER
[ 133.736] (II) Initializing extension DOUBLE-BUFFER
[ 133.737] (II) Initializing extension RECORD
[ 133.738] (II) Initializing extension DPMS
[ 133.739] (II) Initializing extension Present
[ 133.740] (II) Initializing extension DRI3
[ 133.740] (II) Initializing extension X-Resource
[ 133.741] (II) Initializing extension XVideo
[ 133.742] (II) Initializing extension XVideo-MotionCompensation
[ 133.743] (II) Initializing extension SELinux
[ 133.743] (II) SELinux: Disabled on system
[ 133.743] (II) Initializing extension GLX
[ 133.744] (II) AIGLX: Screen 0 is not DRI2 capable
[ 134.126] (II) IGLX: Loaded and initialized swrast
[ 134.127] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 134.127] (II) Initializing extension XFree86-VidModeExtension
[ 134.128] (II) Initializing extension XFree86-DGA
[ 134.129] (II) Initializing extension XFree86-DRI
[ 134.129] (II) Initializing extension DRI2
[ 134.393] (II) config/udev: Adding input device tps65217_pwr_but (/dev/input/event0)
[ 134.394] () tps65217_pwr_but: Applying InputClass “libinput keyboard catchall”
[ 134.394] (II) LoadModule: “libinput”
[ 134.395] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 134.435] (II) Module libinput: vendor=“X.Org Foundation”
[ 134.435] compiled for 1.20.4, module version = 0.28.2
[ 134.436] Module class: X.Org XInput Driver
[ 134.436] ABI class: X.Org XInput driver, version 24.1
[ 134.436] (II) Using input driver ‘libinput’ for ‘tps65217_pwr_but’
[ 134.436] () tps65217_pwr_but: always reports core events
[ 134.436] () Option “Device” “/dev/input/event0”
[ 134.437] () Option “_source” “server/udev”
[ 134.459] (II) event0 - tps65217_pwr_but: is tagged by udev as: Keyboard
[ 134.459] (II) event0 - tps65217_pwr_but: device is a keyboard
[ 134.462] (II) event0 - tps65217_pwr_but: device removed
[ 134.468] () Option “config_info” “udev:/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024/tps65217-pwrbutton/input/input0/event0”
[ 134.469] (II) XINPUT: Adding extended input device “tps65217_pwr_but” (type: KEYBOARD, id 6)
[ 134.469] () Option “xkb_model” “pc105”
[ 134.469] () Option “xkb_layout” “us”
[ 134.485] (II) event0 - tps65217_pwr_but: is tagged by udev as: Keyboard
[ 134.485] (II) event0 - tps65217_pwr_but: device is a keyboard
[ 134.497] (II) config/udev: Adding input device Dell Dell USB Keyboard (/dev/input/event1)
[ 134.497] () Dell Dell USB Keyboard: Applying InputClass “libinput keyboard catchall”
[ 134.497] (II) Using input driver ‘libinput’ for ‘Dell Dell USB Keyboard’
[ 134.497] () Dell Dell USB Keyboard: always reports core events
[ 134.498] () Option “Device” “/dev/input/event1”
[ 134.498] () Option “_source” “server/udev”
[ 134.519] (II) event1 - Dell Dell USB Keyboard: is tagged by udev as: Keyboard
[ 134.528] (II) event1 - Dell Dell USB Keyboard: device is a keyboard
[ 134.531] (II) event1 - Dell Dell USB Keyboard: device removed
[ 134.544] () Option “config_info” “udev:/sys/devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrc.1/usb1/1-1/1-1.1/1-1.1.1/1-1.1.1:1.0/0003:413C:2003.0001/input/input1/event1”
[ 134.544] (II) XINPUT: Adding extended input device “Dell Dell USB Keyboard” (type: KEYBOARD, id 7)
[ 134.544] () Option “xkb_model” “pc105”
[ 134.544] () Option “xkb_layout” “us”
[ 134.566] (II) event1 - Dell Dell USB Keyboard: is tagged by udev as: Keyboard
[ 134.567] (II) event1 - Dell Dell USB Keyboard: device is a keyboard
[ 134.579] (II) config/udev: Adding input device Microchip Technology Inc. AR1100 HID-MOUSE (/dev/input/event2)
[ 134.580] () Microchip Technology Inc. AR1100 HID-MOUSE: Applying InputClass “libinput pointer catchall”
[ 134.580] (II) Using input driver ‘libinput’ for ‘Microchip Technology Inc. AR1100 HID-MOUSE’
[ 134.580] () Microchip Technology Inc. AR1100 HID-MOUSE: always reports core events
[ 134.580] () Option “Device” “/dev/input/event2”
[ 134.580] () Option “_source” “server/udev”
[ 134.658] (II) event2 - Microchip Technology Inc. AR1100 HID-MOUSE: is tagged by udev as: Mouse
[ 134.663] (II) event2 - Microchip Technology Inc. AR1100 HID-MOUSE: device is a pointer
[ 134.665] (II) event2 - Microchip Technology Inc. AR1100 HID-MOUSE: device removed
[ 134.684] () Option “config_info” “udev:/sys/devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrc.1/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.0/0003:04D8:0C02.0002/input/input2/event2”
[ 134.684] (II) XINPUT: Adding extended input device “Microchip Technology Inc. AR1100 HID-MOUSE” (type: MOUSE, id 8)
[ 134.685] () Option “AccelerationScheme” “none”
[ 134.686] () Microchip Technology Inc. AR1100 HID-MOUSE: (accel) selected scheme none/0
[ 134.686] () Microchip Technology Inc. AR1100 HID-MOUSE: (accel) acceleration factor: 2.000
[ 134.686] (**) Microchip Technology Inc. AR1100 HID-MOUSE: (accel) acceleration threshold: 4
[ 134.767] (II) event2 - Microchip Technology Inc. AR1100 HID-MOUSE: is tagged by udev as: Mouse
[ 134.771] (II) event2 - Microchip Technology Inc. AR1100 HID-MOUSE: device is a pointer
[ 134.782] (II) config/udev: Adding input device Microchip Technology Inc. AR1100 HID-MOUSE (/dev/input/js0)
[ 134.782] (II) No input driver specified, ignoring this device.
[ 134.782] (II) This device may have been added with another device file.

1 Like
6

Hello,

I know HDMI gets in the way of particular pins be accessed. So, if you are muxing those pins and HDMI in /boot/uEnv.txt are not commented out, there may be interference.

What pins are you using? Are you using config-pin to mux your pins?

Seth

P.S. For instance, config-pin -q p8.25 will give you what is muxed for that specific pin.

Also…conflicting pins before boot and while booted may create an odd instance. Once booted, find your pins you need for PRU deployment and make sure they are not already allocated by the HDMI and mux them w/ config-pin.

7

It might be useful, to state exactly what image you started with, and what commands you ran for the PRU cookbook. To trace what actually broke what…

Regards,

1 Like
8

Hello @DonTrustee ,

@RobertCNelson is correct. Adding in the image used and commands ran will help everyone assist a bit better.

For instance…

cat /etc/dogtag will give you the image available on the BBB.

and…

If you had run a command at a specific interval with other attachments to the BBB being attached, this may be the cause during the unbootable instance.

Example: Kernel 5.10.x -r54 for me and libGPIOd-dev w/ using the preprocessor directive gpiod.h works for me but when I reboot the machine, it is in a unbootable state for whatever reason. I am working to figure out exactly what is going on during this error…

Seth

P.S. But…the PRU Cookbook, the first revision, may be used w/ or w/out the HDMI being used for LCD displays. Heads up! Also…

Before rebooting the board, give the dmesg output or journalctl -xe output. This may give some insight to you, me, and others looking to help. Speaking of…I need to try this on my board too! Who knows what I can dig up w/ journalctl -xe before rebooting the board?

9

Are you logging the debug port ? That will tell you exactly where it is hanging up.

1 Like
10

Hello @foxsquirrel ,

Not yet! Soon, soon!

Seth

P.S. Soon! I will connect the UART0 on the BBBW w/ the Relay Cape attached. I need to write a new image and then get crackin’ again…

11

Also, GTKterm works very well and is pretty easy to set up for logging and different UART settings if you have other boards.

1 Like
12

Hello @foxsquirrel ,

Hey person of your being. Um, I can no longer sign in. I cannot any longer use UART0 on the BBBW.

Seth

P.S. I am out for now. Does the BBBW work w/ Debian Distros? I have Bullseye on some desktop 'puter. I kept trying w/ ssh debian@beaglebone.local and ssh debian@192.168.6.1. OH! I know…I can use the actual IP Address. Wait. No. It is the Wireless version. Blah. Again, out for now.

13

Not sure, I will have to get one. All we have are BBB and AI64. Assuming it will have the linux debug port on by default so that is should get you connected.

14

Hello,

No…No. What I mean is this idea. Does the BBB work, or in this case the BBBW, w/ Debian Distros on the development desktop computers or would I need to use Ubuntu or Windows?

Seth

15

If its not working check your /etc/hosts file and possibly try using .localhost instead of local.

16

Hello @foxsquirrel ,

Seth here. So, are you telling me that I can use the UART channel for debugging on the header w/ a TTL to USB device?

I only ask b/c I ended up getting one a while back. I still, to this day, cannot connect to the BBBW via the TTL to USB cable on the debug headers.

For whatever reason, IP, I am stuck w/ this awesome board w/out being able to sign in for now. It is odd b/c I never had trouble before today, e.g. 8:45 p.m. CST.

Seth

P.S. I could debug the issue but I am at a loss for now. I can try another UART channel…

17

Do you mean the BBB /W is actually running a desktop OS or the host machine via a connection to the BBB/W?

18

Oh!

Okay…I will try that out.

Seth

19

Right…not the target. The host. My target has a Debian Distro on it supposedly. I used etcher and installed the OS on the BBBW via SD Card.

Seth

20

Several issues exist. If you have a windows host for the terminal make sure you have the correct driver installed or it will not work at all. The linux boxes don’t have the issues and are the best way to go when working on stuff.

1 Like