imrishabh18/pedometer

docs/programming.md

# Programming the assembled board

The bare **CC2340R52E0RGER** is programmable through **J4**, a JST BM05B-SRSS-TB five-pin connector. Use an SHR-05V-S adapter cable to a CC2340R5-compatible SWD probe with 2.5 V target-level support. A debugger's connector may have a different pin order; wire by signal.

| J4 pin | Signal | U1 QFN pin |
|---:|---|---:|
| 1 | VTREF, target 2.5 V | 11 / main supply |
| 2 | SWDIO | 7 |
| 3 | SWCLK | 8 |
| 4 | GND | 25 / exposed pad |
| 5 | RESET_N | 13 |

Power the target from its normal power input and connect ground first. VTREF senses target voltage; it is not a 5 V supply input. J2 USB-C provides charging/power only and cannot carry USB programming data. R14 (100 kΩ) and C24 (100 nF) bias/filter reset.

`bun run check:programming` verifies the source pin map, routed copper continuity for every J4 signal, and the reset components. The [hash-bound result](../review/programming-check.json) covers the CAD design. Flash/readback and debugger attachment must be confirmed on assembled hardware.

For bring-up, use the TI SimpleLink Low Power F3 SDK's CC2340R5 project and select the QFN24 part. Match the DIO mapping and clocks described in [bare-chip notes](bare-cc2340r5.md), then connect the probe, read the device ID, program a diagnostic image, verify flash, reset and observe execution. Do not enable debug-port security before proving recovery and programming.

The supplied portable pedometer C core has host tests. The TI SDK board drivers, GATT service and NVS adapter are still required to make a complete flashable pedometer application; this package does not claim a tested target firmware binary. See [firmware integration](firmware-and-bringup.md).

Source: [TI CC2340R5 datasheet](https://www.ti.com/lit/ds/symlink/cc2340r5.pdf), QFN24 pin table and debug interface.