System test rom/Board
-
- Posts: 326
- Joined: 27 Nov 2016 19:58
Re: System test rom/Board
I take it that the test ROM contents can go on an EEPROM and go into the ROM A socket?
Re: System test rom/Board
It should work fine as a stand alone 8k image replacing the A rom. It's completely self contained.stephen_usher wrote: ↑09 May 2019 22:51 I take it that the test ROM contents can go on an EEPROM and go into the ROM A socket?
-
- Posts: 326
- Joined: 27 Nov 2016 19:58
Re: System test rom/Board
May I suggest a change to the memory test?
When the test fails could the test stop at that location and print a map of which bits failed? This would allow the determination of which chip the fault is in.
Also, is there space for a memory decode test for paged RAM. Maybe fill the "lower" 32K with '1's, page in the upper 16K and write '0's, page it out again and test the 32K again for flipped bits? Maybe do this constantly until interrupted. This would check that the RAM paging sub-system is working properly.
When the test fails could the test stop at that location and print a map of which bits failed? This would allow the determination of which chip the fault is in.
Also, is there space for a memory decode test for paged RAM. Maybe fill the "lower" 32K with '1's, page in the upper 16K and write '0's, page it out again and test the 32K again for flipped bits? Maybe do this constantly until interrupted. This would check that the RAM paging sub-system is working properly.
Re: System test rom/Board
The memory test could be re-written to stop at a failed read back, and then print something along the lines of "Value read :XX value expected :XX". at which point the test would have to stop. I don't think there's enough registers to do much more than that. Re-starting and only halting once the screen space runs out isn't an option.
If it's possible to print the diagnostic message without destroying the values needed to resume the test, then it probably also possible to add in a "press [a key] to resume or [a key] to exit" option too.
There's currently 3 of the EOR memory tests, but they use the same base code. It's the tweaking the input conditions that enables the testing of the 3 different area, which are the 32k of page 0, 48k of page 0 or 16k of page 1.
Before that last test is started, the equivalent area on page 0 is cleared. Though it can't be tested directly the memory dump function of the monitor can be used to check if any shadow writes occur on page 0 during the page 1 test.
Re-writing page 0 after page 1 is written, but before it's read back isn't an option with the current code, as the memory test itself doesn't use paging.
Reading OR Writing to the wrong bank should be picked up on the test, but not both. If, because of paging issues, read and write did go to different banks, the readback would fail. It's very unlikely though that the memory system could fail that way, as the PAL code doesn't use the *RD input in the RAM equations, just *MREQ.
If it's possible to print the diagnostic message without destroying the values needed to resume the test, then it probably also possible to add in a "press [a key] to resume or [a key] to exit" option too.
There's currently 3 of the EOR memory tests, but they use the same base code. It's the tweaking the input conditions that enables the testing of the 3 different area, which are the 32k of page 0, 48k of page 0 or 16k of page 1.
Before that last test is started, the equivalent area on page 0 is cleared. Though it can't be tested directly the memory dump function of the monitor can be used to check if any shadow writes occur on page 0 during the page 1 test.
Re-writing page 0 after page 1 is written, but before it's read back isn't an option with the current code, as the memory test itself doesn't use paging.
Reading OR Writing to the wrong bank should be picked up on the test, but not both. If, because of paging issues, read and write did go to different banks, the readback would fail. It's very unlikely though that the memory system could fail that way, as the PAL code doesn't use the *RD input in the RAM equations, just *MREQ.
-
- Posts: 326
- Joined: 27 Nov 2016 19:58
Re: System test rom/Board
Having it print the expected and obtained values would definitely be useful to identify the bad bit. I'm not sure that you'd want to restart if you've found a bad chip until after you'd replaced that chip anyway. After all, if you replace the chip with a known good one then you only have a maximum of eight tests if they're all bad in some way.
As for the page tests, surely once you know that you have a working unpaged 16K memory then you can then switch over to using memory for further tests? This should simplify things for the code.
As for the page tests, surely once you know that you have a working unpaged 16K memory then you can then switch over to using memory for further tests? This should simplify things for the code.
Re: System test rom/Board
Test rom updated to build 245.
the Ram test has been expanded to stop on read failure with a brief diagnostic as shown on this screen dump from the emulator. Since the emulator never actually fails the read back, this is actually fake,
but it looks better than a photo of my 1980's green screen monitor would !
The update has been made to the common code, so all memory 3 tests will halt on failure and update the diagnostic line.
At this point there is, I think, 6 bytes free in the data area and 8 in the code area, so not much scope for any further changes.
Dumps of the full 32k rom and just the 8k diagnostic rom are in the ZIP below.
the Ram test has been expanded to stop on read failure with a brief diagnostic as shown on this screen dump from the emulator. Since the emulator never actually fails the read back, this is actually fake,
![Very Happy :D](./images/smilies/icon_e_biggrin.gif)
The update has been made to the common code, so all memory 3 tests will halt on failure and update the diagnostic line.
At this point there is, I think, 6 bytes free in the data area and 8 in the code area, so not much scope for any further changes.
Dumps of the full 32k rom and just the 8k diagnostic rom are in the ZIP below.
-
- Posts: 326
- Joined: 27 Nov 2016 19:58
Re: System test rom/Board
Excellent! Yeah, I'm not sure you'd be able to do much in 8 bytes.Martin A wrote: ↑31 May 2019 18:14 Test rom updated to build 245.
the Ram test has been expanded to stop on read failure with a brief diagnostic as shown on this screen dump from the emulator. Since the emulator never actually fails the read back, this is actually fake,but it looks better than a photo of my 1980's green screen monitor would !
NEWTEST.JPG
The update has been made to the common code, so all memory 3 tests will halt on failure and update the diagnostic line.
At this point there is, I think, 6 bytes free in the data area and 8 in the code area, so not much scope for any further changes.
Dumps of the full 32k rom and just the 8k diagnostic rom are in the ZIP below.
roms245.zip
![Smile :-)](./images/smilies/icon_e_smile.gif)
Re: System test rom/Board
You say those are surface mount caps? How do you solder them on the veroboard? I can't picture it?
Steve G
Danish Memotech MTX 512, MFX and loving it
Danish Memotech MTX 512, MFX and loving it
Re: System test rom/Board
With solder ??
0805 is a very convenient size for proto boards. The pad spacing of 0.10" gives sufficient space to fit the 0.08" lenghth of the surface mount part. Plus it leaves room for solder and 30awg hookup wire.
The photo is actually from the network socket of the MFX prorotype because I have that to hand. In shot are 2 4.7k resistors,a pull up and a pull down mounted flat, and couple of 100nf capacitors. One on edge in the foregrounf, one convenrional flat at the back, both for smothing. The ROM board has a couple of flat mounted caps because the were fitted before the wiring. Unlike the sideways one here, that was an "oops forgot something" addition. NB the green wire is connected with a solder bridge to the ground it's another one of the later changes to the board.
I've tried other sizes 1206 fits OK if you go diagonally across 2 pads. at 0.12" its really a bit too long to fit straight. 0603 Is fiddly but workable. 0402 is too small for comfort it barely spans the gap between pads and tends to get pulled all over the place by the solder.
-
- Posts: 2
- Joined: 23 Jan 2024 08:14
Re: System test rom/Board
Hi,
Is there any chance the source for builds 234 and 245 can be posted here ?
Have there been any further developments on this rom since 245 ?
Cheers.
Is there any chance the source for builds 234 and 245 can be posted here ?
Have there been any further developments on this rom since 245 ?
Cheers.