Posted on December 27, 2014 at 12:10CubeMX (CubeMX v4.3.1, STM32Cube V1.0) generated pinout for STM32F429 LTDC is/** LTDC GPIO Configuration PE4 ------> LTDC_B0 PE5 ------> LTDC_G0 PE6 ------> LTDC_G1 PI9 ------>...
Posted on January 13, 2015 at 11:02-I have observed PA9(USART1_TX) & PA10(USART1_RX) pin failure in STM32F107RBT, this pins are 5V Tolerant-FT- STM32 supply voltage is 3.3V- it is interfaced to another micro controller which runs on 5V.
Posted on May 29, 2013 at 16:34Hi, I have an STM32F407IE on a custom board and I am programming/debugging with an Olimex ARM-USB-TINY-H using OpenOCD. I have come across this error with two separate microcontrollers now. It seems as though the mic...
Posted on January 09, 2015 at 15:40Can anyone tell me when the STM32CubeMX configuration tool will support the UFBGA169 package for STM32F429?
Posted on October 28, 2014 at 20:10Is it possible to receive variable length messages in DMA mode with the STM32Cube HAL libraries? It seems like this should be possible at the hardware level by first looking for the RXNE interrupt, and then the Idl...
Posted on January 12, 2015 at 18:29Hello, I would like generate two different signal with the channel 1 and 2 of DAC. I've used two different timer (TIM6 and TIM2) and one DMA address (DAC_DHR12RD_Address 0x40007420). I can generate the signals s...
Posted on May 22, 2014 at 01:06Hi All,We are developing a product that we'd like to connect to a PC and an Android tablet. Using the ST USB-FS-Device-Lib as a guide we created a driver for the STM32L1152D eval board.It works perfectly on a PC. Enu...
Posted on January 09, 2015 at 05:55The original post was too long to process during our migration. Please click on the attachment to read the original post.
Posted on September 14, 2013 at 02:04Hello, I tried to read two analog inputs from PA3(ADC1_IN3) and PA5(ADC1_IN5). I expected tmpADC[0] has the input data of PA3 and tmpADC[1] has the input data of PA5. However, both tmpADC[0] and tmpADC[1] always ...
Posted on January 12, 2015 at 17:35The problem is this: When reading FSMC value always returns the previous value written in the FSMC. And you need a color value of the pixel SSD1963 ... Actually, what's the catch ??? reads as: #define LCD_REG ...
