STM32 MCUs

Hello, I have been working on a project attempting to get Lua 5.5, Freertos running on a STM32h723.I used cubeMX to generate my project with Freertos enabled.I brought in Lua 5.5 library from their website https://www.lua.org/download.htmlI was able to get it compiling and my project as a whole builds and flashes without errors.Now the part that I'm struggling with. If for any reason Lua has a error the STM32 goes into hard fault and most of the time it seems to be a BusFault caused by IMPRECISERR.I'm trying to figure out if getting Lua to work on the Cortex-m7 is more involved than just adding the library. As I was watching a video from a person that was getting LuaJIT ported to the STM32h7 and he had talked about a few issues he had in regards to the Cortex-m7 https://www.youtube.com/watch?v=U9Jnah4uXBY Though I will admit he was trying to port over the Lua Just In Time compiler and other things that I don't believe base Lua has. I would appreciate it if anyo

Dear ST Community,We are currently working on the STM32H747 controller using the MIPI DSI interface in video mode.In our setup, we are using the SN65DSI83TPAPRQ1 bridge to convert MIPI DSI signals into LVDS signals for our display panel.The MIPI configuration and bridge configuration details are attached below.After configuring the CSR registers on the bridge side, we are reading Register 0x0A and Register 0xE5 for status verification, as specified in the SN65DSI83TPAPRQ1 datasheet initialization sequence.We have also enabled the test pattern, and the display turns ON (screenshot attached below).Observations:For Register 0x0A, bit 7  is not reading as 1For Register 0xE5, the expected value is 0x00, but it is reading as 0x01We are observing clock signals at the bridge outputHowever, no data signals are present on the LVDS sideQueries:What could be the reason for bit 7 not being set in Register 0x0A?What does Register 0xE5 reading 0x01 instead of 0x00 indicate?Does this behaviour su

Hello, everyone on the forum.I am using an STM32H735IG, ThreadX, and FileX to create files on an SD card and write data to them. In each iteration, I open the file using `fx_file_open`, seek to the end of the file using `fx_file_relative_seek`, write data using `fx_file_write`, close the file using `fx_file_close`, and finally flush the media using `fx_media_flush`.When performing this operation, each file write takes about 10 milliseconds. If I want to write multiple files in a short amount of time, should I use multithreading and have each thread write a file? Also, when writing data to a file on a regular basis, is it okay to keep the file open and write the data without calling `Open` and `Close`?How often should I run fx_media_flush? I’d appreciate any advice you can offer.

On the STM MB1363 board I want to expand the USB fucntionality to multi port USB HUB using port CN13 through a HUB like given below. I will be connecting UPSTREAM of the given USB Controller chip to the CN13 STM32 MB1363. TUSB4041I-Q1,  CY7C65642-48AXC Is that feasible? What throughput  can I expect?  

Is there an easy way to find devices that support specific CAN buffer configurations?For example, some only have receive queues whilst others allow a number of receive buffers to be configured (which is what I want). I know the H7x7 supports this, but does anything else?

when i run my .stmcx file in stmcsdk 5.4.8v i am getting these type of errors ,how can resolve  

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?- I have tested with the CPU at 160MHz and 2 trace data pins instead of 4, and it works, but the trace buffer overflows every time, as only 2 data lines are too slow for the amount of information.- I also tested with the

Hello,The STM32Cube project Template_LRUN is failed on STM32H7S78-DK:STM32H7S78-DK, MB1736-H7S7L8-D01SW is from the latest master of https://github.com/STMicroelectronics/STM32CubeH7RS/tree/main/Projects/STM32H7S78-DK/Templates/Template_LRUNI also double check with the stm32cubeh7rs-v1-3-0.Follow the instructions from readme:Build Template LRUN projects with CubeIDE v2.0.0Use CubeIDE to load Template_LRUN_Boot.elf to internal flashUse CubeProgrammer to program Template_LRUN_Appli.bin to external Nor-Flash and success.Powerup the DK board and no LED is light-on.By tracing the boot program, the MCU is hangup when copy the program from Nor-Flash to PSRAM. Crash happen on exact the copy to the first address in PSRAM. It seems PSRAM is not ready.The error occurs at: https://github.com/STMicroelectronics/stm32-mw-extmem-mgr/blob/5c92d55af712b20030853a8ac7ddf87ab9eb1adf/psram/stm32_psram_driver.c#L138 /* Execute the command sequence */ for (uint8_t command_index = 0u; command_index < Psra

