From bb2f1fc5472e13fe853a41dd5d88905fc7d6f169 Mon Sep 17 00:00:00 2001
From: Jake <jake.read@cba.mit.edu>
Date: Wed, 3 Jan 2024 10:11:52 -0500
Subject: [PATCH] tailing notes

---
 rpi_spi/2023-12-29_pi-spi-rates.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/rpi_spi/2023-12-29_pi-spi-rates.md b/rpi_spi/2023-12-29_pi-spi-rates.md
index 6ee0fa1..78300c7 100644
--- a/rpi_spi/2023-12-29_pi-spi-rates.md
+++ b/rpi_spi/2023-12-29_pi-spi-rates.md
@@ -101,4 +101,8 @@ There's another oddity in here... the RP2040 only uses SPI framing where the CS
 - do the RP2040-to-RP2040 UART PIO test 
 - finish the thought, blog it up (1 day, max) 
 - take i.e. [notes](https://abyz.me.uk/rpi/pigpio/pigs.html), right ? 
-    - incl. the maybe-likely-change to use PIO spi-slave, not this bs 
\ No newline at end of file
+    - incl. the maybe-likely-change to use PIO spi-slave, not this bs 
+- i.e. go-notes/ref/rp2040 ? 
+    - https://cec-code-lab.aps.edu/robotics/resources/pico-c-api/index.html 
+    - https://github.com/raspberrypi/pico-examples/tree/master 
+    - https://www.circuitstate.com/tutorials/making-two-raspberry-pi-pico-boards-communicate-through-spi-using-c-cpp-sdk/ 
\ No newline at end of file
-- 
GitLab