STM32 MCUs Products

Problem When i call * USBPD_PE_SVDM_RequestAttentionI get a OK message response but the callback never gets called.  * USBPD_VDM_SendAttention Curious to know if there's any good way to debug this?  Current debugging stepsI have a STM32G0-Disco board setup to capture the messages over USB-PD and display them with ST's USB-PD monitoring software.  So i know the attention pin is not currently activating.  I have a breakpoint to make sure that USBPD_PE_SVDM_RequestAttention is being called.  If i wait a few seconds and then trigger it to call USBPD_PE_SVDM_RequestAttention again i get a BUSY error.  So i figure it's trying to send it, it just can't?   My projectI'm using this as my base with a stm32G071- nucleo board.  I grab the CC l

Hi,We are facing the same issue like the below community post. https://community.st.com/t5/stm32-mcus-products/flash-via-i2c-bootloader-problem-for-stm32g0b1kbu6/m-p/636467#M234685 But we are using  'STM32G431RBT6' in our project, kindly let us know if any specific pins need to be handled in this MCU for proper operation.Kindly reply on this as early as possible. Thanks,Ananthu

Hi,I have a strange problem on an STM32L051C8 with the comparators enabled in window mode.If I put the system in stop about 20 seconds after powering the microcontroller, the current draw is about 250 uA. If I then exit the stop mode with a soft reset and put the system back to stop after 20 seconds (without removing the power), the current draw is 0.42 uA.The comparator is initialized in ultra_low_power mode with interrupt enabled to exit the stop mode.What can I look at?Thanks

Hello,    Developing a firmware to update the application via Bootloader over USART2. But, the STM32U5G9BJYXQ is not responding on 0x7F. The MCU is successfully starts from the NSBOOTADD1(0x0bf90000) on driving the BOOT0 pin high while deasserting the reset. The USB-USART tool is sending a proper 0x7F, verified by oscilloscope. Please point to what I might be missing.   

I am using the STM32H725RE (68-pin package).My goal is to have full duplex SPI communication with a 16 bit shift register using the stm32h7 as the SPI master (with no dma controller).I am using the SPI3 with the following pin (12MHz)PA15 (SPI3_nCS), PC10 (SPI3_SCK), PC11 (SPI3_MISO) and PC12 (SPI3_MOSI).With the following code it is already possible to write the data successfully and the shift register also sends the data correctly to the MISO wire. (as you can see in the logic analyser screenshot)But I have problems reading the receive buffer, the flags are set correctly (RXP is set correctly), but when I read the RXDR I only read the data 0xFFFF, although other data should be read as shown in the logic analyser screenshot?

I am trying to flash a .bin file to an STM32F767ZI Nucleo board using UART via STM32CubeProgrammer. While I can successfully connect to the board using ST-LINK, I am unable to establish a connection over UART and encounter the following error:  I have tested USART1, USART2, and USART3 with various baud rates, and configured the BOOT0 pin to logic high followed by pressing the reset button, as described in the reference manual. However, the issue persists. Please suggest possible causes/solutions for this problem.  Thank you. Arun Badiger,

I have seen the question asked many times, references made but the question never gets answered with precision.  So, once again...I want to use HAL_I2C_Master_Seq_Transmit_IT along with receive to read an I2C device register.1. START SLAVEADDRESSWR (N-Byte RegAddress)2. REPEATEDSART SLAVEADDRESSRD (N-Byte returned data) STOPStep 1 would us HAL_I2C_Master_Seq_Transmit_IT Step 2 would use HAL_I2C_Master_Seq_Receive_ITWhat are the "Option" parameters such as I2C_FIRST_FRAME, etc. for each of these calls to avoid a STOP between the sequences and make the REPEATEDSTART occur, and of course finish up with a STOP?And using the memory read/write calls does not work because the register memory address cannot be of arbitrary length.  Don't have a scope handy to see the protocol generated, so I won't know things are working until my device actually returns correct default register values.   

Using the information from the chip's datasheet and reference manual:I have the following routine (using the HAL routines).  My issue is that I have verified code execution and setting of the two OB values via JTAG, but when the system reset is issued I go right back into user code at 0x0800 0000 and not the DFU loader as expected (0x0BF9 0000).This seems like it should be simple... what am I missing or doing wrong?   void EnterFirmwareUpdateMode(void){HAL_StatusTypeDef status; 

