OSD and RESET buttons (wired to GPIO pins) used to work.. now only work in some cores?

[iainjh]

Hi

My Mister is in a custom case /keyboard and for simplicity have the OSD and RESET buttons wired from GPIO to momentary buttons. I use those frequently

I'm not sure when this happened, but I have realised some cores no longer respond when either hard buttons are pressed. AO486, spectrum, appleII etc,

However! - using PC engine, Atom, Electron, and many arcade cores the buttons work fine

I am assuming when I've updated in last weeks I've deleted or changed a mister.ini setting that enables this for some cores. Hopefully this can be re enabled but I cant find it.. can someone please advise what ini or other setting I need change to re enable these buttons in all cores?

thank you!

Iain

[iainjh]

hmm.

I found a backup iso of my microsd card, that I made last year.

I cant find any clues in the 2 x mister.ini's. and if I copy the OLD mister.ini to the current build, the buttons dont work.

if I copy the OLD rbf's over (I copied the old AO486 and appleII as a quick test)- the OSD and RESET buttons work again.

I've part answered by own question, I'll take a closer look at their own settings and will ask in the specific core sections. ta!

[FPGA64]

See this thread

viewtopic.php?t=1492

[iainjh]

thank you. I'll post there.

Nightmare if its been deprecated!

Cheers

[jregel]

I've been having the same problem, is this a common, known issue and does anyone know the answer?

On my MiSTer, following a recent update_all, the three hardware buttons don't do anything from the main menu. As per the thread linked above, I replaced my menu.rbf with the menu_20230223.rbf. On rebooting, the Reset button now works and reboots the MiSTer, the OSD button doesn't seem to do anything, and the User button sort of works and appears to select the currently highlighted menu option.

I also have a problems with most (but not all cores) in that the three buttons don't do anything. Those that work include some of those referenced by the OP (e.g., the Electron core).

I'm going to try different RBF files, but if anyone has knows what has changed and a workaround, that would be appreciated!

[rhester72]

Not sure what to say, other than it's a localized problem. With MiSTer main md5sum 9b9ca1f704d40f6e6d167512abc912ee (dated Dec 27 12:11), my hardware buttons function as expected on the main menu (Reset resets, OSD flips between the two menus, and User does nothing) and they also work as expected in all cores. I want to be wrong, but it sounds like a hardware fault of some variety (particularly if it's misbehaving in main and cores).

[FPGA64]

Not sure what to say, other than it's a localized problem. With MiSTer main md5sum 9b9ca1f704d40f6e6d167512abc912ee (dated Dec 27 12:11), my hardware buttons function as expected on the main menu (Reset resets, OSD flips between the two menus, and User does nothing) and they also work as expected in all cores. I want to be wrong, but it sounds like a hardware fault of some variety (particularly if it's misbehaving in main and cores).

The original post

viewtopic.php?p=94288#p94288

His Mister got an ESD discharge and after that it exhibited the current behaviour

[jregel]

Not sure what to say, other than it's a localized problem. With MiSTer main md5sum 9b9ca1f704d40f6e6d167512abc912ee (dated Dec 27 12:11), my hardware buttons function as expected on the main menu (Reset resets, OSD flips between the two menus, and User does nothing) and they also work as expected in all cores. I want to be wrong, but it sounds like a hardware fault of some variety (particularly if it's misbehaving in main and cores).

Thanks - it was helpful to know the version you are running and the behaviour you get.

I don't understand why some buttons are consistently working in some cores, but it's broken for most. As I've done more testing, it would appear that while the Reset and User buttons work sometimes, the OSD button never works, so I'm guessing if something is fried, then it's probably related to this.

Follow on question... is there a way to tell if the issue is with the analogue I/O board, or with the DE10? Is there any command in Linux that can report of the buttons being pressed that I could check with?

[rhester72]

It appears at least 2 of the equivalent buttons are directly on the Nano board, though I'd take extreme care handling the bare board if you've already had an ESD event:

https://www.rocketboards.org/foswiki/pu ... 1486394232