Solved

Hello, I am using the Zephyr operating system with the STM32U5G9J-DK2 hardware. I intend to collect voltage data using the ADC, but so far, no progress has been made. Here are the steps I have taken: I used the zephyr\samples\drivers\adc\adc_sequence example from Zephyr 4.2.0. I created a new app.overlay file in the root Vmakelists.txt directory with the following content: / { aliases { adc0 = &adc1; }; }; &vbat1 { status = "okay"; io-channels = < &adc1 5 >; };   I compiled using this command:west build -p always -b stm32u5g9j_dk2 --sysbuild . Then I supplied 1V to the PA0 pin (silkscreen labeled PWM/D6), and the log is as follows:     [16:22:28.487] RX←◆*** Booting Zephyr OS build v4.2.0 ***ADC sequence reading [0]: [16:22:29.493] RX←◆- adc@42028000, channel 5, 5 sequence samples: 2684 = 2162mV 1788 = 1440mV 1571 = 1265mV 1532 = 1234mV 1492 = 1202mV adc@42028000, channel 12, 5 sequence samples:

Hi Team,   Could you please assist me with the following situation: CANFD is working with FIFO0, but not with FIFO1, same config, using STM32G0B1KEU6. I am using same channel, FDCAN1. I will attach both files for refference.   Thank you in advance, Aleksandar.  

Hi,I would want to know the default I2C address of the STSAFE-A120 and if it is possible to change it, as it is done in the A110.In addition, is there any documentation about the content of the STSAFE-A120 I2C registers?Thank you in advance.Regards,Luis

Hi, I'm on a applicaiton involving USBX MSC and FileX. The final memory for the application is a NOR flash so I also use LevelX.Acutally, I'm working on a nucleo-U575ZI-Q without NOR flash so I use NOR Simulator on LevelX.My problem is that a file created with FileX is detected by windows, have the right number of bytes but data are wrong.My program do this:1) FileX format the device2) FileX create the file STM32.TXT and put the data "This is FileX working on STM32". I can see this data on the RAM3) FileX close and open the file STM32.TXT and I can read the text4) FileX close the media.5) USBX open the media and on Windows I see the file STM32.TXT but data are not correct. It's like if this data comes from another part on my RAM.When the device is connected to a computer, I can create new file, write on it then unplug / plug USB and the new file is still here. I can also edit STM32.TXT.Has somebody an idea about why FileX can read right data but windows doesn't read

I get a Unhandled: on_readmemory_request not available in PyDevJsonCommandProcessor. error while debugging other python projects. This issue gets resolved when I disable the STM32Cub for Visual Studio Code Core extension and its related extensions.To reproduce: Open an existing python project or package (workspace)Launch the debug session. It tries to start the session and in a few seconds throws this error and stops the debugger.Unhandled: on_readmemory_request not available in PyDevJsonCommandProcessor.Please see https://github.com/microsoft/vscode/issues/249341#issuecomment-3064965337 

Hi,I have configured WB55 project in CubeMX but each time I reopen it, clock config isuue is displayed. When I change SMPS clock source to HSE error dissapears and I can generate project. But onviously it is not saved since next time I open it, error is back and cloc source set again to HSI. Is there way how to fix it or is it just bug in CubeMX? Thanks.David H.   

Hello ST Expert, On our custom board - USB PD, it has  1. HW: TCPP03-M20 with STM32G0B1CBT6 2. SW: X-CUBE-TCPP 4.2.0 ( USBPD Application 4.2.0 - Dual_Role) 3. SW: Board Part tcpp0203 1.2.3 4. Tools: STM32CubeMX (6.15) & STM32CubeIDE 1.19.0 & STM32CubeMonitor-UCPD-1.4    May you guide how to fix below issue? Issue: a) When pluging a usb device (smart phone USB type-c 3.1) in /connect to our custom board, on the "STM32CubeMonitor-UCPD-1.4",  we could see CC1/CC2 is detected, and it (SRC) starts charging the smart phone (SNK). However, only SRC, CCI/2 info is shown on the GUI; data role (UFP/DFP) info is not shown, etc. b) When we try to do Power role swtich, or try to get SRC's capacity by sending message to connected port on  "STM32CubeMonitor-UCPD-1.4", it always shows the message is rejected. (* We already turned on support options on CubeMX - Stack Port 0 Parameters). All messages are rejected. c) Similiar to B), even we enable support all o

