# Version History and Compatibility This page summarizes the major product changes that SANPO SPINE customers can verify from official firmware, release manifests, migration guides, and public repository records. ## Currently Released Versions | Product generation | MCU platform | Current firmware | Application | | --- | --- | --- | --- | | V8 | STM32G0B1RCT6 with an external HSE crystal | V83 | V8 hardware; native passthrough interfaces and V6-compatible protocol mode | | V6 | STM32G0A series | V68 | G0A hardware using the V6 protocol; not interchangeable with G473 firmware | | V6 | STM32G473 | V67 | V6 FDCAN upgrade; CAN FD, Classic CAN, and RS485 | | V4 | STM32F407 | V47 | V4 standard and isolated versions; Classic CAN and RS485 | A complete SPINE board contains two MCUs. During a normal upgrade, program and verify both MCUs separately. Send `AT+VER` through each management serial port and confirm that both chips report the expected version. ## Main Differences Between the Three Generations | Capability | V8 | V6 | V4 | | --- | --- | --- | --- | | Classic CAN | Supported | Supported | Supported | | CAN FD | Supported | Added | Not supported | | Linux SocketCAN | Classic CAN/CAN FD | Classic CAN/CAN FD | Classic CAN in V47 | | USB management-port protocol | Retains V6-compatible protocol mode | Unified `ST/ET/SF/EF/RT` framing | V4 framing | | USB RS485 | One independent USB serial port per channel for direct passthrough, with `RT` protocol mode retained | `RT` framing with selectable RAW channels | V4 protocol framing | | SPI | Retains the V6 SPI protocol | Fixed-length `SHORT/LONG` transfers with CRC-8 | V4 fixed layout | | Native CAN passthrough | Linux `gs_usb`/SocketCAN; Windows 10/11 system WinUSB with SANPO CANgaroo support | Linux `gs_usb` | Linux `gs_usb` | | Offline batch commands | Retained | Retained and extended | Supported | | Customer firmware development | STM32G0B1 framework and direct-development examples | Framework selected for the specific V6 MCU | STM32F407 framework | ## Version Evolution ### V8: Native Passthrough Alongside Protocol Mode V8 uses the STM32G0B1RCT6 and organizes its interfaces around two paths: direct access and compatibility with existing systems. - CAN/CAN FD appears directly as SocketCAN interfaces on Linux. Windows 10/11 uses the system WinUSB driver and can transmit and receive through SANPO CANgaroo or a user application. - The four RS485 channels appear as independent USB serial ports. Raw bytes pass through directly, without first selecting a SANPO Channel. - The management port and SPI retain the V6 `ST/ET/SF/EF/RT` frames, so SANPO Studio, CyberGear, GM8010, communication configuration, and offline batch tasks remain available. - Native passthrough mode or protocol mode can be selected according to the host application, real-time requirements, and compatibility needs. Each MCU enumerates one dual-channel `gs_usb` device, one `SANPO Studio Management Port`, and two `SANPO USB2RS485 Port` interfaces. A complete dual-MCU board provides four CAN/CAN FD channels, two management ports, and four independent RS485 passthrough serial ports. Recorded V8 production firmware releases: | Firmware | Major changes | | --- | --- | | V83 | Retains all V82 functions while adding complete FDCAN error-state reporting and dual-path Bus-Off recovery; older drivers use automatic firmware recovery, while drivers supporting the extended protocol can use `restart-ms` or manual restart | | V82 | Completes the official release package, customer extension framework, CAN/CAN FD/RS485 examples, and J8108-R8 FDCAN test guide; reapplying identical FDCAN parameters restores the live configuration without an unnecessary Flash write | | V81 | First public V8 firmware; released the dual-MCU STM32G0B1 platform, dual-channel `gs_usb`, management port, and independent RS485 USB serial ports | V83 error handling uses standard Linux CAN error frames and does not introduce a proprietary SANPO error format. Only Bus-Off triggers controller recovery. Error Warning and Error Passive report status without incorrectly restarting the channel. CAN-A and CAN-B recover independently and do not actively restart the other CAN channel or RS485. ### V6: CAN FD and a Unified Protocol V6 adds CAN FD while retaining Classic CAN and RS485, and unifies communication framing and parameter configuration. - USB Classic CAN continues to use `ST/ET`, while CAN FD adds `SF/EF`. - USB RS485 normal mode uses the unified `RT + Channel + Len + Data + CRLF` frame. - SPI provides two fixed transfer lengths: 23-byte `SHORT` and 73-byte `LONG`, with CRC-8. - CAN/CAN FD, RS485, and SPI parameters are explicitly configured and stored through AT commands. - Linux SocketCAN supports both Classic CAN and CAN FD. Later V6 firmware is maintained separately for each MCU platform: - **G0A V68**: Retains the V6 protocol and has completed high-frequency stress testing for USB RAW, USB `RT`, and SPI-to-RS485 operation. It is dedicated to G0A hardware and cannot be used with STM32G473 or V8 G0B1. - **STM32G473 V67**: Adds standard SocketCAN error frames, Error Warning, Error Passive, TEC/REC, and Bus-Off handling. Older `gs_usb` drivers continue to use 100 ms firmware-managed recovery. Drivers supporting the extended recovery protocol can control recovery through `restart-ms` or manual restart. Recovery discards stale control frames accumulated during Bus-Off so expired commands are not replayed afterward. When migrating from V4 to V6, a USB Classic CAN application normally only needs to reconfirm its port and Channel. RS485 framing, SPI layout, CAN FD configuration, and communication-parameter setup must be adapted to the V6 documentation. See the [V4 to V6 Migration Guide](https://docs.sanporobot.com/v6/en/v4_to_v6_migration.html) for details. ### V4: Classic CAN and RS485 Foundation V4 established the basic SPINE capabilities for USB, SPI, Classic CAN, RS485, communication-parameter configuration, and offline batch commands. V42 (V4.2) and later firmware support offline batch execution. V47 is the final V4 release. Its main customer-visible state includes: - completed regression coverage for USB CDC, `gs_usb`/SocketCAN, SPI, Classic CAN, and RS485; - corrected Channel information in SPI-to-RS485 response frames; - customer extension projects for STM32CubeIDE and Keil; - `AT+VER` reports `V47`. V4 remains suitable for existing projects that use only Classic CAN and RS485. V4 firmware cannot be programmed onto V6 or V8 hardware.