Solved

I want to understand the current sensing that is done in B-G431B-ESC1 kit. I do not understand the purpose of IN_VOPAMP3 connected to ADC2The opamp3 can be connected to ADC1 and ADC2 as shown in the figure? The software configuration of opamp3hopamp3.Init.InternalOutput = ENABLE;whereas for opamp1 and 2 is hopamp1.Init.InternalOutput = DISABLE;and the code for ADC2 issConfigInjected.InjectedChannel = ADC_CHANNEL_3;sConfigInjected.InjectedRank = ADC_INJECTED_RANK_1;sConfigInjected.InjectedChannel = ADC_CHANNEL_VOPAMP3_ADC2;sConfigInjected.InjectedRank = ADC_INJECTED_RANK_2;Please advise on the above configuration.

I am getting the fault of MC_DURATION after running for few seconds in my customized board but software is same as B-G431B-ESC1. I am not sure why this error is happening, any advise? I have changed the REGULATION_EXECUTION_RATE to 2 from 1 assuming the FOC execution rate is fast so that the FOC is executed after 2 PWM cycles.

Hi,I am using the STM32H747I-DISCO and wanting to write to the QSPI using Filex. I tried using the example FX_Dual_Instance, but could not get this working. Since then I have built a project step by step using the CubeMx initialization tool. Both times my code stops (gets caught in a loop) at fx_media_format. When drilled down with the debugger I found it was waiting for a thread to execute?Any ideas what I'm missing. I've attached my project below.Couple of things to note:Hardware works and has successfully been manipulated using BSP package just not through filex commandsstm32cubeIDE version 1.12.0Thanks,Hannah

I'm using stm32f103 in my hardware, I didn't put pull-up resistor to USB _ D+ pin.The device doesnot appear on PC.Is there any way to make it work without Hardware changes?

I've created list and create callback to this function :And here u see marked line which changes text color but it's not working

I am using a USB CDC device on an STM32H7A3 CPU. Most of the code is generated by the Cube IDE, and I have added my own callbacks. It works fine when plugged into a native Windows host or a native Linux host. However, it has an issue when running on a Linux guest in a Virtualbox VM (Windows host).My application sends some output (a "welcome" message) immediately after start-up. My code calls CDC_Transmit_HS(), which succeeds, and then waits for the CDC_TransmitCplt_HS() callback to occur before sending more. That works fine; as soon as I connect to the device using, e.g., Putty, that callback occurs and I can proceed.However, when I connect using minicom or screen from within a Linux VM, this callback never occurs, and my application hangs. Some USB traffic is working, though, because I can see that there is still more data coming in using the CDC_Receive_HS() function.I wonder, is there some flush or reset occuring when I connect from the Linux VM? Do I have to implement an additional

We are planning to use STM32U599ZI platform for our new project. Could you please help us with the reference design and hardware related documents? ​Thanks in advance for your help.​Contact:Email: santhosh.p@optmsol.com

I use ADC2 and ADC3 (with HAL_ADC_Start_DMA) with no problem, just having problem with ADC1. I'm using FREE-RTOS. STM32CUBEIDE.

HI,I'm using an STM32F4 device and CubeIDE SW to interface with a mouse as a host with an HID. I use the USBH_HID_EventCallback function to trigger mouse readings.Can I change the mouse's polling rate so that it will be triggering faster?The current polling rate (per USBH_HID_GetPollInterval function) is 10ms. In the mouse's data sheet, it states it can reach 1kHz polling rate.Thanks

In the errata sheet,it is mentioned that low drive mode and medium low drive are not working.. but I checked and they work fine...is there any correction in the errata sheet...?..Can I go with low drive mode for LSE (NUCLEO-U575ZQ)???

Looking at the website it cost a lot of money , approx $5k .https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/qualification-listing-fees/Scott

Hello we have integrated ST NFC RFAL stack with RL78 IC and currently we are able to detect NFC card within 1-2seconds. Is there a way to reduce this time less than 1 second to detect NFC card ?

Hi, We are CYIENT technologies focused on Engineering, manufacturing, Data Analytics, Operational and Networking.we are using STM32 controller and other ST components in one of our projects. And our Product will be active 8 years in market. I would like to know, Obsolesce status of this below mention Components.STM32U585AII6QUSTM32U5A5AJUSBLC6-2SC6ESDALC6V1-1U2Thank you!

Please help with eval board part number for STM32F207IEH6

How to download program to MCU through ISP? LPUART1 or USART2?

..

..

I'm using BL-475E-IOTA2 board (STM32L475) which comes with MX25R6435F Flash chip. I'm trying to using Quad SPI to write and read to/from the flash chip. With free running the code(release mode):If I don't use DMA when writing to the flash chip, it can read/write with free running (running in release mode) fine. If I use DMA, it always fails when I send a write enable command to the flash chip:in stm32l4xx_hal_qspi.c, HAL_QSPI_Command() returns HAL_BUSY.With single stepping through the code, with DMA or no DMA, it writes and reads the flash chip fine.I tried QSPI clock prescaler of 1,2,3 but it didn't help. Sys clk and HCLK (to DMA) is 80MHzI also tried adding a 1s delay before and after writing the write enable command to the flash, but it still failed the same way.What could cause this problem?

