Solved

Hello, for the last couple of days I've been trying to set up my STM32F723ZET6 project as a USB HS CDC device with internal PHY.My code gets stuck in this loop do { count++; if (count > HAL_USB_TIMEOUT) { return HAL_TIMEOUT; } } while ((USBx->GRSTCTL & USB_OTG_GRSTCTL_CSRST) == USB_OTG_GRSTCTL_CSRST); inside the function .staticHAL_StatusTypeDefUSB_CoreReset(USB_OTG_GlobalTypeDef *USBx) in the file stm32f7xx_ll_usb.c I've been reading and it seems like a common issue. I've tried applying some solution that work for other people, although they were asking for other models of STM, Without success.For what I read it seems to be some kind of timing or clock problem. I have no experience with USB and I don't really know much about how CUBEMX implementation works.What I tried:- Adding a 50ms delay before this loop- Adding __HAL_RCC_SYSCFG_CLK_ENABLE(); to my HAL_MspInit function (Actually CUBEMX already did that)-Adding __HAL_RCC_USB_OTG_HS_CLK_ENABLE();&nbsp

Hello, I need help in integrating the encoder with spc58ee84e7 module using GTM TIM module.Can you provide a sample  code for the same. I have tried but unable to fetch the timer / counter values.

HiI am working on a project with an STM32H743 and a 32-bit SDRAMThe FMC signals are quite randomly scattered across the package and this makes layout quite convoluted and difficult. I'd like to swap byte-lanes and individual bits within each byte, for example:- connect DQ0 - DQ7 on the SDRAM to DQ24 - DQ31 on the microntroller, then swap the mask signals DQM0 with DQM3.- swap bits within a byte, for example after swapping the bytes as above, connect DQ0 to DQ25 on the micro and DQ1 to DQ24 on the micro.The SDRAM should not care about these type of swaps, but are there any restrictions in the way that the FMC works that would stop this from working?Thanks

Please keep the title short - less than 1 line. Edited.Hello,currently i looking for some suggestions with regards developments or evaluation or nucleo boards for the given controllers:STM32F205RET6STM32F303C8T6 if anyone is currently working or having suggestions with regards to the boards which can be used, please do let me know. and from myside i have searched two nucleo boards, let me know whether these boards can be used?https://www.st.com/en/evaluation-tools/nucleo-f303re.html?ecmp=tt9470_gl_link_feb2019&rt=db&id=DB2196#sample-buyhttps://estore.st.com/en/nucleo-f207zg-cpn.htmlhttps://www.st.com/en/evaluation-tools/nucleo-f207zg.html#sample-buyNOTE: purpose of using these evaluation boards to check the configurations of the timers and also implement the timer based functionalities.Thank you.

Hi,     I am debugging the SCT3288 HDK right now which is programmed with the STM32F405RGT6 microcontroller within it. While I was trying to debug the SCT3288 HDK, UART comport is not being detected because the firmware is got updated with some other file so I need to flash the required bin file to reset the MCU by using STM32 cube programmer application. So can you please help me to flash the bin file by using SWD mode or JTAG mode. As I am not finding the required pins for the JTAG in SCT3288 HDK. Thanks,Kind Regards,K. Manikanta Sai Srinivas.

IS61WV25616MEBLL and IS64WV25616MEBLL are recent Muxed PSRAM from ISSI. I would like to use these with an LQFN100 STM32H750VBTx to avoid complicated routing with SRAM and going to a larger LQFN or BGA package.The FMC of this MCU supports Muxed PSRAM. I am trying to understand if the part is compatible by comparing the datasheet with what I see in CubeIDE. I do not understand:The data sheet has 16 Muxed Address/Data lines but it also has two additional address lines A16, A17 (PSRAM)Byte Enable (CubeIDE)Questions:Do I configure the data as 16-bit or 18-bit? It seems to have 16-bit data and an 18-bit address.In CubeIDE I noticed that when I select the Byte Enable checkbox, I get two pins: FMC_NBL0 and FMC_NBL1. Should I connect these two pins to A16 and A17?Any suggestions on PSRAM parts that are known to work well with STM32H7?

