1
0
Fork 0

dump rp2040 firmware experiments

main
radex 2024-03-18 22:53:04 +01:00
parent 9e964eda5d
commit e8da5f9018
Signed by: radex
SSH Key Fingerprint: SHA256:hvqRXAGG1h89yqnS+cyFTLKQbzjWD4uXIqw7Y+0ws30
7 changed files with 300 additions and 0 deletions

5
firmware/.gitignore vendored Normal file
View File

@ -0,0 +1,5 @@
.pio
.vscode/.browse.c_cpp.db*
.vscode/c_cpp_properties.json
.vscode/launch.json
.vscode/ipch

10
firmware/.vscode/extensions.json vendored Normal file
View File

@ -0,0 +1,10 @@
{
// See http://go.microsoft.com/fwlink/?LinkId=827846
// for the documentation about the extensions.json format
"recommendations": [
"platformio.platformio-ide"
],
"unwantedRecommendations": [
"ms-vscode.cpptools-extension-pack"
]
}

39
firmware/include/README Normal file
View File

@ -0,0 +1,39 @@
This directory is intended for project header files.
A header file is a file containing C declarations and macro definitions
to be shared between several project source files. You request the use of a
header file in your project source file (C, C++, etc) located in `src` folder
by including it, with the C preprocessing directive `#include'.
```src/main.c
#include "header.h"
int main (void)
{
...
}
```
Including a header file produces the same results as copying the header file
into each source file that needs it. Such copying would be time-consuming
and error-prone. With a header file, the related declarations appear
in only one place. If they need to be changed, they can be changed in one
place, and programs that include the header file will automatically use the
new version when next recompiled. The header file eliminates the labor of
finding and changing all the copies as well as the risk that a failure to
find one copy will result in inconsistencies within a program.
In C, the usual convention is to give header files names that end with `.h'.
It is most portable to use only letters, digits, dashes, and underscores in
header file names, and at most one dot.
Read more about using header files in official GCC documentation:
* Include Syntax
* Include Operation
* Once-Only Headers
* Computed Includes
https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html

46
firmware/lib/README Normal file
View File

