STM32 1.9.0 release

https://github.com/stm32duino/Arduino_Core_STM32/releases/tag/1.9.0

Author: mriscoc

.editorconfig

@@ -0,0 +1,17 @@
+[*]
+end_of_line = lf
+insert_final_newline = true
+indent_style = space
+indent_size = 2
+trim_trailing_whitespace =  true
+
+[*.sh]
+# like -i=2
+indent_style = space
+indent_size = 2
+
+#shell_variant      = posix # like -ln=posix
+#binary_next_line   = true  # like -bn
+switch_case_indent = true  # like -ci
+space_redirects    = true  # like -sr
+#keep_padding       = true  # like -kp

.gitattributes

@@ -0,0 +1,44 @@
+# Set the default behavior, in case people don't have core.autocrlf set.
+* text=auto
+
+# Explicitly declare text files you want to always be normalized and converted
+# to native line endings on checkout.
+.astyleignore text eol=lf
+.astylerc text eol=lf
+.editorconfig text eol=lf
+.flake8 text eol=lf
+.gitattributes text eol=lf
+.gitignore text eol=lf
+
+*.adoc text eol=lf
+*.c text eol=lf
+*.cmake text eol=lf
+*.cpp text eol=lf
+*.css text eol=lf
+*.dtsi text eol=lf
+*.gv text eol=lf
+*.h text eol=lf
+*.html text eol=lf
+*.in text eol=lf
+*.ino text eol=lf
+*.json text eol=lf
+*.ld text eol=lf
+*.md text eol=lf
+*.MD text eol=lf
+*.old text eol=lf
+*.patch text eol=lf
+*.pde text eol=lf
+*.properties text eol=lf
+*.py text eol=lf
+*.s text eol=lf
+*.S text eol=lf
+*.sh text eol=lf
+*.spec text eol=lf
+*.txt text eol=lf
+*.yml text eol=lf
+
+# Denote all files that are truly binary and should not be modified.
+*.jpg binary
+*.pdf binary
+*.png binary
+

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at stmduino@st.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,53 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Please, before reporting any issue**
+- Make sure you are using the latest Arduino_Core_STM32 version.
+  https://github.com/stm32duino/Arduino_Core_STM32/releases/latest
+- Make sure the issue is not already reported/fixed on GitHub or discussed on the [stm32duino forum](http://stm32duino.com)
+- Submit a GitHub issue only for reporting a problem related to the [Arduino_Core_STM32](https://github.com/stm32duino/Arduino_Core_STM32).
+- **Avoid** to submit a GitHub issue for project troubleshooting.
+ 
+Any questions/feedback/suggestions should be discussed on the [stm32duino forum](http://stm32duino.com):
+  * questions on the [STM32 Core](http://stm32duino.com/viewforum.php?f=35)
+  * bugs/enhancements on the [STM core: Bugs and enhancements](http://stm32duino.com/viewforum.php?f=38)
+
+When reporting any issue, please try to provide all relevant information:
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Complete source code which can be used to reproduce the issue. Please try to be as generic as possible (no extra code, extra hardware,...)
+
+Steps to reproduce the behavior:
+1. Plug
+2. Press USER_BTN
+3. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. Windows]
+ - Arduino IDE version: [e.g. 1.8.8]
+ - STM32 core version: [e.g. 1.4.0]
+ - Tools menu settings if not the default: [e.g. Newlib Standard, No Serial]
+ - Upload method: [e.g. STLink]
+
+**Board (please complete the following information):**
+ - Name: [e.g. Nucleo F429ZI]
+ - Hardware Revision: [e.g. Rev B]
+ - Extra hardware used if any: [e.g. X-Nucleo IKS01A1]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature-request-improvement.md

@@ -0,0 +1,22 @@
+---
+name: Feature request/improvement
+about: Suggest an idea or improvement for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request/improvement related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context, example or screenshots about the feature request here.
+
+Any contribution is welcome, so do not hesitate to submit a PR.

.github/ISSUE_TEMPLATE/new-variant-request.md

@@ -0,0 +1,20 @@
+---
+name: New variant request
+about: Request for a new board support
+title: "[New Variant]"
+labels: New variant
+assignees: ''
+
+---
+
+**Board description (please complete the following information):**
+ - Name: [e.g. DISCOVERY F769NI]
+ - Link to all relevant information:
+   * Documentations
+   * Schematics
+   * Where this hardware can be purchased
+  * ...
+
+**Note that user can add a STM32 based board following this [wiki](https://github.com/stm32duino/wiki/wiki/Add-a-new-variant-(board))**
+
+Any contribution is welcome, so do not hesitate to submit a PR.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,45 @@
+## Pull Request template
+
+Please, Make sure that your PR is not a duplicate.
+Search among the [Pull request](https://github.com/stm32duino/Arduino_Core_STM32/pulls) before creating one.
+
+IMPORTANT: Please review the [CONTRIBUTING.md](../CONTRIBUTING.md) file for detailed contributing guidelines.
+
+Thanks for submitting a pull request.
+Please provide enough information so that others can review your pull request:
+
+**Summary**
+
+<!-- Summary of the PR -->
+
+This PR fixes/implements the following **bugs/features**
+
+* [ ] Bug 1
+* [ ] Bug 2
+* [ ] Feature 1
+* [ ] Feature 2
+* [ ] Breaking changes
+
+<!-- You can skip this if you're fixing a typo or adding an app to the Showcase. -->
+
+Explain the **motivation** for making this change. What existing problem does the pull request solve?
+
+<!-- Example: When "Adding a function to do X", explain why it is necessary to have a way to do X. -->
+
+**Validation**
+
+* Ensure CI build is passed.
+* Demonstrate the code is solid. [e.g. Provide a sketch]
+
+<!-- Make sure tests pass on both CI. -->
+
+**Code formatting**
+
+* Ensure AStyle check is passed thanks CI
+
+<!-- See the simple style guide. -->
+
+**Closing issues**
+
+<!-- Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such). -->
+Fixes #xxx

.github/actions/pio-build/Dockerfile

@@ -0,0 +1,18 @@
+# Container image that runs your code
+FROM ubuntu:latest
+
+ENV LANG C.UTF-8
+ENV LC_ALL C.UTF-8
+
+# Install prerequisites
+RUN apt-get --quiet=2 update && apt-get install --quiet=2 --assume-yes git python3 python3-pip wget
+
+# Install PlatformIO
+RUN pip3 install --quiet --upgrade platformio
+CMD /bin/bash
+
+# Copies your code file from your action repository to the filesystem path `/` of the container
+COPY entrypoint.sh /entrypoint.sh
+
+# Code file to execute when the docker container starts up (`entrypoint.sh`)
+ENTRYPOINT ["/entrypoint.sh"]

.github/actions/pio-build/README.md

@@ -0,0 +1,15 @@
+# PlatformIO build action
+
+This action build thanks PIO.
+
+## Inputs
+
+### `cmsis-version`
+
+The CMSIS version to use. Default `"5.5.1"`.
+
+## Example usage
+
+```yaml
+uses: ./.github/actions/pio-build
+```

.github/actions/pio-build/action.yml

@@ -0,0 +1,12 @@
+# action.yml
+name: 'PlatformIO Build'
+description: 'Compile using PlatformIO'
+inputs:
+  cmsis-version:
+    description: 'CMSIS package version to use'
+    default: '5.5.1'
+runs:
+  using: 'docker'
+  image: 'Dockerfile'
+  args:
+    - ${{ inputs.cmsis-version }}

.github/actions/pio-build/entrypoint.sh

@@ -0,0 +1,29 @@
+#!/bin/bash
+
+readonly CMSIS_VERSION="$1"
+readonly CMSIS_ARCHIVE="CMSIS-${CMSIS_VERSION}.tar.bz2"
+
+# Install the development version of ststm32 platform
+platformio platform install "https://github.com/platformio/platform-ststm32.git" || {
+  exit 1
+}
+# Prepare framework for CI
+python3 -c "import json; import os; fp=open(os.path.expanduser('~/.platformio/platforms/ststm32/platform.json'), 'r+'); data=json.load(fp); data['packages']['framework-arduinoststm32']['version'] = '*'; fp.seek(0); fp.truncate(); json.dump(data, fp); fp.close()" || {
+  exit 1
+}
+ln --symbolic "$GITHUB_WORKSPACE" "$HOME/.platformio/packages/framework-arduinoststm32" || {
+  exit 1
+}
+# Download and unpack CMSIS package
+wget --no-verbose "https://github.com/stm32duino/ArduinoModule-CMSIS/releases/download/$CMSIS_VERSION/$CMSIS_ARCHIVE" || {
+  exit 1
+}
+tar --extract --bzip2 --file="$CMSIS_ARCHIVE" || {
+  exit 1
+}
+cd "$GITHUB_WORKSPACE/CI/build/" || {
+  exit 1
+}
+python3 platformio-builder.py --board=blackpill_f103c8 --board=remram_v1
+
+exit $?