Add reboot command and late terminal activation

This commit is contained in:
2026-08-23 16:14:19 +02:00
parent f9d3e9ece5
commit 0dcc0d20d4
8 changed files with 86 additions and 2 deletions
+2
View File
@@ -100,6 +100,8 @@ This hardware profile uses both USB controllers for different purposes:
GPIO19 and GPIO20 are connected to the native USB connector and must not be assigned to the MAX3243, display, buttons, or other peripherals while USB CDC is enabled. Both connectors may be attached to the development host during testing so UART0 logs remain available while native USB carries broker data. Compatible DevKit clones can differ in connector labels and power-path design; verify the board schematic before assuming that two attached cables cannot back-power one another.
The USB-to-UART bridge's host DTR/RTS controls are used for automatic boot/reset circuitry and do not provide firmware with a reliable host-open indication. Consequently, attachment cannot be detected like native CDC DTR. After an unattended boot, the UART0 REPL remains in safe basic mode until it receives its first byte; pressing Enter once after attaching an ANSI terminal enables full line editing for the next prompt.
CDC DTR indicates that the host application has opened the native serial port. It controls the lifetime of the `usb-cdc` broker client but is not directly forwarded to the physical DE-9 DTR output. Physical DTR follows the firmware's `serial` configuration. Likewise, host CDC RTS is status information only; GPIO15/DE-9 RTS remains dedicated to UART1 receive flow control when `flow=rts-cts` is enabled.
## Phase 0 loopback tests