Hello,
I have done some testing and this is were i am at now.
Measured all the adress lines and datalines without a ROM, with A12 "patch", and no decoder. I had the trigger on AS and recorded 500ms after it found a trigger. To trigger i held the reset, started the measurment and then released the reset button. This is the results. There was 5 AS low.
Adressline 1 to RIGHT.
AS 1: 00000000000000000000000 LDS:0 UDS:0
AS 2: 10000000000000000000000 LDS:0 UDS:0
AS 3: 01000000000000000000000 LDS:0 UDS:0
AS 4: 11000000000000000000000 LDS:0 UDS:0
AS 5: 11111111111111111111111 LDS:1 UDS:1
Dataline 1 to RIGHT
AS 1: 1111111111111111
AS 2: 1111111111111111
AS 3: 1111111111111111
AS 4: 1111111111111111
AS 5: 1111111111111111
Then i did the same but with a ROM in (which i do not know it was 2.06 or EmuTOS).
Adressline 1 to RIGHT.
AS 1: 00000000000000000000000 LDS:0 UDS:0
AS 2: 10000000000000000000000 LDS:0 UDS:0
AS 3: 01000000000000000000000 LDS:0 UDS:0
AS 4: 11000000000000000000000 LDS:0 UDS:0
AS 5: 00010000000010000110111 LDS:0 UDS:0
Dataline 1 to RIGHT
AS 1: 1110000000000100
AS 2: 0101010000000110
AS 3: 00111101001111?0
AS 4: 000000010000?1?0
AS 5: 111111111111111?
The reason there is questionmarks is becouse the dataline was both values during the duration of AS low. See picture at the bottom. Also on the last AS low on the test WITH ROM it was low for about 8.333us before going high. This happened only on the test when ROM was inserted.
On a sidenote. I dont know if this has any relevance but i thought i might say it just in case. When i measure AS WITH ROM and decoder in place it seems to loop. The weird thing is that the amount of time that an adressline is when its HIGH seems to double each step i take on the adressline.
Adressline 1 has a top thats 1us that loops. When i measure Adressline 2 it has a top thats 2us that loops. A3 has 4us. A4 has 8us and so on. So 23 has over a second as high.
/zChris
- DSC_1388.JPG (168.89 KiB) Viewed 2796 times