• Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.

2.5" SCSI SSD Project

Once this project is done and over with, i am going to make a replacement modem for the PB1XX series
Click to expand...
Sounds like a great candidate for having a Duo Modem Connector's Thru-Holes on the opposite side pf the PCB! ;)

Beautiful Boards, Baby!

mode>

 
I dont know the pinouts of the duo modem connector. I tried looking through developer notes, it doesnt really explain any digital pinout/signaling that i could see. Only the analog side of it, like ring, etc... no TX/RX pins are labeled for the motherboard duo connector.

Only way i am going to be able to find out is if i trace the SCC chip, assuming one knows the pinout of the SCC. Then when i do the CAD drawings, i have to draw in the power buttons exact positioning as well, as the power button is on the modem board. :-)

 
I did screw up when i did the header footprints. I made the hole-size the size of the pins. and copper ring double-that.

Well, of course the header pins dont fit. LOL.

So ill have to solder the headers on the surface.

 
I found out why they sent me 2 boards.

If you look at the connection between R5 and the ID headers, it didnt come out. some of the copper is missing. I looked the whole board over, and started testing connections with my meter, and found that one.

So i looked at the second board, its fine. Thats why they sent me 2 boards. i was wondering. i only ordered 1. but hey, i got an extra, and its a trace that a small regular wire can fix real easy.

I forgot 3 resistors and ran out of room for an electrolytic filter cap anyway.... But all can be fixed.

So when i get them both built and working, i am probably going to sell off one of the prototypes to help pay for the 2.5" ones.

 
Fix the design for this board as you're doing the schematics for the 2.5" prototype, keep one board unpopulated for testing . . .

. . . and do a short run of the 3.5" Form Factor boards and you'll get several orders! [:D] ]'>

Prototypes belong in display cases, production boards are for jump-starting further development! :o)

 
I brought my rework station home from work today, so hopefully ill get a little time this weekend to start assembling the board.

 
Made some assembly progress today, Got all of the SMD ICs mounted in place, except for one. the ATmega165, which was on backorder it should be in this week sometime.

Soldering the transceivers were a PITA, rest wasnt so bad.

I used the flashlight trick to discover and fix any bridges and shorts. then verified all was connected via the meter.

DSC00008.JPG

DSC00009.JPG

 
I got the rest of the parts in today, so hopefully ill have something built and running by the weekend, maybe not running, but at least something for DEBUG. :-)

I had to wait for the ATmega165 to come in, which is used for IC1. IC1 emulates the 53C80/Variants to a degree in target mode. So that was a bit important. lol.

 
the board is finished :-)

at least i hope. lol. Getting ready to start writing/programming/debugging the firmware.

both MCUs are recognized by the utility, so that means my hardware is good and the chips have a heartbeat :-)

 
CF MCU post PASSED. :-) :-) :-) no errors.

CF card locked and mounted. PCMCIA socket services enabled. ATA controller enabled and ready. T_T Nexus established.

But im having SCSI voodoo. im thinking i still have a bug in the SCSI MCU. gotta fixie.

 
Hmmm... Seems this is our problem. MORE debugging to do. YAAAAYYYY

But she is alive.

Code: 
SCSI controller debug system
============================

Hardware: V2.0, Firmware: V1.0 (Build: 2006-06-24T13:27:21 UTC)

Init target:
Create UNIT ATTENTION condition for LUN 0 (Reset)
Enable interrupts ... OK

Target POST:
SRAM test ... OK
POST complete

Init PCMCIA card services:
PCMCIA card found

Init PIA:
Read our SCSI ID from jumper block ... 2
Configure PIA for target mode ...
Cannot configure PIA
Fatal error (E3): PIA failure

I will die now
 
BINGO.... I had an extra interrupt vector in my ASM code. had to fix that. once i fixed that, and removed the org 0x002E, the PIA is now functioning :-)

Code: 
SCSI controller debug system
============================

Hardware: V2.0, Firmware: V1.0 (Build: 2011-04-24T14:40:29 UTC)

Init target:
Create UNIT ATTENTION condition for LUN 0 (Reset)
Enable interrupts ... OK

Target POST:
SRAM test ... OK
POST complete

Init PCMCIA card services:
[PCMCIA CS] Initialize card services
[PCMCIA SS] Initialize socket
[PCMCIA SS] Set address: 0x03FFFFFF
[PCMCIA SS] Set address: 0x00000000
[PCMCIA SS] Set latched control lines: 0x20
[PCMCIA SS] Read socket status: 0x01
[PCMCIA CS] Card status: CP
PCMCIA card found

