2015-10-23 01:06 AM
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 undefinedif (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 MCUdo not have
SPI3?Can
somewhere
report
found
bugs in software
pack ?
Second question. STM32CubeMX generate project for MDK-ARM v5 , Firmware Package v1.2 include own HAL driven own support for FreeRTOS, Software packt v2.0.0 for MDK-ARM supportanother owner
HAL driver, support fro RTX .It is
written
somewhere
how
these things
integrated
and
used in the
same project?
2015-11-18 05:55 AM
Hi Charles,
Thank you for your feedback. The issue has been reported internally.-Syrine-2015-11-25 10:03 AM
Dear user,
On smaller packages some peripherals are not available. It is the case here with SPI3. Regarding the project generation flow, you use STM32CubeMX to select your MCU, perform your configuration (including the toolchain you want to generate your project for). STM32CubeMX will automatically propose the download of the necessary STM32Cube Libraries. Within MDK-ARM IDE, you may have to install the device pack support the MCU you selected. For now, STM32Cube supports only freeRTOS so for RTX you will have to manually update your project within the IDE itself. Best regards