Thread

10bT in Duo Modem Slot - not my hack . . .

10bT in Duo Modem Slot - not my hack . . . Networking 70 posts Feb 25, 2012 — Jun 19, 2013

#31 Sun, 26 Feb 2012 - 06:31

I haven't done much disassembling of these beyond the initial entry points, it was mostly intended as a starting point for you to take a look.

However, DRVRs shouldn't be branching directly to stuff outside themselves. They'll use A-Traps and reference low memory globals, but that's more or less it. The A-Traps here will typically show up as an undisassembled data constant, although if you include the trap_names file from one of the ROM disassemblies on the FDisasm site, FDisasm will correctly display what A-Trap is being called. Including the abs_names file will do the same thing for low memory globals.

The caveat to calling out to another resource is a driver can load another resource using GetResource or similar (it'll show up as an A-Trap, if you include that file), then once loaded, start executing it. The .netBOOT driver does this, it loads the .ATBOOT DRVR resource, installs the driver, then opens it.

#32 Sun, 26 Feb 2012 - 20:18

ugh. this is a pain. lol. I am trying to get all my mac emu files transferred over from my main machine, to a junk laptop that is modern enough to be an intermediate machine. Why? because i need a floppy disk to transfer files between my duo and my main machine as I have no floppy drive.

I dont have a null modem cable made either, so I have to use floppy to transfer between machines, with an in-between machine thats networked to my main machine. Since the in-between machine runs windows 98, and my main machine runs windows 7, they dont "talk" to each other, so I have to use FTP to transfer between the two.

fun... but ill get there.

#33 Sun, 26 Feb 2012 - 21:08

:lol: Been there, done that!

SCSI & USB ZIP Drives & Disk(s) are the answer to all your EtherNet/SneakerNet trials and tribulations.

I can lend you all three for this project, or I can loan you a SCSI <-> EtherNet Box to make your life easier for this project . . . unless you have some interesting trade goods! [

] ]'>

#34 Mon, 27 Feb 2012 - 02:41

I have a parallel ZIP drive, and an internal IDE Zip drive. But that aint gonna help me on my powerbooks. lol.

I also have an internal style Jaz drive, but i lost my external jaz drive. it used the weird type of SCSI cable i had to have an adapter for.

#35 Mon, 27 Feb 2012 - 02:57

ok, i followed your steps, but I got an error on the fdisasm. Map goes to high....

Edit: NVM, i think both resource drivers have to be in the same file. hang on....

#36 Mon, 27 Feb 2012 - 03:02

hmmm.. it didnt disassemble. it gave me a listing, but it appears to be all garbage, and all in dc.b

#37 Mon, 27 Feb 2012 - 03:12

Scroll down, see if there's disassembly starting at around $180ish. The first part of the file is just the resource for header information, which isn't relevant, and isn't executed code...

#38 Mon, 27 Feb 2012 - 03:16

ok, yes i see. But it appears that it only disassembled one subroutine.

#39 Mon, 27 Feb 2012 - 03:18

You should see labels for E_CTBIn_Open, E_CTBIn_Prime, etc. which should each be a Bra instruction, that goes to L0, L1, etc. labels.

#40 Mon, 27 Feb 2012 - 03:22

Ya, I see those. But thats it. no meaty stuff. I guess I am going to have to figure out what those pea.l instructions are i guess. I have no idea what addressing mode this instruction uses.

#41 Mon, 27 Feb 2012 - 03:29

Yup, welcome to my life at the moment. I usually keep a copy of the 68k PRM open while going through the listing.

As an example, here's my current disassembly project of the netBOOT and ATBOOT drivers from the IIsi ROM. It's not exactly fast or sexy work...

#42 Mon, 27 Feb 2012 - 03:39

I guess one way to find out is use easy68k and simulate the sucker. Pretend there is a driver call or something.

#43 Mon, 27 Feb 2012 - 03:47

I don't think it'll get very far in easy68k, but you could write an app that'll open the driver, then trace through it using macsbug... But that will only get you through the open routine. The Control and Status routines each key off the csCode element of the ParamBlock structure, a pointer to which gets passed in A0 (DCtlEntry structure pointer is in A1, return value in D0), so you pretty much either need to disassemble those routines to figure out what values get passed in and what they mean, or set a macsbug breakpoint on those routines and fiddle around with stuff until they get called, then follow them through.

#44 Mon, 27 Feb 2012 - 04:02

Ya, its totally broken in easy68k becuase it doesnt understand the PCrel function that the disassembler used. And it complained about the addressing modes. I am assuming everything in a driver is going to be a relative addressing mode, because it doesnt know what the OS is doing and where the OS places it in memory. You would think anyway...

Ill try the macsbug thing, ill probably use a terminal program and try to talk to the modem. This way, i can see what address the modem resides.

#45 Mon, 27 Feb 2012 - 04:29

Why don't you guys just post in Sanskrit or . . . 8-o

I've re-titled your hack thread, lemme know if it's acceptable . . .

< drags knuckles back to cave workshop to take his frustrations out on a blank of flint, flaking atlatyl dart points . . . :I >