@ -0,0 +1,46 @@
This directory is intended for project specific (private) libraries.
PlatformIO will compile them to static libraries and link into executable file.
The source code of each library should be placed in a an own separate directory
("lib/your_library_name/[here are source files]").
For example, see a structure of the following two libraries `Foo` and `Bar`:
|--lib
| |
| |--Bar
| | |--docs
| | |--examples
| | |--src
| | |- Bar.c
| | |- Bar.h
| | |- library.json (optional, custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html
| |
| |--Foo
| | |- Foo.c
| | |- Foo.h
| |
| |- README --> THIS FILE
|
|- platformio.ini
|--src
|- main.c
and a contents of `src/main.c`:
```
#include <Foo.h>
#include <Bar.h>
int main (void)
{
...
}
```
PlatformIO Library Dependency Finder will find automatically dependent
libraries scanning project source files.
More information about PlatformIO Library Dependency Finder
- https://docs.platformio.org/page/librarymanager/ldf.html

15
firmware/platformio.ini Normal file
View File

@ -0,0 +1,15 @@
; PlatformIO Project Configuration File
;
; Build options: build flags, source filter
; Upload options: custom upload port, speed and extra flags
; Library options: dependencies, extra library storages
; Advanced options: extra scripting
;
; Please visit documentation for the other options and examples
; https://docs.platformio.org/page/projectconf.html
[env:pico]
platform = raspberrypi
board = pico
framework = arduino
lib_deps = fastled/FastLED@^3.6.0

174
firmware/src/main.cpp Normal file
View File

@ -0,0 +1,174 @@
#include <Arduino.h>
#include <FastLED.h>
// #define NUM_LEDS 1
// #define DATA_PIN 23u
// CRGB leds[NUM_LEDS];
#define Q1 5
#define Q2 29
#define Q3 28
#define Q4 27
#define Q5 26
#define Q6 22
#define Q7 21
#define Q8 20
#define Q9 8
#define Q10 19
#define Q11 18
#define Q12 17
#define Q13 16
#define Q14 9
#define Q15 10
#define Q16 11
#define Qout 12
#define SER 2
#define OE 3
#define RCLK 4
#define SRCLK 6
#define SRCLR 7
void printOut() {
Serial.println("------");
Serial.print("SER: ");
Serial.println(digitalRead(SER));
Serial.print("OE_N: ");
Serial.println(digitalRead(OE));
Serial.print("RCLK: ");
Serial.println(digitalRead(RCLK));
Serial.print("SRCLK: ");
Serial.println(digitalRead(SRCLK));
Serial.print("SRCLR_N: ");
Serial.println(digitalRead(SRCLR));
// uint16_t q = digitalRead(Q1) << 8 |
// digitalRead(Q2) << 7 |
// digitalRead(Q3) << 6 |
// digitalRead(Q4) << 5 |
// digitalRead(Q5) << 4 |
// digitalRead(Q6) << 3 |
// digitalRead(Q7) << 2 |
// digitalRead(Q8) << 1 |
// digitalRead(Qout);
// Serial.print("Q: ");
// Serial.println(q, BIN);
Serial.println();
Serial.print(digitalRead(Q1));
Serial.print(digitalRead(Q2));
Serial.print(digitalRead(Q3));
Serial.print(digitalRead(Q4));
Serial.print(digitalRead(Q5));
Serial.print(digitalRead(Q6));
Serial.print(digitalRead(Q7));
Serial.print(digitalRead(Q8));
Serial.print(" ");
Serial.print(digitalRead(Q9));
Serial.print(digitalRead(Q10));
Serial.print(digitalRead(Q11));
Serial.print(digitalRead(Q12));
Serial.print(digitalRead(Q13));
Serial.print(digitalRead(Q14));
Serial.print(digitalRead(Q15));
Serial.print(digitalRead(Q16));
Serial.print(" ");
Serial.print(digitalRead(Qout));
Serial.println();
}
void setup() {
// pinMode(LED_BUILTIN, OUTPUT);
// pinMode(24u, INPUT_PULLUP);
// Serial.begin(9600);
// FastLED.addLeds<NEOPIXEL, DATA_PIN>(leds, NUM_LEDS);
// FastLED.setBrightness(30);
pinMode(Q1, INPUT_PULLDOWN);
pinMode(Q2, INPUT_PULLDOWN);
pinMode(Q3, INPUT_PULLDOWN);
pinMode(Q4, INPUT_PULLDOWN);
pinMode(Q5, INPUT_PULLDOWN);
pinMode(Q6, INPUT_PULLDOWN);
pinMode(Q7, INPUT_PULLDOWN);
pinMode(Q8, INPUT_PULLDOWN);
pinMode(Q9, INPUT_PULLDOWN);
pinMode(Q10, INPUT_PULLDOWN);
pinMode(Q11, INPUT_PULLDOWN);
pinMode(Q12, INPUT_PULLDOWN);
pinMode(Q13, INPUT_PULLDOWN);
pinMode(Q14, INPUT_PULLDOWN);
pinMode(Q15, INPUT_PULLDOWN);
pinMode(Q16, INPUT_PULLDOWN);
pinMode(Qout, INPUT_PULLDOWN);
// 1
pinMode(SER, OUTPUT);
// 2
pinMode(OE, OUTPUT);
digitalWrite(OE, HIGH);
// 3
pinMode(RCLK, OUTPUT);
// 4
pinMode(SRCLK, OUTPUT);
// 5
pinMode(SRCLR, OUTPUT);
digitalWrite(SRCLR, HIGH);
printOut();
}
// uint8_t r, g, b;
uint16_t prevQ = 255;
void loop() {
// r += 3;
// g += 5;
// b += 7;
// leds[0] = CRGB(r, g, b);
// FastLED.show();
// delay(100);
// if (digitalRead(24u) == LOW) {
// Serial.println("Button pressed");
// }
char c = Serial.read();
if (c == 'o') {
printOut();
}
if (c == '1') {
digitalWrite(SER, !digitalRead(SER));
printOut();
} else if (c == '2') {
digitalWrite(OE, !digitalRead(OE));
printOut();
} else if (c == '3') {
digitalWrite(RCLK, HIGH);
digitalWrite(RCLK, LOW);
printOut();
} else if (c == '4') {
digitalWrite(SRCLK, HIGH);
digitalWrite(SRCLK, LOW);
printOut();
} else if (c == '5') {
digitalWrite(SRCLR, !digitalRead(SRCLR));
printOut();
}
}

11
firmware/test/README Normal file
View File

@ -0,0 +1,11 @@
This directory is intended for PlatformIO Test Runner and project tests.
Unit Testing is a software testing method by which individual units of
source code, sets of one or more MCU program modules together with associated
control data, usage procedures, and operating procedures, are tested to
determine whether they are fit for use. Unit testing finds problems early
in the development cycle.
More information about PlatformIO Unit Testing:
- https://docs.platformio.org/en/latest/advanced/unit-testing/index.html