Problems with MT32-pi after updating to v.0.13.0

[retro]

I updated my MT32-pi to the latest release (v0.13.0) today.

Unfortunately this is causing garbled text on the OLED, and also randomly getting Unknown Mode notifications.

U1hwL2e.jpg (70.33 KiB) Viewed 7122 times

ujVWG8j.jpg (85.96 KiB) Viewed 7122 times

I searched online and https://github.com/dwhinham/mt32-pi/issues/292 was the only result I got for this problem.

My MT32-pi HAT (along with every part of the MiSTer except for the DE-10 Nano) was purchased from https://misterfpga.co.uk.

I am using a Raspberry Pi 3B+.

Please advice.

[Bas]

That looks like it'll be fixed in the next firmware build. So you can either build it yourself, wait for the new build or revert to the last known working version.

[MorkMikael]

i may have had the same problem for me if everything worked for you in v0.12.1
what fixed it for me was backing up my config.txt and mt32-pi.cfg
and delete every thing except roms and soundfront.
and go to https://github.com/dwhinham/mt32-pi/releases and get v0.13.0 from there.
and then get the new mt32-pi.cfg file from v0.13.0 and update your options form v0.12.1 mt32-pi.cfg to mt32-pi.cfg file from v0.13.0
and then copy over the files form v0.13.0 except mt32-pi.cfg and config.txt
and then it work for me

e7G78Ng.jpg (602.95 KiB) Viewed 7120 times

[retro]

i may have had the same problem for me if everything worked for you in v0.12.1
what fixed it for me was backing up my config.txt and mt32-pi.cfg
and delete every thing except roms and soundfront.
and go to https://github.com/dwhinham/mt32-pi/releases and get v0.13.0 from there.
and then get the new mt32-pi.cfg file from v0.13.0 and update your options form v0.12.1 mt32-pi.cfg to mt32-pi.cfg file from v0.13.0
and then copy over the files form v0.13.0 except mt32-pi.cfg and config.txt
and then it work for me

Yeah, it was working fine in v0.12.1 without any problems.

I'll try your solution later today and report the outcome. Thank you!

[neogeo81]

Works with my MT32 Pi Zero

[retro]

Found the cause to be the core_freq and core_freq_min lines in config.txt since they were new additions with this latest release, and my backed up copy of this file didn't have them.

Thank you @MorkMikael. Your post led me to this solution