Comes with everything here

The following links are for software and docs.
Software
Coding Vetus
The following links are for software and docs.

The Basics

Vetus Pars is a chip tester, especially for old style chips. Just put the chip you wish to test into the ZIF socket and close the latch. You can then use the control buttons to find the chip you wish to test. Once you have found the chip you wish to test simply move down to [test] then click the [ok] button and your test will start. The chip you want to test isn’t listed? No problem, you can make your own test. Or you can ask in the forums or e-mail help@retrotroniks.com to see if we can accommodate you. Let’s go over everything.

Ribbon Cables

Getting Around

Vetus Pars Retro Chip Tester – User Guide

⸻

1. Introduction

The Vetus Pars Retro Chip Tester is a standalone, microcontroller-driven diagnostic tool designed for testing vintage ICs such as:
• DRAM (4164, 41256, etc.)
• SRAM
• 7400-series logic ICs
• CPUs and misc. chips
• Other TTL/CMOS devices

It uses a 40-pin ZIF socket, a full-color ST7735 display, and a 3-button navigation system to make chip selection and testing simple and intuitive.

⸻

2. Hardware Overview

Your Vetus Pars board contains the following components:
• 40-pin ZIF Socket — Insert ICs here for testing.
• 3 Navigation Buttons
• Button 1 – Back
• Button 2 – OK / Select
• Button 3 – Down / Scroll
• Reset Button — Resets the MCU
• BOOT0 Button — Hold this and power-cycle the device to enter DFU mode for firmware flashing.
• Output Header (Auxiliary 3.3V + GND) — Intended for accessories switching with MOSFET.
(Referred to as “fan control” in firmware.)
• USB-C Connector — Used only for:
• Firmware updates via DFU mode
• Uploading chip tests, fonts, and images via Vetus software

DO NOT use anything other than USB-C or 5v power supply.

⸻

3. Power Requirements

This is extremely important:

✔ You MUST use a 5V power supply.
• 5.0V regulated
• 500mA recommended
• 100mA may work for many chips, but older chips often require more current.

-3.3V will NOT power the device.

-6v+ could damage the Vetus Pars
⸻

4. Buttons and Navigation

The Vetus Pars uses a simple three-button interface:

Button 1 – Back

Moves up one menu or cancels a selection.

Button 2 – OK (Select)

Accepts the highlighted item or begins a chip test.

Button 3 – Down

Moves the highlight down through menu options.

These three buttons are used throughout the entire UI — no other controls are needed for daily operation.

⸻

5. Booting Into DFU Mode (Firmware Update)

The Vetus Pars uses an STM32H7 microcontroller. To update firmware:
1. Power OFF the unit.
2. Press and hold the BOOT0 button.
3. While holding BOOT0, power the device ON.
4. Release BOOT0.
5. The device is now in DFU Mode, ready for flashing via dfu-util or STM32CubeProgrammer.

Reset alone cannot enable DFU mode.
It must be BOOT0 + power cycle.

⸻

6. Basic Operation

Step 1 – Insert your chip

Open the ZIF socket, place the chip at the top of the socket, pin-1 aligned, and close the lever firmly.

Step 2 – Power the device

Use a regulated 5V power supply.

Step 3 – Browse the main menu

Use:
• Down = scroll
• OK = select
• Back = return

Step 4 – Search by Type

Choose the chip family:
• DRAM
• SRAM
• CPU
• 7400 Series
• I/O
• Other

Step 5 – Select the first letter

A graphical letter grid appears.
Choose the starting letter of the chip you want to test.

Step 6 – Select from the matching chips

A scrollable list of chips appears.
Choose your exact chip type and press OK.

Step 7 – Test results

The Vetus Pars will run a complete diagnostic tailored to your chip.
Results show:
• Pass / Fail
• Error details
• Any optional test messages
• Optional screen updates depending on the chip test routine

⸻

7. Auxiliary Power Header (Fan / 3.3V Output)

The board includes a small 3.3V/GND header intended for:
• Cooling fans
• Light modules
• Small accessories

This output is limited and not meant for powering external circuits.
Refer to firmware for fan-control behavior.

⸻

8. Upload Mode (Using USB-C)

Upload Mode allows transfer of:
• New chip definitions
• Fonts
• Images
• Firmware test programs

You can enter upload-mode by clicking ok on USB at the bottom of the main menu. You cannot upload tests or test files unless you are in upload-mode.

⸻

9. Safety Notes
• Always use a proper 5V power supply.
• Insert chips carefully to avoid bent pins.
• Never insert or remove a chip while a test is active.
• High-current vintage ICs may get warm (not HOT) — this is normal.
⸻

10. Troubleshooting

Device doesn’t power on
• Ensure your 5V supply is actually supplying 5V.
• Check that the switch functions properly.

Chip tests instantly fail
• Ensure pin-1 alignment is correct.
• Make sure the pins are seated properly.
• Depending on the test it could simply be a bad chip. Some tests can end immediately on fault.

Cannot enter DFU mode
• You must:
1. Power off
2. Hold BOOT0
3. Make sure the USB is connected to the computer
4. Power on

Menu doesn’t respond
• Check your navigation buttons.
• Reset the unit if necessary.

Vetus Pars Chip Strings Guide

What Chip Strings Are

Each chip may store up to eight text messages.

These are shown on the Vetus Pars display during testing as:

  • PASS / FAIL messages

  • Dynamic values (registers)

  • Loop counters

  • Identity text

  • Status messages

They are stored in the chip’s metadata and uploaded along with code.

Formatting Values in Strings

Strings support standard C printf-style formatting:

  • %d for decimal

  • %u for unsigned decimal

  • %X for hexadecimal uppercase

  • %02X for two-digit hex with zero padding

  • %03d for three-digit decimal with padding

Critical Rule

When inserting a live register into a string, formatting must be separated from the register reference.

Correct:

VALUE %d #R0

DATA %02X #R1

COUNT %03d #R2

Incorrect (these will break formatting):

VALUE%d#R0

DATA %02X#R1

COUNT%03d#R2

The space before the register tag (#R0, #R1, etc.) is required.

What the System Actually Does

The formatting token (%d, %02X, etc.) tells Vetus Pars how to convert a number.

The register tag (#R0, #R1, #R2) tells it which register to display.

Example:

If you write:

BYTE READ %02X #R2

and register 2 currently contains hex A3,

the display will show:

BYTE READ A3

Supported Register Tags

You may reference:

#R0 through #R31

Only one register may follow a formatting tag.

Allowed and Not Allowed Characters

Allowed:

  • Space

  • ASCII letters

  • ASCII numbers

  • ASCII punctuation

Not Allowed:

  • Unicode symbols (✔ ✓ ★ →)

  • Smart quotes (“ ”)

  • Tabs

  • Emojis

If you paste text from Word or macOS Notes, convert it to plain ASCII first.

Leaving Empty Strings

If a slot is not used:

  • leave it completely blank

  • do not type “empty”

  • do not type spaces

Updating Display from Code

String usage typically occurs via the SHOSTR opcode:

Example:

Show string 0 on screen:

SHOSTR 0

Best Practices for Clean Output

  1. Always use % formatting before register substitution.

  2. Always use one space before register tags.

  3. Keep strings short and direct.

  4. Avoid constant screen updates in very tight loops.

  5. Leave unused slots blank.

In Summary

  • 8 strings per chip

  • ASCII only

  • Use standard C printf formatting

  • Require a space before the register tag

  • Update screen with UDSCRN when changing register values

  • GUI safely handles upload formatting, but user text must follow rules