What device names and subprograms were present in the TIPI EPROM that was installed?
See the TIPI wiki for a list of device names: https://github.com/j...pi/wiki/Devices
subprograms: I suspect you are asking about level 2 IO routines: >1x, except the first that is sector read/write, as shown here: https://github.com/j...dsr/dsrlist.a99
What do you mean by, "the Geneve would not even boot off the TI floppy disk controller" - lockup? no access to the TI controller or something else?
I had the crubase of the TIPI board set to >1800 so it should be clear of any DSK1 device search ( since my TI FDC is at >1100 , and is installed, and normally works )
With the TIPI at >1800, and the DSR installed, the TI Floppy controller light turns on, selects the SYSTEM/SYS (if I recall correctly) file, but it never reads a track per the little display on my gotek drive.
The boot eprom first looks for the horizon ramdisk by checking for a device starting with "HD". If found, it looks for subprogram >10 and if found, ramdisk boot code is executed.
Next the boot eprom looks for device WDS starting at CRU 0x1000. If found, it looks for device DSK1 on that same CRU. If THAT is found, LOAD/SYS is loaded via opcode 0x07.
If neither the ramdisk or wds (hfdc) device are found, the final test is for the boot eprom to detect a controller at 0x1100 then determine which low level routine to use.
My guess at this point is your TIPI EPROM has a WDS device name in its linked list, the boot eprom finds DSK1 on the TIPI cru, then hangs or does some other weird thing. You might want to try a TIPI EPROM with just TIPI in the device name list. Then you can determine (1) will the Geneve boot with TIPI in the system when there are no unexpected device name combinations and (2) can you read the TIPI EPROM contents via GPL. (You can do this by placing a value of 0xBA into memory address 0x8002, the memory mapper byte for the 0x4000 page. Assuming Genmod allows that sort of thing.
Edit: was missing the word 'no' in item (1) and needed to clarify which eprom I was referring to in a few sentences.
There are no HD devices in the TIPI DSR ROM, and no WDS devices. WDS only shows up if one of the other crubits on the board is 'set'. It is 'not set' by default.
The POWERUP routine on the board does appear to execute as I do see it reset the TIPI services on the PI.
Someday when I am bored, I'll give that a try... I believe we went through the same process when I couldn't get ROMPAGE to work with my TIFDC but I could see the TIFDC DSR ROM.
Which eprom version are you using with your GenMod Geneve?
The only other thing I could think to suggest, to confirm no decoding issues, is to run MEMTEST to make sure there are no pages with errors. With a GenMod, no pages at >3A and up to >FF should have been tested as the GenMod stock eprom was modified for the GenMod. Still, running the MEMTEST program would confirm no memory issues that could have caused the system to fail.
What it says on the screen is "v1.00" ... "genmod version"
I can maybe test that with the DSR pulled... with the TIPI board installed there should be 2 bytes that fail to retain a value written to them.
Normally memtest indicates I have 1900000ish bytes of ram. Someday.
My priority is getting this project working on the 4A. I'm really not interested in the Geneve in GPL mode. And getting TIPI to work in MDOS is an OS rewrite. So this is an extremely low priority for me.
Maybe it will just work on a normal Geneve. Maybe it is just tripping over my 150ns eprom. Maybe the propagation delay on all the logic in the CPLD is too slow.
Anyway, all the design files and software are up on github. If you want something like TIPI to work, dig in.
My original point stands: I cannot (am not able to) offer any support for the Geneve. I believe I have confirmed that I do not have a known working platform like yours to test in and develop in.