Hello, In the MCU datasheet, there is a table on page 200: Table 72. Typical dynamic current consumption of peripherals.What is the meaning of the current writing in the peripherals on stop modes, since in this mode, all clocks in the core domain are stopped? I saw that there is an option to enable MSIS/HSI16 in stop mode if a peripheral requests it, but according to what frequency?  The frequency of the processor or the frequency that entered the clock tree for the peripheral that required it?moreover, I tried to simulate it on STMCube and saw that adding peripherals does not increase current consumption in stop mode, while on datasheet writes that they consume current in units of uA/MHz. thank you amit

Hi, I am configuring the ADC in single-channel continuous conversion mode using DMA. However, once I call HAL_ADC_Start_DMA(&hadc, &AD_RES, 1), the main loop stops executing, and the HAL_ADC_ConvCpltCallback() function is not triggered.I noticed that setting hadc.Init.DMAContinuousRequests = ENABLE causes the main loop to become blocked.How can I configure DMA to continuously retrieve ADC values without blocking the main loop and the HAL_ADC_ConvCpltCallback() will be called continuously? I'm following this ADC tutorial: https://deepbluembedded.com/stm32-adc-continuous-conversion-mode-dma-poll-interrupt-single-channel/   /* USER CODE BEGIN Header */ /** ****************************

Hello everyone,This is my first post on the ST Community forum.I recently moved from a custom 6-layer board using STM32H725IGKB to a simpler 4-layer board using STM32H723ZGT6. Both designs use an external OCTOSPI memory, with 50 ohm controlled-impedance routing and 33 ohm series resistors on the signals.On the new 4-layer board, I am seeing read/write errors on the OCTOSPI interface, while the original 6-layer board works reliably with similar routing and firmware.I would like to ask whether the OCTOSPI output driver characteristics or output impedance differ between STM32H725 and STM32H723, or if these issues are more likely related to signal integrity, stack-up, or return-path differences on a 4-layer PCB.Any guidance or experience would be appreciated.Thank you in advance.

Can anyone tell me or direct me to a source that shows the minimum connections needed to power up and serially program a STM32F765ZGT6? (144 pin package.) I will be attaching the chip to a breakout board and will be using a St-Link Minie3.  Any help much appreciated.

Hi! I'm working on a Power Delivery Sink using an STM32G484RETx MCU. I managed to get SPR Power Delivery working without any issues, but I'm having trouble handling the EPR handshake.I'm using the latest USB-PD library from ST's GitHub:https://github.com/STMicroelectronics/stm32-mw-usbpd-coreI can successfully enter EPR Mode, but the PD stack automatically calls Evaluate Capabilities and sends an SPR Request (Data Object[2] == 0). I can’t find any option to prevent the stack from running Evaluate Capabilities when Extended PDOs are received from the source.I’ve read @FBL's post on the ST Community, which states that the latest stack should support EPR:

I have swapped from a custom PCB-board with a 6-layer stack using a STM32H725IGKB, to another custom board with a 4-layer stack using STM32H723ZGT6 (simpler package).I am using an external OCTO SPI on both boards, but I have R/W errors with the 4-layer board.Both boards are routed with 50 ohms impedance and uses 33 ohms series resistors for the OCTO SPI.I am wondering if the output impedance is the same for these two H7-devices?

Hello everybody,I am trying to synchronize the ADC1 and ADC2 to work with center-aligned PWM signals in dual-simultaneous regular mode using DMA. My setup:PWM frequency: 5.2 kHZADC conversion frequency: 104/2 = 52 MHZIf I have 3 conversions per ADC with every single one lasting 2.5 cycles, according to the reference manual:One conversion : (2.5 + 12.5)*19ns = 285 nsThree conversions: 285*3 = 855 nsThe problem is when I hook up oscilloscope I see that I am getting 8.2us until I reach my interrupt routine which is much longer than expected. I want to do all of my conversions at the moment when CNT=ARR so that I make sure lower side of the FET is ON. I am doing this by setting another channel of the timer to use it only for the time base and setting its TIMx.Pulse = ARR -1. Also TIM1 and TIM8 are synchronized through master/slave in trigger mode on enabling the counter.    

I am trying to do OTA programming modifications using the DUAL bank feature of my STM32U575 IC with 1Mbyte of memory.I have successfully done this when the program starts in BANK 1 and I reflash BANK 2. I change the User Option byte to OB_SWAP_BANK_ENABLE and the board reboots and successfully runs from BANK 2.Now, on the next firmware update, programming BANK 1 when I am operating from BANK 2 the HAL_FLASH_Program command fails on the first byte.The erase code is attached and it is very similar to others I have found on GIT for other products. Does the U5 have an inherent defect? any help would be greatly appreciated.