Hi everyone. I’m trying to connect a genuine ST-Link V2 to an AT32F415 MCU using SWD, but the debugger always reports “Target not detected” and shows Device Update: false. Here’s my setup: • SWDIO → SWDIO• SWCLK → SWCLK• GND → GND• 3.3V from the board is present (measured ~3.29V)• NRST is connected• Target is externally powered• Several different ST-Link drivers tested• STM32CubeProgrammer, OpenOCD, and ReFlasher all fail to detect the device• Different cables and different USB ports tested My questions: Does ST-Link V2 fully support SWD communication with AT32 (Artery) MCUs, or do I need an AT-Link?If ST-Link V2 should work, what settings or wiring should I double-check?Is there any special sequence needed to connect if the AT32 has read protection enabled?Can ST-Link V2 connect to a target that is running firmware which may have disabled SWD pins?  Any insight or experience with ST-Link + AT32 would be appreciated. Thank you.

Hello,I reviewed a material declaration report for the TS4990IQT online.The attached report lists the MFR item name as "AYX0*Q990ABH."Could you please confirm whether TS4990IQT and AYX0*Q990ABH refer to the same part?Also, does this part contain Dechlorane Plus?I would appreciate your guidance on this matter.Thank you,

Since Updating to new Version is always a lot of manual work i would kindly ask for a Change Log compared to the Major Version 6.4.0.The new Features / Improvements may justify/not justify the move from 6.4.0 -> 6.4.1.

HiDeleted all my first attempts, wanted a new clean start.Then imported the "Templates" part of the ST provided "stm32cubec0-v1-4-0" examples.But it won't run nor build (greyed out).It says "The selection cannot be launched, and there are no recent lauches" (See attached)I've been looking through to make one but with no luck.The built in Help is not providing anything.

__LL_ADC_CALC_VREFANALOG_VOLTAGE macro presumes that VREFINT calibration value is from a 16-bit ADC. However, for STM32H723, the value I see (1522) is from 12-bit ADC conversion. So this macro returns incorrect value. On STM32H747, it works as expected (the value is 24074 which corresponds to 16-bit ADC value). I have not found any information about conversion width in the reference manual nor in the datasheet.#define __LL_ADC_CALC_VREFANALOG_VOLTAGE(__VREFINT_ADC_DATA__,\ __ADC_RESOLUTION__) \ (((uint32_t)(*VREFINT_CAL_ADDR) * VREFINT_CAL_VREF) \ / __LL_ADC_CONVERT_DATA_RESOLUTION((__VREFINT_ADC_DATA__), \ (__ADC_RESOLUTION__), \ LL_ADC_RESOLUTION_16B) \ )

Hello, Can I say that "IDLE" is equivalent to "RTO with 8-10 bits (depending on framing)"?Or are there some other subtle differences? My goal is to transfer received data with DMA and start interpretation of the data when nothing is received on the line which, in my application's world, is equivalent to an end of frame. ThanksJulien 

Hi,We have the X-NUCLEO-67W61M1 (for ST67W) attached to a custom STM32U5-board. Disappointingly we just found out the whole architecture of X-CUBE-ST67W61 seems to rely on FreeRTOS while our app architecture is based on ThreadX…A light weight bare metal approach would be highly appreciated when starting up simple testing with e.g AT-commands! Then we want to use ThreadX for an HTTP server among other things.Any recommendations on potential work arounds using the X-CUBE-ST67W61 without switching to FreeRTOS?Thanks in advance

Hello,let say that STM32H753 mCU has connected VBUS (via resistor divider to be sure that voltage on VBUS detection pin (PA9) would never exceed AMR), D-, D+ and GND lines with PC, before mCU core is supplied. At the moment when mCU core is then connected to power supply, would enumeration starts normally as it should or fact that USB module of mCU was connected to PC before core parts of mCU were supplied could bring problems?Thanks!

