Testladen

Firmware & software

Keep the controller and module firmware current for the latest features and fixes. Always back up your configuration before an update.

Update procedure

Firmware images are published at docs.bitcrushtesting.com and distributed as signed .tlfw files. The appliance verifies the signature before flashing.

Via the CLI:

testladen-cli --host testladen.local firmware update --file testladen-1.5.0.tlfw

The SYS LED shows amber during the update. Do not remove power while it is flashing. The appliance reboots automatically and returns to solid green when complete.

Via the web UI: browse to http://testladen.local/, open Settings → Firmware, upload the .tlfw file and confirm. Progress is shown on screen.

Module firmware is updated the same way; the image targets the specific module and slot. Verify the result with:

testladen-cli --host testladen.local status
testladen-cli --host testladen.local module list

Version compatibility

  • Controller and module firmware are released together. A module reporting error E30 indicates a controller/module version mismatch — update both to the same release train.
  • ⚡ Never downgrade the controller below the minimum version printed in a module's release notes; the module may fail to initialise.
  • 10BASE-T1S and HMI capture modules require controller firmware 1.3.0 or later and a Rev B backplane (see Module overview).
  • Release notes list the supported upgrade paths. Update one minor version at a time if you are several releases behind.

Backup and restore

The configuration — hostname, network settings, rail definitions, tokens and module presets — can be exported to a portable JSON file.

Back up:

testladen-cli --host testladen.local config backup bench-01-config.json

Restore (for example after a factory reset or onto a replacement unit):

testladen-cli --host testladen.local config restore bench-01-config.json

⚡ A restore overwrites the current configuration and reboots the appliance. Restore only files exported from a compatible firmware version.

Store backups in version control alongside your test suites so a bench can be rebuilt reproducibly. See Troubleshooting for the factory-reset procedure.