Skip to the content
2 layers99.8 × 99.8 mmPistormTester, the printed circuit board in 3D

A Breakout and visualization board for monitoring PiStorm outputs.

Size
99.8 × 99.8 mm
Copper layers
2
Thickness
1.6 mm
Parts
92
Nets
127
Pads
451
Tracks, vias
1,086, 137
Pours
4
Routed
Yes
KiCad
KiCad 5 (file 20171130)
Created
21 Jun 2021
Updated
5 Dec 2022

Overview

PistormTester is an open-source printed circuit board by abrugsch, from the abrugsch/PistormTester repository on GitHub. It is a 2-layer board of 99.8 × 99.8 mm with 92 parts on 127 nets, routed with 1,086 tracks and 137 vias.

Its parts include 60 diodes, 9 connectors, 4 capacitors, 2 ICs and 1 resistor.

README

README.md

PiStorm Tester

image

Assistance:

If you've gone through the instructions below and watched the video and you need more help decoding what the board is telling you (some things are not so obvious if you're not ultra familiar with the PiStorm schematic) then feel free to hit me up. the best way is usually through Discord via the PiStorm server and I'm @ABrugsch on there too.

Donate:

If you build these, consider Buying me a coffee I have spent a considerable amount of time refining the board and the tests that go with them, and will often help people understand what their ZZ9 is telling them. A little coffee goes a long way to helping me keep my sanity 🙂
ko-fi

What is?

PiStorm Tester is a PCB that exposes all the IO's of the 68000 DIP64 socket that PiStorm uses. There are status LED's on all the control/Address/Data Bus lines to easily see if a single line is stuck high or low. Each IO is also broken out to a header for easy connection to an external microcontroller such as an arduino for more accurate analysis of the outputs, or for pulling inputs high or low as required. where the line is either an input or bi-directional (such as the Data bus) the headers have a handy VCC and GND rail adjacent for easy jumpering. Combined with testing programs on the pi such as buptest, it becomes easy to narrow down individual faults such as unsoldered or broken individual flip-flops.

Make Them

  • Latest Version gerbers: RevC.1

You can build them by hand. submit the gerbers (Rev C gerbers have adjustments made for ZIF sockets with bigger pins. If you definitely don't want to use a ZIF, a Rev-B board might fit better but RevC should be universal) to a PCB fab of your choice (AllPCB has a free promotion ATM) but then you have to place and solder 60 0603 LED's and 15 4x0402 resistor arrays by hand. That's pretty tedious so I've also included the JLCPCB production files to get them assembled. All the JLC parts are basic parts so it costs barely more to get them assembled than to just order the bare boards. (10x costs around $50 including UK delivery by courier)

  • PistormTester-top-pos-JLC.csv - JLC position file
  • PistormTester-BOM-jlc.csv - JLC BOM file
  • gerbers/PiStormTesterRevC.1.zip - latest gerber files

The big caveat is that they(JLCPCB assembly) don't have a 5v 7-ish MHz oscillator in their assembly catalog so that part has an LCSC part number (C387338) but must be sourced and placed separately. As of RevC.1 there is now a 3.3v oscillator and regulator so that all parts can be assembled by JLC with the included BOM. There are even alternative 3.3v Oscillators if the one in the BOM is out of stock. If you use a RevC or older gerber set, then the BOM and position files will be incorrect so please roll them back to earlier versions.

IMPORTANT There is now a jumper 0 Ohm resistor in the BOM and position file. If you use the 3.3v regulator and oscillator you MUST exclude R1 from the build. If you use a 5v Oscillator you MUST exclude U1, C3 and C4 from the build and keep R1.

If you do a JLC run of 10 boards, they should come in at around $30 (plus taxes and delivery - Total cost to the UK using an SMD voucher and their cheapest (about 2 weeks) delivery was $37 last time I did a batch, £35 for all red LEDs.)

The biggest costs in producing these boards are the LED's and the oscillator. If you don't care about colo(u)r of LEDs the cheapest option is to use all red ones as they are significantly cheaper than any other colo(u)r so there is an alternative BOM file with all the LED's using the cheaper RED part. (Although now that the BOM LCSC part numbers have been tweaked to put more expensive ones on places where the lowest quantity are, the difference isn't so great: about $2 between All-Red and different colours.)

  • PistormTester-all-red-BOM-jlc.csv

How to

The code folder of this repo has some simple tests for checking that the address and data busses are behaving correctly. Here are the instructions for using them on PiStorm. For more advanced tests, see the note at the bottom of this readme.

