CAN Isolated Firmware and Downloads
Check the current firmware release boundary, download the vendor-neutral USB CAN checklist and review the artifacts required for a future release package.
Firmware and document downloads for the CAN Isolated pilot. The absence of a release package is shown explicitly so an upstream binary is not mistaken for MallMars firmware.
Available now · vendor-neutral PDF
USB CAN selection and bench checklist
This four-page worksheet records CAN generation, host driver, isolation boundary, connector, termination and capture evidence. It is not firmware and does not establish compatibility with a specific unit.
Device release package
Scroll the table horizontally on a narrow screen.
| Artifact | Current state | Required before publication |
|---|---|---|
| Source repository and tag | Not published | Canonical repository, exact commit/tag, reproducible build instructions and modification record. |
| Firmware binary | Not published | Target board and MCU, semantic version, build date, SHA-256 hash and signature or equivalent integrity record. |
| USB identity mapping | Not published | VID/PID, product string, driver binding and mapping to hardware and firmware revisions. |
| Recovery package | Not published | Bootloader entry, known-good image, rollback limits, recovery steps and failure stop conditions. |
| Licences and notices | Draft policy only | Every upstream component, licence text, source offer, modification and redistribution obligation. |
| Compatibility record | DVT pending | Named host, driver/backend, application, bitrates, test method, evidence identifier and known limits. |
Before flashing any candidate unit
- Match the exact PCB, MCU, bootloader, oscillator, transceiver and USB identity to the release manifest.
- Preserve the original firmware and verify that a documented recovery path works on a sacrificial sample.
- Verify the downloaded hash and retain the source URL, release tag and licence record.
- Do not flash a marketplace clone merely because its product name resembles an upstream project.
- Stop after any mismatch, failed verification or undocumented recovery step.
Publication rules
A future firmware download will name the applicable hardware revision, source tag, binary hash, build method, USB identity, host dependencies, recovery route, security or safety notes, known issues and superseded releases. A binary without those fields will not be labelled a MallMars release.
Read the rights and revision record
Review the open-source notices, changelog and compatibility matrix together. One document without the other two is not a complete release package.