stmicroelectronics / cmsis_device_f1 Goto Github PK

I'm building a linux toolchain for STM32, but I found some file's license does not permitted distribution it, they are in directory Source/Templates/gcc/linker

These files with this license:

(c)Copyright Ac6.
You may use this file as-is or modify it according to the needs of your
project. Distribution of this file (unmodified or modified) is not
permitted. Ac6 permit registered System Workbench for MCU users the
rights to distribute the assembled, compiled & linked contents of this
file as part of an application binary file, provided that it is built
using the System Workbench for MCU toolchain.

Can you provide a free/open-source license or replace it to free/open-source licensed linker script.

Could not set proper VECT_TAB_OFFSET in a case with a bootloader.

Compiling .pio/build/genericSTM32F103C8/src/display.o
/home/marat/.platformio/packages/framework-cmsis-stm32f1/Source/Templates/system_stm32f1xx.c:95:0: warning: "VECT_TAB_OFFSET" redefined
 #define VECT_TAB_OFFSET  0x00000000U /*!< Vector Table base offset field.

<command-line>:0:0: note: this is the location of the previous definition

A possible solution in the attachment:

fix-flash-offset.zip

Describe the set-up

• Any F1-based board, e.g. Nucleo-F103RB
• I'm using PlatformIO (https://platformio.org), which uses arm-eabi-none-gcc and an unmodified CMSIS install.

Describe the bug
The default clock speed for all F1xx chips is wrong. It is set to 16000000, but should be 8000000, see
https://github.com/STMicroelectronics/cmsis_device_f1/blob/master/Source/Templates/system_stm32f1xx.c#L141

How To Reproduce

1. Any CMSIS-based build which does not reconfigure the clock tree will have the wrong SystemCoreClock value.
   This will cause baudrate calculations to be wrong, for example.

2. The modules that you suspect to be the cause of the problem (Driver, BSP, MW ...)
   Source/Templates/system_stm32f1xx.c, line 141

3. The use case that generates the problem
   See 1.

4. How we can reproduce the problem
   See 1.

Additional context
This bug was first reported here: platformio/platform-ststm32#698

Screenshots
N/A.

A commit named v4.3.2 was push but no proper release was made, could someone make a formal release for 4.3.2

Caution
The Issues are strictly limited for the reporting of problem encountered with the software provided in this project.
For any other problem related to the STM32 product, the performance, the hardware characteristics and boards, the tools the environment in general, please post a topic in the ST Community/STM32 MCUs forum.

Describe the set-up

• The board (either ST RPN reference or your custom board)
• IDE or at least the compiler and its version

Describe the bug
A clear and concise description of what the bug is.

How To Reproduce

1. Indicate the global behavior of your application project

2. The modules that you suspect to be the cause of the problem (Driver, BSP, MW ...)

3. The use case that generates the problem

4. How we can reproduce the problem

Additional context
If you have a first analysis or patch correction, thank you to share your proposal.

Screenshots
If applicable, add screenshots to help explain your problem.