I already asked Brian, and he told me, that you are working on it…
Maybe you might give me a hint.
I am trying to establish a MiDi-Input an a Pi5. It seems that dtoverlay midi-uart0 doesnt work anymore. It should teak the UART clock for ttymidi to run the native MIDI-Bad rate. However, ttymidi -b 38400 -v outputs garbage when pressng the keyboard.
Doi you have an idea?
Thiis is my /boot/firmware/config.txt so far:
# For more options and information see
# http://rptl.io/configtxt
# Some settings may impact device functionality. See link above for details
# Uncomment some or all of these to enable the optional hardware interfaces
# Automatically load initramfs files, if found
auto_initramfs=1
# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d,noaudio
max_framebuffers=2
# HIFIBerry
dtoverlay=hifiberry-dacplus
force_eeprom_read=0
# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1
# Run in 64-bit mode
arm_64bit=1
# Disable compensation for displays with overscan
disable_overscan=1
# Disable Bluetooth
dtoverlay=disable-bt
# Run as fast as firmware / board allows
arm_boost=1
# Enable Status-LEDs
#dtoverlay=gpio-led,gpio=23,label=cpuload,trigger=cpu
dtoverlay=gpio-led,gpio=23,label=wifi,trigger=rfkill0
dtoverlay=gpio-led,gpio=24,label=heartbeat,trigger=heartbeat
dtoverlay=gpio-led,gpio=25,label=mmc,trigger=mmc0
[cm4]
# Enable host mode on the 2711 built-in XHCI USB controller.
# This line should be removed if the legacy DWC2 controller is required
# (e.g. for USB device mode) or if USB support is not required.
otg_mode=1
[all]
# Enable UART for classic MIDI and disable BT
dtoverlay=disable-bt
#GPIO15
dtparam=uart0_console=on
dtparam=uart0=on
dtoverlay=midi-uart0
# Daten auf /dev/serial0
As you see, i didn’t find an easy way of changing UART clock yet. Perhaps you have better luck. If not, i hope some smart guy from the RPI foundation will help with this.
Indeed, they should bring us something like the midi-uart0 overlay
Hello and sincere thankyou to you.
Well, it’s good to know that there IS an issue about midi-uart0. I was wondering and trying for about two weeks now.
BTW: Envoking the dtoverlay midi-uart0 more than one time leads to the errormessage which I described in the raspberry-forum. This however seems NOT to be the problem.
To me it seems that simply spoken dtoverlay midi-uart0 doesn’t work at all at Pi5.
And another thing which Brian dipped my nose at:
There are multiple sourcecode of ttymidi.c.
The latest ones accepts -b 31250 as the Baudrate-parameter. The earlier ones did not.
Just to have in mind.
Obviously!! The Pi5 has a very different I/O subsystem, managed by a new chip, the RP1.
I will take a look. Anyway, 31250 is not a standard baud rate and can’t be set from the standard Linux OS side. You can request it, but you are not going to get it in a “normal” system. It must be supported by the kernel driver, what is not the case in standard systems.
Or as we did in the past, we could simply tweak the base UART clock to fake the system, and then request a standard baud rate that gives a close-enough result.
Just in order to revive this topic a bit, @jofemodo and @riban:
Is there still in place a general development timeline, for RPi5 support in Oram 64 and - consequentially - the release of the V5+Pi5 upgrade kit (or possibly even a refashioned aluminum case)?
I seem to gather from the forum that switching to RPi5 appears to be posing more arduous technical challenges than foreseen.
