Email or username:

Password:

Forgot your password?
Top-level
Tube🍂Time

pulled the main power transformer for reverse engineering purposes.

92 comments
Tube🍂Time replied to Tube🍂Time

last night i reverse engineered it. the design is simple so it wasn't too hard. the files are here: github.com/schlae/Thinkpad700C

Tube🍂Time replied to Tube🍂Time

it also explains the mystery "INPUT SIGNAL" pin on the old 4-pin IBM Thinkpad power connector. this pin simply increases the output current limit when it is pulled low by the laptop. it's because the power brick is also the battery charger, and when the laptop is turned on, you have to increase the current to compensate.

Tube🍂Time replied to Tube🍂Time

anyway, isopropyl alcohol wipes and a bath in Simple Green has mostly taken care of the bad smell.

Tube🍂Time replied to Tube🍂Time

now for that pesky docking connector: I've discovered that a 1.2mm PCB fits perfectly in the connector, so I made a set of two boards that stack and break out all the pins to 0.1" headers.

George Laskowsky replied to Tube🍂Time

@tubetime Please don't step on those! Lego is bad enough already

math blasterson replied to Tube🍂Time

@tubetime Haha, that was actually my first thought when you started this thread. "Those are just dressed up card-edge connectors." Nice job.

Tube🍂Time replied to Tube🍂Time

now you know why I need a working logic analyzer. these pins also go to the hard disk connector inside, which makes me think they are the internal bus. the trick is to figure out what they do.

Dustin replied to Tube🍂Time

@tubetime holy smokes you are really deep-diving on this one, well done!

Tube🍂Time replied to Tube🍂Time

next step is to identify control lines vs address and data

DrYak replied to Tube🍂Time

@tubetime when you manage ti document it, you're probably going to make a few hardcore ThinkPad fan happy.

Expect retro OPL2/3 sound card and joystick ports to appear.

Tube🍂Time replied to Tube🍂Time

starting to pick out a few lines. between the cursors is an extended bus cycle

Tube🍂Time replied to Tube🍂Time

now I'm writing short programs in DEBUG to help me figure out which data lines are which.

Tube🍂Time replied to Tube🍂Time

i've got all the address and data lines mapped out, and all the basic control lines. now to figure out the DMA lines...

Tube🍂Time replied to Tube🍂Time

and that's 99% of it figured out. i haven't untangled which IRQ is which, and there are a small number of signals i don't understand yet. but this is functional enough to start building adapters. i'll publish this at some point.

Tube🍂Time replied to Tube🍂Time

there are a few signals unique to the hard drive connector, so I'm figuring those out now.

Tube🍂Time replied to Tube🍂Time

the unique signals are the card setup line (turns out this is slot 1 and the dock connector is slot 2), the high address bits predecoded, IDE style, and what seems to be a system reset line.

Tube🍂Time replied to Tube🍂Time

the hard disk drive has a weird 60-pin AMP CHAMP connector (5176376-2) but that just gets wired to a 52-pin 2mm header. the pin wiring is 1:1 except for the last 8 pins which are not connected.

Tube🍂Time replied to Tube🍂Time

it was surprisingly hard to figure out that AMP part number, btw. connector manufacturers constantly scrub all information about old products because who knows 🙃

Tube🍂Time replied to Tube🍂Time

and yes, the hard drive is vaguely like IDE but it uses the Micro Channel bus instead of ISA. IBM called it DBA (direct bus attach) ESDI. this drive uses the POS ID code DF9F.

Tube🍂Time replied to Tube🍂Time

i needed to figure out which interrupt lines were which, so i wrote a quick and dirty program to detect when an interrupt fires. then i manually triggered them by grounding each pin in turn.

Tube🍂Time replied to Tube🍂Time

on to a few physical repairs! this corner got really trashed by the hinges, so i need to figure out a way to restore it.

Tube🍂Time replied to Tube🍂Time

i've used a similar technique to repair an Amiga 500. the idea is to 3d print the missing piece.

Tube🍂Time replied to Tube🍂Time

it's a quick 20 minute print even with a 0.3mm nozzle, 0.12mm layer height, and 100% infill.

Tube🍂Time replied to Tube🍂Time

the next step is to carefully carve away at the plastic so that it fits well. small gaps are ok, there needs to be a little room for the glue.

