nucleus-p4 0.1.85

Superseded by 0.1.86. The 0.1.85 images predate the label fix.

Nucleus 0.1.85 for the OSSM Flagship (build env flagship_p4). Prerelease: keep the e-stop in reach. The Flagship board is pre-production.

Power down the motor before you connect USB. Then flash it at https://openvalence.org/flash/#flagship, or with esptool. The flasher never erases the chip: NVS holds the hub identity, the trust ledger and pairing.

File	Offset
bootloader.bin	0x2000
partitions.bin	0x8000
ota_data_initial.bin	0xF000
nucleus-p4-0.1.85-app.bin	0x20000 (ota_0)

App only, keeps the saved Wi-Fi:

esptool --chip esp32p4 --port COMx --baud 921600 write-flash 0x20000 nucleus-p4-0.1.85-app.bin

If esptool cannot connect, hold the BOOT pad TP903 to GND while you plug in USB. Then try again.

Later updates go through Phosphor:

1. Open the Firmware card.
2. Select Update.
3. Double-press PAIR.

Changes since 0.1.82:

• Log lines, refusals and setting descriptions use plain words. The motor replaces the drive or servo. The carriage replaces the emitter. Every number, unit and next step stays. A log filter or script that matches the old words needs the new ones.
• Phosphor fetches the machine's catalog again once after this update, because the setting descriptions changed. A few Phosphor labels change: "Requested position" (was "Asked position"), "Oscillations per second" (was "Cycles a second"), "Motion plans computed" and "Motor ramp".
• Long log lines keep their ends. The machine keeps the first 103 characters of each log line; about 25 lines are now shorter or split in two.
• One name per thing. "max travel" replaces "rail limit". "motor power trip" replaces "EN node trip". "Wi-Fi join" replaces "wifi join". "J7 thermistor" replaces THERM. The motor switch lines read "trip line" for the voltage on the line that cuts motor power. The matching refusal reads "a hardware kill holds motor power tripped".

No file holds a network name, a password or an OTA key. Checksums in SHA256SUMS.txt.

Built from Nucleus commit fa2ef94.