Actualizaciones OTA

Industrial wireless charging deployments cannot rely on bench-only programming: pads mounted in warehouse floors and receivers buried in AGV chassis require secure, verifiable firmware updates without dismantling hardware. SiCore OTA architecture uses signed image packages, dual-bank or A/B flash partitions, and explicit rollback rules so failed updates never brick safety-critical power controllers mid-shift.

OTA interacts with real-time control: downloads and flash programming occur in idle or service states; cryptographic verify runs before bank swap; first boot after update executes expanded self-test before enabling full power transfer.

01Update pipeline

• Package delivery: fleet gateway, Ethernet on dock, or CAN-based chunked transfer to receivers in maintenance bay.
• Authentication: ECDSA or RSA signature over image hash; optional encrypted payload for IP protection.
• Staging: write to inactive bank with resume support and per-block CRC.
• Activation: reboot into new image after watchdog-covered verification boot chain.
• Rollback: revert to previous bank on failed self-test, loop crash counter, or explicit fleet command.

02Fleet coordination

Dock and receiver firmware versions are interdependent when session protocols evolve — SiCore release notes define minimum compatible pairs. Fleet managers schedule pad updates during low-throughput windows; receiver updates often batch when vehicles enter maintenance. Simultaneous update of all pads in one aisle is avoided without backup wired charge capacity.

Configuration blobs migrate separately from application images where schema allows forward compatibility; breaking config changes bump major version and trigger factory-default fallback with technician review.

03Safety and compliance

Bootloader is immutable or protected by MPU and option bytes; debug ports disabled in production unless physical unlock. OTA never skips signature verify even on LAN — supply-chain integrity applies equally to warehouse networks. Update audit logs record image version, timestamp, and initiating operator or gateway ID for regulatory traceability alongside existing electrical safety documentation.