ZS Pico Slim (w/PICO W) - failing on NeXTstation mono slab

[vom513]

Apologies in advance if this should be a discussion - please change it to one if prudent.

I just got my first ZS PS today. I soldered the Pico on, and soldered the db25 on. From what I can tell from the pictures - the pico side is the "bottom". Therefore I mounted the db25 as such.

Trying to get the Nextstation to read from CDROM on this results in errors. Even when it tries to boot the HDD image it gives an error.

I hooked up one of my ZS 1.2 boards to it and was able to boot, install, and run NextStep 3.3. So I'm pretty sure my Nextstation is good.

I will attach the ini file and log (I had debug on). As you will see, the log messages look as though the PS boots fine, it's running the latest FW (I upgraded it on first power on). It sees my HD and CD images. It's just when SCSI messages actually try to pass that things fall apart.

Thanks for any insight.

PS: I don't have time today but I will try the Pico Slim on one of my Sun sparc machines as well (I'll probably try the IPX).

[vom513]

zululog-next.txt

zuluscsi-next.ini.txt

[vom513]

So I put the PS on my Sparcstation 10. I normally have a ZS 1.2 in there. You can see the strange way the OBP detects the PS (two targets, tons of LUNs).

The 1.2 comes up normal/expected with HDDs at 1 + 3 and a CDROM at 6.

[aperezbios]

@vom513 I converted this to a discussion, as it doesn't appear to be a hardware problem. With any self-assembled kit, you are your own QA guy, so if you haven't already, please double-check all of your solder joints. Chances are high that the underlying issue resides here.

It isn't possible for you to solder the DB25 connector on backwards, as the DB25 pins are staggered between the two sides and it's therefore extremely obvious which way is correct, and which is not.

In the NeXT log you supplied, I see the folllowing:
[14662ms] DBG ---- COMMAND: WriteFilemarks
This tape-specific SCSI command is unsupported. Where is it coming from?

[ZigZagJoe]

It looks strongly like you have an issue with the SCSI data bus; command 0x0 is TestUnitReady, which is a sensible thing for a SCSI exchange to start with. Command 0x10 is WriteFilemarks which is not sane. Odds are it's a soldering issue somewhere.

[vom513]

Yep it was soldering. I was much too frugal on the Pico soldering and there were some positions not connected.

I just made another pass and I'm installing NextSTEP on it now.

Thanks for the guidance and sorry for the noise.