Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/dev/ttyAMA0 Short or failed write! #1762

Open
peternewman opened this issue Jan 13, 2022 · 6 comments
Open

/dev/ttyAMA0 Short or failed write! #1762

peternewman opened this issue Jan 13, 2022 · 6 comments

Comments

@peternewman
Copy link
Member

Then I made a test to leave the first serialport alone and use it for bluetooth instead
so I commented out the following in /boot/config.txt

#dtoverlay=disable-bt
#init_uart_clock=16000000
#enable UART
#enable_uart=1

please note even the line with the baudrate setting is commented out.

I only use uart2 to uart5

dtoverlay=uart2
dtoverlay=uart3
dtoverlay=uart4
dtoverlay=uart5

and the baudrate is still correct on the used ports

However when I run olad with --log-level 3
I get a lot of errors about the uart that is not in use:
plugins/uartdmx/UartWidget.cpp:129: /dev/ttyAMA0 Short or failed write!
the port It is not patched to any universe.
but anyway its working.

Thanks
/Magnus

Originally posted by @MagnusHerrlin in #1749 (comment)

@peternewman
Copy link
Member Author

@MagnusHerrlin can we see your ola-uartdmx.conf file please?

@peternewman
Copy link
Member Author

I'd also be curious what this outputs:
vcgencmd get_config init_uart_clock

@MagnusHerrlin
Copy link

MagnusHerrlin commented Jan 13, 2022

Hi

Sorry my fault
as soon I read this:

@MagnusHerrlin can we see your ola-uartdmx.conf file please?
I understood that I forgot to remove the unused port from this file.

So everyting is working now

Except for one thing that I think is more important and that is
to get @shenghaoyang s fix for ola_recorder merged.
But since I'm not sure how to merge it
I downloaded his repo first and compiled and saved the ola_recorder file
I then downloaded and compiled and installed @peternewman s fix 1760
and then copied ola_recorder manually.
I'm not sure how to do this with git.

vcgencmd get_config init_uart_clock
outputs this: init_uart_clock=2dc6c00

But as you might already know vcgencmd is'nt installed on Bullseye
I copied all of /opt/vc/ from the Buster installation.

Speaking about Bullseye I am not impressed of how this (upgrade?) was done.
First of all they abandoned openbox (And I just made a really nice compact desktop installation with it)
then removed omxplayer (that I use in my nodescript to play videos)
removed the whole directory /opt/vc
the old way of recording and taking pictures with the camera was removed
so from now on every tutorial written about taking a pictures and recording with the camera is useless.
(although they now have some legacy camera support) added.
The transparency of the taskbar disappeared.

I'm amazed of how much that was destroyed with the move to Bullseye
I my humble opinion if you are going to make a transition like this
then you better fix the backwards compability of programs first, before the release.
or write a new program with the same name with added arguments to it.

You don't just don't remove programs and folders like that.

I don't like it at all and it makes me quite angry.

I have tried several installations with Bullseye now, but it feels unstable.
sometimes it locks up for seconds before executing whatever you clicked or started from the commandline.
One thing that did improve is the videoplayback in chromium.

So I have moved back to Buster for the time being.
sorry for my rant

Anyway this issue turned out not to be an issue so I guess it can be closed now.

Thanks
/Magnus

@shenghaoyang
Copy link
Contributor

shenghaoyang commented Jan 13, 2022

Hey @MagnusHerrlin , you can download patch files for github pull requests:

Just add .patch to the end of the pull request URL:

https:/OpenLightingProject/ola/pull/1680.patch

Git should be able to apply that patch (assuming that there's no conflicts)

Or you can cherry pick commits by having my branch fetched as well.

I've used this quick and dirty approach for quite a few interesting pulls 😆

I've gotten lost in that PR myself now since that was so long ago - I've switched to figuring out if there's some sort of playback engine that we can use as a dependency instead of rolling a complete one ourselves (I experimented with using VLC to playback universes that were converted to video files through its raw YUV output).

If there's still interest in that PR I can go and address some of the comments and fix that up.

@MagnusHerrlin
Copy link

MagnusHerrlin commented Jan 13, 2022

Thanks @shenghaoyang

So do I
git clone https:/OpenLightingProject/ola/pull/1680.patch and
git clone https:/OpenLightingProject/ola/pull/1760.patch
before compiling or how do you mean?

@shenghaoyang (I experimented with using VLC to playback universes that were converted to video files through its raw YUV output).
This sounds really interesting.
How many universes can you store in a videofile is it one or more?

Thanks
/Magnus

@shenghaoyang
Copy link
Contributor

You can simply download those and supply them to git apply.

git apply x.patch & git apply y.patch

git am should also work if you want to pull in the actual commits.

@shenghaoyang (I experimented with using VLC to playback universes that were converted to video files through its raw YUV output).
This sounds really interesting.
How many universes can you store in a videofile is it one or more?

I've a repo here: https:/shenghaoyang/ola_video_convert

Takes a bit too much setup to be practical, though. But may be useful for 24x7 looping style stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants