i2c scaner ESP32

ESP32/OLED_ESP32/.gitignore

@@ -3,3 +3,4 @@
 .vscode/c_cpp_properties.json
 .vscode/launch.json
 .vscode/ipch
+.vscode

ESP32/i2c_scaner_esp32_dev/.gitignore

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

ESP32/i2c_scaner_esp32_dev/.travis.yml

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

ESP32/i2c_scaner_esp32_dev/include/Colors.h

@@ -0,0 +1,48 @@
+
+#ifndef COLORS_H
+#define COLORS_H
+
+//RESET
+String fontReset = "\e[0m";
+
+//COLORS - REGULAR 
+String Black = "\e[0;30m";
+String Red = "\e[0;31m";
+String Green = "\e[0;32m";
+String Yellow = "\e[0;33m";
+String Blue = "\e[0;34m";
+String Purple = "\e[0;35m";
+String Cyan = "\e[0;36m";
+String White = "\e[0;37m";
+
+//COLORS - BOLD
+String boldBlack = "\e[1;30m";
+String boldRed = "\e[1;31m";
+String boldGreen = "\e[1;32m";
+String boldYellow = "\e[1;33m";
+String boldBlue = "\e[1;34m";
+String boldPurple = "\e[1;35m";
+String boldCyan = "\e[1;36m";
+String boldWhite = "\e[1;37m";
+
+//COLORS - UNDERLINED
+String underlineBlack = "\e[4;30m";
+String underlineRed = "\e[4;31m";
+String underlineGreen = "\e[4;32m";
+String underlineYellow = "\e[4;33m";
+String underlineBlue = "\e[4;34m";
+String underlinePurple = "\e[4;35m";
+String underlineCyan = "\e[4;36m";
+String underlineWhite = "\e[4;37m";
+
+//BACKGROUND - 
+String backgroundBlack = "\e[40;30m";
+String backgroundRed = "\e[41;31m";
+String backgroundGreen = "\e[42;32m";
+String backgroundYellow = "\e[43;33m";
+String backgroundBlue = "\e[44;34m";
+String backgroundPurple = "\e[45;35m";
+String backgroundCyan = "\e[46;36m";
+String backgroundWhite = "\e[47;37m";
+
+#endif

ESP32/i2c_scaner_esp32_dev/include/README

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

ESP32/i2c_scaner_esp32_dev/lib/README

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

ESP32/i2c_scaner_esp32_dev/platformio.ini

@@ -0,0 +1,6 @@
+[env:esp32doit-devkit-v1]
+platform = espressif32
+board = esp32doit-devkit-v1
+framework = arduino
+monitor_speed = 115200
+monitor_flags = --raw 

ESP32/i2c_scaner_esp32_dev/src/main.cpp

@@ -0,0 +1,38 @@
+#include <Arduino.h>
+#include <Wire.h>
+#include <Colors.h>
+void setup()
+{
+  Serial.begin(115200);
+  Wire.begin();
+}
+
+void loop()
+{
+   byte error, address;
+  int nDevices;
+
+  Serial.println(Red+"Escaneando...");
+  Serial.println("**************"+ fontReset);
+
+  nDevices = 0;
+  for (address = 1; address < 127; address++)
+  {
+
+    Wire.beginTransmission(address);
+    error = Wire.endTransmission();
+
+    if (error == 0)
+    {
+      Serial.print("Encontrado dispositivo I2C dirección: ");
+      Serial.print(boldBlue + "0x");
+      if (address < 16)
+      Serial.print("0");
+      Serial.print(address, HEX);
+      Serial.println(fontReset);
+      nDevices++;
+    }
+  }
+  Serial.println(Red + "**************" +fontReset);
+  delay(5000); 
+}

ESP32/i2c_scaner_esp32_dev/test/README

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