Just a thought, for the GBA and GB 2P cores and the unofficial NES, MS and Megadrive 3D cores, is it worth just copying the main core images and renaming them accordingly and putting those in the repo?
Yeah the GBA and GC 2 player cores are both released, I think both are in Main now. They aren't included in the official update script to not confuse people (which I personally would prefer them to be).
The 3D cores aren't official, and won't make it into main as they are apparently a bit hacky in order to make them work, but certainly SMS and NES are working well by all accounts I have seen.
Has anyone made Japanese NES and SNES variants for Famicom and Super Famicom? Conscious of the fact the table doesn't really accommodate alternates too well.
Been trying to keep up with the new and upcoming cores and add them to the sheet, there are a couple of new computer cores Compukit UK101 and Interact Home Computer and lots of arcade cores.
There are a few more that could use existing images:
I put a note on the sheet, but wanted to flag, did the ScumVM image make it into the repo? I marked it as yes awhile back, but actually I am not sure it is actually in there and needs its file name added.
They could use the same, or I (or someone else) could edit the current one to add a "2P" indication somewhere on it. I might work on that later tonight or tomorrow night...
venice, RealLarry and I are proud to announce the next integration level for tty2oled:
d.ti_small_tty2oled_wroom_32d.jpg
The PCBA connects directly to the 3.12" display. No further adapter/MCU boards needed. The design relies on ESP32-WROOM-32D module with Micro USB Socket at back side. Additional SPI and I2C Sockets available for further hardware extension:
d.ti wrote: ↑Mon Aug 23, 2021 3:57 pm
Hello together,
venice, RealLarry and I are proud to announce the next integration level for tty2oled:
The PCBA connects directly to the 3.12" display. No further adapter/MCU boards needed. The design relies on ESP32-WROOM-32D module with Micro USB Socket at back side. Additional SPI and I2C Sockets available for further hardware extension:
I've been observing some strange interactions between my tty2oled and other hardware in my MiSTer setup recently and after chatting about it on the discord it was suggested I post about it here.
MiSTer Configuration:
128MB RAM
Digital IO board v1.2
USB Hub v2.1
- K400+ keyboard dongle
- bluetooth dongle
- 2.4GHz M30 controller dongle
- tty2oled (TTGO-T8 with SSD1322 on 6" USB cable)
MT32-pi (on 6" USB cable)
Wired ethernet connection
HDMI via CEC blocker to Sony sounder and LG OLED55B8
The MiSTer, MT32-pi and tty2oled are all running the most up to date software releases as of this morning 27/8/21
First problem:
With the tty2oled connected and running, at boot the M30 controller is unresponsive, but if I disconnect and reconnect the M30 dongle it works. Rebooting the MiSTer displays the same behaviour, controller is unresponsive until the dongle is replugged. With the tty2oled unit disconnected the behaviour is not observed.
Second problem:
With the tty2oled connected and running, spurious level meter activity is sometimes observed on the MT32-pi. This can be a single meter rising and falling or all meters showing lots of activity, eventually followed by a "sysex overload" message and the MT32-pi appearing to reboot. d0pefish stated this was down to something "wiggling" the serial port pin that the MT32-pi uses to communicate with the MiSTer. Others suggested it may be down to RF interference from a noisy OLED board on the tty2oled, so I connected it up via a 3m USB extender cable, moved the tty2oled to the opposite side of the room, and still observed the strange meters activity.
As a further experiment, while the meters were moving without any MT32-pi audio activity I disconnected the tty2oled from the USB cable and the behaviour persisted. I took this further and reset the MiSTer using the button on the Digital IO board and the meter activity persisted until the MT32-pi was initialised.
At one point while cycling through cores to precipitate the behaviour the MT32-pi display became completely corrupted and shifted. Again, d0pefish attributed this to corruption of the i2c data connection between the pi and the display and suggested RF interference.
I'm not looking for a fix, as I hardly use the tty2oled to be honest, but wanted to present my experience in case someone else has similar issues or there's an obvious solution fix. MT32-pi and tty2oled both use serial communications, although the MT32-pi connects directly rather than via a USB serial device, so I'm really not sure.
Thanks for reporting this.
I have two systems with external powerred USB Hub's v2.1 and never had problems while my tty2oled is connected.
One system has an MT32pi connected as well. Never saw "Self Meter Moving".
WiteWulf wrote: ↑Fri Aug 27, 2021 2:32 pmSecond problem:
With the tty2oled connected and running, spurious level meter activity is sometimes observed on the MT32-pi. This can be a single meter rising and falling or all meters showing lots of activity, eventually followed by a "sysex overload" message and the MT32-pi appearing to reboot. d0pefish stated this was down to something "wiggling" the serial port pin that the MT32-pi uses to communicate with the MiSTer. Others suggested it may be down to RF interference from a noisy OLED board on the tty2oled, so I connected it up via a 3m USB extender cable, moved the tty2oled to the opposite side of the room, and still observed the strange meters activity.
I'd a similar issue some days ago after finishing and testing my MiSTer-AjSTer setup. 'till finishing up the whole setup (including mt32-pi by USB cable via user port and tty2oled) I've used a MeanWell GST40A05-P1J power supply and this was working fine. But after completing the setup with the official USB hub (Y-cable from power supply to MiSTer and hub) I could measure voltage drops down to 4.7V on one line (4.8V went fine, depending on moonphase and used drugs). Swapped the power supply against a MeanWell RS-25-5 set to 5.1V (and it's doing this and nothing other) all problems are gone and whole setup is running stable since then.
USB hub supplies BT, WiFi, Keyboard, Mouse, Joystick and tty2oled - MiSTer supplies mt32-pi
After I updated one of my MiSTer's with "Update All" today (Release 20210825) the tty2oled stops working.
I had to run the Updater again to get the Scripts back onto the MiSTer and I had to rename /etc/init.d/S60tty2oled to /etc/init.d/S99tty2oled to get it working again.