#46 Mon, 27 Feb 2012 - 04:40

it seems as if your pissed off at us about something?

#47 Mon, 27 Feb 2012 - 05:14

No, I just finished reading all of this. I think he's actually impressed. I know I am.

#48 Mon, 27 Feb 2012 - 05:21

Not a chance, RUN WITH IT!!!!!!!!!!! [

] ]'> Go team 68kMLA!!!!!!!!!!!!! :approve:

Dinosaurs get pissed off at themselves for becoming Dinosaurs! [

] ]'>

BTW: check the last post of the first page, I requested a suitable title and offered to change it to anything you suggested. This stuff if fabulous!

I'm just embarrassed that I can't follow even 10% of a great discussion/learning experience/hacking project . . . :-/

edit: Right on the money! I am VERY impressed!

#49 Mon, 27 Feb 2012 - 05:32

Hey, don't feel too bad. I'm right there with you barely following this. I've always wanted to be that level of hacker but couldn't. So I'll sit on the sidelines and cheer y'all on. I'm with Trash80toHP_Mini, keep goin with this. It's projects like this that keep our old machines alive and still productive.

PS: Great example would be the NADSBox at club100

#50 Mon, 27 Feb 2012 - 05:34

ok. good. I was just afraid. Well you know how it is, a person can read text a 1000 different ways and put thier own assumed personality to it. Sorry

#51 Mon, 27 Feb 2012 - 05:35

NoPro! I put "not my hack" in the title so the rest of the gang would take this project seriously! :lol:

edit: Holy crap, Batman! Two Full Pages of serious reverse engineering already . . . and counting!

#52 Mon, 27 Feb 2012 - 06:12

FWIW, I've added mappings for a near full disassembly of the CTP drivers, and a mostly complete disassembly of the DSP driver.

duodsp4.dsk

Nothing popped out at me while disassembling, but I haven't followed it closely. I mostly just set up the mappings.

From the Duo System devnote, it's probably somewhere in the $5000 0000 - $5FFF FFFF range, since that's dedicated to IO devices.

#53 Mon, 27 Feb 2012 - 22:03

Somewhere? ROFL.... thats a pretty large range. But in the devnote some of this could be eliminated

#54 Tue, 28 Feb 2012 - 01:59

Well i could take the brute-force method out, wiring the modem slot address/data lines to buffers and then to LEDs.

Then using a small BASIC app i could rotate through the addresses until I hit the one that lights the LEDs. Bad thing about this, is if there is a configuration register or data direction register somewhere that has to be set before this bus will operate, but i doubt it.

#55 Tue, 28 Feb 2012 - 02:52

i tried your new disk image, I keep getting map goes to high on the fdisasm.

#56 Wed, 29 Feb 2012 - 01:47

Yea, I must be missing something. I cannot get this to disassemble with your new setup.

#57 Wed, 29 Feb 2012 - 01:49

I might have to pull out my 68K duo instead of my PPC duo running OS8. And put a fresh load of system 7 on my 68k duo, and try it again. On a hardware note, I wonder if i will trip any system errors or GPFs if i "scan the band" if you know what mean, until i find the one that controls the modem.

#58 Wed, 29 Feb 2012 - 03:52

I've been (and will probably continue to be for a week or so) distracted, but...

It sounds like your file doesn't match my file. You'll probably need to get the DRVRs from 7.1, like what I've got.

But... Are you sure the data pump is wired into the address space at all? The PowerBook Duo System devnote includes a pinout of the modem connector, and it is pretty modem specific. No address or data lines in the description.

#59 Wed, 29 Feb 2012 - 03:58

No, becuase they are not listed in the Devnote. Why they didnt list them, I have no idea. There isnt even a hint of a serial port either. Just control lines they list. I guess it wasnt intended for 3rd party manufacturers to produce modems.

However If you pull the datasheet to the RCV144DPL, you will notice that the IC requires a Data and Address control bus. The IC does also give you a full RS232 serial port, but its Synchronous (USRT) so it requires a clock signal for the Send and Receive control lines, its for the V.24 compressor. But its all done in software/CPU i think on the duo. Plus, why would they have 50 pins on the connector? almost all of them are used it appears.

#60 Wed, 29 Feb 2012 - 12:27

Is this the place I drop the fact/factoid/rumor that the Mac serial ports can take an external clock signal, and run faster than Localtalk? I know the Farallon serial/ethernet adapters do it.

Also, the second hardware serial port is available from the docking connector, yeah?

And:

http://www.sparkfun.com/products/10004

http://www.sparkfun.com/products/10253

http://www.sparkfun.com/products/10269

http://www.sparkfun.com/products/10808

http://www.sparkfun.com/products/10822 (versions available with on-PCB antenna or antenna socket)

http://www.sparkfun.com/products/11049 (bare module version of above)

Seems to me the cleanest thing from a Mac point of view would be something that pretends to be a modem, and squirts Ethernet/WiFi packets out the other end (which, from my reading, some of the above do).

I picked one of these things up because, well, for

Agreed

But Trash - you have gotta get it clear in your head that just because something says USB doesn't mean it converts both ways!