HiI am trying to flash new FW to STM32L496 on custom board.When I try to flash the ELF file from the GUI Cube-Programmer on windows using STLINK all I have to do is select the .stldr file, .elf file, and the programming goes on smoothly.On my custom board I put the STM chip into bootloader mode, but when I try to flash the new FW I get Segmentation Fault error.It looks like the error occur only when I use the -el flag with a .stdlr file.Any help would be appreciated. 

I wrote a code for this microcontroller to test the CAN protocol, and it worked successfully in loopback test mode—data was transmitted and received correctly without using any external CAN transceiver. Then, I switched the CAN mode from loopback to normal mode and physically connected the TX and RX pins together using a wire. However, with the same code (only changing the test mode), I noticed that in Live Watch, the TX pin shows activity (data being transmitted), but the RX pin shows nothing—no data being received. I even checked the signals on an oscilloscope, and the waveforms on TX and RX were identical, confirming that the signal is physically present on both lines. Yet, according to the software, no data is received. This led me to wonder: since some microcontrollers support external loopback modes while others do not, could it be that this microcontroller does not support external loopback in normal mode by simply wiring TX and RX together? Is that correct?

Hi,I'm using Motor Control Workbench 6.2.0 with a custom power board that supports a maximum of 1200Vdc. The motor to be controlled also supports a maximum of 1200Vdc.When creating the project, I noticed that on the Power Supply tab, the application requires the bus voltage level to be specified within a range compatible with the power board and motor specifications, which in my case is [100 - 1200] Vdc.However, regardless of the value set in the bus voltage level text box, the Voltage Scale field on the Speed Sensing Config. tab appears to be out of range: it indicates a maximum allowed value of 1000V.Moreover, from the HSO startup guide, I read that the voltage scale value can't be lower than the maximum voltage that can be measured based on the hardware design (which makes sense due to internal firmware scaling).So, I wonder if there's a way for my application to work with bus voltages in the range of (1000 - 1200] Vdc?Is this an intentional limitation of Motor Control Workbenc

Hello, I build two different projects with MCSDK version 6.3, one with use the NUCLEO-F302R8 and the other one the NUCLEO-F030R8, the motor and the power board are the same, I use FOC and for both projects I use the same parameter set, in particular in the Regular execution time is set to  3 PWM.When I run the motor the behavior of the two nucleo boards is different.When I use the NUCLEO-F302R8 the behavior is as expected.When I use the NUCLEO-F030R8 the motor speed read from STM Motor Pilot (V.1.2.9) is different from the measured motor speed with an external instrument, when I set a speed of 1000 RPM the speed feedback read from Motor Pilot is 1000 RPM but the motor run at 600 RPM. Moreover the motor is not able to run at maximum speed with the load, around 1150 RPM, but it runs at 1020 RPM maximum.Attached the two MC workbench projects.Any suggestion to solve this issue?

Hello,I am experiencing an issue with the Motor Profiler in MotorControl Workbench 6.3.0. When I enable the Hall Effect in the generated source code, the program triggers the HardFault_Handler during execution.Here are the details of my setup:Tools:MotorControl Workbench 6.3.0STM32CubeIDE 1.15.1STM32CubeMX 6.11.1Hardware:Control Board: NUCLEO-G474REPower Board: X-NUCLEO-IHM17M1The following configurations work fine with this setup:Motor Profiler with Hall Effect OFFFOC with Main Sensor Observer+PLLFOC with Main Sensor Observer+PLL and Auxiliary Sensor Hall SensorHowever, when running the Motor Profiler with Hall Effect ON, the debugger shows that the HardFault_Handler is called within the FOC_Init() function, specifically at the HT_Init(&HT, false) call. The error message is:Can't find a source file at "C:\Motor_Control\MC_Releases\6.3.0\MotorProfilerLibs\Projects\NUCLEO-G431RB-X-NUCLEO-IHM07M1-3Sh\MotorControlDev\MCSDK\MCLib\Any\Src\mp_hall_tuning.c"Locate the file or edit the sou