Tube🍂Time replied to Tube🍂Time

for the glue i am using JB Weld. a little excess is ok since i can file and sand it down afterwards. the locking forceps are clamping the plastic part to the metal tab i installed a few weeks ago.

Tube🍂Time replied to Tube🍂Time

I'm also doing the other side as well where the damage was less extensive. unfortunately the DC-IN legend is damaged and the connector icon is half missing, so I need to figure out how to replace it. a water slide decal might work.

Cellivar replied to Tube🍂Time

@tubetime Paint pen and a steady hand? ;)

Your work is great to watch!

Darryl Ramm replied to Tube🍂Time

@tubetime All this is making me miss my old Thinkpad 701 Butterfly. Damn that keyboard design was so neat.

Tube🍂Time replied to Tube🍂Time

the glue has dried. I'm not crazy about the fit but it is much better than before. it should look pretty good after I paint it, someday.

Tube🍂Time replied to Tube🍂Time

the laptop was missing the modem cover so I'm making a new one. this design is supposed to slide in place, but I think the original was supposed to hinge down, and probably didn't have any openings in it.

Tube🍂Time replied to Tube🍂Time

oh wow i found documentation for the weird protocol used by the 2.5" ESDI hard drive!

Tube🍂Time replied to Tube🍂Time

a simple program should be able to retrieve these error codes. perhaps i can fix the hard drive?

SLeiBt replied to Tube🍂Time

@tubetime Fingers crossed it's not something that needs opening the enclosure to fix, as doing so outside of a clean room would most likely render it toast (bad sectors developing) a short while afterwards.

Tube🍂Time replied to Tube🍂Time

i did a little logic analyzer probing. it's waiting like 288ms for the HDD to respond, and when it reads the status register, it gets FAFF. this doesn't really make sense because upper bits should be 000 indicating the drive, not the controller.

FozzTexx replied to Tube🍂Time

@tubetime Other endian and the bits are inverted?

Tube🍂Time replied to Tube🍂Time

i needed to verify that the DMA arbitration bits were in the correct order on the docking port, so i've decided to use the Type 3 parallel port to trigger arbitrary DMA transfers. you can configure the arbitration level in the setup program.

Tube🍂Time replied to Tube🍂Time

this simple program configures the parallel port for Type 3 operation, turns on DMA, and starts a single DMA send transfer.

Tube🍂Time replied to Tube🍂Time

the operation won't start until the parallel port is ready--i had to pull the BUSY line low with a jumper, and now i instantly get this error! good luck figuring that one out
EDIT: i figured it out, 113 is a DMA arbitration error, presumably the "5" is the arbitration value. DMA controller going off into the weeds lol

Tube🍂Time replied to Tube🍂Time

ok, the machine crashed because we didn't set up the DMA controller, but that doesn't matter because the number '5' showed up on the arbitration bus! this experiment, along with a few others, let me confirm which arbitration pin is which.

Tube🍂Time replied to Tube🍂Time

i'm troubleshooting the weird DBA-ESDI drive (type DF9F) and it's very strange because it sets a bit indicating a power on self test failure, but when you try to retrieve the failure code (basic and advanced) it's all zeros.

William D. Jones replied to Tube🍂Time

@tubetime Where's the code setting up the DMA channel so the parallel port doesn't read/send data from the weeds? :D

lopta replied to Tube🍂Time

@tubetime I've seen 3.5" ESDI but never 2.5"!

George R. M. 🇩🇪🇺🇦 replied to Tube🍂Time

@tubetime for a second there I forgot these use the aptly-nicknamed "ThinkPad 700 drive". What a cursed thing it was, DBA-ESDI 2.5".

Glen Akins replied to Tube🍂Time

@tubetime My guess would be acquisitions and not caring about all the product lines of the acquired company. Good news is now that TE owns all connector manufacturers*, they won't have this excuse going forward. (*slight exaggeration)

Brad Bell replied to Tube🍂Time

@tubetime I like how they keep making the connector but change the names and numbers

bitsavers.org replied to Tube🍂Time

@tubetime

I started archiving catalogs from connector companies just because of that problem.

Jeff Haluska replied to Tube🍂Time

@tubetime Haven't seen somebody do that in about 25 years.

Go Up