diff --git a/README.md b/README.md index 75be53e6c645bf923f4a5b919491558feddfd317..e9af750801675ca7d44844381119eff3fdf1d915 100644 --- a/README.md +++ b/README.md @@ -1,93 +1,59 @@ -# NEST Firmware - Arduino Version +# NEST Firmware - Arduino Version (Wearable Prototipo Propio) +Este repositorio contiene el firmware para el proyecto **NEST (Non-intrusive dEviceS for Telemedicine)**, desarrollado para un **wearable prototipo propio** en la plataforma **Arduino**. El firmware controla el monitoreo de **frecuencia cardÃaca (BPM)** y **saturación de oxÃgeno (SpO2)** mediante el sensor **MAX30102** y el microcontrolador **nRF52840** con **Bluetooth Low Energy (BLE)** integrado. Este repositorio incluye el bootloader y las bibliotecas necesarias para compilar y programar el código. +## Estructura del repositorio -## Getting started +- **/bootloader**: Archivos del bootloader para el nRF52840. +- **/firmware**: Código fuente del firmware desarrollado en Arduino. +- **/libraries**: Biblioteca necesaria, como **Ucglib.h**, utilizada para controlar la pantalla TFT. +## Requisitos para Programar en Arduino -To make it easy for you to get started with GitLab, here's a list of recommended next steps. +### Paso 1: Instalar Arduino Core para nRF52840 -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! +1. **Descargar e instalar Arduino IDE** (al menos v1.6.12): [Arduino IDE](https://www.arduino.cc/en/software). +2. Iniciar el Arduino IDE y entrar a las **Preferencias**. +3. En **Additional Board Manager URLs**, agregar: + `https://adafruit.github.io/arduino-board-index/package_adafruit_index.json` +4. Reiniciar el Arduino IDE. +5. Ir a **Herramientas > Placa > Gestor de Placas** y buscar "Adafruit nRF52" e instalar **Adafruit nRF52 by Adafruit**. +6. Una vez instalado, seleccionar **Adafruit Feather nRF52840 Express** desde **Herramientas > Placa** para configurar el sistema. +### Paso 2: Instalar Controladores y Herramientas -## Add your files +- **Adafruit nrfutil**: En Linux, ejecuta el siguiente comando para instalar nrfutil, necesario para cargar sketches vÃa el puerto serie: + + ```bash + pip3 install adafruit-nrfutil --user -- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: +### Paso 3: Cargar el Bootloader con J-Link: -``` -cd existing_repo -git remote add origin https://git.cti.espol.edu.ec/nest/nest-firmware-arduino-version.git -git branch -M main -git push -uf origin main -``` +```markdown +### Paso 3: Cargar el Bootloader con J-Link -## Integrate with your tools +1. Instalar el **Segger JLink Software and Documentation Pack** y **Nordic nRF5x Command Line Tools**. +2. Asegurarse de que puedes ejecutar `nrfjprog` desde tu terminal. +3. Conectar el **J-Link** a la placa. +4. Abrir el Arduino IDE y seleccionar: + - **Herramientas > Placa > Adafruit Feather nRF52840 Express** + - **Herramientas > Programador > J-Link for Feather52** + - **Herramientas > Grabar Bootloader** para cargar el bootloader en la placa. +### Paso 4: Programar el Bootloader manualmente con nrfjprog -- [ ] [Set up project integrations](https://git.cti.espol.edu.ec/nest/nest-firmware-arduino-version/-/settings/integrations) +Si prefieres cargar el bootloader manualmente, sigue estos pasos: -## Collaborate with your team +1. Ejecuta los siguientes comandos en tu terminal para borrar la memoria y cargar el bootloader: -- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) -- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) + ```bash + nrfjprog -e -f nrf52 + nrfjprog --program bin/bootloader/feather_nrf52840_bootloader.hex -f nrf52 + nrfjprog --reset -f nrf52 -## Test and Deploy +## Descripción del Firmware -Use the built-in continuous integration in GitLab. +El firmware permite las siguientes funcionalidades: +- Monitoreo de **BPM** y **SpO2** utilizando el sensor **MAX30102**. +- Interacción con el usuario a través de una pantalla **TFT** controlada con la biblioteca **Ucglib.h**. +- Transmisión de datos a una base de datos remota utilizando **Bluetooth Low Energy (BLE)**. +- Gestión de encuestas de dolor y recordatorios de medicación. -- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) -- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) -*** - -# Editing this README - -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template. - -## Suggestions for a good README - -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. - -## Name -Choose a self-explaining name for your project. - -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. - -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. - -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. - -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.