Here's my setup:Nucleo G431RBIHM08M1 (Setup for 3 phase current sensing)MCSDK v6.3Motor is Annaheim Automation BLWS234D-36V-4000 (BLDC motor - Delta winding- 2 pole pairs)I've tried many different settings to try to get my motor to spin. Currently trying to go to the most basic setup and just input current in open loop mode but it seems the behavior is not what I would expect. I'm setting the speed ramp to ramp up to some speed and I expected that this would result in a cycle of PWM outputs at the given speed and at a duty cycle proportional to my voltage refence. Instead it appears to try pushing some current for a couple seconds then just gives up. I'm not getting any faults and there are no current measurements showing up in the Id or Iq boxes. I would expect those values to come to some steady state. I feel like I'm missing something here.

     I'm trying to control a PMSM motor using Nucleo-G474RE and STEVAL-IHM023V3 motor control boards and Motor Control WorkBench (Version 6.2.1).     I have noticed that the values of shunt resistors (R55, R68, and R101) are given as 150 mOhm in User Manual UM1823 (pages 13, 14, 15) while 100 mOhm in source code (power_stage_parameter.h, line 46) and Motor Control Workbench software. I have visually inspected the STEVAL-IHM023V3 motor control board and seen that shunt resistors' values are 150 mOhm.     The PMSM motor is rotating normally when I create, compile and run the source code via Motor Control WorkBench (for default 100 mOhm shunt resistor value in the Motor Control Workbench).     But when i changed the RSHUNT value at the power_stage_parameter.h, line 46 to 150 mOhm, PMSM motor started to rotate abnormally.     Can someone explain to me the value differency between the source code and the user manual

Hello everyone,I am encountering an issue with the HAL_Delay() function and ThreadX in my project. Before initializing ThreadX, HAL_Delay() works as expected. Specifically, the callback function:void HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef *htim) { /* USER CODE BEGIN Callback 0 */ /* USER CODE END Callback 0 */ if (htim->Instance == TIM6) { HAL_IncTick(); } /* USER CODE BEGIN Callback 1 */ WR_TIMER_process(); /* USER CODE END Callback 1 */ }is triggered correctly, and the uwTick variable increments as intended.I am using Timer6 for the system ticks on a custom PCB with an STM32H743BIT MCU. However, after calling the MX_ThreadX_Init() function, the uwTick variable stops updating, and the HAL_TIM_PeriodElapsedCallback is no longer triggered. Here is my setup:MCU: STM32H743BITCompiler: arm-none-eabi-gcc (Arm GNU Toolchain 14.2.Rel1 (Build arm-14.52)) 14.2.1 20241119CubeMX Version: 6.14.0ThreadX Version: 6.4.0Debugger: J-Link 8.32Ozone Version: 3.38g It seems

