Thread
Duo 2300c/180 MHz 603e QFP Graft/Hack . . .
Me too, ciao! 
)
) The Duo has it all in ROM, remember Apple announced a PCMCIA Dock and then didn't deliver, even after Newer had done the Design and had the Tooling done for the PCMCIA UltraDock. They wound up just using it for everything BUT housing the T-Rex/Card Cage.
I wouldn't be at all surprised if the 1400, 5300 and 2300 all use what is basically the same ROM, because they're very close being different packaging of the the same machine, IIRC. The Duo 2300c was released with the PB 1400, if memory serves.
We'll probably have to cook up a Dock DeclROM to do it though, but that's fairly well documented . . .
. . . for an Apple product/spec. :
Dock DeclROM? only if the dock PDS is on a different interrupt vector level or something than the original TREX driver requires it to be.
But if its in ROM, then it should already be there. just load the PCMCIA driver and go.
But if its in ROM, then it should already be there. just load the PCMCIA driver and go.
You might be right, however, while I'm at it, it sure would be nice to lie to the friggin' thing, so I can uncouple the ^&%$^#%$# left and right speaker channels . . .
. . . among other juicy little tidbits I'v been working on/whittling away at . . . lo, these many years! }
Muahahahahahhahahahaaaaaaaaa!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! :lol:
. . . among other juicy little tidbits I'v been working on/whittling away at . . . lo, these many years! }
Muahahahahahhahahahaaaaaaaaa!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! :lol:
i know how these "many years" things goes. there are soo many projects I need to complete myself and never have.
I had an RC lawnmower that was all electric, i made from scratch. control circuitry, remote, all of it. took me 2 years until i got it done. finally got it done, had some bugs and other similar issues, but overall it worked ok. it cut the lawn. and i didnt have to physically ride or push it. LOL.
But it burned up in a fire. since the cutting deck was home made out of wood, the drunks decided to burn it in a fire. NICE. :disapprove: (i live in a boarding house environment)
couple of other unfinished projects is a set-top audio spectrum analyzer which i still need to finish, using soviet VFD display tubes.
I also need to finish the MP3 player that uses SD storage, and uses another VFD as its display tube. has a VU meter, and 14 segment alphanumeric. VS1001 decoders are hard to come by, which is why it never got finished.
I made an encrypted cordless phone that worked for awhile and eventually something went screwy in the modem and i never got around to fix it. I used a standard cordless phone with a 24kbit AAC (i think) codec IC, and scrambled the 512-byte stream buffer with a 512bit RSA key in an ATmega128. it worked great. ;-) only major pitfall is the phone ONLY worked if the other person had the same phone, and the audio quality was TERRIBLE, but that was the fastest i could go, as the phone line bandwidth is obviously limited so the modulator couldnt go any faster. it was running fast enough support the 24kbit AAC, I also had to use a 5 block size buffer, not only becuase the encryption took a little while, the audio was choppy. the buffer fixed the choppy audio, but increased the lag time. i didnt care as long as audio wasnt choppy.
the modulator/demodulator consisted of XR2204 AFSK decode/Encode ICs, if memory serves. it was AFSK hot all the time. The "magic" (modulator/scrambler/encoder) sat in between the microphone and the MIC amplifier on the handset. I had to remove the low pass filters to get the entire bandwidth of the handset. Same thing with the earpiece. the demodulator sat in between the earpiece and the amplifier on the handset.
This also meant i couldnt hear plaintext or analog sounds. ONLY the modulated sounds. so i coudlnt hear DTMF tones, or dialtones. just hope like hell it worked. hehe. and it always did. If someone picked up the phone, it would sound like the old time fax machines on the line. lol. I never added a mixer circuit so I could hear the analog as well as digital, and once the Exar IC locked, it would "disable" the analog mix path. it would have been simple to do, just didnt bother. Another cumbersome setback was I had to turn off the MIC modulator while i was dialing, or the "AFSK noise" would interfere and cause issues dialing. But no big deal, after i dialed the phone i would switch the modulator on.
me and a buddy of mine would call each other and use them all the time, and not have to worry about eavesdroppers. Then he passed away, and the project died, never did fix the issue. as he had the other handset.
Before he passed away, the future plans were to fix those issues, and add new ones, such as modulating ASCII text transmissions, so i would know "who" was calling besides what the caller ID said. But i dunno if the PSTN would transmit anything unless the other end "picked up" so it probably wouldnt work until i picked up the phone anyway. I would have also added the ability to change keys on the fly, as I would set my phone up as a master phone, transmit the key to the secondary phone and "rotate keys" for each call or something. Bad thing about that would be, unless i could encrypt the key that i transmit, the encryption could be broken.
I had an RC lawnmower that was all electric, i made from scratch. control circuitry, remote, all of it. took me 2 years until i got it done. finally got it done, had some bugs and other similar issues, but overall it worked ok. it cut the lawn. and i didnt have to physically ride or push it. LOL.
But it burned up in a fire. since the cutting deck was home made out of wood, the drunks decided to burn it in a fire. NICE. :disapprove: (i live in a boarding house environment)
couple of other unfinished projects is a set-top audio spectrum analyzer which i still need to finish, using soviet VFD display tubes.
I also need to finish the MP3 player that uses SD storage, and uses another VFD as its display tube. has a VU meter, and 14 segment alphanumeric. VS1001 decoders are hard to come by, which is why it never got finished.
I made an encrypted cordless phone that worked for awhile and eventually something went screwy in the modem and i never got around to fix it. I used a standard cordless phone with a 24kbit AAC (i think) codec IC, and scrambled the 512-byte stream buffer with a 512bit RSA key in an ATmega128. it worked great. ;-) only major pitfall is the phone ONLY worked if the other person had the same phone, and the audio quality was TERRIBLE, but that was the fastest i could go, as the phone line bandwidth is obviously limited so the modulator couldnt go any faster. it was running fast enough support the 24kbit AAC, I also had to use a 5 block size buffer, not only becuase the encryption took a little while, the audio was choppy. the buffer fixed the choppy audio, but increased the lag time. i didnt care as long as audio wasnt choppy.
the modulator/demodulator consisted of XR2204 AFSK decode/Encode ICs, if memory serves. it was AFSK hot all the time. The "magic" (modulator/scrambler/encoder) sat in between the microphone and the MIC amplifier on the handset. I had to remove the low pass filters to get the entire bandwidth of the handset. Same thing with the earpiece. the demodulator sat in between the earpiece and the amplifier on the handset.
This also meant i couldnt hear plaintext or analog sounds. ONLY the modulated sounds. so i coudlnt hear DTMF tones, or dialtones. just hope like hell it worked. hehe. and it always did. If someone picked up the phone, it would sound like the old time fax machines on the line. lol. I never added a mixer circuit so I could hear the analog as well as digital, and once the Exar IC locked, it would "disable" the analog mix path. it would have been simple to do, just didnt bother. Another cumbersome setback was I had to turn off the MIC modulator while i was dialing, or the "AFSK noise" would interfere and cause issues dialing. But no big deal, after i dialed the phone i would switch the modulator on.
me and a buddy of mine would call each other and use them all the time, and not have to worry about eavesdroppers. Then he passed away, and the project died, never did fix the issue. as he had the other handset.
Before he passed away, the future plans were to fix those issues, and add new ones, such as modulating ASCII text transmissions, so i would know "who" was calling besides what the caller ID said. But i dunno if the PSTN would transmit anything unless the other end "picked up" so it probably wouldnt work until i picked up the phone anyway. I would have also added the ability to change keys on the fly, as I would set my phone up as a master phone, transmit the key to the secondary phone and "rotate keys" for each call or something. Bad thing about that would be, unless i could encrypt the key that i transmit, the encryption could be broken.
:O About 90% of the technical end of that phone phreakin' $#!+ went . . .
< Peanut Mode >
eeeerrrrwwwwwtttttttt!!!!!!!!!!!!!!!!!!!!
< /Peanut Mode >
. . . right over my head! :I
Sounds way cool though! :approve:
Cripes! You sound nuttier than me . . . and that's goin' a fer piece! The only thing I ever wanted to do that'd p1$$ off the NSA was to write a one time pad encryption routine that'd use specific AOL installation CD releases as generally available, non transmitted, Digital One Time Pad Keys . . .
. . . and you're doing that kind of crap over the phone lines!!!!!!!!!!!!!!!!!!!!!! 8-o
Yeah, I know, waaayyyyyy too much Clancy in my noggin's bibliography, but not enough Programming Texts ( I have a love/hate relationship with coding . . . with a major league side order of procrastination and laziness as garnish [
] ]'> ) to do anything really useful. So I mull things over and think up outlandish hardware hacks and try to pull 'em off without resorting to programming!
Necessity may be the "mother of invention," but creative laziness and tomfoolery are the "whacked out uncles" of invention . . .
. . . that none of the respectable members of the family ever talk about! } :beige: )
< Peanut Mode >
eeeerrrrwwwwwtttttttt!!!!!!!!!!!!!!!!!!!!
< /Peanut Mode >
. . . right over my head! :I
Sounds way cool though! :approve:
Cripes! You sound nuttier than me . . . and that's goin' a fer piece! The only thing I ever wanted to do that'd p1$$ off the NSA was to write a one time pad encryption routine that'd use specific AOL installation CD releases as generally available, non transmitted, Digital One Time Pad Keys . . .
. . . and you're doing that kind of crap over the phone lines!!!!!!!!!!!!!!!!!!!!!! 8-o
Yeah, I know, waaayyyyyy too much Clancy in my noggin's bibliography, but not enough Programming Texts ( I have a love/hate relationship with coding . . . with a major league side order of procrastination and laziness as garnish [
] ]'> ) to do anything really useful. So I mull things over and think up outlandish hardware hacks and try to pull 'em off without resorting to programming!Necessity may be the "mother of invention," but creative laziness and tomfoolery are the "whacked out uncles" of invention . . .
. . . that none of the respectable members of the family ever talk about! }
:beige: )
Chip's here, pics are up!
Spent a bit of time with the digital camera yesterday after picking the CPU Card from the Complex Rental Office the evening before.
I've got some more things and materials to order/scrounge up, along with some other victims coming in for practice runs before I start doing SMT rework on this lil' puppy. So don't expect results to be posted very soon, I'll be taking my time.
As a side note: thee has been some real progress on the SuperDuo front!
I finally had a chance to test something I've wanted to check out ever since the inception of the 2300cG3 project . . .
. . . and it fits!
Next experiment: Check to see if Sonnet's NuBus Accelerator will run reliably on the end of its matching PDS extension cable. }
Spent a bit of time with the digital camera yesterday after picking the CPU Card from the Complex Rental Office the evening before.
I've got some more things and materials to order/scrounge up, along with some other victims coming in for practice runs before I start doing SMT rework on this lil' puppy. So don't expect results to be posted very soon, I'll be taking my time.
As a side note: thee has been some real progress on the SuperDuo front!
I finally had a chance to test something I've wanted to check out ever since the inception of the 2300cG3 project . . .
. . . and it fits!
Next experiment: Check to see if Sonnet's NuBus Accelerator will run reliably on the end of its matching PDS extension cable. }
oh jeebus. NOW we are in trouble......... hahaha.
that 603 is pretty. wish i had one, that CPU pitch is the same pitch of the SCSI transceivers from TI that i just soldered down on the AVR SCSI board.
ive got 2 duo 2300s. one of them is a real 2300 missin some parts (side rubbers) and torn trackpad cable.
and the other one is a duo 280c upgraded 2300 (complete minus SCSI HDD)
that 603 is pretty. wish i had one, that CPU pitch is the same pitch of the SCSI transceivers from TI that i just soldered down on the AVR SCSI board.
ive got 2 duo 2300s. one of them is a real 2300 missin some parts (side rubbers) and torn trackpad cable.
and the other one is a duo 280c upgraded 2300 (complete minus SCSI HDD)
I got a 7100 from a friend of a friend who used it in college and wanted to find it a good home! }
I haven't done anything drastic yet, but I set up the Upgrade on a Stick (PDS extension cable above) test in it, (didn't wanna risk either my Radius 81/110 or the extra board for it) mounted a fan to blow air in for cooling where I had it flopped over the carrier card and . . .
. . . no joy at all. :'(
Works fine in the slot, but not hangin' out onna' limb.
I'll give Sonnet a call, it might just be be an addressing/slot assignment issue, but somehow I don't think two adapter boards and this Flex Circuit are going to be the simplified solution I was looking for.
SuperDuo is gonna take a bit more thinkin' n researchin', BLEH! :disapprove:
I haven't done anything drastic yet, but I set up the Upgrade on a Stick (PDS extension cable above) test in it, (didn't wanna risk either my Radius 81/110 or the extra board for it) mounted a fan to blow air in for cooling where I had it flopped over the carrier card and . . .
. . . no joy at all. :'(
Works fine in the slot, but not hangin' out onna' limb.
I'll give Sonnet a call, it might just be be an addressing/slot assignment issue, but somehow I don't think two adapter boards and this Flex Circuit are going to be the simplified solution I was looking for.
SuperDuo is gonna take a bit more thinkin' n researchin', BLEH! :disapprove:
IIRC, that PDS extender only works on the downstream side of the G3 upgrade, ie between the G3 and a PDS video card - and only a video card. I don't think anything but a video card even works plugged straight into the PDS passthru on the G3, so it's likely the ribbon only has enough lines for that and nothing else.
But wait ... you're hoping to run a desktop G3 upgrade card in a Duo?
But wait ... you're hoping to run a desktop G3 upgrade card in a Duo?
Nope, still looking at ways to adapt a CrescendoPB to the Modem Cubic, this was just a down and dirty test of the cable.
BTW, if a CrescendoPB works, ANY 1400 ProcCard ought to work! :b&w:
BTW, if a CrescendoPB works, ANY 1400 ProcCard ought to work! :b&w:
...why? Surely you're going to need a completely different cable for the actual hack?
Which gives you the option of using vanilla 1400 CPU cards as disposable testbeds
. . . and allows other DuoHackers to find far less expensive/READILY AVAILABLE, cache-on-board 603ev ProcCards from the 1400 series to speedbump their 2300s . . .
. . . instead of the CrescendoPB! }
I'm not yet convinced that Sonnet's cable won't work, it looks like a straight passthru cable to me (that fits!) with some intervening circuitry that likely allows 2 PDS cards to be addressed in one PDS Slot.
It's probably very similar to that super-expensive SE/30 multicard adapter with the mysterious PAL on board. Disable that kinda nonsense and I'll bet the Sonnet Card will run just fine on the end of its matching cable!
If this doesn't work out, I'll just have to do ONE adapter card that's a lot more complex a task than doing two simpler cards for the ends of the existing/available Sonnet cable . . .
Ahhhh now I understand - you want to go socket->cable->G3->HPV, instead of socket->G3->cable->HPV, so you can move the G3->HPV elsewhere in the case. Well, seeing as both the HPV and the G3 can sit in the 601 PDS socket, sure, why not?
You may not have to. If I remember my PDS lore, the cards themselves (at least 030 PDS ones) carry pseudo-slot IDs - the relative position on a multi-card chain matters not.
Only one fly in that ointment, they're all BGA CPUs on those cards. However, if I can get 1400 cards and T-Rex to work within the Duo's case, I might be tempted to try overclocking it!
I think my precious QFP 603e is going to go into my best (read: Beater Quality Plastics) 5300ce. There's already some overclocking info from TomLee available and that beautiful 800x600x16bit Spanned Display tips the scales in that direction . . .
. . . not to mention the T-Rex/Card Cage already on board! }
EDIT: forgot to mention the 5300ce 64MB (artificial) RAM limit > the 2300c 48MB (waaaayyyyyyyy artificial) RAM ceiling.