I'm starting a bare-metal firmware that will display basic graphics on a LTDC connected LCD screen. For the moment I'm using a STM32H53-EVAL2 board (rev E I think) Right now I write a fix image in the frame buffer. The image is correctly displayed except it's kind of blinking. Since the image never changes I suspect it is due to the setup of the LTDC interface or LCD screen. I based my software on STM32CubeH7 source code example (LTDC_Paint application).     Do you know: - the screen model on the eval board ( I couldn't find the model in the STM32H753-EVAL2 reference manual) - what configuration parameter could cause the "blinking" of a fixed image ?   Thank you

Hello! I'm now using a STM32F469 to drive a screen with MIPI-DSI Interface. I need to send the initial codes with low power command transmission, and then drive the screen in video mode. I think LPDT it is supported by this MCU, but I'm not sure how to use it. Could anyone give me some advice or instructions?

Hello,I am trying to get the OEMiROT example projects running on STM32H563 from "STM32CubeH5\Projects\NUCLEO-H563ZI\Applications\ROT" and this page : https://wiki.st.com/stm32mcu/wiki/Security:How_to_start_with_OEMiRoT_on_STM32H573_and_563%E2%80%93TrustZone_enabled Provisioning works well, unfortunately, I'm blocked on the firmware update step through the internal bootloader. After the message 'Start download with STM32CubeProgrammer through supported interfaces (USART/SPI/I2C/USB)', when I connect CubeProgrammer with uart connection, the bootloader seems to work correctly as I received:Chip ID:0x484 Bootloader protocol version : 4.0Then, CubeProgrammer freezes for 2 mins and the device is disconnected with this message log: 09:54:32 : Error: RDP is set to level 1 or target is held under reset, try using Read UnProtect (-rdu) command in order to remove the Read Out Protection. 09:54:32 : UPLOADING OPTION BYTES DATA ... 09:54:32 : Bank : 0x00 09:54:32 : Address : 0x4

You may encounter an issue when developing for the STM32 microcontroller using STM32 development boards where a pin that is configured for reading on a General Purpose Input/Output (GPIO) reports a high state even when it is not physically connected to any circuit. Pins are not expected to output neither high or low when left floating.  This can lead to significant difficulties when developing for the target. In my specific use case, this behavior resulted in an LED flashing when the jumper was not bridged, leading to confusion and misinterpretation of the system's status. It took me more than a week to understand what was happening because debugging step by step using the STMCubeIDE always resulted in the expected functionality. I believe such an issue can arise due to floating inputs and/or electrical noise, mainly if the board is sitting on an isolator.To fix this please make sure to implement pull-up or pull-down resistors in your design to ensure that the GPIO pin h

I've been beating my head for a while trying to use OpenOCD to download my program to the chip, and I'm getting error messages which cite a write algorithm error (errors attached below). I'm not really too sure what I'm doing wrong, and would greatly appreciate any help and insight with resolving this!TL;DR. I'm getting errors likeError: flash write algorithm aborted by target Error: error executing stm32l4 flash write algorithm Error: flash write failed = 00000088 Error: block write failed Error: error writing to flash at address 0x08000000 at offset 0x00000000in the Console log from OpenOCD.I've reproduced the error using OpenOCD with STM32CubeIDE as follows where I set up a fresh project, demonstrate that using ST-LINK (ST-LINK GDB SERVER) works, and finally demonstrate that using OpenOCD fails.I create a new project withFile > New > STM32 ProjectAnd go to "Board Selector", then select the "Commercial Part Number" to NUCLEO-U575ZI-Q.I press "Next >", then fill out the

Hi all,I am using a nucleo board F412ZG with the Middelware FreeRTOS. I use only one task for now, but I will use others in future.By the way, I set TIM2 as the timer system for FreeTOS:Now I am trying to enable pin PC8 as an external interrupt in order to detect a falling edge: When I generate the code I notice that the TIM2 interrupts is deleted, but I do not understand why. Anyone can help me?Below I leave the screens of the generated code modifies from git:      