Hi Experts,I'm almost a newbie at STM32F7xx even though I've been working with STM32F4 series.I wanted to handle the flash memory as IAP.I tried flash erase as same as what I do on STM32F4 but it failed.So I checked and found that thera are two kind of bank modes in STM32F7.I'm familiar with the address map of single bank mode and I tried to change Dual bank mode to Single bank mode in my code like below. FLASH_OBProgramInitTypeDef OBInit = {0}; // 1. Unlock Flash and Option Bytes HAL_FLASH_Unlock(); HAL_FLASH_OB_Unlock(); // 2. Read current Option Bytes HAL_FLASHEx_OBGetConfig(&OBInit); // 3. Set DBANK to 0 (Single Bank) OBInit.OptionType = OPTIONBYTE_USER; OBInit.USERConfig = OB_NDBANK_SINGLE_BANK; if (HAL_FLASHEx_OBProgram(&OBInit) != HAL_OK) { // Error handling HAL_FLASH_OB_Lock(); HAL_FLASH_Lock(); return; } // 4. Launch Option Bytes loading (MCU will reset) HAL_FLASH_OB_Launch(); // 5. Lock Option Bytes and Flash HAL_FLASH_OB_Lock(); HAL_FLASH_Lo

 SPD_GetInstElSpeedDpp is implemented in speed_pos_fdbk.h  static inline int16_t SPD_GetInstElSpeedDpp(const SpeednPosFdbk_Handle_t *pHandle) { #ifdef NULL_PTR_CHECK_SPD_POS_FBK return ((MC_NULL == pHandle) ? 0 : pHandle->InstantaneousElSpeedDpp); #else return (pHandle->InstantaneousElSpeedDpp); #endif }  The returned variable pHandle->InstantaneousElSpeedDpp is however only updated when using STO+PLL as speed sensing method (see sto_pll_speed_pos_fdbk.c). For any other method (sensored or sensorless) InstantaneousElSpeedDpp is never updated.SPD_GetInstElSpeedDpp is used in mc_tasks_foc.c (mc_tasks.c before version 6.3.0) to do do reverse park angle compensation. This means that REV_PARK_ANGLE_COMPENSATION_FACTOR does not work as expected for any other speed sensing method than STO+PLL.  hElAngle += SPD_GetInstElSpeedDpp(speedHandle)*REV_PARK_ANGLE_COMPENSATION_FACTOR;  As far as I can figure out, SPD_GetInstElSpeedDpp s

I want to make a communication between 2 microcontrollers by can protocol i put after each microcontroller  a can transceiver and the problem is that we send data but i other board we don't receive it, i mean after the second receiver we don't have proper output in RX,TX even it's CANH,CANL input of transceiver is ok and the transceiver doesn't have problem because i changed them but the problem remain! and i archived the codes if you want to take look...if you know where the problem is pls tell me. 

Hi,   I first worked with CAN with STM32H563 with normal mode. It worked. Later Again I tried it is not working with same code. Loop back mode is working fine. I would like to use other pins for CAN since I am using PD0 and PD1. May I know which pins are good for working with CAN. Please find the attached code and let me know if there any issues in the code.   Thanks & Regards, Keerthi

Good afternoonI am working on the STM32H755 and am dealing with the retransmissions from my CAN FD periphery. According to the ISO-11898-1:2024 standard, the number of retransmissions should be configurable:"- from 0 (no retransmission),- to at least 6 (6 retransmission attempts),- and the highest number in this range can allow unlimited retransmission attempts."Currently I have FunctionalState AutoRetransmission in FDCAN_InitTypeDef set to ENABLE and on the oscilloscope I see an infinite number of retransmissions when I disconnect between two nodes. Now I want to limit the retransmission count to 6 retransmissions.Can I do this?Thank you very much for your answer.Manuel

Hello,I'm trying to port the example found here: https://blog.embeddedexpert.io/?p=1680 to NUCLEO-U385RG-Q.The example in the link is for STM32F411. I've successfully tried the example.Verbatim port of the code leads to USEF being set in GPDMA_C0SR.There are some unclear things about GPDMA:Reading generated HAL code: when memory-to-peripheral is chosen, DREQ bit is set in GPDMA_CxTR2, otherwise, SWREQ is set. I can't make sense of this fact and documentation given in RM0487.To achieve circular mode (i.e. setting CIRC bit in DMA_SxCR for STM32F411) do I have to use linked-list mode?I can imagine a linked list of length one pointing back to itself. Or does it have to be linked list of length two (First element is for setting GPIO bit, second element is for resetting GPIO bit) ?Thanks in advanceint main(void) { /* USER CODE BEGIN 1 */ /* USER CODE END 1 */ /* MCU Configuration--------------------------------------------------------*/ /* Reset of all peripherals, Initializes the Fl

I have designed a board with a STM32H573 and a KSZ8081RNACA PHY. As soon as I enable ETH clocks the ETH_DMAMR:SWR bit gets set.Verified:1. The 50 MHz clock from the PHY is present and stable (oscilloscope) at PA12. GPIO PA1 is configured for AF11, NOPUPD, SPEED100 as well as all other RMII pins PA2; PA5, PA7, PB12, PB15,PC1,PC4 and PC53. HCLK is stable 250MHz4. Tried forced ETH reset before and after clock enable.5. Tried to add delays after clock enable6. Tried to enable ETH clocks one by one or together7. MDIO is working and all ETH registers are writable8. I can see traffic on RXD0 (oscilloscope)If I ignore the set SWR bit I can continue but I never get a ETH interrupt.I am out of ideas and did not find anything in the errata about it. On a STM32H753 I used for another project a compensation cell bit needed to be set but I dont find this for the STM32H573.

I used the example code in RM, and room temperature is arround 31℃，the ADC value is 10644, calculated temperaure is 4127,  does it means 41.27℃？what will happen if minus temperature?/* Temperature sensor calibration value address */#define TEMP130_CAL_ADDR ((uint16_t*) ((uint32_t) 0x1FF8007E))#define TEMP30_CAL_ADDR ((uint16_t*) ((uint32_t) 0x1FF8007A))#define VDD_CALIB ((uint16_t) (300))#define VDD_APPLI ((uint16_t) (330))int32_t ComputeTemperature(int32_t measure){int32_t temperature;temperature = ((measure * VDD_APPLI / VDD_CALIB) - (int32_t) *TEMP30_CAL_ADDR ) ;temperature = temperature * (int32_t)(130 - 30);temperature = temperature / (int32_t)(*TEMP130_CAL_ADDR - *TEMP30_CAL_ADDR);temperature = temperature + 30;return(temperature);}

Hello,I met these logs when I try to deploy a model on stm32n6d570-dk:1 physical GPUs, 1 logical GPUs [INFO] : Setting upper memory limit to 4GBytes on gpu[0] [INFO] : Running `deployment` operation mode [INFO] : ClearML config check [INFO] : The random seed for this simulation is 127 INFO: Created TensorFlow Lite XNNPACK delegate for CPU. [INFO] : Generating C header file for Getting Started... loading model.. model_path="yolov8n_256_quant_pc_uf_od_coco-person-st.tflite" loading conf file.. "../../application_code/object_detection/STM32N6/stmaic_STM32N6570-DK.conf" config="None" "n6 release" configuration is used [INFO] : Selected board : "STM32N6570-DK Getting Started Object Detection (STM32CubeIDE)" (stm32_cube_ide/n6 release/stm32n6) [INFO] : Compiling the model and generating optimized C code + Lib/Inc files: yolov8n_256_quant_pc_uf_od_coco-person-st.tflite setting STM.AI tools.. root_dir="", req_version="" Cube AI Path: "E:\ST\STEdgeAI\2.0\Utilities\windows\stedgeai.exe". [INFO]

I have an odd issue.  I am setting up a timer compare channel for a 5ms delay in the future.  I set the counter to 0, set the compare value to 5ms in the future.  The compare interrupt does not occur, until the timer wraps all the way around and passes the compare value for a second time.  It passes the compare value the first time with no interrupt.Setup is:  STM32H753 (on custom HW), TIM2, Ch1/Ch2 used for PWM input capture. Ch3 used for timeout if IC does not occur.  All setup is using STM32Cube MX.  See code below.  The timers are started with the following code:The idea is that the PWM input rising edge on Ch1 will reset the counter every cycle (1kHz), but if the counter does not get reset due to no PWM input signal for 5ms, Ch3 compare happens.  Everything works as expected except if there is no input signal from the start, the timeout takes a full timer roller over, instead of 5ms, then is always 5ms after that! It is like the ti

I've got the NUCLEO-G491RE board and have it connected to my PC over the only USB port which is of course also used for the debugger. Both printf() and HAL_UART_Transmit() work to send data to a terminal program on the PC, but I can't use polling for my communication (there's too much else going on).  If I call HAL_UART_Transmit_IT() it returns HAL_OK but doesn't actually transmit anything, and any subsequent calls to printf() or HAL_UART_Transmit() no longer do anything. I'm assuming this is because this isn't a "real" UART but some kind of virtual UART that gets converted into USB commands that cooperate with the debugger. Is there a way to use interrupt-driven communication over this (virtual) serial port? Thanks, Chris