Solved

Hi !  I am very happy to start STM32F1 Series  for IOT projects. So i have experience of arduinoide software tool and STM32cube is new for me so which one will be best for smooth work ?

I have a monochrome display and use the framebuffer B/W with one bit per pixel. With the framebuffer and the TouchGFX Designer I can display text, but I have problems with small black and white images or e.g. a progress bar. Either only a black block or a black block with white highlights is displayed. But nothing usable. Has anyone had a similar problem and found a workaround?

I have tried every solution mentioned here. I have also contacted my friends and family members whom have tried to download this software and other libraries (CubeIDE, CubeMX, F1, F4, F7 and H7 Libraries). Same issues I need help urgently as I need to set software up as I have shifted to a new PC.    

Hi all,We are using an STM32H730IBK6Q.PA10 is not configured and STM32CubeMx generates code that initializes the pin as "Analog" as expected.Now if we enable USB (specifically, when setting `USBx->GCCFG |= USB_OTG_GCCFG_PWRDWN;`), that pin goes high, which is to me unexpected since AF10 (OTG_HS_ID) is not configured.Is there any way to tell the USB PHY not to attach a pull-up to that pin? It seems like it gets hijacked even if not configured. In the block diagram in the reference manual, that pin is mentioned, but I was under the assumption that if it is not configured as OTG_HS_ID in CubeMX, it would not be touched: As a workaround, I have configured it as GPIO output and set it to RESET, and that works, the pin stays low and USB communication is operational. Do you see any drawbacks with that? We operate as a USB device (not host) at all times.Thank you and best regards!

Hi, could I please get access to the 3D CAD Models for the LPS28DFW and VL53L4CD products? On both of their "CAD Resources" page you only offer the PCB Footprint and Symbol and not the 3D Model. I need to utilize the 3D model for designing a component that utilize both of these sensors. The datasheet dimensional information provided is not sufficient for this. Any help with this would be greatly appreciated. Thank you

Hi,I am getting the below warning when I compile my application. However, HAL_RTC_GetTime API expects the first argument of type pointer to a RTC_HandleTypeDef structure, thats what I provide, but I get this warning as highlighted below. 15:34:16 **** Incremental Build of configuration Debug for project RTC **** make -j8 all arm-none-eabi-gcc "../Core/Src/main.c" -mcpu=cortex-m4 -std=gnu11 -g3 -DDEBUG -DUSE_HAL_DRIVER -DSTM32F407xx -c -I../Core/Inc -I../Drivers/STM32F4xx_HAL_Driver/Inc -I../Drivers/STM32F4xx_HAL_Driver/Inc/Legacy -I../Drivers/CMSIS/Device/ST/STM32F4xx/Include -I../Drivers/CMSIS/Include -O0 -ffunction-sections -fdata-sections -Wall -fstack-usage -fcyclomatic-complexity -MMD -MP -MF"Core/Src/main.d" -MT"Core/Src/main.o" --specs=nano.specs -mfpu=fpv4-sp-d16 -mfloat-abi=hard -mthumb -o "Core/Src/main.o" ../Core/Src/main.c: In function 'HAL_RTC_AlarmAEventCallback': ../Core/Src/main.c:337:49: warning: passing argument 1 of 'HAL_RTC_GetTime' from incompatible pointer t

UM2884-Rev 3, chapter 5.5 Results interpretation, shows in table 4 (list of available target status) a short description of the target status 0 to 13 and 255. Question 1: Our application sometimes also shows status 14, which is not described there. What is its meaning? Question 2: Some of the short descriptions are self-explanatory, others are not clear. Is it possible to provide a more detailed description that explains the status in more detail, i.e. what it really means, under what conditions does it occur and what is recommended to avoid it?

HAL_ADC_Start_DMA() takes a pointer to a uint32_t buffer, but the cubeMX can configure the DMA for word, half_word or byte.So therefore you can only configure the DMA for word transfers?I was setting the cubeMX to half_word or uint16_t and using 12bit adc, but I noticed the compiler warning about HAL_ADC_Start_DMA() taking a uint32_t.It is simple for me just to use a uint32_t buffer, but am I missing something?

