otisolsen70 has quit [Remote host closed the connection]
otisolsen70 has joined #beagle
marcheu has quit [Read error: Connection reset by peer]
vagrantc has quit [Quit: leaving]
marcheu has joined #beagle
KartikANK has joined #beagle
KartikANK has quit [Client Quit]
ikarso has joined #beagle
<markand>
we have issues trying to use multiple uart ports at the same time, I just would like to be sure that we can use UARTs 1, 2, 4 and 5 simultaneously?
<markand>
we also have an issue that the beaglebone restart automatically while... booting: https://bpa.st/N6NA
fakuivan has joined #beagle
set_ has joined #beagle
starblue has quit [Ping timeout: 240 seconds]
starblue has joined #beagle
Shadyman has quit [Remote host closed the connection]
xet7 has quit [Ping timeout: 256 seconds]
xet7 has joined #beagle
set_ has quit [Remote host closed the connection]
buckket has quit [Quit: buckket]
buckket has joined #beagle
set_ has joined #beagle
<zmatt>
markand: different uarts are independent and have nothing to do with each other
<zmatt>
i.e. they can all be used simultaneously
<zmatt>
that log looks like a clean shutdown is being performed
<zmatt>
maybe something causing a spurious power button event?
<markand>
strange
<markand>
it boots the second time but it always does this
<markand>
at least once
<markand>
we have fixed the issue regarding UARTs, in fact the very old and deprecated rxtx java library does not like to specify /dev/ttyO2 (even though it's a symlink)
<zmatt>
/dev/ttyO* are deprecated anyway, use /dev/ttyS*
xet7 has quit [Remote host closed the connection]
xet7 has joined #beagle
florian has quit [Quit: Ex-Chat]
vagrantc has joined #beagle
vagrantc has quit [Ping timeout: 240 seconds]
vagrantc has joined #beagle
samnob has quit [Ping timeout: 240 seconds]
samnob has joined #beagle
Konsgn has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
zjason` has joined #beagle
zjason has quit [Ping timeout: 240 seconds]
set_ has quit [Ping timeout: 256 seconds]
<Konsgn>
I'm having a weird problem debugging why a yocto build targeting pocketbeagle hardware is not powering off.
<Konsgn>
seems like kernel is getting to the function of omap_rtc_power_off(void), but the pmic enable pin is not actually turning off on the 5.9.16 kernel. Beaglebone's 5.4 kernel is powering off correctly
<Konsgn>
*facepalm .... Every 1.0s: cat /sys/class/rtc/rtc0/time shows 00:00:00.... rtc clocks not running.