hal_stm32/scripts
Gerard Marull-Paretas 79a847bf2b scripts: tests: update genpinctrl tests
Update genpinctrl unit tests to match latest changes.

Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
2020-12-03 08:39:09 -06:00
..
genllheaders scripts: genllheaders: add script to generate common LL headers 2020-11-05 22:00:15 -06:00
genpinctrl scripts: genpinctrl: use STM32 open pin data 2020-12-03 08:39:09 -06:00
tests scripts: tests: update genpinctrl tests 2020-12-03 08:39:09 -06:00
.coveragerc scripts: tests: genpinctrl: add initial tests 2020-09-29 09:03:24 -05:00
.flake8 scripts: add Python development tools 2020-09-29 09:03:24 -05:00
README.rst scripts: fully redesign STM32Cube update scripts 2020-11-05 22:06:47 -06:00
requirements-dev.txt scripts: add Python development tools 2020-09-29 09:03:24 -05:00
requirements-test.txt scripts: tests: update genpinctrl tests 2020-12-03 08:39:09 -06:00
requirements.txt scripts: genpinctrl: script for DT pinctrl generation 2020-09-29 09:03:24 -05:00
serie_update.py scripts: serie_update.py: add systematic compilation of '_hal_rcc_ex.c' 2020-11-05 22:06:47 -06:00
update_stm32_package.py scripts: serie_update.py: add systematic compilation of '_hal_rcc_ex.c' 2020-11-05 22:06:47 -06:00

README.rst

STM32Cube HAL packages updater.
###############################

Introduction:

This module provides scripts to update the STM32Cube for Zephyr.
Follow below steps to update the STM32Cube HAL from the latest
version found in STM32CubeXX repositories.

Step 1: Modify the code
***********************

In order to update all the STM32CubeXX versions at once, run::

    $ python3 ./update_stm32_package.py

Alternatively, in order to update STM32CubeXX versions one by one, run for example::

    $ python3 ./update_stm32_package.py -s stm32f1

Check STM32CubeXX changes
=========================

Check that all existing change to modules are correctly reported
in the new hal_stm32 version

Update each modified stm32cube/stm32XXxx/README in the last section,

Remove the following line::
	--> please check that the following list is still valid:


Step 2: Open a pull requests
****************************

hal_stm32 PR
============
Open a single pull request with 1 commit per stm32 familly (stm32xx)
in repo https://github.com/zephyrproject-rtos/hal_stm32


Modify the west.yml
===================
In order to benefit from this PR in zephyr, modify zephyrproject/zephyr/west.yml
so that hal_stm32 points to above pull request. Example::

	    - name: hal_stm32
	      revision: pull/60/head
	      path: modules/hal/stm32


Open a 2nd pull request with west.yml in repo
https://github.com/zephyrproject-rtos/zephyr


Step 3: After Merge
*******************

re-Modify the west.yml
======================

Once the hal_stm32 pull request is merged (see step 2), in the zephyrproject-rtos/hal_stm32

then change again the zephyrproject-rtos/zephyr/west.yml

to reflect the actual zephyrproject-rtos/hal_stm32 SHA1, example::

	    - name: hal_stm32
	      revision: a813cd83b0cfbaaa625f4941d04baa3f93c37476
	      path: modules/hal/stm32

The zephyrproject-rtos/zephyr pull request (see 2) must be updated consequently.

COMMENT:

- "set the SHA1 after merge of STM32Cube versions (modules/hal/stm32)"

See Example : https://github.com/zephyrproject-rtos/zephyr/pull/23259


clean
=====
once all is correct, clean .rej and .log files, with :

::

 $ git clean -fdx