General Category > Lisa Troubleshooting and Repair
Lisa Video, ProFile power issue, NiCad Leak fixes, etc.
rayarachelian:
--- Quote from: AlexTheCat123 on June 15, 2021, 01:27:09 pm ---
--- Quote ---If you have a large logic analyzer it may help you debug futher
--- End quote ---
I have a USB logic analyzer, but the vast amount of data that it produces when connected to the Lisa makes it impossible to go through it all. The text and CSV files that it outputs are so large that I can't open them in any program without it crashing.
--- End quote ---
Yeah, those HP ones understand 650x and 68000 busses and can show you what the CPU is doing, what address it accesses, read/write and value and timing.
With a USB one, you'd need specialized software to analyze it.
AlexTheCat123:
So I played around with the logic analyser some more and it revealed something interesting. I hooked it up to the BD0-BD7 lines as well as the address lines A1-A7 that feed into the muxes that allow the CPU to access the shared floppy RAM. I also connected it to the select signal (S) on the muxes so that I can see when they're allowing the CPU to address the floppy RAM. I then went into service mode and tried to read the I/O ROM version number from location FCC031. Interestingly, every time it successfully read the version number, the select signal went low and stayed low for around 600ns, but each time it failed the select signal only stayed low for around 100ns. You can see this behavior in the two screenshots that I've attached. What could be causing this?
rayarachelian:
--- Quote from: AlexTheCat123 on June 17, 2021, 10:00:40 am ---So I played around with the logic analyser some more and it revealed something interesting. I hooked it up to the BD0-BD7 lines as well as the address lines A1-A7 that feed into the muxes that allow the CPU to access the shared floppy RAM. I also connected it to the select signal (S) on the muxes so that I can see when they're allowing the CPU to address the floppy RAM. I then went into service mode and tried to read the I/O ROM version number from location FCC031. Interestingly, every time it successfully read the version number, the select signal went low and stayed low for around 600ns, but each time it failed the select signal only stayed low for around 100ns. You can see this behavior in the two screenshots that I've attached. What could be causing this?
--- End quote ---
Looking at: https://lisaem.sunder.net/LisaSchem/Lisa1SysIO4.gif
By Select you mean !CS on pin 8 of the two SRAMs, yes?
Could be R28 (s/b 47Ohm) or U4C LS157 pin 12 (4Y), or it's input lines 4A, 4B. 4A should go to ground, so that's easy to check.
4B goes to Y0 of U5A S139, so one of it's inputs could be the cause.
That could be the XNOR S02 gate at U8A (pin 10), A11, A12 of the 6504, but likely these aren't it as those come from the 6504 itself.
There's also some fun components in the center left of the schematic, right under the SRAMs, there's a transistor Q7 with 3 resistors going to capacitor 28.
Not sure if those can pull down the signal or mess with it, doesn't look like it, but who knows, if they're messed up in some way they might.
(R54 is acting as a pullup from the looks of it, and R26 too)
Lisa2:
Guys,
Just to clarify, the drawing that Ray linked is actually the 2/10 I/O board with the IWM chip.
I have attached the correct drawing for the 2/5 I/O board.
rayarachelian:
--- Quote from: Lisa2 on June 17, 2021, 05:27:14 pm ---Just to clarify, the drawing that Ray linked is actually the 2/10 I/O board with the IWM chip.
I have attached the correct drawing for the 2/5 I/O board.
--- End quote ---
D'Oh! Thanks for that. That came from here: https://lisaem.sunder.net/cgi-bin/bookview2.cgi?zoom=0?page=8?book=6?Go=Go and is labeled "Lisa 1 I/O Board 4" - are the ones labeled "Lisa210Sys" swapped with the "Lisa1" ones?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version