Solved

Hi,I’m using an STM32L052 with LQFP32 package, VDD = 1,8V.According to the datasheet:“VDD_USB = 1.65 to 3.6V: external power supply for USB transceiver, USB_DM (PA11) and USB_DP (PA12). To guarantee a correct voltage level for USB communication VDD_USB must be above 3.0V. If USB is not used this pin must be tied to VDD or VSS. On packages without VDD_USB pin, VDD_USB voltage is internally connected to VDDvoltage”Since in the LQFP32 package VDD_USB is internally connected to VDD, it is therefore powered at 1,8V in my design.As expected, the USB interface does not operate when I connect the board to a PC and risk of damage because D+ and D- tied to 1,8VCould you please confirm that the internal USB PHY cannot operate correctly at 1,8 V, and that USB operation requires VDD ≥ 3.0 V even when VDD_USB is internally tied to VDD ?If so, what would be the recommended workaround for designs that operate the MCU at 1,8 V ?Thanks in advance for your clarification.

 Dear  Team,We are currently working with the STM32MP257F-DK board and would like to confirm whether the LPDDR4(MT53E1G32D1FW) memory mounted on this board supports inline ECC (Error Correction Code).Could you please provide details on the ECC capability and any relevant documentation regarding its configuration or usage? Thanks & Regards Akshitha Pattem

Hardware: STM32L071CZTXSoftware Versions:STM32CubeMX 6.14STM32CubeIDE 1.18Problem Description:I'm experiencing code generation issues with both Cube software tools on an existing STM32L071CZTX project:Issue 1 - STM32CubeMX 6.14:Code generation process gets stuck and becomes unresponsiveOnly way to terminate is through Task Manager (killing OpenJDK Platform binary process)Issue 2 - STM32CubeIDE 1.18:Code generation fails when modifying clock parametersNo code is generated after clock configuration changesSteps Already Taken:Performed complete uninstallation of all STM32 softwareFresh installation using newly downloaded files from ST websiteVerified MyST account login on both applicationsRequest: Has anyone encountered similar issues with these software versions? Any guidance on resolving these code generation problems would be greatly appreciated.Thank you for your assistance. 

