peterm6881 has joined #Speedsaver
<peterm6881> hey Xogium
<peterm6881> are you there?
<Xogium> yeah
<peterm6881> ive connected a lichee zero to the alarm box via CP210 Bridge
<peterm6881> and installed screen
<Xogium> oh, fancy
<peterm6881> can you confirm you can talk to the Lichee
<Xogium> let me see
<peterm6881> its booted BR 2022.05 from git
<Xogium> yep seems to run very nicely
<peterm6881> sweet
<peterm6881> it has a gps module on i2c0, but also connect a usb module to the otg port, which will have a fix
<peterm6881> this will stay on permanently because its powered via the CP210, one big advantage of a lower powered platform than the OPi0
<peterm6881> the CP210 couldnt pass enough juice for the OPi0
<peterm6881> but the Lichee seems happy with it
<Xogium> I'm even surprised you can power devices through a serial to usb bridge tbh
<peterm6881> it has 5 V and a 3.3 V pins
<Xogium> interesting
<peterm6881> the OPi0 was too power hungry
<Xogium> er…
<Xogium> ah yeah
<peterm6881> yeah when you get your lichee, you should be ok to power it through your CP210
<peterm6881> whats then screen command to connect to the lichee?
<peterm6881> [peterm6881@alarm ~]$ screen /dev/ttyUSB0 115200
<peterm6881> [screen is terminating]
<Xogium> oh I won't touch that cp210 you sent me, its connected on the orange pi you sent me as speedsaver and I don't know how to plug it right
<peterm6881> im doing something dumb, as usual ;)
<Xogium> yep trying to connect there when I'm already there
<peterm6881> is that the right command?
<Xogium> it is
<peterm6881> I thought i tried it before i told you about it, but i could be wrong
<peterm6881> ok
<Xogium> you might need sudo in front, but the thing is you tried to connect to the serial port when I'm already on, it would either not work at all or give you garbage input and output
<peterm6881> so, it would make sense to send you a CP210 with your lichee then, already connected
<peterm6881> are you disconnected now?
<Xogium> nop, sec
<Xogium> now I am
<Xogium> if it doesn't let you use without sudo then you know what to do
<peterm6881> yeah it working. I expected a login prompt but im straight in, wtf
<Xogium> that's because I didn't log out
<peterm6881> lol
<peterm6881> makes sense
<Xogium> you can terminate screen without logging out of a serial console, useful sometimes
<peterm6881> # uname -r
<peterm6881> 5.3.5
<peterm6881> # cat os-release
<peterm6881> NAME=Buildroot
<peterm6881> VERSION=2022.02-521-g114487dfd2
<peterm6881> ID=buildroot
<peterm6881> VERSION_ID=2022.05-git
<peterm6881> PRETTY_NAME="Buildroot 2022.05-git"
<peterm6881> okie dokie
<peterm6881> remind me the proper way to terminate scren!
<peterm6881> screen
<peterm6881> i can never remember
<peterm6881> ive logged out of the lichee
<Xogium> ctrl+a then k and answer with y
<peterm6881> ok im out
<Xogium> and you probably guessed it, but the way to terminate screen without logging out is you just don't log out before you do that
<peterm6881> i connected a usb gps dongle with a fix to otg, but we dont have usb in that image. But its for later
<Xogium> actually, we do have usb, but probably not that specific driver required
<peterm6881> ahh
<peterm6881> makes sense
<peterm6881> Bus 001 Device 001: ID 1d6b:0002
<peterm6881> # lsusb
<peterm6881> all right, its all yours
<Xogium> well right now I can't do much with it lol
<peterm6881> well, if there was anything you wanted to check :) I could enable more shit in BR if you like
<peterm6881> brb, need to boot into Windows
peterm6881 has quit [Remote host closed the connection]
<Xogium> well I have to work on our image now anyway
peterm6881 has joined #Speedsaver
<peterm6881> back
<Speedsaver> Speedsaver/ArduiPi_OLED: peterbmckinley commented on issue #1 "Speedsaver/ArduiPi_OLED@37230d8 may be too aggressive" (https://github.com/Speedsaver/ArduiPi_OLED/issues/1#issuecomment-1101514802): Closing issue as it's been decided to revert the anti spamming fix
<Speedsaver> Speedsaver/ArduiPi_OLED: peterbmckinley closed issue #1
<Speedsaver> Speedsaver/ArduiPi_OLED: peterbmckinley opened issue #2 "Revert last 2 commits" (https://github.com/Speedsaver/ArduiPi_OLED/issues/2)
<Speedsaver> Speedsaver/ArduiPi_OLED: peterbmckinley assigned issue #2 to sc6502
<peterm6881> blah
<Xogium> why do you want to revert this ?
<peterm6881> Hey Xogium
<Xogium> heya
<peterm6881> Since that fix was deployed, I've been experiencing random events of having no oled display at boot, and my suspicion is the two are connected. I had suggested having it try to write to the oled for 5 seconds before giving up, but from sc6502's response that was too simplistic
<peterm6881> Its better to revert the fix, see if the problem goes away, and make sure you always have an oled connected
<peterm6881> since thats representative of the end product
<peterm6881> Does that sound fair?
<Xogium> huh… I guess… But I had no oled at all with mangopi and from the sound of things it seemed like you would send me just a lichee board with cp210 and possibly speaker
<Xogium> so I'd hook it onto my breadboard
<Xogium> so no oled there either
<peterm6881> I'll include an oled with male pins. and advise you the connections
<peterm6881> you can check the previous issue, it sounded like a world of pain trying to debug why it occasionally would give a blank screen
<peterm6881> which was never an issue before the fix
<Xogium> are you sure it came from that ?
<Xogium> didn't you say it could be coming from not getting enough power ?
<peterm6881> yes, it was never an issue before the fix
<Xogium> and to be honest there, you never tried navit and friend without that fix on mangopi, so for all we know its a bug on mangopi lol
<peterm6881> no the power hasnt changed
<Xogium> but yeah, there's a fair chance it comes from that fix either way
<Xogium> just pointing out that you never had the previous arduipi oled on mangopi
<peterm6881> yes its true we didnt do a lot of testing on mangopi, before the fix was deployed, so it could be a mangopi specific problem
<peterm6881> i did wonder if the fix is also in use on the Speedsaver for OPi0 repo, or if the fix only applies to the mangopi repo?
<Xogium> only on mangopi
<peterm6881> which further highlights the fact its introduced a level of confusion, id rather just eliminate it
<peterm6881> and make sure you guys always have an oled. I dont trust it
<Xogium> well to be fair I wanted to also upgrade that package in orange pi but well
<peterm6881> we shouldnt really be testing anything in an unnatural test environment, that was always a not great idea
<peterm6881> if we sign off on stuff, it really should be tested on representative hardware
<peterm6881> lol no umm, dont do that, thank you
<Xogium> its still not nice to get spammed 2030000 times by i2c errors as soon as yoiu don't have a oled tbh
<Xogium> and no I don't exagerate that number
<peterm6881> if you want, you can continue to debug it with Steve
<Xogium> not really… I couldn't know if the oled is blank anyway
<peterm6881> I think we're better off without it. If you get spammed you'll know you need to check your oled connections. m condifent we introduced something that made the system unreliable
<peterm6881> im confident
<peterm6881> but i agree it could be mangopi specific
<peterm6881> just dont wanna risk it
<Xogium> alright then
<Speedsaver> master @ Speedsaver/ArduiPi_OLED: sc6502 pushed 1 commit (https://github.com/Speedsaver/ArduiPi_OLED/compare/37230d87c3b8...e5479b6de452):
<Speedsaver> master @ Speedsaver/ArduiPi_OLED: sc6502 e5479b: Revert last two commits. (https://github.com/Speedsaver/ArduiPi_OLED/commit/e5479b6de452b4e95bb447fd28396dfc54805d53)
peterm6881 has quit [Read error: Connection reset by peer]