Hello everyone!I am making a project with STM32F072 MCU and I have 3 devices that need to be controlled via I2C: a DAC, an ADC and a current monitor that has an ADC integrated. I've made the connections and part choices so that I have 3 different 7-bit addresses for them: 1001001, 1000000 and 1100000.There is one question that I have: I don't understand from the datasheet if it supports 3 devices or just 2 on the same I2C1 Bus.... can someone clarify me if its possible, or I need the other I2C as well for 3rd device?Can someone clarify if I need to use the 2nd I2C for my 3rd device or not? Thanks

..

Hi thereI am using a B-G431B-ESC1 board with a BLDC motor with hall sensor.The project is generated MC Workbench and is working just fine.Now I need to know the number of revolutions that the motor have taken since it was started (for application purposes). Since the setup is with a hall sensor, this information must be available somewhere but I cannot find this information in the MC_Api. Any ways to obtain this information?

I use B-U585I-IOT02A to read after writing Flash Memory, 0xFF is read, but once I reset it, I can read the written value.Similarly, when I use it to read after erasing the Flash Memory, the value before erasing is read, but once I reset it, I can read 0xFF.In short, the correct value cannot be read unless reset once for both Write and Erase.Is there any processing that must be done after programming or erasing?

Our project is run on the STM32F411E-DISCO board running under Segger Embedded Studio.  All Timers TIM2/TIM5/TIM9/TIM10/TIM11 are being used.  Under a debug session everything runs correctly.  If we leave the board programmed with the debug code and power it up without the J-Link connection attached everything runs correctly.  However, if we run a release build then the 32-bit timers run correctly but the 16-bit timers do not.  From what we can see the 16-bit timers are running too fast as if the check we do for the rollover TIMx->SR & TIM_SR_UIF is always returning true.  We looked at the RCC register settings in a debug session and none of the RCC or APB1/2ENR registers appear to have any bits enabled that weren't set by our code. This issue was actually solved while this post was being written, so this is being posted anyway in case someone else runs into the same issue.  Our initialization code runs generically for all timers and

Hello everyone,I have the STEVAL WBC86TX and RLC38RX evalboard here and I am currently testing them with the STSW-WPStudio.In my application I want to implement an custom inband communication between RX <--> TX. It seems that there is the possibility to do that in the Software with the MSG RECV and MSG SEND registers. How can I do that there. When I am writing the data to the the memory in the software and reading the data on the other board, there does not receive any of them. Could you please explain me, how that works?Is there any documentation and application note, where I can find more informations about that and how the different registers should be adressed?Thanks

This is how i the GPIO for the timer:// Hallsensors (Tim1 capture) my_GPIO_InitStruct.Pin = GPIO_PIN_0 | GPIO_PIN_1 | GPIO_PIN_2; my_GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; my_GPIO_InitStruct.Pull = GPIO_PULLUP; HAL_GPIO_Init(GPIOC, &my_GPIO_InitStruct); GPIOC->AFR[0] |= ( GPIO_AFRL_AFSEL0_1 | // AF2 (all) GPIO_AFRL_AFSEL1_1 | GPIO_AFRL_AFSEL2_1);This is the timer config:void initTim1AndTim8Hall(){ __disable_irq(); __HAL_RCC_TIM1_CLK_ENABLE(); SET_BIT( TIM1->CR2, TIM_CR2_TI1S); // config all 3 hall signals (PC0-2) via XOR to timer 1 WRITE_REG(TIM1->ARR, 0xFFFF); // Max value (is reset by input signal) WRITE_REG(TIM1->PSC, TIM1_PRESC - 1); // Mind the 1 that is added in the uC ! WRITE_REG(TIM1->CCR2, 20); // Delay value for PWM change trigger WRITE_REG(TIM1->CCMR1, 0); // set zero SET_BIT( TIM1->CCMR1, TIM_CCMR1_CC1S_0); // channel is configured as input, tim_ic1 is mapped on tim_ti1 SET_BIT( TIM1->CCMR1, TIM_CCMR1_OC2M_

