Limejig

LimeJig

Public source snapshot for the LimeJig V0 LimeSDR Mini fixture.

This repository contains the RP2040 controller firmware, host CLI/Qt source, test policy and result schema, and the editable KiCad schematic/PCB with lean project-local symbol and footprint libraries.

Hardware preview

• LimeJig V0 schematic PDF
• Full-resolution PCB 3D top view

Both previews were exported with KiCad 10.0.3. The schematic PDF comes from the sanitized editable source. The 3D preview is a rendered derivative made with the controlled private model set; the underlying vendor 3D files are not included here.

Privacy and provenance

This is a sanitized source-only repository with new Git history. It does not contain the private production repository, production DUT records, serials, operator logs, HIL/release evidence, fixture recovery captures, credentials, network configuration, deployment images, or fabrication correspondence.

The initial snapshot was prepared from private LimeJig source commit 50d1615f8766ef7c7afc20b8388b80bd5dc6c6c7 without importing that repository's commits or tags. See PUBLIC-SOURCE-MANIFEST.md for the exact inclusion and exclusion boundary.

The records under examples/test-data/ are synthetic documentation/test fixtures. They are not production results.

Source layout

CM5 account and installation boundary

This repository does not define a default login or password. Never assume that a credential used on a development fixture is suitable for another jig. Create each appliance credential during OS provisioning, prefer SSH keys, and use a unique password if password login remains enabled.

The supplied kiosk service runs as the dedicated limejig OS account and uses /var/lib/limejig as its working directory. A manual deployment must create that account and directory, grant the hardware permissions required by the fixture, install the runtime files, and only then enable the service. Merely cloning this repository does not perform those system changes.

There is no LimeJig apt repository or public CM5 appliance bootstrap in this snapshot. The apt command in the GitHub Actions workflow installs only the generic dependency needed by the public source check; it is not a jig install procedure. A CM5 that already has the controlled appliance packages and their dependencies can use this source for review and development. A fresh CM5 needs an independently maintained OS/package provisioning procedure.

Important limitations

• Vendor datasheets, spreadsheets, STEP/WRL models, fabrication exports, board archives, and package/deployment payloads are intentionally absent.
• KiCad files retain references to omitted 3D assets. Schematic and PCB editing remain available, but complete 3D rendering requires the user to source correctly licensed models independently.
• CM5 image creation, Debian appliance packaging, factory recovery, and signed production-release reproduction require private controlled inputs and are not represented as public build targets.
• The FT601 recovery and QSPI restore self-tests require intentionally omitted stock EEPROM/gateware images. The public gate checks those helpers' syntax and CLI surfaces but cannot execute their binary-dependent recovery self-tests.
• This snapshot is useful for source review and development; it is not a production acceptance record or a replacement for a released fixture bundle.

Quick checks

Run the non-hardware public gate:

tools/check-public.sh --skip-gui

With Qt 6 development packages, CMake, and Ninja installed:

tools/check-public.sh

Firmware build prerequisites and commands are described in firmware/rp2040/README.md. No command above accesses USB devices, fixture power, FT601 EEPROM, QSPI flash, or a DUT.

Licensing

LimeJig is released under the MIT License; see LICENSE. Inherited RP2040 DirtyJTAG material also retains its original MIT notices in firmware/rp2040/LICENSE and applicable source headers.