Skip to content

Commit 6f816c4

Browse files
committed
v1.0.0
Signed-off-by: Vincent ABRIOU <[email protected]>
1 parent 801f98a commit 6f816c4

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

43 files changed

+13445
-1
lines changed

.gitignore

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
Projects/*/*/*/STM32CubeIDE/Application
2+
Projects/*/*/*/STM32CubeIDE/Drivers
3+
Projects/*/*/*/STM32CubeIDE/Middlewares
4+
Projects/*/*/*/STM32CubeIDE/release
5+
Projects/*/*/*/STM32CubeIDE/.settings
6+
Projects/*/*/*/STM32CubeIDE/*.launch

.gitmodules

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
[submodule "Drivers/CMSIS"]
2+
path = Drivers/CMSIS
3+
url = https://github.com/STMicroelectronics/cmsis-core.git
4+
[submodule "Drivers/CMSIS_Device/ST/STM32N6xx"]
5+
path = Drivers/CMSIS_Device/ST/STM32N6xx
6+
url = https://github.com/STMicroelectronics/cmsis-device-n6.git
7+
[submodule "Drivers/STM32N6xx_HAL_Driver"]
8+
path = Drivers/STM32N6xx_HAL_Driver
9+
url = https://github.com/STMicroelectronics/stm32n6xx-hal-driver.git
10+
[submodule "Drivers/BSP/Components/Common"]
11+
path = Drivers/BSP/Components/Common
12+
url = https://github.com/STMicroelectronics/stm32-bsp-common.git
13+
[submodule "Drivers/BSP/Components/mx66uw1g45g"]
14+
path = Drivers/BSP/Components/mx66uw1g45g
15+
url = https://github.com/STMicroelectronics/stm32-mx66uw1g45g.git
16+
[submodule "Drivers/BSP/Components/rk050hr18"]
17+
path = Drivers/BSP/Components/rk050hr18
18+
url = https://github.com/STMicroelectronics/stm32-rk050hr18.git
19+
[submodule "Drivers/BSP/STM32N6570-DK"]
20+
path = Drivers/BSP/STM32N6570-DK
21+
url = https://github.com/STMicroelectronics/stm32n6570-dk-bsp
22+
[submodule "Middlewares/ST/STM32_USB_Device_Library"]
23+
path = Middlewares/ST/STM32_USB_Device_Library
24+
url = https://github.com/STMicroelectronics/stm32-mw-usb-device.git
25+
[submodule "Middlewares/ST/STM32_ISP_Library"]
26+
path = Middlewares/ST/STM32_ISP_Library
27+
url = https://github.com/STMicroelectronics/stm32-mw-isp.git
28+
[submodule "Middlewares/ST/STM32_Camera_Middleware"]
29+
path = Middlewares/ST/STM32_Camera_Middleware
30+
url = https://github.com/STMicroelectronics/stm32-mw-camera.git
31+
[submodule "Drivers/BSP/Components/aps256xx"]
32+
path = Drivers/BSP/Components/aps256xx
33+
url = https://github.com/STMicroelectronics/stm32-aps256.git

CODE_OF_CONDUCT.md

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at https://www.st.com/content/st_com/en/contact-us.html. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available [here](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html).
72+
73+
[homepage]: https://www.contributor-covenant.org
74+
75+
For answers to common questions about this code of conduct, refer to the FAQ section [here](https://www.contributor-covenant.org/faq).

CONTRIBUTING.md

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
# Contributing guide
2+
3+
This guide serves as a checklist before contributing to this repository. It mainly focuses on the steps to follow to submit an issue or a pull-request.
4+
5+
## 1. Issues
6+
7+
### 1.1 Before opening an issue
8+
9+
Please check the following points before posting an issue:
10+
* Make sure you are using the latest commit (major releases are tagged, but corrections are available as new commits).
11+
* Make sure your issue is a question/feedback/suggestions **related to** the software provided in this repository. Otherwise, please refer to section [3](CONTRIBUTING.md#3-support-requests-and-questions) below.
12+
* Make sure your issue is not already reported/fixed on GitHub or discussed on a previous issue. Do not forget to browse into the **closed** issues.
13+
14+
### 1.2 Posting the issue
15+
16+
When you have checked the previous points, create a new report from the **Issues** tab of this repository. A template is available [here](../../issues/new/choose) to help you report the issue you are facing or the enhancement you would like to propose.
17+
18+
## 2. Pull Requests
19+
20+
### 2.1 Before opening a pull-request
21+
22+
STMicrolectronics is happy to receive contributions from the community, based on an initial Contributor License Agreement (CLA) procedure.
23+
24+
* If you are an individual writing original source code and you are sure **you own the intellectual property**, then you need to sign an Individual [CLA](https://cla.st.com).
25+
* If you work for a company that wants also to allow you to contribute with your work, your company needs to provide a Corporate [CLA](https://cla.st.com) mentioning your GitHub account name.
26+
* If you are not sure that a CLA (Individual or Corporate) has been signed for your GitHub account you can check the [CLA](https://cla.st.com) dedicated page.
27+
28+
Please note that:
29+
* The Corporate CLA will always take precedence over the Individual CLA.
30+
* One CLA submission is sufficient, for any project proposed by STMicroelectronics.
31+
32+
### 2.2 How to proceed
33+
34+
* We recommend to engage first a communication thru an issue, in order to present your proposal, just to confirm that it corresponds to STMicroelectronics' domain or scope.
35+
* Then fork the project to your GitHub account to further develop your contribution. Please use the latest commit version.
36+
* Please, submit one pull-request per new feature or proposal. This will ease the analysis and the final merge if accepted.
37+
38+
## 3. Support requests and questions
39+
40+
For support requests or any other question related to the product, the tools, the environment, you can submit a post to the **ST Community** on the appropriate topic [page](https://community.st.com/t5/stm32-mcus/ct-p/stm32-mcus).

Drivers/BSP/Components/Common

Submodule Common added at 6893c33

Drivers/BSP/Components/aps256xx

Submodule aps256xx added at cdc4592

Drivers/BSP/Components/mx66uw1g45g

Submodule mx66uw1g45g added at 4c358c6

Drivers/BSP/Components/rk050hr18

Submodule rk050hr18 added at acc765c

Drivers/BSP/STM32N6570-DK

Submodule STM32N6570-DK added at 9e4dd51

Drivers/CMSIS

Submodule CMSIS added at 1a2f783

0 commit comments

Comments
 (0)