Hi, MURALI SELVAM from India. I using "STM32H743VIT6" I want know heart beat signal hardware configuration, in the project I using three MCU for safety purpose, in case 1st MCU will get failure, 2nd one is take control, 2nd one will get  failure, 3rd one will take control for this I have taking "heart beat signal processing" but I don't know how to do hardware configuration and what kind of communication interface between three processor suitable for this like SPI, I2C. Anyone who know about it kindly let me know.

Hi there,I want to try touchGFX on my homemade board with the STM32F429BIT6 and a band flash chip H27U1G8F2B.I initial the FMC NAND flash by following the code:and test the NAND flash as below:The LOG output is like this(the data value sometimes change, but always data[0] err):By the LOG, the operation of the NAND flash is successful, but the result is wrong!Am I making a mistake?Thanks for your help in advance! 

Hi there,I am trying a touchGFX demo on my homemade board with STM32H743IIT6.Everything is OK except the HAL_Delay() is not working after the MX_TouchGFX_Init().The following code works well: ... MX_GPIO_Init(); MX_FMC_Init(); MX_CRC_Init(); MX_DMA2D_Init(); MX_LTDC_Init(); HAL_Delay(1); MX_TouchGFX_Init(); MX_TouchGFX_PreOSInit(); osKernelInitialize(); ...However, the change below will stop the program at HAL_Delay(1): ... MX_GPIO_Init(); MX_FMC_Init(); MX_CRC_Init(); MX_DMA2D_Init(); MX_LTDC_Init(); MX_TouchGFX_Init(); HAL_Delay(1); MX_TouchGFX_PreOSInit(); osKernelInitialize(); ... I saw some talking(see details ) about this issue, but it does not seem to have an official solution.How is this issue going now?(I need the HAL_Delay() to initial my touch sensor after peripherals initialization)

Most I2C EEPROM (eg M24M01E) need some time after a write command to transfer the written data into the internal EEPROM. During that time (eg max 3.5 ms) the device does not respond to I2C.My question is about the timeOut parameter in the HAL_I2C_Mem_Write (and other HAL_I2C_Mem_xxxx) :Is this timeOut intended or suited to deal with this unavailability of the device after a write operation ? If I want to do 2 write operations (and I do not insert a delay between both HAL calls myself), will the second call automatically retry until timeOut, and so if I set timeOut to 4 ms, I could in the application simply ignore the needed delay after a write operation. 

 I was wondering what the maximum current limit is for the 5V output pin. I looked at the datasheets but couldn't figure it out.

Hi,I'm doing a university project on top down people counting and the existing People Counting program in the FP-AI-VISION1 package seems perfect. I'm new to microcontrollers and AI, generally speaking, but I just wanted to know if it was possible to retrain the existing program with a data set I created? Any help or tips would be appreciated. Thanks,Darrin

For these EEPROMs there is a WP pin, which must be (active) low to enable write operations. I am driving this pin from an MCU, (ie. it is not tied to GND).Also these EEPROMs need some time after a write command to effectively write the data into the EEPROM, eg. 3.5 ms max.Now my question is : does the WP need to stay active low during those 3.5 ms after the write command ? 

Hello everyone,  I am using SPI to communicate two Nucleo Boards (a NUCLEO-L432KC and a NUCLEO-F411RE one), and i found out a weird behavior. The idea was to perform a transaction Master -> Slave in order to select a "register" to read. Once the Slave has received the "register", the Master request the information and the Slave shall send the information to the master. In order to perform this, interruptios were used in the slave side. The "register" logic is still not present, but the concept is the aforementioned one.The Master code is as follows (only SPI-Related lines): HAL_SPI_Transmit(&hspi2, txbuff, 2, 1000); HAL_Delay(1); /* DELAY BETWEEN TRANSACTIONS */ HAL_SPI_Receive(&hspi2, rxbuff, 12, 1000); And for the slave, following code is used: /* USER CODE BEGIN 2 */ HAL_SPI_Receive_IT(&hspi1, buffreg, BUFFREG); /* USER CODE END 2 */ SPI Interruption handlers are as follows: void HAL_SPI_RxCpltCallback(SPI_HandleTypeDef *hspi) {

I am new to cubeide can someone let me know how to add new board library to cube ide . Currently i am getting Stm32H753 but not Stm32H750