Skip to content

Latest commit

 

History

History
61 lines (49 loc) · 3.22 KB

INSTALL.md

File metadata and controls

61 lines (49 loc) · 3.22 KB

Experimental PAROL6 bootloader installation

This package is for STM32F446 PAROL6 PCBs, with stepper modules, motors and other actuators disconnected for initial testing. It is not a production robot update package. Keep SWD recovery available. Do not use F103 binaries, stock PAROL6 application binaries or a whole-chip erase recipe.

  1. Save a complete 512 KiB internal flash backup, MCU UID, option-byte state and a backup/ownership review of the external staging range 0x501000..0x560fff. Installation is not a migration of an existing board.
  2. Verify SHA256SUMS.txt. Flash the loader HEX through SWD; its addressed records begin at 0x08000000. A BIN requires that explicit address. Keep sector 4 metadata and sectors 5–7 application separate. Do not change option bytes. A board with old unrelated bytes in metadata needs an explicitly reviewed sector-4-only initialization, after backup.
  3. Reset normally and select the board's actual USB port. Never auto-select another board. On the tested ST-Link Utility setup, a reset without the extra Run operation recovered USB when the reset-plus-Run sequence did not. Debugger attach can also set IWDG freeze and fault the supervised app; do not interpret debugger maintenance as a clean watchdog test.
  4. Inspect the loader, copy its UID, then use only a cooperating relocated app:
python host/update.py hello --transport usb --port COMx
python host/update.py info --transport usb --port COMx
python host/update.py flash --transport usb --port COMx --uid <verified-24-hex-uid> --image parol6-bootloader-V1-alpha.3-probe.bin --version 1 --require-runtime-handoff --start

The loader must be reachable before running these commands. A valid installed app normally boots immediately; use its documented recovery request or the board's recovery entry policy. The probe's USB byte B returns to recovery. The full engineering app uses its explicit prepare/enter workflow. Opening a port is not an instruction to reset a legacy application.

The status LEDs distinguish idle recovery (double flash), updating (rapid alternation) and the new application's heartbeat (single flash). Internal-flash erase stalls can briefly pause the update pattern.

To start an already-committed app from an idle loader without rewriting flash:

python host/update.py start --transport usb --port COMx --uid <verified-24-hex-uid>

A Start acknowledgement is not proof of application health. Reconnect after USB re-enumeration and check the expected application identity/watchdog separately. Versions are not anti-rollback protection; CRC and SHA-256 are not signatures.

Read-only full NOR backup in idle loader mode:

python host/nor.py --port COMx --uid <verified-24-hex-uid> --out nor-backup-01

host/staging_test.py is an explicit destructive test of only the first three staging sectors, after a complete matching backup. It cannot send Install, Boot or reset commands, and leaves the loader idle. Do not run it on an unreviewed partition or treat a full-array read as whole-chip write testing.

The release bundle intentionally supplies no automatic first-install script, UART candidate binary, whole-board combined image, or energized-arm update flow.