diff --git a/docs/progress.md b/docs/progress.md index 9fd092c..f4e2ce9 100644 --- a/docs/progress.md +++ b/docs/progress.md @@ -30,7 +30,9 @@ - [ ] Port springSD bus routines; SC16IS740 driver - [x] Companion protocol: framing, builders (DEVICE_QUERY, APP_START, GET_CONTACTS, SYNC_NEXT_MESSAGE), parsers (SELF_INFO, contacts, v3 contact/channel messages); host tests from real captures + MeshCore layouts - [x] USB bench link: app (`HsUd`) → Visor USB cradle → `tools/visor_bridge.py` → FTDI → XIAO D6/D7. Query radio shows `Reply 0x000D, 82 bytes` on the Visor -- [ ] Wire the protocol into the app: connect sequence, contact list, message sync on PUSH_MSG_WAITING +- [x] Connect screen: DEVICE_QUERY + APP_START via session.c; shows node, freq, BW/SF/CR, TX power, firmware (verified on the Neo over the USB bridge) +- [ ] Contact list: GET_CONTACTS into a Palm database + contacts screen +- [ ] Messages: sync on PUSH_MSG_WAITING, store, per-contact/channel views - [ ] UI: contacts, DMs, channels - [x] Install method confirmed: HotSync over the USB cradle from the dev Mac (`make install`) @@ -61,3 +63,4 @@ - UART path verified: FT232R on D6/D7 at 115200 8N1 gets the same DEVICE_INFO as USB. The radio side of SB-LoRa is proven; what remains is the carrier board (SC16IS740 + bus) and the Palm transport for it. - Protocol layer for the read-only commands, built against MeshCore's MyMesh.cpp and captured replies (DEVICE_QUERY, APP_START → SELF_INFO, GET_CONTACTS with 0 contacts, SYNC → NO_MORE_MESSAGES). LE fields are assembled byte by byte for the big-endian 68k. The radio is on MeshCore factory defaults (869.618 MHz / 62.5 kHz / SF8, 22 dBm, no name). - **First end-to-end round trip from the Visor:** DEVICE_QUERY from VisorMesh on the Neo went over USB, through the Mac bridge and the FTDI adapter, into the XIAO's UART, and DEVICE_INFO came back and decoded on the Visor. `HsUd` turned out to use the Visor's HOTSYNC USB port (2); the endpoints stall around open/close and need clear-halt. +- Connect screen verified on the Neo: shows the radio's real SELF_INFO/DEVICE_INFO (9B1E4F92, 869.618 MHz, BW 62.5 SF8 CR5, 22 dBm, v1.17.1). Fixed a hand-typed DEVICE_INFO fixture that had two bytes shifted. diff --git a/palm-client/README.md b/palm-client/README.md index fe7cef6..b6cdf47 100644 --- a/palm-client/README.md +++ b/palm-client/README.md @@ -62,7 +62,7 @@ tools/visor_bridge.py /dev/cu.usbserial-XXXX # radio's D6/D7 UART on a 3.3 V tools/visor_bridge.py /dev/cu.usbmodemXXXX # or the XIAO's own USB companion link ``` -In VisorMesh, set **Link** to **USB** and tap **Query radio**. The app opens the Neo's `'HsUd'` Serial Manager driver, so the Visor appears on USB. The bridge reads the Visor's port list (vendor request `0x03`), forwards bytes to the radio, and logs every companion frame in both directions. What we found while getting it working: +In VisorMesh, set **Link** to **USB** and tap **Connect**. The app opens the Neo's `'HsUd'` Serial Manager driver, so the Visor appears on USB. The bridge reads the Visor's port list (vendor request `0x03`), forwards bytes to the radio, and logs every companion frame in both directions. What we found while getting it working: - `HsUd` sends on the Visor's HOTSYNC USB port (2), not GENERIC (1). The bridge listens on every port and replies on whichever one the Visor used. - The endpoints stall briefly around open and close, so the bridge clears them (`libusb_clear_halt`) and carries on. diff --git a/palm-client/tools/visor_bridge.py b/palm-client/tools/visor_bridge.py index 4e81325..38f7a45 100755 --- a/palm-client/tools/visor_bridge.py +++ b/palm-client/tools/visor_bridge.py @@ -8,7 +8,7 @@ bytes between it and the radio, logging each companion frame. visor_bridge.py /dev/cu.usbserial-XXXX # radio on a USB-TTL adapter (D6/D7) visor_bridge.py /dev/cu.usbmodemXXXX # radio's own USB companion link -Then put the Visor in its USB cradle and tap "Query radio" with Link = USB. +Then put the Visor in its USB cradle and tap Connect with Link = USB. The app's 'HsUd' driver turns out to send on the Visor's HOTSYNC port (2), so the bridge also grabs the Visor during a HotSync: stop it before `make install` (the Makefile does this for you). @@ -107,7 +107,7 @@ class FrameLogger: def wait_for_visor(lib): - print('Waiting for the Visor (open VisorMesh, Link = USB, tap Query radio)...', flush=True) + print('Waiting for the Visor (open VisorMesh, Link = USB, tap Connect)...', flush=True) while True: h = lib.libusb_open_device_with_vid_pid(None, VISOR_VID, VISOR_PID) if h: