clocked_input example clarification

Open
#339 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
c
Domain
documentation, embedded-iot

Research direction

The issue refers to the clocked_input example; start by locating and reading that example, then run it while examining how PIO sampling relates to the SPI0 clock. Done means documenting whether the sampling is synchronous and exact, using the example's existing documentation or comments.

Written by the indexing model from the issue text.

Description

Hello. As part of a project I've been tinkering with, I've been playing with the idea of turning a raspi
pico into a LPC (Low Pin Count) sniffing device to synchronously sample the lpc bus signals, do some
light parsing and decoding with the data, and report that over usb or uart (were the usb interface fast
enough I'd just grab the raw data and process it in sigrok or similar but alas, 12mbps is far too slow
for the 33.3Mhz lpc clock).

Am I correct in reading the example that the pio samples in sync with the spi0 clock more or less
exactly?

Dominant language
C
Stars
3.9k
Forks
1k
Avg merge
1d 16h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/pico-examples

All issues in raspberrypi/pico-examples

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.