Init PIA:
Read our SCSI ID from jumper block ... 2
Configure PIA for target mode ...
[PIA] Init PIA
[PIA] Get status ...
[PIA] Read STATUS register: (0x04) OK
[PIA] Check status: Ready
[PIA] Send CONFIGURE command to PIA ...
[PIA] Write CONTROL register: (0x01) OK
[PIA] Write DATA register: (0x02) OK
[PIA] Write DATA register: (0x01) OK
[PIA] Wait for IRQ ... Got it
[PIA] Get status ...
[PIA] Read STATUS register: (0x05) OK
[PIA] Check status: Ready and enabled
[PIA] Init was successful
PIA has enabled the SCSI interface

Boot complete

Starting taskrouter
[Task router] Prepare for next task
[PIA] Get status ...
[PIA] Read STATUS register: (0x05) OK
[Task router] Idle
 
Ok, time to try it on the SCSI bus.

I tried 3 programs. all 3 have failed. 2 of them lock up, and 1 of them actually shows the drive ID2 but no VENDOR info for it. hmm.

I attached the logs of DEBUG.

apple SCSI HD setup and HWT harddisk toolkit keep wanting to select LUN 14 command EE over and over and over again. hangs up the APP of course.

It wants to IDENTIFY LUN14. there is no lun14. only lun0 is supported. what could be in LUN14? Makes you want to go hmmmm...... The firmware is SCSI-3 compliant. it should work, guess not.

Log of those 2 apps:

Code: 
SCSI controller debug system

============================


Hardware: V2.0, Firmware: V1.0 (Build: 2011-04-25T00:07:43 UTC)


Init target:

Create UNIT ATTENTION condition for LUN 0 (Reset)

Enable interrupts ... OK


Target POST:

SRAM test ... OK

POST complete


Init PCMCIA card services:

PCMCIA card found


Init PIA:

Read our SCSI ID from jumper block ... 2

Configure PIA for target mode ...

PIA has enabled the SCSI interface


Boot complete


Starting taskrouter

[Task router] Prepare for next task

[Task router] Idle

[Task router] An initiator selects us

[Task router] Connected to initiator with SCSI ID 7

[Task router] I_T nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message: EE 

[Task router] IDENTIFY message received

[Task router] LUN 14 selected

[Task router] I_T_L nexus established

[Task router] ATTENTION condition detected
but Micronet utility v6.9.5 actually shows the drive, but no info for it. it produces a different debug output, giving me a command timeout error.

Log of that program:

Code: 
SCSI controller debug system

============================


Hardware: V2.0, Firmware: V1.0 (Build: 2011-04-25T00:07:43 UTC)


Init target:

Create UNIT ATTENTION condition for LUN 0 (Reset)

Enable interrupts ... OK


Target POST:

SRAM test ... OK

POST complete


Init PCMCIA card services:

PCMCIA card found


Init PIA:

Read our SCSI ID from jumper block ... 2

Configure PIA for target mode ...

PIA has enabled the SCSI interface


Boot complete


Starting taskrouter

[Task router] Prepare for next task

[Task router] Idle

[Task router] An initiator selects us

[Task router] Connected to initiator with SCSI ID 7

[Task router] I_T nexus established

[Task router] ATTENTION condition detected

[Task router] Receive message from initiator

[Task router] Message transmission error

[Task router] Release SCSI bus

[Task router] Prepare for next task

[Task router] Idle
 
I just wanted to make sure you knew you weren't talking to yourself . . .

. . . but in my case . . . you may as well be at this point. :-/

Good luck on the DEGUB trail! :o)

 
I am trying to find someone that is familiar with the mac scsi interface.

because to the SCSI docs, EE would fall as an illegal IDENTIFY signal, as it sets one of the reserve bits when both are supposed to be cleared. So that tells me i have crosstalk or signal distortion.

 
Have you got Designing Cards and Drivers for the Macintosh Family? One of the design examples is a NuBus SCSI Interface Card, IIRC.

Maybe that'd help? :-/

 
You must log in or register to reply here.

Similar threads

zigzagjoe
Repair of a basket case DiimoCache030
Replies
5
Views
551
Bolle
Bolle
A
LC 575 / 577 / 578 - PDS and Comm Slot failure due to factory omission of U33 on logic board (with fix)
Replies
3
Views
937
dougg3
D
B
Mac OS on ANS - Modding a ROM DIMM
2
Replies
24
Views
2K
joevt
J
David Cook
ADTX SCSI IDE 2.5 inch Adapter Compatibility and Performance
Replies
11
Views
5K
hauke
H
croissantking
How to repair a Powerbook 140-180 interconnect cable
Replies
12
Views
3K
demik
demik
Back
Top