I would like to upload a project built with cmake gui in the Window10 to mcu board based on stm32f427II chip. When I build cmake, configure is configured as VS2017, and the result is as shown below. However, to upload to the board, I think I need to ...
Hi, I have a strange behavior with the RTC alarm only with some MCU. In my project use the STM32L476, when I set the alarm the MCU wake up without problem, but this work fine only with some board. On the other boards with the same MCU and the same FW...
I'm trying to use interrupts for SPI, but am a little lost. I see the Transmit_IT function in the HAL library, but I'm not certain how to use it in a non-blocking state. Is there an example on how to use it?
Posted on January 09, 2016 at 20:34Hello.I recently started testing the communication over I2C on a NUCLEO-L476RG board using the HAL API.Looking through the reference manual (http://www.st.com/st-web-ui/static/active/en/resource/technical/document/...
I am using the QSPI on my nucleo STM32F767zi board to access a WINBOND FLASH chip. I am using cubeMX 2.61 with IAR compiler 7.80. I can access the FLASH chip using HAL_QSPI_COmmand(). I appear to get dat when I issue a command to read the chip and...
Iam trying to Flash an LL_Example (GPIO) onto the Nucleo-G071RB board. i Get the following message;Error: Flash Download failed - "Cortex-M0+"The build goes ok though. I did update the DFP for STM32G0. Any suggestion would be helpful...
I am running out of SRAM on a project with an F407 and an investigating using an F427. My basic question is does anyone know of the issues with doing this? I have already read through the migration document (AN3364) and am continuing to investigate.I...
To begin, I have a question regarding the CanTxMsgTypeDef and the CanRxMsgTypeDef configurations (listed here.)My question is, how to properly initialize the parameters :uint8_t Data[8]; of CanTxMsgTypeDef and uint8_t Data[8]; CanRxMsgTypeDefI can lo...
We're seeing what looks like an extra or spurious read from the QSPI block on our STM32F765BI. As yet, we're not able to pinpoint the cause and could use some ideas of where else to look. Sorry that this gets a bit long. Background:We're using the...
