wyerd Posted December 12, 2014 Share Posted December 12, 2014 (edited) I'm waiting for my HxC to arrive, but in the meantime I've added the 80/80/80 EPROM chips to the FDC board. Tursi suggested that I could test the FDC by issuing the command OLD DSK1.X which should reply with an error code other than I/O ERROR 50, but it returns with 50. http://atariage.com/forums/topic/232560-just-connected-my-peb-for-the-first-time/?p=3128503 Is possible to fault find the FDC board, or is it beyond hope, which I hope not as it would be $50 down the drain? I expect it's my soldering skills, or lack of! Thanks, Dave. Edited December 21, 2014 by wyerd Quote Link to comment Share on other sites More sharing options...
Stuart Posted December 12, 2014 Share Posted December 12, 2014 Does the FDC LED flash when you power on the console? Have you got a Minimem cartridge, which can be used to check the DSR can be read? Quote Link to comment Share on other sites More sharing options...
wyerd Posted December 12, 2014 Author Share Posted December 12, 2014 (edited) Does the FDC LED flash when you power on the console? Have you got a Minimem cartridge, which can be used to check the DSR can be read? Nothing from the led. I've got Extended Basic V2.7. That's about it. The flex cable and 32Kx8 card leds do flash and work ok. Edited December 12, 2014 by wyerd Quote Link to comment Share on other sites More sharing options...
+Ksarul Posted December 12, 2014 Share Posted December 12, 2014 Try something crazy and put it into a different PEB slot and try again--sometimes pins in those connectors go bad. . . Quote Link to comment Share on other sites More sharing options...
atrax27407 Posted December 12, 2014 Share Posted December 12, 2014 I can send you a replacement chipset if you wish. If you think that is the problem but I doubt that is the case since you got a valid error message on your first P-Box test. Quote Link to comment Share on other sites More sharing options...
Stuart Posted December 12, 2014 Share Posted December 12, 2014 In your last photo, second pin up from the bottom left - is that a solder blob up against the trace that runs past it? No other solder blobs - a bit difficult to tell from the photo? Quote Link to comment Share on other sites More sharing options...
wyerd Posted December 12, 2014 Author Share Posted December 12, 2014 Try something crazy and put it into a different PEB slot and try again--sometimes pins in those connectors go bad. . . Tried that, same result. Quote Link to comment Share on other sites More sharing options...
wyerd Posted December 12, 2014 Author Share Posted December 12, 2014 I can send you a replacement chipset if you wish. If you think that is the problem but I doubt that is the case since you got a valid error message on your first P-Box test. I'm sure the EPROMs you sent are ok, but I'm not sure where the valid error message was. They gave either 00 or 50, the last 0 being the device error. That's my understanding of the explanation Tursi gave. I expect that I'm totally wrong! Quote Link to comment Share on other sites More sharing options...
wyerd Posted December 13, 2014 Author Share Posted December 13, 2014 In your last photo, second pin up from the bottom left - is that a solder blob up against the trace that runs past it? No other solder blobs - a bit difficult to tell from the photo? Yes, it does look like there's a tiny blob on or extremely near to the trace. I'll check with a magnifying glass. The traces are extremely close together, more than I'm used to. Quote Link to comment Share on other sites More sharing options...
RXB Posted December 13, 2014 Share Posted December 13, 2014 (edited) If you have RXB 2001 or later you can do a CALL IO command. IO PAGE I10 ------------------------------------------------------------- Programs Line 100 clears screen. | >100 CALL CLEAR Line 110 explains program. | >110 CALL HPUT(4,7,"This is a | demo of the",6,7,"CALL IO(3 | ,8,2176,B)",8,7,"3 = TYPE(CR | U output)",10,7,"8 = NUMBER | OF BITS",12,7,"2176=address/ | 2") Line 120 turn off card, show | >120 CALL IO(3,8,2176,0):: FO the present byte value being | R B=0 TO 255 :: CALL HPUT(14 sent. | ,7,"B=byte (value "&STR$(B)& | ")") Line 130 display block to get | >130 CALL HPUT(18,5,"******** attention. | ******************",19,5,"WA | TCH THE DRIVE LIGHTS",20,5," | **************************") Line 140 send byte to card and| >140 CALL IO(3,8,2176,B):: NE when done with loop, clear for| XT B :: CALL HCHAR(14,24,32, starting over program. | 7):: GOTO 110 | The above program will only work on a REAL TI not EMULATORS. Line 100 explains program. | >100 ! TURNS OFF/ON/OFF EACH | CARD FROM >1000 TO >1F00 BUT | WILL LOCKUP WITH CERTAIN | CARDS. Line 110 cru address from | >110 FOR CRU=2048 TO 3968 STE >1000 to >1F00 | P 128 Line 120 turn off card, turn | >120 CALL IO(3,8,CRU,0,3,8,CR on card, delay for 2 seconds, | U,255)::FOR A=1 TO 200::NEXT turn off card. | A::CALL IO(3,8,CRU,0) Line 140 loop till done. | >140 NEXT CRU Options Some CRU address are used by the Operating System or XB and any attempt to redefine them will create problems. Also some of the address areas will return incorrect values as they have changed since IO has accessed them. These problems will never become completely apparent at first, so take care. Additionally some cards have the same problem, if the card has a program that has a interrupt or CRU links turned on as you access it, a complete lock up will result as a fight for control ensues. So with that happy thought, a alternate way is to use EXECUTE or LINK instead. The above RXB program will find the Disk Controller card and turn on the DSR of each card and test if they work. 100 CALL CLEAR 110 CALL HPUT(4,7,"This is a demo of the",6,7,"CALL IO(3,8,2176,B)",8,7,"3 = TYPE (CRU output)",10,7,"8 = NUMBER OF BITS",12,7,"2176=address/2") 120 CALL IO(3,8,2176,0) :: FOR B=0 TO 255 :: CALL HPUT(14,7,"B=byte (value "&STR$(B)&") ") 130 CALL HPUT(18,5,"************************",19,5,"*WATCH THE DRIVE LIGHTS*",20,5,"************************") :: CALL INVERSE(42) 140 CALL IO(3,8,2176,B) :: NEXT B :: CALL HCHAR(14,24,32,7) :: GOTO 110 The above RXB program will test each Disk Drives all at once all drive lites will come on. You can change the value in CALL IO to spin up each drive and test the mother board on each drive. (Note: these demos will not work on any Emulator.) Edited December 13, 2014 by RXB Quote Link to comment Share on other sites More sharing options...
kl99 Posted December 13, 2014 Share Posted December 13, 2014 afaik another check would be to compare the SIZE values in XB with and without the Disk controller Card. If the DISK DSR initializes, it reserves part of the memory for its file buffer and io handling. And isn't the TI Diagnostics on your XB 2.7 to try out? BR Klaus 2 Quote Link to comment Share on other sites More sharing options...
+Ksarul Posted December 13, 2014 Share Posted December 13, 2014 Definitely try the TI Diagnostics program in the XB 2.7 Suite out--it may help you isolate the problem. Quote Link to comment Share on other sites More sharing options...
wyerd Posted December 13, 2014 Author Share Posted December 13, 2014 afaik another check would be to compare the SIZE values in XB with and without the Disk controller Card. If the DISK DSR initializes, it reserves part of the memory for its file buffer and io handling. And isn't the TI Diagnostics on your XB 2.7 to try out? BR Klaus Size is the same with or without the FDC. 13928 & 24488. Quote Link to comment Share on other sites More sharing options...
wyerd Posted December 13, 2014 Author Share Posted December 13, 2014 Definitely try the TI Diagnostics program in the XB 2.7 Suite out--it may help you isolate the problem. OK. I'm running the Automatic option, then option 2. is that correct? Thanks for helping out guys. Quote Link to comment Share on other sites More sharing options...
wyerd Posted December 13, 2014 Author Share Posted December 13, 2014 There's definitely power going to it as the rear voltage regulator is very hot (ouch!) Quote Link to comment Share on other sites More sharing options...
wyerd Posted December 13, 2014 Author Share Posted December 13, 2014 it's cycled the auto test a couple of times with No Error Detected. Quote Link to comment Share on other sites More sharing options...
wyerd Posted December 13, 2014 Author Share Posted December 13, 2014 Yes, it does look like there's a tiny blob on or extremely near to the trace. I'll check with a magnifying glass. The traces are extremely close together, more than I'm used to. I removed the blobs before I started the tests above. Quote Link to comment Share on other sites More sharing options...
wyerd Posted December 13, 2014 Author Share Posted December 13, 2014 Blobs removed. Looks better but still doesn't work. Quote Link to comment Share on other sites More sharing options...
+Ksarul Posted December 13, 2014 Share Posted December 13, 2014 You should definitely see a difference in memory size, the 13K should drop to about 12K, with no change to the 24K. One additional idea: try it with the original EPROMs if you didn't destroy them. That will help eliminate one of the problem vectors. Quote Link to comment Share on other sites More sharing options...
wyerd Posted December 13, 2014 Author Share Posted December 13, 2014 You should definitely see a difference in memory size, the 13K should drop to about 12K, with no change to the 24K. One additional idea: try it with the original EPROMs if you didn't destroy them. That will help eliminate one of the problem vectors. Originals had their legs cut off unfortunately. Not looking good. Quote Link to comment Share on other sites More sharing options...
atrax27407 Posted December 13, 2014 Share Posted December 13, 2014 I can send you a chipset that restores the original configuration. Send me a PM. Quote Link to comment Share on other sites More sharing options...
atrax27407 Posted December 14, 2014 Share Posted December 14, 2014 You didn't, by any chance, solder the EPROMs directly into the circuit board, did you? Quote Link to comment Share on other sites More sharing options...
wyerd Posted December 14, 2014 Author Share Posted December 14, 2014 No. You should be able to see the EPROMs in the sockets in the first photo above. Quote Link to comment Share on other sites More sharing options...
atrax27407 Posted December 14, 2014 Share Posted December 14, 2014 Just wanted to make sure everything was eliminated. Quote Link to comment Share on other sites More sharing options...
wyerd Posted December 14, 2014 Author Share Posted December 14, 2014 Sure. Thanks for taking another look. Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.