Solved

I’m using the X-NUCLEO-BNRG2A1 in network coprocessor mode (UART), but I’m stuck trying to run the BLE_Beacon example.Here is what I have done so far:I followed the AN5651 guide using a NUCLEO-L433RC-P.Since BlueNRG-1ST-LINK does not work on Windows 11, I used RF-Flasher Utility to flash the DTM_UART.hex file onto the X-NUCLEO. I took this hex file from the STSW-BLUENRG1-DK packageThis part worked correctly, and the X-NUCLEO is now configured as a network coprocessor through UART.The problem appears on the STM32 side.The STSW-BLUENRG1-DK package includes several applications such as BLE_Beacon, but they are written for EWARM (IAR) and are not integrated into CubeIDE.I tried flashing BLE_Beacon_NWK_UART.hex to my NUCLEO STM32 board using CubeProgrammer, but after it configured, the communication with the module doesn't work. I assume this is because the application is configured for the NUCLEO-L476RG, not the L433, so the pins or hardware settings do not match.As a result, I’m stuck and

Hello,I'm slightly confused about the options in the STM32CUBE VSCode extension Project setup window.From the left dropdown i can select the Project, where i have options x, x_AppliSecure, x_AppliNonSecure and x_FSBL, for each of the left options, i can select Secure, Secure-only and Non-secure from the right dropdown for the Security model. I haven't found documentation which describes what do these options mean.For example, if i select x_AppliSecure from the left dropdown and Non-secure from the right drop down, which sounds like a conflict, what happens? In which scenario should i choose which of the 12 available Project-Security model combinations? Also, I assume that Secure means Secure + Non-secure, as Secure-only must mean secure only and Non-secure probably means Non-secure only?In the same window, multiple rows can be added to the list from the + button in the bottom right, what do the rows represent?Thanks! 

Hello! I need help. STM32L073RZT6 MCU.How can I write, for example, 2 times 8 Bytes into any second half-page of flash memory?Every first page is recorded successfully and read successfully. For example, I write 8 Bytes of data to the beginning of the _writeBuf buffer (half page size) (fill the rest with zeros), erase the entire page of interest (*(__IO uint32_t *)_write_address = 0;), write _writeBuf to the first half page, the recording is successful. Write a next 8 bytes of data to _writeBuf after current 8 Bytes of data and I write it down in the first half page in the same way, it also goes well. With a similar operation, the first 8 Bytes are written to any second half page successfully, but when the next 8 Bytes are written to any second half page, the NOTZEROERR error occurs.

Hi.I am trying to test out a fault handler for our STM32G (right now, the fault handler just tries to determine the location of the code that caused the fault).If I force a fault (divide by zero) in "normal" non-interrupt handler code, I can easily read the stack frame, find the PC and determine the location of the fault (stack frame is located in the process stack).If I force a fault in an interrupt handler (USART1, using HAL code), the stack frame on the main stack does not make sense to me (what I think the PC is, does not point to a location in flash memory). If I add 0x50 to the address in the MSP, then I can see a stack frame with the correct PC.Is there a section in PM0214 that can explain what I'm seeing?I attached a few screenshots from the debugger in STM32CubeIDE that show the call stack and memory.In my example, the MSP in the fault handler points to 0x2001fde8, and the LR is 0xfffffff1.  The stack frame I'm expecting to see is at 0x2001fe38.Thank you! 

Hello ST Community team,on the MB2046 schematic, there is a button called B3 or Boot mode pin:But the UM3353 (chapter 7.9) mention only B1 and B2:Could you please correct this on the coming doc revisions.Best Regards.II

I am developing a TouchGFX user interface on a STM32U5G9 with a 24bit RGB LCD screen. I have developed the user interface on the STM32U5G9J-DK2 development board, where it works fine. I imported the TouchGFX project on my custom board the framework stops after the first full screen is displayed.As a test I have added a start-up screen with two colored boxes and a image in internal flash. I have configured interactions to jump to the main screen after 3 seconds. When I set a breakpoint inside model.tick(), it triggers before 25 ~30 times before it stops triggering. The other threads of the application run as intended (ThreadX). If I look at the thread list in CubeIDE, the TouchGFX thread has state ready, and it's run count stops increasing after the first frame is displayed on the screen. I compared both projects of the devboard and my projects in cubeMX, and I can't find any differences. I compared both IDE projects with winmerge, but also nothing found which could cause

