Changelog
Version | Date | Remark |
|---|---|---|
1.5 | 28.02.2021 | reworked uGOAL package platform and parameter settings |
1.4 | 17.12.2021 | update with uGOAL release 2.1.1, change package original source folder name from Middleware to Middlewares |
1.3 | 19.07.2021 | update package sources GOAL and uGOAL with release 2.1.0 |
1.2 | 01.07.2021 | add description for uGOAL and differences to the classic GOAL framework |
1.1 | 15.06.2021 | Update SoM sources, minor changes in package user interface, add support for IAR and Keil IDE |
1.0 | 15.04.2021 | Initial version |
...
Please select the core and an appl / example that is of interest
additional information to the examples iRJ45 / SoM - GOAL examples
The package is now integrated and available under “Software packs”. The package can be activated / deactivated (Mode-> checkmark) and the parameters can be edited, if necessary, via the STMCubeMX surface
...
The Tab “Parameter Settings” show the most used configuration of the middleware: The Heap is activated (value "1") with the corresponding buffer size. The special feature for debugging the application core is disabled (value "0")
the Tab “Platform Settings” shows the necessary existing and assigned interfaces for the operation of the package on an application core
...
The “Platform Settings” shown are already suitable for the STM32F429_Nucleo platform
The platform independent code of the middleware can be adapted to the special underlying STM32 platform via these settings
Now the source code can be generated via the code generator in the STMCube-IDE (menu “Project-> Generate Code”), then the code is now also generated from the SoM expansion package and “rolled out” in the project (here folder Middleware, SoM and additional the necessary HAL-Drivers)
...
The adaptation to the target board used, takes place in the STMCubeMX Configuration (*.ioc) generated by STM32CubeMX. For some targets that are already supported (e.g. STM32F429ZI_nucleo), these * .ioc files are already included in the SoM expansion package. These can serve as a template for new targets or for porting to your own hardware. In the source code of the GOAL/uGOAL software no adjustments must be made except in the STM32Cube project and the “Parameter “Platform Settings” from expansion package.
...
Label | Description | necessities | GPIO |
GOAL_TARGET_LED1 | User LED1 on target board | optional | PB0 |
GOAL_TARGET_LED2 | User LED2 on target board | optional | PB7 |
GOAL_TARGET_LED3 | User LED3 on target board | optional | PB14 |
GOAL_TARGET_EXT_INT | User button on target board | optional | PC13 |
GOAL_TARGET_SPI_CS | SPI chip selects, active low | mandatory | PD14 |
GOAL_TARGET_SOM_RESET | SoM external reset, active low | mandatory | PF13 |
Table 2: GPIO assign
...
Adaption in the
...
“Platform Settings” in the STMCubeMX surface
Adapt the mandatory “Parameter “Platform Settings” to the prepared HW interfaces, if necessary. The notation here is suitable for the STM32 HAL-Layer API.
...
Additional adaptions in the STMCube project
...