Dear community, I’m sharing an application that has been highly requested recently: a demo running TouchGFX on the STM32N6570-DK with a camera module.Please note that this demo is NOT yet finalized. We plan to significantly enhance it over the coming weeks, and once it is ready, it will be directly available in TouchGFX Designer as a board-specific demo (under the Demo tab).In the meantime, since there has been strong demand, here is an early draft that you can already use and draw inspiration from.Another note, we’ll provide only limited support for any questions about this draft, as we are aware of the application’s limitations and are working on a much better version. Again, this demo is not final and does not reflect the quality of an official demo.The project works with TouchGFX 4.25.0 and with STM32CubeIDE. We advise NOT to regenerate code from STM32CubeMX (because there is a limitation here). You can use the flashing scripts provided in the project to flash your board.  

Hi, I'm using stm32cubeide version 2.1.1 and version 1.15.1/windows11, both are compiling the same project on my PC at slower speed compared to a lab computer.(3min vs 20seconds) Any idea what could be causing the issue? Thanks!

Hello everyone,If you've ever tried running Azure RTOS with an HTTP server, an FTP server, multiple TCP sockets, and a handful of threads on a standard NUCLEO-144 board, you know exactly where this is going.You hit the memory wall.1 MB of internal RAM sounds like a lot — until ThreadX, NetXDuo, and FileX each want their own byte pools, packet pools, and thread stacks. Add an HTTP server for a web interface, an FTP server for remote file access, and you're fighting for every kilobyte before your actual application even starts. And storage? The NUCLEO boards don't have any. If you want to serve a web dashboard or datalog sensor readings, you're out of luck.Then there's the documentation gap. ST provides excellent examples for HTTP servers with NetXDuo. FTP gets reasonable coverage. But WebSockets? Real-time bidirectional communication between a browser and your STM32? Good luck finding an ST example for that. And it's the one thing that turns a static web page into a live control interfa

TouchGFX version 4.25.0 CubeMX version 6.17.4*  STMCubeIDE version 2.0.0*edited versionI created a development environment starting with TouchGFX and used Generate Under Root in CubeMX.  This did a great job of setting up the directory structure without links so that it is easier to navigate in the STM32CubeIDE application.Part of this process automagically moves the middleware and driver directories from the STM32CubeIDE directory to the root directory.When the .project file is created by the TouchGFX code generation it handles the movement of all these files and include directories like a champ, except the Properties=>C/C++ Build=>Settings=>MCU/MPU G++ Linker=>Libraries=>Library search path for the libtouchgfx-float-abi-hard.a library.It sets the path to "${workspace_loc:/STMCubeIDE/Middlewares/ST/touchgfx/lib/core/cortex_m7/gcc}" instead of "${workspace_loc:/${ProjName}/Middlewares/ST/touchgfx/lib/core/cortex_m7/gcc}"It's a quick fix to edit it to

Hi,I do not plan to use USB, and the STM32N6's VDD is 1.8V.However, creating a new 3.3V power supply just only for the VDD33USB pin is too inefficient.The datasheet lists the absolute maximum ratings for VDD33USB as ranging from 0V to 3.6V when USB is not used, and the comment below states the following:1. All main power and ground pins must always be connected to the external power supply, in the permitted range.Therefore, Finally if I do not plan to use USB on the STM32N6, which of the following options should I choose for the VDD33USB pin?(have to consider leakage current in stop mode)1) NC2) 3.3V (by creating a new power supply)3) 1.8V4) GNDthanks in advance.