Hi, I tried to build my project but I faced these errors :--------------------------------------------------------------------------------------------------------------------------------------------------C:/ST/STM32CubeIDE_1.12.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/ST/STM32CubeIDE_1.12.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/lib/thumb/v7e-m+fp/hard\libc_nano.a(libc_a-closer.o): in function `_close_r':(.text._close_r+0xc): warning: _close is not implemented and will always failC:/ST/STM32CubeIDE_1.12.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eab

Hi, I am using a STM32F411CEU6. I am trying to make the One Pulse Mode of TIM1 start every time TIM2 has counted its ARR. However, I don't seem to really understand what the relevancy of the ARR of TIM1 is when having  TIM2 controlling the start(except if it is longer than TIM2 ARR i guess). Now I have 90MHz on both APB1 and APB2 and the PSC of both TIM1 and TIM2 is 90. I was following an example online where he sat the ARR of TIM1 to 50000 and ARR of TIM2 to 60000. The Pulse of TIM1 was 10000. From my understanding when I am running in output compare mode PWM1, TIM1 should start every 60ms and have a ON time of 10ms. Instead I see an ON time of 20ms and a period of 60ms. However when I change the ARR of TIM1 this ON time also changes. Is there something I am missing completely here? (I also have to change the OCMODE of TIM1 to PWM1 because it does not seem to be an option in MX)Thanks in advance!

Hi,I would like to know what is the stop band attenuation of LPF1 and LPF2 for the sensors ISM330DLC & IIS2DLPC. Thank you!

AN5296Application noteASM330LHH: automotive inertial module digital 3-axis accelerometer and digital 3-axis gyroscope3 Operating modes”To guarantee proper power-off of the device, it is recommended to maintain the duration of the VDD line to GND for at least 100μs."About the statement:If the power is turned on before reaching the GND level, what will be the effect?

I am finding it difficult to get clear direction on best practices for how to do the layout for CSI and CSO.  App note AN4985 says that "parasitic capacitance to ground should be made as small as possible", and then recommends using a coupling capacitor up to 2.7pF (C_COUP, between the 2 electrodes, I think... not sure).  But, on the other hand, the reference design (Discovery Kit ST25R3911B-DISCO) has no C_COUP shown in the schematic -- maybe because there is enough capacitance already between the electrodes? --  and it has an RC of 1k and 12pF on both CSI and CSO, without explanation.  It is not clear why we want to minimize parasitic capacitance to ground, but then we deliberately add 12pF of capacitance to GND.  Some clarity on the design goals for CSI and SCO would really be appreciated.  thanks! 

I am currently working on a new hardware design using the STM32U575VIT6 (LQFP64, 10 × 10 mm) microcontroller.I would like to request:Reference schematics and layout guidelines for STM32U575 in LQFP64 packageRecommended power supply and decoupling capacitor designCrystal oscillator and reset circuit design guidelinesAny available design checklists or application notesMy design overview:,low-power IoT sensor node Peripheral interfaces planned: SPI, I²C, ADC, etc.Kindly share any relevant schematics, PCB layout examples, and design documentation to ensure proper implementation.Thank you very much for your assistance.ThanksHarshith

@Issamos  Am planning to Quad SPI, which port we can use, i cannot able to find the data sheet below listed pins can use Controller -STM32U575VIT6 (LQFP64, 10 × 10 mm)QSPI_CLK → PB2QSPI_NCS → PB6QSPI_IO0 → PD11QSPI_IO1 → PD12QSPI_IO2 → PE2QSPI_IO3 → PE3Pls suggest the pins details 

Dear All,I would like to confirm that two M24C04-F, one in a DNF5 package and one in a FDFPN8 cannot be used together on the same bus. Is that correct? To provide some background, we are using M24C04-F DNF5 but there is a need to add another EEPROM on the same bus. Adding UFDFPN8 device with accessible E1,E2 pins should allow us to add another EEPROM with a different address, however, we found out that the DNF5 variant actually responds to multiple I2C addresses, not just 0x50/0x51 as defined in the DS.The DS states that the pins E1, E2 aren't accessible but E1, E2 bits must always be set to logic 0 for proper communication with the DNF5 variant. However, it also states that "No other I2C device using address 1010 xxxx (x = don't care) can be connected to the same bus."I assumed that the E1,E2 are set to 0 internally in the DNF5 variant but it seems more like they aren't checked during addressing. Can someone from ST provide the reason for this? &nbsp

 Hello, the NFC reader I use is ST25R100. My card is Mifare Desfire EV2. Does it support it?My configs are like this, but it doesn't read the uid. It reads the NFCA type correctly. 

I would like to identify the following two diodes, please.

I have a Flash Full test failed issue with the STM32F427 ClassB library V4.0.0 code in Keil project.The project is generated from the STM32F446RE-Nucleo examples. Attached please find my scatter file and the post-build command batch file. (I have tested the official CubeIDE project and it can pass the Flash Full test and also the runtime partial flash test.) Project.sctLR_IROM1 0x08000000 0x00080000 { ; load region size_region (512KB FLASH) ; Interrupt Vector Table and Program Code (FLASH) ; Full 512KB flash region ; Note: CRC area (0x0807FFFC-0x0807FFFF) should be excluded from flash test ER_IROM1 0x08000000 0x00080000 { ; load address = execution address (full 512KB) *.o (RESET, +First) *(InRoot$$Sections) .ANY (+RO) .ANY (+XO) } ; RAM Memory Region (192KB) ; Backup buffer section (for STL) - 32 bytes (0x20), placed first in RAM, UNINIT (NOLOAD) backup_buffer_section 0x20000000 UNINIT 0x20 { * (backup_buffer_section) } ; Initialized data (loaded from FLAS

Hello,I’m using an STM32F429I-Discovery board with an MT9M001 camera module, trying to display the camera image on the board’s built-in LCD.However, I found that the following pins conflict between the DCMI and LTDC functions (please correct me if I misread the pin mapping):PA4: DCMI_HSYNC vs LTDC_VSYNCPA6: DCMI_PIXCLK vs LTDC_G2PC7: DCMI_D1 vs LTDC_G6PB8: I2C1_SCL vs LTDC_B6PB9: I2C1_SDA vs LTDC_B7In this situation, what is the typical way to handle such pin conflicts?Would it be necessary to change the board or the camera module?Any advice would be greatly appreciated.Thank you in advance.

Hello, I want to use LTDC on the STM32H743VIT6 microcontroller, but when I enable this peripheral in CUBEMX, it does not activate correctly. For example, the pins for B are from B3-B7, while they should be from B0-B4, and the same goes for R, G.  

Hello, I bought STM32H743XIH6 board and first tried to program it with FTDI programmer and STM32CubeProgrammer. It looks like the serial interface detects the board correctly as I can see it in the STM32CubeProgrammer but fails at a read attempt of 0x080000000 address with error message like "error occured during read at address 0x08000". Next, I read that I need ST-LINK to over come UART problem so I did. I purchased ST-Link V2 and gave it a try:22:33:27 : UR connection mode is defined with the HWrst reset mode22:33:27 : UR connection mode is defined with the HWrst reset mode22:33:27 : ST-LINK SN : 37FF71064E57343691A3134322:33:27 : ST-LINK FW : V2J46S722:33:27 : Board : --22:33:27 : Voltage : 3.26V22:33:27 : SWD freq : 4000 KHz22:33:27 : Connect mode: Normal22:33:27 : Reset mode : Hardware reset22:33:27 : Device ID : 0x45022:33:27 : Revision ID : Rev V22:33:27 : UPLOADING OPTION BYTES DATA ...22:33:27 : Bank : 0x0022:33:27 : Address : 0x5200201c22:33:27 : Siz

I'm designing a circuit to convert sensor values ​​to ADC using the STM32U073MC (LQFP-80).Unfortunately, I'm new to the STM32U0 series.I read the RM0503(Rev 4) Reference manual(page 427) and found that the OPAMP1_VOUT can be connected to ADC1_IN8.However, I checked the datasheet's(DS14548 - Rev 2 - March 2024) port table(page 32/Table 12. STM32U073x8/B/C pin/ball definition) and it seems to be connected to ADC1_IN7.1. Which information is correct? (ADC1_IN7 or ADC1_IN8)2. Also, could you briefly explain how to make the desired connection using CubeMX provided by ST?  - I wish configure VM_SEL bits as “inverting not externally connected” with CubeMX. 

Hi, we are designing a product around the STM32WB5MMGH6TR but cannot find a full datasheet.On the product page we can find what is described as a datasheet (main purple download button at the top) but is only a 37 pages "technical brochure" that does not show the current consumption in various modes, nor many technical parameters.There are plenty other documents but none of them show the current consumption nor all the technical specs and details you normally get from an MCU datasheet.Where can I find a full datasheet showing the all current consumption data?Thank youRick

Hello,I want to adapt the STGSH50M120D to the circuit I already have working, but I have a question about pins K1 and K2. Will there be any problem with the STGSH50M120D if I don't use K1 and K2, leaving them disconnected?   

Hello, I am fighting about a week to enable USB-PD comms on my STM32G0B1 MCU and even chat GPT literally told me - he don't have a solution ( shock, a?) One last try before I quit, is to try 1.5.0 package version but I can see in cube MX  only 1.6.0 the earliest. (attached). Repository has 1.5.0 folder and zip. Any ideas?

Hi ST, I'm looking for STM32 boards that are permitted for end-product usage. In particular, I find Nucleo wonderful but my understanding is they are not to be distributed in the product. Does ST offer any comparable SBCs to Nucleo that can be essentially be mounted on a host board without having to do a custom PCB just for the MCU? If not, to what extent can Nucleo/Discovery boards be used, f.e. development/evaluation only, test/cert, etc? Historically I have seen assortments of off-the-shelf SBCs being used even in industrial/medical equipment which struck me as very practical and I haven't come across anything from ST for this, so maybe I am looking in the wrong place. Open to suggestions and guidance. Thank you!

Hi there! Not entirely sure if I'm missing anything here: I've been running issue when usign FatFs library with SDMMC1 on a STM32H755ZI due to the MBR sector readback been partially incorrect. Specifically during check_fs() where we check location where the ASCII for "FAT32" is store in the MBR sector (first 512bytes). The card can be verified to function correctly using HxD tool on Windows:However, through SDIO on the STM32 platform, I was getting different result for the byte [82:86], as the location is completely cleared. byte[32:24] seems to be offset to a completely different location instead:Here is the code snippet where I used HAL library to grab the first (block) 512bytes: const uint32_t BlockAdd = 0; const uint32_t NumberOfBlocks = 1; HAL_StatusTypeDef status = HAL_SD_ReadBlocks( hsd, (uint8_t*)pData, BlockAdd, NumberOfBlocks, Timeout ); if (status == HAL_OK) { if (HAL_SD_GetCardState(hsd) != HAL_SD_CARD_TRANSFER) { return HAL_ERROR; } }If anyone have any

Hello,Need information about, does LPUART can wakeup? if the clock source is LSI (32Khz)?Because I have tried multiple examples to wakeup but it only works in debug mode but not in release mode.I have also work on optimization level, currently optimization is None for both debug and release.Thanks,Nitin

Hi everyone,We’re developing an IoT node for agricultural applications and plan to make it compliant with certification requirements (CE, CRA, RED).We’re using the X-CUBE-AZURE package as our starting point and want to use TF-M (Trusted Firmware-M) for security.We’re new to cybersecurity and TrustZone, so I’d like to ask the community:Which peripherals and parts of the application stack should be implemented on the secure side of TF-M in this case?In our design we have various interfaces: UART, I2C, SPI, Wi-Fi module, Digital I/O, Analog I/O, CANBus, Modbus, and SDI-12.Which of these should be configured as secure or non-secure, and which parts of the Azure IoT stack are typically expected to run in the secure vs non-secure world?Any practical examples or recommendations based on your experience with X-CUBE-AZURE and TF-M would be very helpful. Thanks in advance!