Hi,I'm searching for a MCU with one or two advanced motor control timers to control 1 or 2 bldc motors.For this purpose I use the MCU selection tool from here: STM32 family of 32-bit microcontrollers (MCUs) - STMicroelectronicsWhen I use the filter for one or two advanced motor control timers the MCUs from the STM32G series are never displayed and I don't understand why? How should I search for all MCUs with motor control functionalities?Thanks for every hint!Best regards,Roger

Hi,still pretty, pretty new to STM32CubeIDE, I'm trying to understand how it works by doing little things. So right now I'm trying to combine both debugger with a terminal both running in STM32CubeIDE.To include terminal in STM32CubeIDE I have followed instruction given here:How to use the STM32CubeIDE terminal to send and receive data (Knowledge Base) So far, running a little test program, I was succesfull doing it at least for very first debug session (i.e. after power cycling the Nucleo-Board). I quit the debug session with the indicated button shown on attached figure belowHowever, when I start a debug session a second time, I get always(!) the same error message (see below)The only way I found so far is to make a hard power cycle to the Nucleo-Board to make it connected in the STM32CubeIDE again.Well, in STM32CubeIDE, because I also installed Tera Term and here everything is working fine. But actually I'm a fan of having thing in one application that can be in one.So my quest

Hello ST Community team.As a user who visits this Community several times a day, I’ve noticed the mixed feedback regarding the full separation between STM32CubeMX and STM32CubeIDE. Personally, I fully support this decision, and I believe it brings a positive direction for the tools. At the same time, I would like to suggest keeping the CubeMX plug-in available as an optional component in future versions of CubeIDE, so that users who prefer the integrated workflow can still enable it if they wish. This could help accommodate the different preferences within the community. Thank you for your continuous work.Best Regards.II

In the lower-end STM32L4, covered by RM0394, SRAM is partitioned into two parts, SRAM1 and SRAM2.SRAM2 (besides being "special" in that it has ECC and automatic erase facities), is mapped at both 0x1000'0000 and at the end of SRAM1 in the 0x200x'xxxx area.In Figure 1 System architecture, SRAM2 does not have the connection needed for that second mapping, i.e. to the S-bus of the processor.JW

Hello everyone! My problem is supposed to be a very simple one. I use an interrupt to send messages to my PC, then I send a message back to my STM32. The message is received in good order but I can't print it out. I watched every single YouTube video out there, implemented every single solution (including connecting the SWO to the PB3 pin) - nothing works so far.Can anyone tell me where am I mistaken? My Debug Configuration:Main.c, main.h, and syscalls.c are attached

In function LL_RTC_ALMB_SetDay of file stm32u0xx_ll_rtc.h line 2198  Original:__STATIC_INLINE void LL_RTC_ALMB_SetDay(RTC_TypeDef *RTCx, uint32_t Day){MODIFY_REG(RTC->ALRMBR, (RTC_ALRMBR_DT | RTC_ALRMBR_DU),(((Day & 0xF0U) << (RTC_ALRMBR_DT_Pos - 4U)) | ((Day & 0x0FU) << RTC_ALRMBR_DU_Pos)));} Missing x in RTC->ALRMBR __STATIC_INLINE void LL_RTC_ALMB_SetDay(RTC_TypeDef *RTCx, uint32_t Day){MODIFY_REG(RTCx->ALRMBR, (RTC_ALRMBR_DT | RTC_ALRMBR_DU),(((Day & 0xF0U) << (RTC_ALRMBR_DT_Pos - 4U)) | ((Day & 0x0FU) << RTC_ALRMBR_DU_Pos)));} Personal opinion: I would recommend compiling code with the -Wall, -Wextra, and -pedantic compiler flags.From my point of view, confidence in the quality of code that contains such easily detectable errors is greatly limited. For this reason, I prefer not to use HAL drivers. 

