yyy

2 files changed, 72 insertions, 72 deletions

diff --git a/include/README b/include/README
index 49819c0..630164d 100644
--- a/include/README
+++ b/include/README
@@ -1,37 +1,37 @@
-
-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 convention is to give header files names that end with `.h'.
-
-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
+

+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 convention is to give header files names that end with `.h'.

+

+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

diff --git a/include/settings.h b/include/settings.h
index aae29e6..a06b8c5 100644
--- a/include/settings.h
+++ b/include/settings.h
@@ -1,35 +1,35 @@
-#pragma once
-
-// OLED
-const int OLED_WIDTH  = 128;
-const int OLED_HEIGHT = 64;
-const int OLED_ADDR   = 0x3C;
-
-const int SCL_PIN = 8;
-const int SDA_PIN = 10;
-
-// RGB LED
-const int RED_PIN   = 2; 
-const int GREEN_PIN = 4; 
-const int BLUE_PIN  = 6;
-
-// MOTORS
-const int EN12 = 40;
-const int IN1 = 38;
-const int IN2 = 36;
-
-
-const int EN34 = 13;
-const int IN3 = 37;
-const int IN4 = 35;
-
-
-
-
-// const int EN34 = 13;
-// const int IN3 = 7;
-// const int IN4 = 5;
-
-
-// BUZZER
-const int BUZZER_PIN = 3;
+#pragma once

+

+// OLED

+const int OLED_WIDTH  = 128;

+const int OLED_HEIGHT = 64;

+const int OLED_ADDR   = 0x3C;

+

+const int SCL_PIN = 8;

+const int SDA_PIN = 10;

+

+// RGB LED

+const int RED_PIN   = 2; 

+const int GREEN_PIN = 4; 

+const int BLUE_PIN  = 6;

+

+// MOTORS

+const int EN12 = 40;

+const int IN1 = 38;

+const int IN2 = 36;

+

+

+const int EN34 = 39;

+const int IN3 = 37;

+const int IN4 = 35;

+

+

+

+

+// const int EN34 = 13;

+// const int IN3 = 7;

+// const int IN4 = 5;

+

+

+// BUZZER

+const int BUZZER_PIN = 13;