FlexROM is just an adapter. It has two headers that you can connect to jumper wires and route them to the option rom compartment. To write a new rom to the system, you don't have to open the whole system, you just pop open the option rom compartment, hook the jumpers to the REX and then somehow write to the system rom. It's pretty confusing, but seems like a neat feature.
There's more info here: http://tandy.wiki/FlexROM_100 Like you suggested, I'll probably just use that board as an adapter and test the rom in Virtual T. On Sun, Nov 12, 2023 at 06:16:02PM -0500, Stephen Adolph wrote: > Sorry, no REX# does not include the function to replace the main ROM. > How I would tackle a custom ROM in the M100 > * develop in inside Virtual T > * get a socket adapter PCB for a 27C256 EPROM, or better still use an > EEPROM > * once you have a prototype in VT, burn it and install in the M100 > > Maybe FlexROM helps? is it a better way to get the ROM swapped? I > don't know much about it. > ...Steve > > On Sun, Nov 12, 2023 at 5:10 PM runrin <run....@rin.run> wrote: > > Hi all, > > I've got a REX# in my m100 and was wondering if it was compatible > with > the FlexROM, which I see uses some jumper cables to interface with > the > original REX. The REX# doesn't seem to have the pins to connect > those > jumpers. > > My priority is changing the keymap for the m100 since I don't use > QWERTY, but being able to hack the ROM right from the machine with > the > REX seems like a nice feature. I will likely order a FlexROM board > anyway, since it seems like the best option to swap my LH535618 > system > rom. > > Has anyone had any success getting the FlexROM working with the > REX#? > Any tips would be appreciated. I don't mind hacking the REX# with > bodge > wires if that's what I have to do. > > If anyone has other suggestions for the best way to swap the rom, > it's > unlikely I will be doing it regularly once I have my keymap working > the > way I want, so I'd be open for suggestions there too. > > Thanks!