If you have a recent pull of the main PiStorm repo then you do not need to copy any files as the test files are now included in the PiStorm root folder, though you will still need to follow the build instructions below, but the code files are probably already in your PiStorm folder.
If not, then copy the files in the code folder of this repo to your pistorm folder on your pi. (put the files in directly, not in a subfolder.)
Run

./build_zz9tests.sh

to build the test program just like buptest.
Then run

sudo ./zz9fulltest

  • Test 1:
    Watch the LED's on the address bus. they should all light in turn from A1 to A23. AS should dim slightly as it goes from being held high to being pulsed. All data bits should appear to be on for the duration of this test.
  • Test 2:
    Watch the Data bus LED's. They should light in turn from D0 through to D15.
  • Test 3:
    THIS TEST ONLY WORKS FOR NON-A VARIANT FLIP-FLOPS On A-Variant flip-flops (LVC16373A or LVC16374A) the data bits won't even appear to light up as they are only on for such a brief period of time
    The zz9fulltest program will then walk the databus lines individually and read the state back so if there is a discrepancy between what is written and what is read then it will be displayed as a data mismatch error. If you want to force an error, you can go ahead and set one of the data lines high or low with the breakout area by bridging the centre row with an adjacent vcc or gnd. This is probably best done with a ~1K resistor, but not entirely necessary.

Any discrepancies at this point can be referenced to the schematic to find the appropriate pin that might need attention.

For a more thorough test of the data reads there is also zz9readloop which will loop for 2 minutes reading the data bus and displaying the results on screen in Hex and Binary.

simply run

sudo ./zz9readloop

and then modify data bits using the tweak headers and see what comes on the screen. A-variant flip-flops (LVC16373A or LVC16374A) will hold the data after you set it, allowing you to set multiple bits at a time while only using one wire/resistor to do it.

The program will read at half second intervals for 2 minutes.
ctrl-c will terminate early
There is now a video demonstrating the use of the ZZ9 board:
PiStorm Tester Howto!

Typical problems:

  • Address or data bus LED's don't come on when they are supposed to:
    This usually means the output pin of the flip-flop that should be connected to the CPU pin isn't actually connected. This can either be an incorrectly soldered CPU pin or flip-flop pin. Knowing which Data or Address pin is at fault can then be directly traced through the schematic in the code folder. It can also mean a connection from the CPLD to the flip-flops is broken. This can manifest as both an address pin AND a data pin being out. e.g. A3 and D3, due to the way the internal data path is shared.
  • Address or data LED's stuck on
    can either be a short to VCC or sometimes open circuit on the flip-flops input as the inputs can float high.
  • LED's show correct but there's a buptest read mismatch
    Run zz9readloop and while it's doing the loop, put each data pin high or low and see that the program shows the read data correctly (the state of the lights is displayed directly on the read loop in both Hex and Binary (bit) format)
    Example: if you make D3 high (connect to vcc) zz9readloop should say READ16: read data: 0x0008(hex) 0000000000001000 (binary)
  • Whole 8-bit blocks of any of the address/data busses are not working:
    each 8-bit bank (A1-7, A8-15, A16-24, D0-7, D8-15) is enabled by an output enable pin on the respective latch chip and is controlled by the CPLD. They are active low and if left floating can have unpredictable results, but usually simply fail to operate the entire bank. The OE pins to check for each bank are as follows:
bankchippin
A1-7U21
A8-15U224
A16-23U61
D0-7U51
D8-15U524

If you need to address any of these issues, here's where to start:
Data read is handled by U3 on the PiStorm
Data write is handled by U5

Address bus (write only) A1-A15 is handled by U2
Address bus A16-A23 is handled by U6

Reference the Pistorm schematic for further details of specific pins to target

Advanced tests

Currently the included tests only cover the address and data busses. There are 18 other signal lines that are handled by this tester and at the moment nothing has been written to assess these other lines.
When viewing the board, in normal operation the following should be lit (dimly as they are being strobed)

  • IPL0
  • IPL1
  • IPL2
  • BG
  • VMA
  • E
  • UDS
  • LDS
  • RW

This only covers the output of the 384 data buffers, and therefore there could also be hidden disconnections between the 384's and the CPLD.
Example: a disconnected pin on the 384 on the CPLD side of the RST line meant the CPLD I/O was floating. The test board appeared correct (light off) but in use the emulator wouldn't start because RST was toggling on and off due to floating. Re-flowing the suspect 384 resolved the problem.

