nikola-wan
Veteran Member
Jos,
I have some good news - I think I found a combination of components that work in both your first MFM board and my assembly with different RTC, and both work in my 4052 and 4054A!
The components that made the difference are:
Since both MFM ran the same tests, in both slots of my 4052 and 4054A and passed all the tests - I think the SLOW logic is not needed.
[tr]
The only ROM image that has issues in the MFM is the 4907 File Manager, but my workaround was removing the 4907 File Manager from the MFM and installing the 4907 ROM pack in the left slot and MFM in the right slot.
This could be a software problem due to the order of the ROM images in the MFM - but it doesn't have to be solved right now.
Here is a table of what I tested:
[tr]
There are a couple of issues - but I don't think they should block other folks from enjoying your Multifunction ROM Pack for the 4052
I would also recommend you provide the right GAL and EPROM, pre-programmed and tested, as I spent weeks ordering different ones that didn't work.
Example ones that don't work:
4052 ROM images that I did not test:
There was one other oddity during my testing, I was able to get your Diagnostic ROM Pack in the left slot to dump the CRCs for your MFM ROM pack in the right slot only in my 4054A.
Since all the reported CRCs matched CRC-16 calculated by HxD for each of the images in my MFM15.BIN, I think this is the best confirmation that your MFM is working.
The oddity is neither your original MFM nor my assembled MFM report any checksums when installed in the right slot of my 4052 with the Diagnostic ROM pack in the left slot.
I thought it might be due to the same issue as the RS-232 slot number (crossed BSX signals between left and right slots?), so I changed my test program to address the MFM as if it was in the left slot and that hung the 4052.
I don't think this should keep anyone from using the MFM, in particular I think the folks would find adding the Diagnostic ROM to slot 1 in the MFM valuable to tell them what BASIC firmware version they have by running my CRCDUMP program that does not attempt to access the ROM Expander slots.
Thanks for all your hard work on this 4052/4054 ROM Pack Jos!
The ROMs in the MFM15.BIN image I tested provide support for all the programs I have uploaded to github - and the programs that run on floppy will work by plugging in a 4907 ROM Pack plus your MFM, so total success!
Monty
I have some good news - I think I found a combination of components that work in both your first MFM board and my assembly with different RTC, and both work in my 4052 and 4054A!
The components that made the difference are:
- GAL: Lattice 22V10D-25
- ROM: AMD AM27C010-70DC
- No SLOW logic components installed
- Your 0903 JED file
- My MFM15.BIN ROM image:
Since both MFM ran the same tests, in both slots of my 4052 and 4054A and passed all the tests - I think the SLOW logic is not needed.
ROM Pack image | Expansion ROM slot# | Hex address range |
Blank | 1 | 00000-03FFF |
Blank | 2 | 04000-07FFF |
RS-232 Printer Interface | 3 | 08000-0BFFF |
741RTC TransEra Real Time Clock | 4 | 0C000-0FFFF |
750SPU TransEra Super Utilities | 5 | 10000-13FFF |
Graphics Enhancement R12 | 6 | 14000-17FFF |
Character & Symbol R11 | 7 | 18000-1BFFF |
Blank | 8 | 1C000-1FFFF |
The only ROM image that has issues in the MFM is the 4907 File Manager, but my workaround was removing the 4907 File Manager from the MFM and installing the 4907 ROM pack in the left slot and MFM in the right slot.
This could be a software problem due to the order of the ROM images in the MFM - but it doesn't have to be solved right now.
Here is a table of what I tested:
ROM Pack tested | Test Program | Result | Comments |
RS-232 | LIST @43: (MFM in 4052 right slot) LIST @53: (MFM in 4054 right slot) | Passed with bluewire from IFC1 pin 5 to pin 7 (DTR to DCD) | DTR/DCD hardware handshake needed or the bluewire. Slot is wrong in 4052 - I think BSX signals in slots are swapped in 4052, see text for more info. |
741RTC | RTCTEST.TXT program | Passed | including reboot with the small program stored in RTC CMOS |
750SPU | CALL "750SPU" | Passed | I need to do more testing of other CALLS |
GraphEnh | R2D2 program | Passed | lots of fast graphics calls |
Chr&Symbol | couple of simple CALLs | Passed | need to create a test program for this |
There are a couple of issues - but I don't think they should block other folks from enjoying your Multifunction ROM Pack for the 4052
- Opposite slot number for RS-232 in 4052, but right slot number in 4054
- 4907 File Manager didn't work in MFM, but needs to be separate ROM slot
- Diagnostic ROM image in slot 1 works to show the BASIC ROM CRCs, but not MFM ROMs
I would also recommend you provide the right GAL and EPROM, pre-programmed and tested, as I spent weeks ordering different ones that didn't work.
Example ones that don't work:
- Atmel AF22V10C15PU and Atmel ATF22LV10CQZ-30PU both did not work in this design
- Lattice 22V10D - I got on EBAY must have been clones, could not be programmed
- Atmel AT27C010-70PU EPROM was one-time-programmable - only worked once
4052 ROM images that I did not test:
- EDITOR ROM - I don't think this is needed, I use Notepad++
- 4909 Advanced File Manager - I don't have a 4909 hard disk system
- GPIB Enhancement for 4052 or A-series - I haven't used these ROM Packs
- TransEra 735-SIF RS-232 interface, not needed, particularly if the Tek RS-232 can replace the backpack RS-232 you get full support from the internal BASIC including TERMIN
- TransEra 764 Auxiliary Memory - I don't have the memory box, but wonder if the ROMs would work on a big static RAM - future Jos project
There was one other oddity during my testing, I was able to get your Diagnostic ROM Pack in the left slot to dump the CRCs for your MFM ROM pack in the right slot only in my 4054A.
Since all the reported CRCs matched CRC-16 calculated by HxD for each of the images in my MFM15.BIN, I think this is the best confirmation that your MFM is working.
The oddity is neither your original MFM nor my assembled MFM report any checksums when installed in the right slot of my 4052 with the Diagnostic ROM pack in the left slot.
I thought it might be due to the same issue as the RS-232 slot number (crossed BSX signals between left and right slots?), so I changed my test program to address the MFM as if it was in the left slot and that hung the 4052.
I don't think this should keep anyone from using the MFM, in particular I think the folks would find adding the Diagnostic ROM to slot 1 in the MFM valuable to tell them what BASIC firmware version they have by running my CRCDUMP program that does not attempt to access the ROM Expander slots.
Thanks for all your hard work on this 4052/4054 ROM Pack Jos!
The ROMs in the MFM15.BIN image I tested provide support for all the programs I have uploaded to github - and the programs that run on floppy will work by plugging in a 4907 ROM Pack plus your MFM, so total success!
Monty