I have used the 70STM32H7 template in TouchGFX Designer 4.26.1 to create a project for a Riverdi RVT70 board.I've created a basic start screen, generated code and built it using CubeIDE 2.1.0.The code loads onto the target and runs as expected.If I open the project's .ioc file, I am told that the project uses V1.12.1 of the STM32Cube FW_H7 and V.13.0 is available. Upgrading to this version, saving and regenerating the code results in the project failing to build:In file included from ../../../CM7/USB_HOST/Target/usbh_conf.h:98, from ../../../Middlewares/ST/STM32_USB_Host_Library/Core/Inc/usbh_core.h:27, from ../../../Middlewares/ST/STM32_USB_Host_Library/Class/MSC/Inc/usbh_msc_bot.h:28, from C:/TouchGFXProjects/GFX/Middlewares/ST/STM32_USB_Host_Library/Class/MSC/Src/usbh_msc_bot.c:27: ../../../Middlewares/Third_Party/FreeRTOS/Source/CMSIS_RTOS_V2/cmsis_os.h:32:10: fatal error: cmsis_os2.h: No such file or directory 32 | #include "cmsis_os2.h"This can be fixed by adding a new i

@Mahmoud Ben Romdhane I am still seeing this on ST Cube MX 6.16.1 when generating for the STM32F723E-DISCO target. This is using the latest STM32F7 package, 1.17.4. Attached is my IOC file if that's helpful.I know its a trivial fix but wanted to report this is ongoing.

Hi,UID is set at factory for all products? Wholesale ICs comes already programmed? I need to repair some machines and IC needs to have same UID as replaced. Thanks

Hello,I successfully improved the TouchGFX based Clock Example demo app to use RTC chip (and LSE crystal clock) of the N6570 MCU. Because the STM32N6570-DK board does not provide backup battery the RTC loses the current date/time during every power off. One solution would be to sync the RTC chip with an SNTP server via Internet. I successfully solved this with STM32H7474I-DISCO board with LwIP and SNTP client, but the STM32N6570-DK board does not support LwIP.I found an example for the STM32N6570-NUCLEO-144 board which is probably similar (or close) to STM32N6570-DK board. The problem is that the found Nx_SNTP_Client application uses NetXDuo and AzureRTOS while my project runs under FreeRTOS op system.How can I solve this? When create a new TouchGFX project I can choose between FreeRTOS or ThreadX op systems only. I can't use AzoreRTOS...Can anybody help?Thanks,Louis 

I am developing a multi-node system (16 nodes) based on the STM32G0C1MET6. During normal operation, all nodes communicate at 500k (Standard CAN). To perform a firmware update, the Master initiates the following transition sequence: Reconfiguration: The Master sends a global command. All nodes switch their FDCAN configuration to 250k (CAN FD) and enter Listen-Only Mode. Trigger: The Master then sends a specific SDO command to a single target node to trigger a jump to the System Bootloader (System Memory). Reflash: Once in Bootloader mode, the target node is expected to respond via FDCAN1 (as per AN2606/AN5405) to begin the reflash process. The Master repeats this node-by-node. The Issue: While most nodes perform the jump and reflash successfully, some specific units enter the bootloader (confirmed by status LEDs) but never respond to CAN messages. These units appear "deaf" to the Master's CAN FD frames at 250k. Environment: MCU: STM32G0C1MET6 Interface: FDCAN1 (Pins: PD0/PD1) Trans