Testing of the supporting signals will probably have to be done with a logic analyzer or a complementing microcontroller dev board such as an arduino (one that's 5v tolerant) to read the pins and log what states they take. This board was originally intended to have a socket for a mini/micro arduino but for the sake of flexibility was left off.

As Advanced tests are created by myself or the PiStorm community, they will be documented here. (please submit issues or pull requests for any suitable tests you need or have come up with)

Parts

92
QtyValueFootprintReferences
15R_Pack04Resistor_SMD:R_Array_Concave_4x0402RN1, RN2, RN3, RN4, RN5, RN6, RN7, RN8, RN9, RN10, RN11, RN12, RN13, RN14, RN15
3Conn_01x16_FemaleConnector_PinSocket_2.54mm:PinSocket_1x16_P2.54mm_VerticalJ4, J5, J6
21uFCapacitor_SMD:C_0402_1005MetricC3, C4
10 RResistor_SMD:R_0402_1005MetricR1
10.1uFCapacitor_SMD:C_0402_1005MetricC1
115pFCapacitor_SMD:C_0402_1005MetricC2
168000DZZ9 parts:DIP-64_W22.86mm_Socket_LongPads-big_holesU2
18MHzOscillator:Oscillator_SMD_EuroQuartz_XO32-4Pin_3.2x2.5mmX1
1AP2127N-1.0Package_TO_SOT_SMD:SOT-23U1
1Conn_01x02Connector_PinSocket_2.54mm:PinSocket_1x02_P2.54mm_VerticalJ9
1Conn_01x06_FemaleConnector_PinSocket_2.54mm:PinSocket_1x06_P2.54mm_VerticalJ3
1Conn_01x13Connector_PinSocket_2.54mm:PinSocket_1x13_P2.54mm_VerticalJ8
1Conn_02x12_Odd_EvenConnector_PinSocket_2.54mm:PinSocket_2x12_P2.54mm_VerticalJ2
1Conn_02x13_Odd_EvenConnector_PinSocket_2.54mm:PinSocket_2x13_P2.54mm_VerticalJ7
1LED_A1LED_SMD:LED_0603_1608MetricD1
1LED_A10LED_SMD:LED_0603_1608MetricD10
1LED_A11LED_SMD:LED_0603_1608MetricD11
1LED_A12LED_SMD:LED_0603_1608MetricD12
1LED_A13LED_SMD:LED_0603_1608MetricD13
1LED_A14LED_SMD:LED_0603_1608MetricD14
1LED_A15LED_SMD:LED_0603_1608MetricD15
1LED_A16LED_SMD:LED_0603_1608MetricD16
1LED_A17LED_SMD:LED_0603_1608MetricD17
1LED_A18LED_SMD:LED_0603_1608MetricD18
1LED_A19LED_SMD:LED_0603_1608MetricD19
1LED_A2LED_SMD:LED_0603_1608MetricD2
1LED_A20LED_SMD:LED_0603_1608MetricD20
1LED_A21LED_SMD:LED_0603_1608MetricD21
1LED_A22LED_SMD:LED_0603_1608MetricD22
1LED_A23LED_SMD:LED_0603_1608MetricD23
1LED_A3LED_SMD:LED_0603_1608MetricD3
1LED_A4LED_SMD:LED_0603_1608MetricD4
1LED_A5LED_SMD:LED_0603_1608MetricD5
1LED_A6LED_SMD:LED_0603_1608MetricD6
1LED_A7LED_SMD:LED_0603_1608MetricD7
1LED_A8LED_SMD:LED_0603_1608MetricD8
1LED_A9LED_SMD:LED_0603_1608MetricD9
1LED_ASLED_SMD:LED_0603_1608MetricD24
1LED_BERRLED_SMD:LED_0603_1608MetricD58
1LED_BGLED_SMD:LED_0603_1608MetricD42
1LED_BGACKLED_SMD:LED_0603_1608MetricD55
1LED_BRLED_SMD:LED_0603_1608MetricD56
1LED_D0LED_SMD:LED_0603_1608MetricD25
1LED_D1LED_SMD:LED_0603_1608MetricD26
1LED_D10LED_SMD:LED_0603_1608MetricD35
1LED_D11LED_SMD:LED_0603_1608MetricD36
1LED_D12LED_SMD:LED_0603_1608MetricD37
1LED_D13LED_SMD:LED_0603_1608MetricD38
1LED_D14LED_SMD:LED_0603_1608MetricD39
1LED_D15LED_SMD:LED_0603_1608MetricD40
1LED_D2LED_SMD:LED_0603_1608MetricD27
1LED_D3LED_SMD:LED_0603_1608MetricD28
1LED_D4LED_SMD:LED_0603_1608MetricD29
1LED_D5LED_SMD:LED_0603_1608MetricD30
1LED_D6LED_SMD:LED_0603_1608MetricD31
1LED_D7LED_SMD:LED_0603_1608MetricD32
1LED_D8LED_SMD:LED_0603_1608MetricD33
1LED_D9LED_SMD:LED_0603_1608MetricD34
1LED_ELED_SMD:LED_0603_1608MetricD44
1LED_FC0LED_SMD:LED_0603_1608MetricD45
1LED_FC1LED_SMD:LED_0603_1608MetricD46
1LED_FC2LED_SMD:LED_0603_1608MetricD47
1LED_HALTLED_SMD:LED_0603_1608MetricD51
1LED_IPL0LED_SMD:LED_0603_1608MetricD53
1LED_IPL1LED_SMD:LED_0603_1608MetricD41
1LED_IPL2LED_SMD:LED_0603_1608MetricD54
1LED_LDSLED_SMD:LED_0603_1608MetricD49
1LED_RSTLED_SMD:LED_0603_1608MetricD52
1LED_RWLED_SMD:LED_0603_1608MetricD50
1LED_SPARE1LED_SMD:LED_0603_1608MetricD59
1LED_SPARE2LED_SMD:LED_0603_1608MetricD60
1LED_UDSLED_SMD:LED_0603_1608MetricD48
1LED_VMALED_SMD:LED_0603_1608MetricD43
1LED_VPALED_SMD:LED_0603_1608MetricD57
1USB_B_MicroMy_parts:micro_usb_U-F-M5SS-W-1J1

Similar boards

  • 2 layers102.4 × 211.3 mmHaxophone001, the printed circuit board in 3D

    Haxophone001

    cardonabits/haxo-hw

    Haxophone, an electronic musical instrument that resembles a saxophone

    92 parts674
  • 2 layers40.6 × 110 mmEuropi surface mount, the printed circuit board in 3D

    Europi surface mount

    Allen-Synthesis/EuroPi

    EuroPi: A reprogrammable Eurorack module based on the Raspberry Pi Pico

    92 parts584CC0-1.0
  • 2 layers142.5 × 101 mmHillside46, the printed circuit board in 3D

    Hillside46

    mmccoyd/hillside

    Family of split ergonomic keyboards with three rows of six or five keys and a generous thumb arc

    92 parts448MIT
  • 2 layers217.6 × 68.1 mmKeezyboost40, the printed circuit board in 3D

    Keezyboost40

    ChrisChrisLoLo/keezyboost40

    4x10 ortholinear with an LCD in the middle. Uses the Raspberry Pi Pico, as well as Rust firmware

    92 parts202CC-BY-SA-4.0
  • 2 layers39 × 40 mmMdb ai bridge esp32s3, the printed circuit board in 3D

    Mdb ai bridge esp32s3

    nodestark/mdb-esp32-cashless

    ESP32-based MDB cashless device for vending machines, supporting EVA DTS DEX/DDCMP telemetry and payments over the MDB protocol via Bluetooth and MQTT

    92 parts190MIT
  • 2 layers227.5 × 87.4 mmWizza MX VIK, the printed circuit board in 3D

    Wizza MX VIK

    AlaaSaadAbdo/battoota

    Keyboards

    92 parts188
  • 2 layers120 × 70 mmEdrumulus 3hhh, the printed circuit board in 3D

    Edrumulus 3hhh

    corrados/edrumulus

    Open Source E-Drum Trigger Module

    92 parts163GPL-2.0
  • 2 layers93.9 × 80.7 mmFroggyswadge, the printed circuit board in 3D

    Froggyswadge

    cnlohr/cnhardware

    My dumping grounds for all my kicad projects and random hardware bringup.

    92 parts114

Questions

How big is the PistormTester PCB?

It measures 99.8 × 99.8 mm and has 2 copper layers, 1.6 mm thick.

What parts does the PistormTester use?

92 parts. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the PistormTester KiCad files?

From the abrugsch/PistormTester repository on GitHub, at the commit this page was made from: the board is PistormTester.kicad_pcb. PCBKit opens the board in the browser, with nothing to install.

Can I use the PistormTester design in my own project?

Its repository states no licence, so its author keeps all rights: ask abrugsch before reusing the design.