Hey!I'm trying to run my AI model on my NUCLEO-657X0-Q, following @Julian E. great guide in here.I have 2 questions:1. My model has some running issues during booting.In the FSBL code that suppose to jump to the application (JumpToApplication) there is some crash between the start of __set_MSP() and the start of _set_PRIMASK(), I would say it maybe an error in the pointer to the application code, but when I run it step by step in the IDE's debugger it works just fine.Do you have an idea of why would that happen / how to debug it? (I don't have printings at this stage, and turning in the LEDs in the middle of stack switch makes it fail in the debugger too).2. When my model do run (in the debugger) I get to the point where I start the epoch block, but no outputs / epoch end, and it just gets stuck in the loop. Does it happens because it's in debugger mode, or maybe my model is not compatible? when I validated it in CubeMX AI extension it looked ok.Is there any way to debug

Hello. I'm trying to get the LVGL library running on the STM32H7S78. The simple DMA2D variant (LV_USE_DRAW_DMA2D) with 16-bit color depth works perfectly, but it's not very performant.  Therefore, I'm trying to get the LV_USE_NEMA_GFX variant running instead. The basis is LVGL version V9.3, which already runs on an STM32U5 with NEMA_GFX. However, the problem is that it always crashes during initialization in lv_draw_nema_gfx_init(). lv_draw_nema_gfx_unit_t * draw_nema_gfx_unit = lv_draw_create_unit(sizeof(lv_draw_nema_gfx_unit_t)); /*Initiallize NemaGFX*/ nema_init(); draw_nema_gfx_unit->base_unit.dispatch_cb = nema_gfx_dispatch; draw_nema_gfx_unit->base_unit.evaluate_cb = nema_gfx_evaluate; draw_nema_gfx_unit->base_unit.delete_cb = nema_gfx_delete; draw_nema_gfx_unit->base_unit.name = "NEMA_GFX"; /*Create GPU Command List*/ draw_nema_gfx_unit->cl = nema_cl_create(); /*Bind Command List*/ nema_cl_bind_circular(&(draw_nema_gfx_unit->cl)); 

 Issue SummaryOn STM32N6570-DK, enabling ANY peripheral together with ThreadX or FreeRTOS causes an immediate HardFault, even in a minimal CubeMX-generated project with no user code.This includes peripherals such as:DCMIPPLTDCSDMMCUSBUARTI2CSPIGPIO with interruptsDMAAnything beyond simple GPIO outputThe issue is NOT limited to the camera/display pipeline.EnvironmentBoard: STM32N6570-DKIDE: STM32CubeIDE (latest)CubeMX: latest versionFirmware: STM32N6 HAL/BSP (latest)Security Modes Tested:FSBL + Application (secure/non-secure)Non-secure Application only (no FSBL)Both show the same problem.What Works✔ RTOS disabled → All peripherals work✔ Camera + display pipeline works bare-metal✔ GPIO output works with RTOS (LED blink, simple logic)What Fails:cross_mark:ThreadX + ANY peripheral init → HardFault:cross_mark:FreeRTOS + ANY peripheral init → HardFault:cross_mark:Even minimal projects with zero user code crash before scheduler start:cross_mark:Commenting a peripheral moves the crash to

Dear experts,I'm reading RMs for STM32 models with dual flash banks (F4, H7...) and don't quite understand how to use bank switching.Take the firmware update scenario when old firmware is in bank1 and new is programmed to bank2. So it programs some option byte to switch banks and next time should boot from bank2.If the new version is bad, I'd like to boot automatically from bank1. But how? the option byte is written. Is there a way to control bank switch by external pin? On some systems that I've seen before we did it in the following way: we made a simple watchdog (CPLD or whatever) that automatically toggles the boot selector pin. If the CPU does not touch the watchdog in defined time since reset, it will switch the selector pin and reset again.So if the new firmware fails to boot, the system will reboot to the old firmware.I'd like to implement the same on STM32, with external widget if needed, but better without it.On the other hand, for H7 you can define alternative start addresse