I've developed my own PCB using an STM32H723ZGT6 microcontroller.  I'd like to store data to a microSD card that's onboard, and I've designed it to use SDMMC2 for the better transmission rate.  I have no external pullup resistors, but I have enabled the internal pullup resistors (found to be 38kOhms using a multimeter) on each of the data lines and the CMD line.  I have ESD protection inline using the EMIF04-1005M8.  The bus is configured in 1-bit mode until successful connection is made.  Additionally, I've tried two different micro SD cards, a 32GB SanDisk, and an 8GB Gigastone micro SD card.  I run into issues in HAL_SD_Init, which is called in the MX_SDMMC2_SD_Init.  I've stepped through the code using the ST-Link and have found the issue to be in this loop: while (!__HAL_SD_GET_FLAG(hsd, SDMMC_FLAG_RXOVERR | SDMMC_FLAG_DCRCFAIL | SDMMC_FLAG_DTIMEOUT | SDMMC_FLAG_DATAEND)) { if (__HAL_SD_GET_FLAG(hsd, SDMMC_FLAG_RXFIFOHF)) { for (count = 0U;

I get the build warning (which is treated as an error):```CompressedUnmappedFontCache.cpp:146:66: error: unused parameter 'glyphNode' [-Werror=unused-parameter] [build]   146 | void CompressedUnmappedFontCache::unableToCache(const GlyphNode* glyphNode, int byteSize)```This is easily fixed withvoid CompressedUnmappedFontCache::unableToCache(const GlyphNode* /*glyphNode*/, int /*byteSize*/) { while(1); }​But, it's generated code, so I have to make this fix every time a regenerate. This warning happens in both `CompressedUnmappedFontCache` and `CompressedFontCache`.

I am using the EVLSPIN32G0B1 demo board and the MC Workbench v6.4.1 software, and I would like to use the FOC control algorithm.More specifically, I would like to use the Hall sensors when the motor starts and operates at low speeds, and then switch to sensorless control at higher speeds.I have read that the library does not support automatic switching, so I will need to implement it manually in the code.How should I proceed?Thank you for your support.

Hi everyone!I have generated a code from CubeMX for USB-PD in bare-metal configuration like this:  Then I started testing the code and the function USBPD_PE_Init at this line: /* PE SET UP : Port 0 */ CHECK_PE_FUNCTION_CALL(USBPD_PE_Init(_port_index, (USBPD_SettingsTypeDef *)&DPM_Settings[_port_index], &DPM_Params[_port_index], &dpmCallbacks));returned false.I have looked in the assembler window and found out that some members of static const USBPD_PE_Callbacks dpmCallbacks = { USBPD_DPM_SetupNewPower, USBPD_DPM_HardReset, NULL, USBPD_DPM_Notification, USBPD_DPM_ExtendedMessageReceived, USBPD_DPM_GetDataInfo, USBPD_DPM_SetDataInfo, USBPD_DPM_EvaluateRequest, NULL, NULL, // Like this one!!! USBPD_PE_TaskWakeUp, #if defined(_VCONN_SUPPORT) USBPD_DPM_EvaluateVconnSwap, USBPD_DPM_PE_VconnPwr, #else NULL, NULL, #endif /* _VCONN_SUPPORT */ USBPD_DPM_EnterErrorRecovery, USBPD_DPM_EvaluateDataRoleSwap, USBPD_DPM_IsPowerReady };are not a

Hello,As a lot of people here, i'm trying to implement USB in standalone mode (bare metal, no OS used).I'm using NUCLEO-STM32WBA65RI board.CubeDE 1.19CubeMX 6.15.0 still can't make it work. I'm looking for help. I checked a lot of forum posts, a lot of github pages.I based myself on :https://github.com/STMicroelectronics/x-cube-azrtos-h7/blob/dev/usbx/Projects/NUCLEO-H723ZG/Applications/USBX/Ux_Device_CDC_ACM_Standalone/USBX/App/app_usbx_device.cand tried to implement the AzureRTOS USBX standalone versionHere is my Cube MX configuration :Clock USB :I only used X-CUBE-AZRTOS-WB and desactivated USBX : Using buffer <10*1024 would rise a memory error flag in ux_device_stack_initialize() : The rest is default configuration. Then USB_OTG_HS : Device_Only and :Then i generated the code,I added : if(MX_USBX_Device_Init() != HAL_OK) { for(;;); }And inside of it : /* USER CODE BEGIN MX_USBX_Device_Init1 */ USBX_APP_Device_Init(); /* USER CODE END MX_USBX_Device_Init1 */A

What could be the reason that configuring in CubeIDE SWV as enabled the MCU on debug flashes and stops responding? Flashing works fine both ways, SWO is connected. Time elapsed during verifying operation: 00:00:00.082Download verified successfullyTarget is not responding, retrying...Shutting down... Failed to read registers from targetError: Failed to set breakpoint at address: 0x80005c0.Error: Failed to set more breakpointsFailed to read all registers from targetExternal target MCU is STM32L412. STLink is upgraded to the latest version.Since flashing works, SWD is connected properly.MCU is configured as trace asynchronous Sw and there are no reconfiguration of SWD pins.  

I'm trying to create an empty project for the NUCLEO-U3C5ZI-Q using STM32CubeIDE v2.1.1 under MacOS. All available updates have been applied.I've used File/STM32 Project Create to create an STM32CubeIDE Empty Project for the NUCLEO-U3C5ZI-Q board (all settings at the defaults offered).The project is created, along with the startup and linker files, but there is no .ioc file.