sorry following the complete debug after reboot.
Hyperbian + Hyperion ng + ezcap 269
- Tyler983
- Erledigt
-
-
Yep, I noticed and replied as you wrote it
-
Well Summarizing
1) i have 2 sd: 1 for rpi3 and 1 for rpi4. On the rpi4 I installed raspbian lite with your fork and it function on rpi3. On the rpi3 I have hyperbian with hyperion ng alpha 8 official. Both sd function on rpi3 but doesn't on the rpi4
2) Right, on rip 4 nothing works -
Check again what I wrote: that part of the system grabber particularly. It works on Rpi3 but doesnt work on Rpi4 and it was enabled.
-
Right, I'm doing it. Soon I'll tell you how's gone
-
Ok done, leds are off.
Following the debug complete -
now debug show it in addition to what I posted before
2020-09-26T16:17:09.613Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'adalight' signals error: 'Timeout writing data to ttyACM0' 2020-09-26T16:17:09.618Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) LED device: disabled 2020-09-26T16:21:43.795Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1032:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.50.129 -
Yes, the timeout is coming back.
On Rpi4 Bluetooth shouldn't be a problem according to the doc. So something else steal AMA0.
I suspect console so could you repeat that steps with editing config cmdline.txt (removing console0) and disabling serial-getty@ttyAMA0.service ? -
This is what I got, what should I delete?
console=serial0,115200 console=tty1 root=PARTUUID=ca5dffb5-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait -
How can I disable serial-getty@ttyAMA0.service ?
-
remove console=serial0,115200
also put dtoverlay=disable-bt at the end of config.txt if it's missing (it was missing for some reason in your latest config so you had some difference from Rpi3 you must watch it) -
Done
nothing happened.
following the debug -
-
Right
-
If nothing helps: disabling bluetooth, console0 and serial-getty@ttyAMA0.service then it seems that I'm out of ideas.
Maybe it's a problem of Raspbian, maybe Hyperion from some reason can't talk on faster architecture with AMA0, dont know.
Loosing USB3.0 from Rpi4 it's a serious downgrade for Ezcap 269 but at least you have working Rpi3 setup. I would put that Light-berry USB converter on unsupported device list for Rpi. -
I think I’ll put it in the list, but just for rpi4. Thx a lot for your time, really
-
I think I’ll put it in the list, but just for rpi4. Thx a lot for your time, really
Hi Tyler
I've got one genuine Arduino UNO (you've got some chinese clone as serialnumber is empty) that is installed on the same ttyACM0 port as your Leonardo/Ligthberry converter.
But it works out of box on Rpi4/Hyperbian as I tested it.At least at baud rate 9600, not the 115200 you have but it's up to the code that it's uploaded to USB to Lightberry converter. Dont know what's inside of it. You can play with manual port settings (speed for ex. ...,9600, 19200, 38400, 57600, 115200, 460800 to test).
-
-
No, no the Rpi4 The arduino component inside your the Lightberry converter.
-
Ok ok i will play with the Baudrate, but let me know about the genuine Arduino are you talking about. Maybe buying it I can solve, do you have a link to the product I can see?
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!