v1.0.0

Signed-off-by: Vincent ABRIOU <[email protected]>

.gitignore

@@ -0,0 +1,6 @@
+Projects/*/*/*/STM32CubeIDE/Application
+Projects/*/*/*/STM32CubeIDE/Drivers
+Projects/*/*/*/STM32CubeIDE/Middlewares
+Projects/*/*/*/STM32CubeIDE/release
+Projects/*/*/*/STM32CubeIDE/.settings
+Projects/*/*/*/STM32CubeIDE/*.launch

.gitmodules

@@ -0,0 +1,33 @@
+[submodule "Drivers/CMSIS"]
+	path = Drivers/CMSIS
+	url = https://github.com/STMicroelectronics/cmsis-core.git
+[submodule "Drivers/CMSIS_Device/ST/STM32N6xx"]
+	path = Drivers/CMSIS_Device/ST/STM32N6xx
+	url = https://github.com/STMicroelectronics/cmsis-device-n6.git
+[submodule "Drivers/STM32N6xx_HAL_Driver"]
+	path = Drivers/STM32N6xx_HAL_Driver
+	url = https://github.com/STMicroelectronics/stm32n6xx-hal-driver.git
+[submodule "Drivers/BSP/Components/Common"]
+	path = Drivers/BSP/Components/Common
+	url = https://github.com/STMicroelectronics/stm32-bsp-common.git
+[submodule "Drivers/BSP/Components/mx66uw1g45g"]
+	path = Drivers/BSP/Components/mx66uw1g45g
+	url = https://github.com/STMicroelectronics/stm32-mx66uw1g45g.git
+[submodule "Drivers/BSP/Components/rk050hr18"]
+	path = Drivers/BSP/Components/rk050hr18
+	url = https://github.com/STMicroelectronics/stm32-rk050hr18.git
+[submodule "Drivers/BSP/STM32N6570-DK"]
+	path = Drivers/BSP/STM32N6570-DK
+	url = https://github.com/STMicroelectronics/stm32n6570-dk-bsp
+[submodule "Middlewares/ST/STM32_USB_Device_Library"]
+	path = Middlewares/ST/STM32_USB_Device_Library
+	url = https://github.com/STMicroelectronics/stm32-mw-usb-device.git
+[submodule "Middlewares/ST/STM32_ISP_Library"]
+	path = Middlewares/ST/STM32_ISP_Library
+	url = https://github.com/STMicroelectronics/stm32-mw-isp.git
+[submodule "Middlewares/ST/STM32_Camera_Middleware"]
+	path = Middlewares/ST/STM32_Camera_Middleware
+	url = https://github.com/STMicroelectronics/stm32-mw-camera.git
+[submodule "Drivers/BSP/Components/aps256xx"]
+	path = Drivers/BSP/Components/aps256xx
+	url = https://github.com/STMicroelectronics/stm32-aps256.git

CODE_OF_CONDUCT.md

@@ -0,0 +1,75 @@
+# 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 https://www.st.com/content/st_com/en/contact-us.html. 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 [here](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, refer to the FAQ section [here](https://www.contributor-covenant.org/faq).

CONTRIBUTING.md

@@ -0,0 +1,40 @@
+# Contributing guide
+
+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.
+
+## 1. Issues
+
+### 1.1 Before opening an issue
+
+Please check the following points before posting an issue:
+* Make sure you are using the latest commit (major releases are tagged, but corrections are available as new commits).
+* 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.
+* 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.
+
+### 1.2 Posting the issue
+
+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.
+
+## 2. Pull Requests
+
+### 2.1 Before opening a pull-request
+
+STMicrolectronics is happy to receive contributions from the community, based on an initial Contributor License Agreement (CLA) procedure.
+
+* 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).
+* 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.
+* 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.
+
+Please note that:
+* The Corporate CLA will always take precedence over the Individual CLA.
+* One CLA submission is sufficient, for any project proposed by STMicroelectronics.
+
+### 2.2 How to proceed
+
+* 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.
+* Then fork the project to your GitHub account to further develop your contribution. Please use the latest commit version.
+* Please, submit one pull-request per new feature or proposal. This will ease the analysis and the final merge if accepted.
+
+## 3. Support requests and questions
+
+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).

LICENSE.md

@@ -0,0 +1,17 @@
+|Component                     |Copyright                              |License
+|---------                     |----------                             |-------
+| CMSIS                        | ARM Limited                           | [Apache-2.0](https://opensource.org/licenses/Apache-2.0)
+| STM32N6xx CMSIS Device       | ARM Limited, STMicroelectronics       | [Apache-2.0](https://opensource.org/licenses/Apache-2.0)
+| STM32N6xx HAL/LL Drivers     | STMicroelectronics                    | [BSD-3-Clause](https://opensource.org/licenses/BSD-3-Clause)
+| STM32N6570-DK BSP Drivers    | STMicroelectronics                    | [BSD-3-Clause](https://opensource.org/licenses/BSD-3-Clause)
+| BSP Component aps256xx       | STMicroelectronics                    | [BSD-3-Clause](https://opensource.org/licenses/BSD-3-Clause)
+| BSP Component Common         | STMicroelectronics                    | [BSD-3-Clause](https://opensource.org/licenses/BSD-3-Clause)
+| BSP Component mx66uw1g45g    | STMicroelectronics                    | [BSD-3-Clause](https://opensource.org/licenses/BSD-3-Clause)
+| BSP Component rk050hr18      | STMicroelectronics                    | [BSD-3-Clause](https://opensource.org/licenses/BSD-3-Clause)
+| Camera driver IMX335         | STMicroelectronics                    | [BSD-3-Clause](https://opensource.org/licenses/BSD-3-Clause)
+| Camera driver VD55G1         | STMicroelectronics                    | [BSD-3-Clause](https://opensource.org/licenses/BSD-3-Clause)
+| Camera driver VD6G           | STMicroelectronics                    | [BSD-3-Clause](https://opensource.org/licenses/BSD-3-Clause)
+| STM32 Camera Middleware      | STMicroelectronics                    | [SLA0044](https://www.st.com/SLA0044)
+| STM32 USB Device Library     | STMicroelectronics                    | [SLA0044](https://www.st.com/SLA0044)
+| STM32 ISP Library            | STMicroelectronics, LACROIX - Impulse | [SLA0044](https://www.st.com/SLA0044)
+| ISP IQTune application       | STMicroelectronics                    | [SLA0044](https://www.st.com/SLA0044)

Projects/DCMIPP_ISP/ISP_IQTune_App/LICENSE.md

@@ -0,0 +1,85 @@
+This software component is provided to you as part of a software package and
+applicable license terms are in the Package_license file. If you received this
+software component outside of a package or without applicable license terms,
+the terms of the SLA0044 license shall apply and are fully reproduced below:
+
+SLA0044 Rev5/February 2018
+
+Software license agreement
+
+ULTIMATE LIBERTY SOFTWARE LICENSE AGREEMENT
+
+BY INSTALLING, COPYING, DOWNLOADING, ACCESSING OR OTHERWISE USING THIS SOFTWARE
+OR ANY PART THEREOF (AND THE RELATED DOCUMENTATION) FROM STMICROELECTRONICS
+INTERNATIONAL N.V, SWISS BRANCH AND/OR ITS AFFILIATED COMPANIES
+(STMICROELECTRONICS), THE RECIPIENT, ON BEHALF OF HIMSELF OR HERSELF, OR ON
+BEHALF OF ANY ENTITY BY WHICH SUCH RECIPIENT IS EMPLOYED AND/OR ENGAGED AGREES
+TO BE BOUND BY THIS SOFTWARE LICENSE AGREEMENT.
+
+Under STMicroelectronics’ intellectual property rights, the redistribution,
+reproduction and use in source and binary forms of the software or any part
+thereof, with or without modification, are permitted provided that the following
+conditions are met:
+
+1. Redistribution of source code (modified or not) must retain any copyright
+notice, this list of conditions and the disclaimer set forth below as items 10
+and 11.
+
+2. Redistributions in binary form, except as embedded into microcontroller or
+microprocessor device manufactured by or for STMicroelectronics or a software
+update for such device, must reproduce any copyright notice provided with the
+binary code, this list of conditions, and the disclaimer set forth below as
+items 10 and 11, in documentation and/or other materials provided with the
+distribution.
+
+3. Neither the name of STMicroelectronics nor the names of other contributors to
+this software may be used to endorse or promote products derived from this
+software or part thereof without specific written permission.
+
+4. This software or any part thereof, including modifications and/or derivative
+works of this software, must be used and execute solely and exclusively on or in
+combination with a microcontroller or microprocessor device manufactured by or
+for STMicroelectronics.
+
+5. No use, reproduction or redistribution of this software partially or totally
+may be done in any manner that would subject this software to any Open Source
+Terms. “Open Source Terms” shall mean any open source license which requires as
+part of distribution of software that the source code of such software is
+distributed therewith or otherwise made available, or open source license that
+substantially complies with the Open Source definition specified at
+www.opensource.org and any other comparable open source license such as for
+example GNU General Public License (GPL), Eclipse Public License (EPL), Apache
+Software License, BSD license or MIT license.
+
+6. STMicroelectronics has no obligation to provide any maintenance, support or
+updates for the software.
+
+7. The software is and will remain the exclusive property of STMicroelectronics
+and its licensors. The recipient will not take any action that jeopardizes
+STMicroelectronics and its licensors' proprietary rights or acquire any rights
+in the software, except the limited rights specified hereunder.
+
+8. The recipient shall comply with all applicable laws and regulations affecting
+the use of the software or any part thereof including any applicable export
+control law or regulation.
+
+9. Redistribution and use of this software or any part thereof other than as
+permitted under this license is void and will automatically terminate your
+rights under this license.
+
+10. THIS SOFTWARE IS PROVIDED BY STMICROELECTRONICS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS, IMPLIED OR STATUTORY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NON-INFRINGEMENT OF THIRD PARTY INTELLECTUAL PROPERTY RIGHTS, WHICH ARE
+DISCLAIMED TO THE FULLEST EXTENT PERMITTED BY LAW. IN NO EVENT SHALL
+STMICROELECTRONICS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
+PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
+OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+11. EXCEPT AS EXPRESSLY PERMITTED HEREUNDER, NO LICENSE OR OTHER RIGHTS, WHETHER
+EXPRESS OR IMPLIED, ARE GRANTED UNDER ANY PATENT OR OTHER INTELLECTUAL PROPERTY
+RIGHTS OF STMICROELECTRONICS OR ANY THIRD PARTY.

Projects/DCMIPP_ISP/ISP_IQTune_App/README.md

@@ -0,0 +1,33 @@
+v1.0.0
+
+# ISP IQTune App
+
+This application is running on the target and allow interaction between
+the STM32 ISP IQTune software (executed on the host) and the target to
+control and tune any ISP parameters.
+
+When the application is launched, you can connect your host computer to
+the board USB1 (CN18) connector unsing an USB-C cable.
+Then you must execute the STM32 ISP IQTune desktop application software
+on you host computer. The main page of the software lists the available
+com port. You just need to select the one suitable for your target and you
+can start controlling ISP parameters.
+
+# supported camera sensors
+
+The software is natively compatible with the MB1854B IMX335 and STEVAL-66GYMAI
+VD66GY camera modules. Simply change the camera module and restart the software.
+No software reconfiguration is needed.
+
+Note:<br>
+ - For customer camera module, the sensor driver must be added in the Camera
+ Middleware and a first tuning must be performed with the STM32 ISP IQTune
+ desktop application to generate the final isp_param_conf.h that can be updated.
+
+# ISP siple preview application
+
+To execute the simple preview application, remove the ISP_MW_TUNING_TOOL_SUPPORT
+compilation flag from the project configuration and rebuild the software.
+
+# Documentation
+[STM32 ISP IQTune: application for sensor image quality tuning](https://wiki.st.com/stm32mcu/wiki/ISP:STM32_ISP_IQTune:_application_for_sensor_image_quality_tuning)

Projects/DCMIPP_ISP/ISP_IQTune_App/STM32N6570-DK/Inc/aps256xx_conf.h

@@ -0,0 +1,47 @@
+ /**
+ ******************************************************************************
+ * @file    aps256xx_conf.h
+ * @author  GPM Application Team
+ *
+ ******************************************************************************
+ * @attention
+ *
+ * Copyright (c) 2023 STMicroelectronics.
+ * All rights reserved.
+ *
+ * This software is licensed under terms that can be found in the LICENSE file
+ * in the root directory of this software component.
+ * If no LICENSE file comes with this software, it is provided AS-IS.
+ *
+ ******************************************************************************
+ */
+
+/* Define to prevent recursive inclusion -------------------------------------*/
+#ifndef APS256XX_CONF_H
+#define APS256XX_CONF_H
+
+#ifdef __cplusplus
+extern "C" {
+#endif
+
+/* Includes ------------------------------------------------------------------*/
+#include "stm32n6xx_hal.h"
+
+/** @addtogroup BSP
+  * @{
+  */
+#define CONF_HSPI_DS   APS256XX_MR0_DS_HALF
+#define CONF_HSPI_PASR APS256XX_MR4_PASR_FULL
+#define CONF_HSPI_RF   APS256XX_MR4_RF_4X
+
+#define DEFAULT_READ_LATENCY_CODE  APS256XX_READ_LATENCY_5
+#define DEFAULT_WRITE_LATENCY_CODE APS256XX_WRITE_LATENCY_5
+/**
+  * @}
+  */
+
+#ifdef __cplusplus
+}
+#endif
+
+#endif /* APS256XX_CONF_H */