40 lines
1.8 KiB
Plaintext
40 lines
1.8 KiB
Plaintext
|
menu "micrOBU firmware"
|
||
|
|
config MICROBU_TEST_CHANNEL
|
||
|
|
bool "Test channel on the serial link (software lower tester, ETSI campaign hooks)"
|
||
|
|
default y
|
||
|
|
help
|
||
|
|
Serves serial frame type 0x11: mirror or divert every AL_DATA.request the stack
|
||
|
|
makes to the tester, inject AL_DATA.indication, GN-DATA.request for the
|
||
|
|
Security ATS. Not part of the phone interface; disable for a production image.
|
||
|
|
config MICROBU_LOG_OVER_LINK
|
||
|
|
bool "Also carry ESP_LOG output as LOG frames (0x7F) on the native USB link"
|
||
|
|
default n
|
||
|
|
help
|
||
|
|
The colleague's single-port board has no other place for its log. This board keeps
|
||
|
|
the console on UART0 (the CH343 bridge port), so the phone's link carries no text.
|
||
|
|
config MICROBU_BLE_USB_IDLE_MS
|
||
|
|
int "USB link idle time before BLE advertising resumes (ms)"
|
||
|
|
range 1000 60000
|
||
|
|
default 3000
|
||
|
|
help
|
||
|
|
BLE and the 5.9 GHz radio share the C5's single RF front end. While the phone is
|
||
|
|
using the USB link (any frame received within this window), BLE advertising is
|
||
|
|
stopped so it cannot take airtime from ITS-G5. An existing BLE connection is left
|
||
|
|
alone. The phone sends a PoTi update with every GNSS fix, which keeps the window
|
||
|
|
open for as long as it is connected over USB.
|
||
|
|
config MICROBU_TX_LED_GPIO
|
||
|
|
int "Active-low activity LED GPIO (-1: none)"
|
||
|
|
range -1 28
|
||
|
|
default -1
|
||
|
|
help
|
||
|
|
The colleague's XIAO ESP32-C5 has its yellow user LED on GPIO27. On this project's
|
||
|
|
board GPIO27 is not a plain LED, so the indicator is off unless configured.
|
||
|
|
config MICROBU_TX_LED_BLINK_MS
|
||
|
|
int "LED indication pulse (ms)"
|
||
|
|
range 10 2000
|
||
|
|
default 100
|
||
|
|
config MICROBU_LED_INVERTED_RX
|
||
|
|
bool "Inverted LED mode for receiver/bridge (normally ON, blink OFF on packet)"
|
||
|
|
default n
|
||
|
|
endmenu
|