# nRF52832 — Board Knowledge

## Hardware Overview
- **SoC:** nRF52832 (ARM Cortex-M4F, 64 MHz)
- **Flash:** 512 KB
- **RAM:** 64 KB
- **Radio:** 2.4 GHz (BLE 5.0, ANT, 2.4 GHz proprietary)
- **USB:** None (no native USB)
- **NFC:** NFC-A tag

## Board Target
Use `nrf52dk/nrf52832` as the build target (Zephyr format: `<board>/<soc>`).

## Development Kit: nRF52 DK (PCA10040)
- **J-Link debugger:** On-board SEGGER J-Link OB (supports RTT + SWD)
- **UART:** Physical UART pins routed to on-board J-Link (appears as `/dev/ttyACM0` or `COM<N>`).
- **Buttons:** 4 user buttons
- **LEDs:** 4 user LEDs
- **Arduino header:** Yes

## Key Considerations
- **64 KB RAM is tight.** BLE + logging can exhaust RAM quickly. Monitor with `west build -d <build_dir> -t ram_report`. (see SDK.md for more info)
- No USB means no USB-CDC. UART logging uses physical UART pins through J-Link.
- RTT is strongly recommended over UART on this board to save UART for application use.
- Stack size must be carefully managed — default `CONFIG_MAIN_STACK_SIZE=1024` may be too small for BLE peripheral + GATT.
- Thread/Zigbee/802.15.4 are **NOT supported** on nRF52832 (single-protocol radio only: BLE or proprietary).

## Common DeviceTree Overlay Use Cases
- Remap UART pins if custom PCB moves them from default DK routing
- Adjust GPIO for sensor connections
