Star on GitHubStar2.4k stars

Case study

LD2410S: investigating radar buses and firmware

The LD2410S investigation documents the I2C and SPI traffic between a Hi-Link FMCW radar board's components and examines its Puya controller firmware. It includes Saleae captures, oscilloscope images, an interpreted Range FFT frame, firmware strings and an interrupt vector map. The author labels the investigation as work in progress.

Targets
Firmware · Protocol
Category
Protocol analysis tools
Relationship
Foundation tool
Sources reviewed
Evidence class
C2 code & docs, no demo or download
Stars
0
Last commit
2025-08-09

GitHub data as of 2026-11-10

Copy as MarkdownView JSONCite

Evidence

Observed
Code, documentation and a demo observed; no download method found.
Checked
2026-11-08

How evidence classes are assigned

Requirements & limits

  • Prerequisites: Access to an LD2410S radar module and capture equipment is needed to repeat the bus observations.
  • Prerequisites: The firmware investigation uses pyOCD and an ST-Link V2.
  • Limits: The investigation is work in progress.
  • License: No licence file in the repository.

Cite

BibTeX

@misc{ld2410s-reverse-engineering-case,
  title = {{LD2410S: investigating radar buses and firmware}},
  howpublished = {\url{https://github.com/h0lad/LD2410S_ReverseEngineering}},
  url = {https://github.com/h0lad/LD2410S_ReverseEngineering},
  urldate = {2026-11-06},
  note = {Awesome REA entry: \url{https://awesomerea.org/resources/ld2410s-reverse-engineering-case/}}
}

Plain text

LD2410S: investigating radar buses and firmware. https://github.com/h0lad/LD2410S_ReverseEngineering (accessed 2026-11-06). Awesome REA entry: https://awesomerea.org/resources/ld2410s-reverse-engineering-case/

Useful? Star Awesome REA on GitHub2.4k

About this entry

The description was reviewed against primary sources.

Report an outdated entry Suggest a translation fix

Primary sources

  1. README.md GitHub · h0lad/LD2410S_ReverseEngineering · Revision 20790a3

More in Protocols

All 720 entries in ProtocolsProtocols case studies (645)

↑↓ move↵ open⌘↵ new tab