This commit is contained in:
Patrick Moessler 2020-06-23 02:04:07 +02:00
commit d2ceedd05f
10 changed files with 299 additions and 0 deletions

5
.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

67
.travis.yml Normal file
View file

@ -0,0 +1,67 @@
# Continuous Integration (CI) is the practice, in software
# engineering, of merging all developer working copies with a shared mainline
# several times a day < https://docs.platformio.org/page/ci/index.html >
#
# Documentation:
#
# * Travis CI Embedded Builds with PlatformIO
# < https://docs.travis-ci.com/user/integration/platformio/ >
#
# * PlatformIO integration with Travis CI
# < https://docs.platformio.org/page/ci/travis.html >
#
# * User Guide for `platformio ci` command
# < https://docs.platformio.org/page/userguide/cmd_ci.html >
#
#
# Please choose one of the following templates (proposed below) and uncomment
# it (remove "# " before each line) or use own configuration according to the
# Travis CI documentation (see above).
#
#
# Template #1: General project. Test it using existing `platformio.ini`.
#
# language: python
# python:
# - "2.7"
#
# sudo: false
# cache:
# directories:
# - "~/.platformio"
#
# install:
# - pip install -U platformio
# - platformio update
#
# script:
# - platformio run
#
# Template #2: The project is intended to be used as a library with examples.
#
# language: python
# python:
# - "2.7"
#
# sudo: false
# cache:
# directories:
# - "~/.platformio"
#
# env:
# - PLATFORMIO_CI_SRC=path/to/test/file.c
# - PLATFORMIO_CI_SRC=examples/file.ino
# - PLATFORMIO_CI_SRC=path/to/test/directory
#
# install:
# - pip install -U platformio
# - platformio update
#
# script:
# - platformio ci --lib="." --board=ID_1 --board=ID_2 --board=ID_N

7
.vscode/extensions.json vendored Normal file
View file

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

3
.vscode/settings.json vendored Normal file
View file

@ -0,0 +1,3 @@
{
"python.pythonPath": "C:\\Users\\lord\\.platformio\\penv\\Scripts\\python.exe"
}

5
extra_script.py Normal file
View file

@ -0,0 +1,5 @@
Import("env")
env.Replace(
UPLOADCMD="scp $SOURCE pi@retropie:dev/fw.elf && ssh pi@retropie dev/prog_avr.sh dev/fw.elf"
)

39
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
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

17
platformio.ini Normal file
View file

@ -0,0 +1,17 @@
; 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:pro8MHzatmega328]
platform = atmelavr
board = pro8MHzatmega328
framework = arduino
extra_scripts = extra_script.py
upload_protocol = custom
build_flags = -Wall -O3

99
src/main.cpp Normal file
View file

@ -0,0 +1,99 @@
#include <Arduino.h>
static const uint8_t PORTD_ROWN = 0xFF;
static const uint8_t PORTD_ROW0 = ~((1 << PD0));
static const uint8_t PORTD_ROW1 = ~((1 << PD3));
static const uint8_t PORTD_ROW2 = ~((1 << PD1));
static const uint8_t OUT_LEN = 2;
volatile uint8_t output[OUT_LEN];
static inline void wait(uint16_t del) {
auto begin = millis();
while (millis() - begin < del);
}
static inline void update_output() {
PORTD = PORTD_ROW0;
delayMicroseconds(30);
uint8_t tmp = (PIND >> 4) & 0x0F;
PORTD = PORTD_ROW1;
delayMicroseconds(30);
tmp |= (PIND & 0xF0);
output[0] = tmp;
PORTD = PORTD_ROW2;
delayMicroseconds(30);
output[1] = (PIND >> 4) & 0x0F;
PORTD = PORTD_ROWN;
delayMicroseconds(30);
}
volatile uint8_t ctr = 0;
// ISR(SPI_STC_vect) {
// SPDR = output[ctr];
// ctr = (ctr + 1) % OUT_LEN;
// }
ISR(PCINT0_vect){
if (!(PINB & (1 << PB2))) {
while(!(SPSR & (1<<SPIF)));
SPDR = output[1];
while(!(SPSR & (1<<SPIF)));
SPDR = output[0];
}
// if (PINB & (1 << PB2)) {
// SPDR = output[0];
// } else {
// while(!(SPSR & (1<<SPIF)));
// SPDR = output[1];
// }
}
void setup() {
Serial.end();
// port D for Button Matrix
DDRD = (1 << PD0) | (1 << PD1) | (1 << PD3);
PORTD = PORTD_ROWN;
// port B for SPI slave
DDRB &= ~((1 << 2) | (1 << 3) | (1 << 5));
DDRB |= (1 << 4);
PORTB |= 0x1E;
// Button Buffer
output[0] = 00;
output[1] = 00;
// SPI slave
SPCR &= ~(1 << MSTR);
SPCR |= (1 << SPE) /*| (1 << SPIE)*/ | (1 << DORD);
// SPI CS int
PCMSK0 |= (1<<PCINT2);
PCICR |= (1<<PCIE0);
// SPI prepare
update_output();
// SPDR = output[0];
// ctr = 1;
}
void loop() {
update_output();
wait(100);
// if (PINB & (1 << PB2)) {
// SPDR = output[0];
// ctr = 1;
// } else {
// ctr=0;
// }
}

11
test/README Normal file
View file

@ -0,0 +1,11 @@
This directory is intended for PIO Unit Testing 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 PIO Unit Testing:
- https://docs.platformio.org/page/plus/unit-testing.html