We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
STM32F1 v2.0.0 SW pack for MDK-ARM, STM32CubeMX? I installed Software Pck for STM32F1 v2.0.0 to my MDK-ARM v5.16a, create project for STM32F103RB, add support for device SPI, in RTE_DEvice.h select SPI1, but when compule have eeror C:\Keil\ARM\PACK\Keil\STM32F1xx_DFP\2.0.0\RTE_Driver\SPI_STM32F10x.c(316): error: #20:
identifier "RCC_APB1RSTR_SPI3RST" is undefined if (spi == SPI1) { RCC->APB2RSTR |= RCC_APB2RSTR_SPI1RST; } else if (spi == SPI2) { RCC->APB1RSTR |= RCC_APB1RSTR_SPI2RST; } else if (spi == SPI3) { RCC->APB1RSTR |= RCC_APB1RSTR_SPI3RST; }
a software developer at ST unaware that low and medium density STM32F1 MCU do not have SPI3? Can somewhere report found bugs in software pack ?
The STM32F1 Software Pack is based on the ST Peripheral Library and not on STM32Cube. The reason is that STM32Cube consumes more resources than Peripheral Library.
Also we have many customers that have already started with Peripheral Library, and the current pack is less disruptive.
We are waiting for an optimized STM32Cube before we retarget the CMSIS-Driver.
We have solved the issue you have reported with the RTE_Device.h on STM32F103RB. The new pack will be released soon (in about 2 weeks).
For a pre-release, please contact our support (support.intl@keil.com) with reference to this thread.
Thank you. It was primarily about reporting bugs, for myself, I have it solved quite easily. Anyway. It would not be the case right here on the forum to introduce a section for reporting bugs, suggestions for improvement etc.