It's in the code ttymidi.c snip included in the post. set_custom_baudrate. It does not work.And how are you trying to do that? Ask for a baudrate of 38400 and it just works.Even with just the overlay active, anyway, I can't get 31.25K baud on pins 14-15.
The function is deprecated. - This is on my syslog and dmesg.
And even without applying the bento-ttymidi bridge approach, which tries to set the baudrate, but
using just activating ttymidi-sysex systemwide, and relying on the dtoverlay, it doesn't.
I have been monitoring the pins 14-15 with active Midi input going in or out, and those pins just
stay high all the time. It seems there is a bug or something.
Why there had to be applied a pull /6735 in the first place and Midi_uartp5 also had to be fixed?
When those fixes where aggregated to Raspbian, was it only the last Bookworm kernel?
Maybe because I did an rpi-upgrade from Bullseye on a Pi4 I didn't receive it?
Or the fix has not been properly tested for Pi4 boards? Idk, it seems unlikely
that the former upgrade could behave differently on Bullseye and Pi4.
Would you suggest start fresh with a 64bit Bookworm img for the Pi4b at this point?
I'll try again tonight if I can. Sorry, I have windows where I can get stuff done, and others when
I can't get a coffe machine working. I am in the latter case these last few days of scorching heat.
Statistics: Posted by Zool64Pi — Thu Jul 03, 2025 11:45 pm