I am using the software of b-g431b-esc1 and the driver used in the board as per schematics is in my board the micro is RB series but the problem is with the Mosfet driver which has an active low signal, IR2108What changes do i need to make in the software to make it work? Will it be huge or minor changes? Please advise.

I have a board that is running well. There are about 50+ PCBs in production operating fine. The firmware is pretty complex, but the hardware relatively simple, just some SPI devices and some PWM outputs.I revved the board, and the new board doesn't work at all. Well, it works enough to execute some code, but not much. So to debug, I started with a blinky program:int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init();   while (1) { HAL_GPIO_TogglePin(FAULT_GPIO_Port, FAULT_Pin); HAL_Delay(1000); } }If I configure the RCC to use the HSI, the program gets as far as `HAL_Delay(1000)` at which point it chokes on `HAL_GetTick()`.If I configure the RCC to use the HSE (a crystal is present), the program only gets as far as `SystemClock_Config()`, where it again chokes on `HAL_GetTick()` or sometimes `HAL_RCC_OscConfig()`.By "choke" I mean it throws a HardFault. Though for a reason I can't understand, it won't execute my handler.So, the code runs ok using the HSI at 16

hello,For me stm32f746-disco has two versions.1) The first is the green PCB. The following label is attached. MBI1191 B-03 / 2154300550 -> LCD screen normal operation / LCD Touc normal recognition2) The second one is the blue PCB. The following label is attached. MB1191-F746-C01 / C220200062​ -> LCD screen normal operation / LCD Touc normal operation not recognizedThe purchase is Mouser, but first I bought the normally working red PCB and after 1 year I bought the BLUE PCB.https://www.mouser.kr/ProductDetail/STMicroelectronics/STM32F746G-DISCO?qs=KuGPmAKtFKV4xEByQ7IKqA%3D%3DI want to know why the touch recognition doesn't work normally on the newly purchased green PCB.

Hey,I was able to successfully flash the Starter Package following this article and after building the OpenSTLinux distribution following this, I'm having trouble with flashing it. After completeing the build process, inside the flashlayout_st-image-weston, there are 3 folders optee, extensible and deleteall. I was looking for trusted folder like in starter package but it is not available. Then I tried to follow article found here with cube programmer interface and through terminal with FlashLayout_sdcard_stm32mp157f-dk2-optee.tsv but i'm getting following error.Error: failed to download Segment[0]   Error: failed to download the File   Error: Download partition 0x05 failed   Error: TSV flashing service failedAfter that I tried to flash with FlashLayout_sdcard_stm32mp157c-dk2-optee.tsv in Starter Package but it also showed the same issue. I have attached the cube programmer terminal output. Apreciate if anyone can help me with this.Thanks.

I am trying to incorporate the X-Cube-EEPROM package into an existing STM32WB55 Nucleo design that I have. In the process one of the compile errors refers to an RCC bit:​'RCC_CR_HSEBYP' undeclared (first use in this function); did you mean 'RCC_BDCR_LSEBYP'?​Your stm32wbxx.h file within the CMSIS/Device/ST/STM32WBxx/Include folder calls out the RCC_CR_HSEBYP as bit 18.​This bit doesn't even exist in the manual....What kind of code is this???This is VERY subpar.

I am trying to connect LCD (SPI interface) to my custom stm32f030c8 board, PB13 -> SCK, PB15 -> MOSI (Transmitt only mode).I created a test project with cube configurator (attached a screenshot).I did not change anything in the generated code, just added sending test:/* Initialize all configured peripherals */ MX_GPIO_Init(); MX_ADC_Init(); MX_SPI2_Init(); MX_TIM1_Init(); MX_TIM14_Init(); MX_TIM16_Init(); MX_TIM17_Init(); MX_USART1_UART_Init(); /* USER CODE BEGIN 2 */   uint8_t testData[] = { 0x11, 0x22, 0x33, 0x44 }; HAL_SPI_Transmit(&hspi2, testData, 4, 5000); /* USER CODE END 2 */   /* Infinite loop */ /* USER CODE BEGIN WHILE */ while (1) { /* USER CODE END WHILE */   /* USER CODE BEGIN 3 */ }I uses ST-Link to debug. All initializations pass so as the transmit subroutine, but there are no any signals on MOSI and SCK appears (I use oscilloscope with sync by signal front). I tried to change pins mode to general outputs and to toggle output

Hello everybody:I’m facing the following problem. To boot the microcontroller right know I have pin PA14 – BOOT0 to GND through a 10K pull down resistor (This pin is also shared with SYS_SWCLK) and BOOT0, nBOOT_SEL bit to 0 -> Boot area main Flash memory.I want to achieve the same thing with nBOOT_SEL, nBOOT1, NBOOT0 bits. To do that, I connect the programmer and access the option bytes -> user configuration -> set the pins as shown in the image and apply.When I disconnect the programmer, power off then power on again the program doesn’t boot (now PA14 – BOOT0 is not connected with pull-down resistor). I am doing something wrong?Thanks in advance.