Hi What is the function of the RES pins on the ASM330LHHX?The datasheet indicates: “Connect to VDDIO or GND.”Is there a preferred connection?Can I add a 4.7 kΩ pull-up or pull-down resistor?BR

Hi, I’m trying to better understand how the USB PMA and BTABLE work on the STM32F103. After reading the reference manual, I’m still unsure how the descriptor table size relates to the number of endpoints.I have two possible interpretations of how the USB Descriptor Table and PMA layout work on the STM32F103, and I need clarification from ST to confirm which one is correct.I will provide two diagrams (Figure A and Figure B) to illustrate the scenario, assuming BTABLE offset = 0.Scenario: BTABLE = 0x0000Figure A (Fixed 8×8 bytes BTABLE)In this interpretation:The USB descriptor table is always 8 × 8 bytes = 64 bytes (0x0000–0x003F), assuming the device supports 8 endpoints.The usable PMA buffer area always starts at 0x0040, regardless of how many endpoints are actually used (for example, even if only 3 endpoints are used).Therefore the usable PMA region would always be 0x0040–0x0200.Question A:Is this interpretation correct? Is the descriptor table size always fixed at 64 bytes in the STM

Hi,In the GPIO interrupt configuration, the port information is ignored and only the pin number is used for identification. As a result, pins with the same pin number on different ports cannot be enabled as interrupt sources at the same time. stm32_gpio_irq_line_t stm32_gpio_intc_get_pin_irq_line(uint32_t port, gpio_pin_t pin){    ARG_UNUSED(port);    return linenum_to_ll_exti_line(pin);} int stm32_gpio_intc_set_irq_callback(stm32_gpio_irq_line_t line, stm32_gpio_irq_cb_t cb, void *user){    const struct device *const dev = DEVICE_DT_GET(EXTI_NODE);    struct stm32_exti_data *data = dev->data;    uint32_t line_num = ll_exti_line_to_linenum(line);    if ((data->cb[line_num].cb == cb) && (data->cb[line_num].data == user)) {        return 0;    }    /* if callback already exists/maybe-running return busy */    if (data->cb[line_num].cb != NULL) {&nbsp

I am using STM32 Nucleo-l476rg. I am trying to use the CAN peripheral and have tried every resource I came across. I am unable to send or receive messages:I have no filter, everything is wired correctly, what could be the issue? I even made it so that it just toggles an LED when the interrupt occurs. In case the interrupt is not set up properly, I have it polling HAL_CAN_GetRxFifoFillLevel, and if it is >0, it toggles the LED, but the LED never toggles. Am I missing something that is not autogenerated after configuring the peripherals in the .ioc file? In all the videos I have watched, it seems quite straightforward. What am I missing?

Owing to a developer (me) firmware blunder, I successfully "bricked" several STM32C011J6 (SO8 package) devices so that I cannot access them using STM32CubeProgrammer and STLINK.My error was this - my firmware reconfigured pins 7 (SWDIO) and 8 (SWCLK) as GPIO immediately after reset and also initialized pin 1 (nRST) as GPIO at the same time (rather than looking for another pin (button press during power up) that would have held off these steps).After my errant firmware was installed via STM32CubeProgrammer and STLINK, the STLINK device was/is no longer able to connect to the device.I am using STM32CubeProgrammer version 2.21.0 and a USB-attached STLINK device.I have transplanted one of the affected (few) devices to a PCB containing only a connector for the STLINK device, power, ground, and Pin 1 (NRST), so there is no other hardware potentially interfering with STLINK connection.As pin 1 (nRst) was repurposed at start-up time, I don't believe hardware reset (set by STM32CubeProgrammer)

Hi, I am really struggling to get clangd to work correctly in a setup I am trying to get going. I'm new to this VSCode workflow, and am finding VSCode seems to have a lot of persnickety behaviors that really require a lot of specificity to get things working right. Here is what I am trying to do:I start with a fresh workspace, and ONLY the STM32Cube vscode extension pack installed. I add two folders to my workspace:an stm32 project folder, as created by cubeMXa shared_code folder, which contains multiple subfolders, each of which contain .c/.h files. Nothing particularly fancy here. I can get this setup compiling fine, but clangd is complaining about various #include files in my shared code area. I understand that the reason for this is because there is no .clangd file in my shared_code area, so clangd can't "see" it from my project area. Intrepid internet searching has led me to adding this to my code-workspace file:{ "folders": [ { "name": "stm32_project", "pa

Hi, please can someone help me?when I try to deploy I get the following error:Spoiler (Highlight to read)PayloadTooLargeError: request entity too largeat readStream (C:\Users\diego.mavillonio\AppData\Local\STM32CubeMonitor\resources\app\node_modules\raw-body\index.js:163:17)at getRawBody (C:\Users\diego.mavillonio\AppData\Local\STM32CubeMonitor\resources\app\node_modules\raw-body\index.js:116:12)at read (C:\Users\diego.mavillonio\AppData\Local\STM32CubeMonitor\resources\app\node_modules\body-parser\lib\read.js:79:3)at jsonParser (C:\Users\diego.mavillonio\AppData\Local\STM32CubeMonitor\resources\app\node_modules\body-parser\lib\types\json.js:138:5)at Layer.handle [as handle_request] (C:\Users\diego.mavillonio\AppData\Local\STM32CubeMonitor\resources\app\node_modules\express\lib\router\layer.js:95:5)at trim_prefix (C:\Users\diego.mavillonio\AppData\Local\STM32CubeMonitor\resources\app\node_modules\express\lib\router\index.js:328:13)at C:\Users\diego.mavillonio\AppData\Local\STM32CubeMon

Is there an option in the STM32CubeIDE settings to reset to factory settings or something like “Default Settings”?I can’t restore the console window to its original state. When I compile the code, the console window used to appear at the bottom, but now it doesn’t show up anymore.

Hello,I recently bought the newly released development kit STM32N6570-DK that includes a touch screen and a MIPI camera manufactured by ST. It comes preprogrammed with some nifty demos, including the AI demo which should show off the AI capabilities with a stream from the included camera. When I load the AI demo the screen freezes up, and I can see the backlight to the screen turn off.Additionally I noticed there are some level shifters (TR1 on the camera module) on the PCB for the camera that either carry a clock or data line for MIPI. When I activate the demo the 3.3V line starts toggling at about 160MHz for about 2ms, and then stays low after that.For reference, I am powering the dev kit off of a USB 3.0 port on my laptop.Could you help me identify if this is a camera module, dev kit, power, or cable issue?Thanks,-Alex

Hi, I am using 2 FDCAN ports on my custom board with STM32G0B1x MCU. As per application note AN5348, I can set message RAM offset for second port. But I don't see this setting in STM32Cube MX. As per reference manual, I got following details: But I am not sure where to set start and end addresses. Please help. Thanks, Pradeep      

Hi, the current STM32CubeIDE for Visual Studio Code 3.6.4. (and maybe before) "Create empty project" generates in CMakeLists.txt # Core MCU flags, CPU type, instruction set and FPU setup set(cpu_PARAMS # Other parameters # -mthumb # -mcpu, -mfloat, -mfloat-abi, ... )The comments are misleading, because in cmake\vscode_generated.cmake:set(cpu_PARAMS ${cpu_PARAMS} ${CPU_FLAGS})and therefore, my cpu_PARAMS will be combined with the CPU_FLAGS which already include -mcpu etc.which effectively overwrites my settings.hthKnarfB

Hi,I'm facing some issues with some STM32G474RET6s, and want to rule out counterfeit chips, even if that seems unlikely.After googling for some solutions, I confirmed the AP IDR register and the DBGMCU_IDCODE both hold a revision ID of 3, which I expected from the X code on the label. However, I noticed that the markings on the chip match the LQFP80 footprint, rather than the LQFP64 we purchased.I have read the qualifications about how device markings can differ, but it doesn't hurt to ask: is this outdated documentation, or is there a possible issue?Thanks.

Hi, When I create a new project on STM32CubeMX, it either freezes when I try to set up some peripherals, or I just get a blank screen when I try to reopen the porject after generating the code. I have tried rolling back to an older version, completely reinstalling, tried it on an ubuntu VM, switched devices, but nothing worked. kind regards, Sam