Hyperbian + Hyperion ng + ezcap 269

Tyler983 · September 19, 2020 at 9:00 PM

Ok i will post it tomorrow cause now I'm on the rpi3...

Tyler983 · September 21, 2020 at 10:54 PM

@Awawa I installed a fresh build of Raspbian lite, your last fork and deactivate bluetooth with the command line you suggested. Ezcap is plugged to the usb3 port but nothing happen... leds are off.
attached you can find last dmesg and the errors are always the same.
What to do?

Awawa · September 21, 2020 at 11:28 PM

These errors are specific for that system/config, if other things work on Rpi3 then you can ignore them on Rpi4 too.
Try remove console=serial0, console=ttyAMA0 and console=ttyS0 from cmdline.txt.
Seems that ttyAMA0 is taken over at start up again (not by bluetooth).

https://www.raspberrypi.org/documentation/…uration/uart.md

It's highly problematic USB to lightberry converter, sorry.

Tyler983 · September 22, 2020 at 7:13 AM

I think you’re right, cause I have the same errors on the rpi3 but there less are on...
Where I can remove those strings?

Awawa · September 22, 2020 at 8:32 AM

https://www.circuits.dk/setup-raspberry-pi-3-gpio-uart/

Tyler983 · September 22, 2020 at 8:43 AM

Thx i'll give it a read
another thing... i generate a lut file, but as you explain in the first post, i haven't : the Hyperion configuration folder.

Typically /home/pi/.hyperion/.....

I searched it with cyberduck but folder "pi" is empty.

Awawa · September 22, 2020 at 9:48 AM

Read hyperion logs

Tyler983 · September 23, 2020 at 8:45 AM

Good day @Awawa yesterday i deleted the strings you suggested from cmdline.txt but the result is always the same: no leds...I don't know what to do with this rpi4.

Awawa · September 23, 2020 at 9:18 AM

Post dmesg after changes

Tyler983 · September 23, 2020 at 9:52 AM

Ok when i'll be at home i'll post it

Tyler983 · September 26, 2020 at 3:22 PM

Hi @Awawa following the dmesg as you asked. This is the ssd with your last fork installed, rpi4, ezcap269, usb3 plugged.
Nothing to do, leds are all off.
The same sd go like a charm in the rpi3.
What to do?

Awawa · September 26, 2020 at 4:52 PM

OK, lets try this:

Code

sudo systemctl stop serial-getty@ttyAMA0.service
sudo systemctl disable serial-getty@ttyAMA0.service
sudo systemctl mask serial-getty@ttyAMA0.service
sudo reboot

If it doesn't help could you provide output after reboot of:

Code

ls -l /dev/ttyACM0
(try to execute it again with lightberry connected/disconnected to compare, reboot before each action)

and content of /boot/config.txt and logs from hyperion WWW page to check what's happening inside.

Tyler983 · September 26, 2020 at 5:32 PM

Sudo commands doesn't function, so I tried with lightberry connected and this is the result
pi@raspberrypi:~ $ ls -l /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0 Sep 26 16:20 /dev/ttyACM0

with lightberry disconnected:
pi@raspberrypi:~ $ ls -l /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0 Sep 26 16:22 /dev/ttyACM0

Awawa · September 26, 2020 at 5:38 PM

Quote

[hyperiond DISPMANXGRABBER] (ERROR) Previous line repeats 200 times

Definitely not good. Forget for now about Lightberry. Did you disabled system/platform grabber as it's completely broken in Hyperion.NG alpha 8 on Rpi4?

Tyler983 · September 26, 2020 at 5:41 PM

Tradotto in:
Italiano
Spettacolo originale
Now I've disabled it... there's something other I ca do?

[LEFT]Original text[/LEFT]
Contribute a better translation

Awawa · September 26, 2020 at 5:42 PM

Yes, post logs from Hyperion after change

Tyler983 · September 26, 2020 at 5:44 PM

2020-09-26T15:43:39.709Z [hyperiond DAEMON] (ERROR) The CEC handler can not be instantiated, because it has been left out from the build 2020-09-26T15:44:33.787Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'adalight' signals error: 'Timeout writing data to ttyACM0'

Awawa · September 26, 2020 at 5:47 PM

With your previos log you've got that error ('Timeout writing data to ttyACM0') only when the light-berry was disconnected. Did you connect it again and rebooted? PS: put debug level to DEBUG as now we can see only errors.

Tyler983 · September 26, 2020 at 5:49 PM

Yes, I've pugged lightberry and rebooted it.
this is the log in debug mode:

2020-09-26T15:43:39.709Z [hyperiond DAEMON] (ERROR) The CEC handler can not be instantiated, because it has been left out from the build 2020-09-26T15:44:33.787Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'adalight' signals error: 'Timeout writing data to ttyACM0' 2020-09-26T15:48:40.024Z [hyperiond V4L2:AUTO] (DEBUG) (V4L2Grabber.cpp:992:process_image()) Video FPS: 29.88, av. delay: 38ms, good: 1773, bad: 20 (60.03,15)

Awawa · September 26, 2020 at 5:58 PM

Strange, because there wasn't that error in the log before, maybe it was taken to soon before it occured.
Anyway it isn't fully log from Hyperion in DEBUG mode but a part of it.

Summarize:
1) you took full copy of working system from Rpi3 to Rpi4
2) Rpi4 doesnt work. In normal circumstances we can exclude Hyperion as a suspected because the config is the same and it works on Rpi3.
3) But it isn't that case as Alpha 8 has broken system grabber on Rpi4. And system grabber is enabled...
4) We try to overcome Serial port problem again but it's dead end as the Hyperion isn't working (didnt you notice it in the hyperion log?)
5) Now we have AMA0 in unknown state after some experiments. Not sure if it isnt problem but the path of changes to make it work was definitely wrong based on wrong diagnosis.

So I propose to disable system grabber on Rpi 3 then to make a full copy of that working system to another card and try to run it on Rpi 4 again

Hyperbian + Hyperion ng + ezcap 269

Participate now!

Users Viewing This Thread