Hello everyone,We are having trouble getting tracing to work with our target at full clock speed and would like to understand why, we have an application running on STM32U575 @ 160MHz CPU clock, we also connected the J-Tracer to it using a connector glued next to the uC and short wires (~10mm) to PE2 ... PE6 (pins 1 to 5 on the LQFP100), the GPIO pins are all configured (using a JLinkScript) as AF and at maximum speed, and from what we understood on the documentation (Arm trace technical specification - SEGGER Wiki​) the trace clock and trace data operate at half the CPU speed, I checked the ST datasheet and the GPIOs we are using should be good up to 100MHz, so in theory the trace should be possible with the CPU running at 160MHz and outputting trace data @ 80MHz, or?

Hi,If I use STM32CubeIDE 1.19 to start a new project for the STM32H755 Nucleo board, the startup assembly files in both the CM7 and CM4 sub-projects are the same file with the same contents, startup_stm32h755zitx.s.  It looks like this file is the one generated for the M7 core that just gets copied over to the M4 directory, because inside it has: .cpu cortex-m7Now, I know both cores share all the peripherals and interrupts.  But I would assume the ".cpu" definition would need to be cortex-m4 for the M4 core.  So far I haven't seen any issue, but this is probably a hidden bug.Thanks,-m

What is meant by watermark concept in chromArt Controller, Whats the application of it can you explain in detail and clearly

I am facing very weird issue in STM32 ADC.1. I used single channel in polling mode and interrupt mode the value i got was 4095, even the pin voltage was 1.7V, i used DSO to look for any serious noise on the pin but it was clean.Also if i gave 0V to this pin (pin 29 Ch10) it displayed adc value round 30.2. Then i tried DMA for single channel CH0 it behaved same.3. Then i tried DMA for 3 channel Ch9,Ch10,Ch11... behavior was same but this time if i touched any of the ADC Channel from ch9 & ch11 the value of Ch 10 became 2200, which was quite correct.4. Then i tried DMA for only Ch10 then adc value became 4095 for 1.7V and touching any pin doesnt do anything.Just if i give 0V instead of 1.7V adc value come near to 30-40.5. Circuit checked multiple times its a custom PCB, connections are solid.. track distances are well above the standard.6. I am using STM32CUBEIDE to generate the code. Unable to figure out w

Hello everyone, I am working on a project related to CAN communication, and I don't have complete knowledge about the RTR Remote and RTR DATA features within CAN. Should I use RTR Remote in a complex system?

Hi There,So, I got some of the STM32C011J6 MCUs for my simple project of reading sensors data and generating an interrupt.But I am in a dilemma, that the MCU's has I2C Pins, SWD Pins for programming, GPIO pins to act as interrupt but how to initialize it in CUBEMX.I am planning to build PCB after I successfully assign pins in CUBEMX.When I choose I2C, It blocks the SWD Pins and Vice versa. Also, is External Crystal necessary for such MCU? Looking forward to most of the suggestions and resources.My plan is to read a sensor data via I2C and generate interrupt on a GPIO Pin. 

Been reading thru the F103 datasheet to try and figure out why my TinyUSB based code isn't working. The datasheet says.. "For mono-directional/single-buffer endpoints, a single register can be used to implement two distinct endpoints". The F103 has 8 physical endpoint registers. There are no flags in those registers to set mono or bidirectional mode. Each register only holds one EP address value. My application requires creating EP0 (IN+OUT) + 4 * (Bulk IN+Bulk OUT+Interrupt In)=2+4*(1+1+1)= 14 EP addresses in total. The datasheet continues on to say "The number of registers is 8, allowing up to 16 mono-directional/single-buffer or up to 7 double-buffer endpoints(a) in any combination. For example the USB peripheral can be programmed to have 4 double buffer endpoints and 8 single-buffer/mono-directional endpoints." So how can you get 14 EP addresses into 8 endpoint registers?  

Hello @Imen.D , A side question: RM0440 for G4 says oversampling mode does not support offset. Any change to this position as like the H7 change?  Solved: 'H7 ADC offset correction in oversampling mode - STMicroelectronics Community Thank you. SK

Hello,    I'm working into writing firmware image to a STM32H7A3AII6Q via internal boot-loader. I'm using AN2606 and AN3155 as reference documents.     The boot-loader entry sequence I'm using:State 1: BOOT0: high              RST: lowState 2: Wait 200 msState 3: BOOT0: high              RST: highThen I'm sending 0x7F over USART2 but, getting no response(0x79).Can you please help me what might be wrong here?