Solved

Hi,Many thanks for the experimental incremental flash feature! For me it speeds up the dev cycle considerably.  (Note https://wiki.st.com/stm32mcu/wiki/STM32CubeProgrammer_errata_2.21.x seems to be broken.)Dan 

Does the STM32N657 run AzRtos / threadx / filex / etc?  The libraries don't seem to be available in the latest IDE.  Is this coming soon?

Hi,I have a project derived from the demo6 from ST on the STM32U5G9J-DK1 devkit, where I want to display SVG images. The only difference is that the rounded display of the original kit has been substituted with another rounded display of the same resolution (480x480 pixels) but smaller. The PCB of the display is then different as well as the display driver chip which is driven through MIPI-DSI commands (and not using video mode of MIPI-DSI like the original demo is). I'm using latest version of TGFX 4.25.0.All the subdemos of this demo6 project are working the same as on the original display, but not the SVG subdemo. All the .SVG images of this specific sub demo, which should animate and start bouncing on the screen, are simply not rendered at all. I only see the background image which is a .PNG file. And I can come back on the main screen as the touch display is working.I tried to strip down this demo6 project and display a simple background .PNG image and on top of this last, some .S

I have a question regarding the use of the STSAFE-A110.Currently, the default I2C address of the STSAFE-A110 is set to 0x20. It is possible to change this address?If it is possible, could you please explain how to do it? Thank you in advance for your assistance.

In my project for an STM32H7S3, I'm using the Ethernet module, and it works fine.However, I don't need the ETH_CLK pin. In RCC settings, there's an option which suggests I can turn it off; however, clicking the tickbox has no effect. (Note also that the text for this option is "Digital clock input" - even though the pin is an output.)Instead, I can set the pin itself to its Reset state, and that works. However, next time I open the IOC file, that setting is missing, and I have to change the pin state again. In addition, if I save the IOC file without making any changes at all, I can see in the diff that the settings for that pin have been changed:Previously, the generated value of ETH_CLK was outside its valid range (HSE was too low, and any setting from PLL3S was too high), and even though I wasn't using it, Cube wouldn't let me generate code without disabling this pin, because ETH_CLK is an input to the ETH Clock Mux, and presumably all inputs to this mux must be valid

The VSCode extension RTOS Views (and STM32Cube RTOS Views) does not support ThreadX, which is one of the two RTOS officially offered by ST. Are there any plans to add this support, or make the new toolchain compatible with the Microsoft Embedded Tools extension? In this state the new toolchain is quite useless for ThreadX applications.Best regards

 I'm trying to build a simple HTTP server using Mongoose with the LWIP IP stack on FreeRTOS CMSIS_V1. It is important that I let LWIP handle the network interface since I'm also using it to advertise a service using mDNS. This is what my task looks like:void StartMongooseTask(void const * argument) { /* init code for LWIP */ MX_LWIP_Init(); /* init code for USB_DEVICE */ MX_USB_DEVICE_Init(); while (netif_default == NULL || !netif_is_up(netif_default) || !ip4_addr_isany_val(*netif_ip4_addr(netif_default)) ) { osDelay(100); } extern struct dhcp_state_enum_t; struct dhcp *dhcp_client = netif_dhcp_data(netif_default); while (dhcp_client == NULL || dhcp_client->state != 10) { osDelay(100); } ip = *netif_ip4_addr(netif_default); printf("IP acquired: %u.%u.%u.%u", ip4_addr1(&ip), ip4_addr2(&ip), ip4_addr3(&ip), ip4_addr4(&ip)); mdns_resp_init(); mdns_resp_add_netif(netif_default, "22223335", 3600); mdns_resp_add_service(netif_defa

Hardware Design Observations for STM32N6570-DK and STM32H747I-DISCO BoardsWhile working with the STM32N6570-DK and STM32H747I-DISCO boards, I noted a few aspects of their hardware design that could be improved for usability.1. Shared I²C Bus Between Codec and TouchscreenThe shared I²C bus used by the audio codec and the touchscreen looks elegant from an architectural standpoint, but in practice it creates some challenges.1a. Access to the codec can take a relatively long time, while the touchscreen is accessed internally by the TouchGFX library.Although mutex protection can be implemented in the BSP to manage concurrent access, this does not fully resolve the issue — touchscreen responsiveness can still be affected.1b. On the dual-core STM32H7 board, if one core manages the codec and the other handles the display, additional synchronization is required to ensure safe concurrent access. This can be achieved, but only with extra development effort.Proposal:Connect the codec and display t

Good day. I am working on a 32-pin STM32U083KCU6. This requires the use of LSE 32.768kHz crystal. I referred to AN2867 as the oscillator design guideline.The LSE has the following specs:Shunt capacitance - 1.15pF,ESR - 70k,Load capacitance - 7pF.Calculated crystal gm is less than the STM32 Gmcrit so I think this crystal is ok to use.My concern is the determination of Rext value as the measurement of the current through the crystal is not an easy measurement. To set baseline in the Rext value, I used the evaluation board NUCLEO-U083RC as reference since it uses a similar STM32U083RCT6. Looking at the evaluation board schematics, I see that the Rext R34 and R35 are both set to 0R. The LSE used in the evaluation board is NX2012SA-32.768KHZ-EXS00A-MU00527 which has a max level drive of 0.5uW. May I ask to what drive level is the MCU set to drive the crystal in the evaluation board? What is the power level the MCU drives the crystal considering the max level of drive of the LSE is 0.5uW? Ap

I don't know if this is caused by the vscode extension or stm32cubeclt, but after the installation(everything related to the extension works), I noticed that the system path variable had been modified to add stm32cubeclt bin directories(I found this script: /etc/profile.d/cubeclt-bin-path_1.15.1.sh).Is this normal? I want to use my system default cmake, is there a workaround instead of using /usr/bin/cmake every time?I'm using debian 12.

I'm currently encountering an issue with the P-NUCLEO-IHM001 motor. I'm using STM32Cube version 6.10 and X-CUBE-MCSDK version 5.4.8. During file generation, the problem shown in the image has arisen. How should I resolve this? *This post has been translated from Chinese to comply with the ST Community guidelines.

1. How does the STM32H562RI MCU burn firmware into the internal flash of the MCU? What Settings need to be made for hardware or software? Can it also be burned to an external flash? How is it operated?2. Can the STM32H562RI MCU be boot from an external flash? How was it achieved?

Hi all,I am using an STM32H563 (device ID 0x484).When attempting to update the MCU firmware using stm32flash 0.7, I am encountering the following error.=============stm32flash 0.7http://stm32flash.sourceforge.net/Interface serial_posix: Baud Rate : 115200, Data Bit : 8, Parity : E, Stop Bit : 1GET returns unknown commands (0x50)Unknown/unsupported device (Device ID: 0x484) I would like to know what the 0x50 command is and what content should be added to devices[] for the STM32H.The following is what I found through a search, but I don't know if it's accurate.=============const stm32_dev_t devices[] = {/* ID "name" SRAM-address-range FLASH-address-range PPS PSize Option-byte-addr-range System-mem-addr-range Flags *//* H5 *//* {0x474, "STM32H503xx" , 0x20004000, 0x20008000, x , x , x, x, , x , x , 0x0BF87000, 0x0BF90000, x}, *//* {0x484, "STM32H563xx/573xx , 0x20000000, 0x200A0000, x , x , x, x, , x , x , 0x0BF97000, 0x0BFA0000, x}, *//* {0x478, "STM32H523xx/33xxx , 0x20004000, 0x20

Hi Guys, for an internship I am making a dual channel datalogger. So for that datalogger, I am using DS1338 RTC. Now instead of doing I2C normally, I am doing Bit-banging. I am using Nucleo-F030R8 board for my prototyping and I am using PA0(SDA) and PA1(SDA).  After using DSO I was able to verify start condition, stop condition and slave address transfer. Also I tried to test ack by manually pulling the sda down and the output was as expected.  Now the issue is I am not able to write or read the RTC and I am getting FFFF while reading it. And there are no hardware issues as I have tested the RTC. This makes me think there is problem with my I2C read function. Following is the snippet of code I am using for this purpose -#define I2C1_SDA_HIGH() (GPIOA->BSRR = (1U << SDA1_PIN)) #define I2C1_SDA_LOW() (GPIOA->BSRR = (1U << (SDA1_PIN + 16))) #define I2C1_SCL_HIGH() (GPIOA->BSRR = (1U << SCL1_PIN)) #define I2C1_SCL_LOW() (GPIOA->B

Hello,I am working with an STM32U585I-IOT02A development board and using STM32CubeProgrammer.I changed the RDP level to DC and set a password. After that, I am unable to get back to RDP level AA.I tried entering the correct password, but the unlock option does not disable the protection.I also attempted the "unlock RDP1 level" process, but it does not seem to work.Currently, I am unable to flash any code onto the device.Is there any way to recover the board back to RDP AA level and make it programmable again?What is the correct procedure to unlock the RDP DC level after a password has been set?Thanks in advance.

Hi. I recently started using set "NUCLEO-L476RG" and "NUCLEO-NFC08A1"..I launched the existing "NFC08A1_PollingTagDetect" project, which works via SPI, and everything worked fine.Then I decided to redesign the project for I2C. I ran into some problems and questions.Questions:1) According to the "X-CUBE-NFC6" manual for implementing I2C:3.5.1:• solder ST2 and ST4 jumpers.• solder R116 and R117 pull-up resistors.• remove the SPI solder bridge.• install the I²C solder bridge.However, according to 6.2 of the same manual:it is also necessary to "Connect jumper wires from ST2 to ST5 and ST3 to ST6."Question: So, which step should I follow? Do I need to connect ST2 to ST5 and ST3 to ST6?2) If I still need to connect ST2 to ST5 and ST3 to ST6, then ST3 is missing in the "NUCLEO-NFC08A1". What should I connect instead?Problems:What I did:Hardware:• solder ST2 and ST4 jumpers.• solder R116 and R117 pull-up resistors.• remove the SPI solder bridge.• install the I²C solder bridge.• solder ST2 to S

We are using the LSM6DSV80X sensor in our battery-powered device for an industrial application. However, we could not find the thermal resistance from junction to ambient (θJA) specified in the datasheet. Could you kindly provide this information to support our thermal design calculations?

Hi everyone,I’m currently working with the STM32H533RET6 and I’m wondering whether an external crystal oscillator is required (or at least recommended) for reliable communication over RS485 and CAN.From my understanding, even at the highest baud rates, the internal clock (HSI) should be accurate enough for both interfaces, since the STM32’s internal oscillator is fairly precise and stable.So my questions are:Is the internal clock sufficient for high-speed RS485 and CAN communication?Under what conditions would it be better or necessary to use an external crystal (HSE)?Thanks in advance for any insights or practical experience!

I have an STM32H753ZI core board and I'm looking for a driver for the ILI9341 TFT. Any ideas?Thank you very much.

I am new to the STM32N6  and wanted to to knwo where could I get the documentation that explains the APIs of every peripheral in the STM32N6 MCU.

HiI am using the function below to erase the flash, but am not able to do the same.I have to erase from address 0x0803E000UL i.e. page 124The function does basically 1. HAL_FLASH_Unlock2. HAL_FLASHEx_Erase(&erase_init, &page_error) - where page is 124 3. reads the erased flash area 4. HAL_FLASH_LockAm I missing something? I would not prefer to run the function in ramI have MCUboot running and my application running on slot 0 is based on FreeRTOS.  I am trying to erase slot1. #define SLOT1_BASE_ADDR 0x0803E000UL void erase_slot1_flash(void) { HAL_StatusTypeDef status; uint32_t page_error = 0; FLASH_EraseInitTypeDef erase_init; uint32_t page_index; /* Determine actual flash size (in KB) from system memory register */ uint32_t flash_size_kb = *(uint16_t *)FLASHSIZE_BASE; uint32_t flash_start = FLASH_BASE; uint32_t flash_end_addr = FLASH_BASE + (flash_size_kb * 1024UL) - 1UL; printf("SLOT1_BASE_ADDR = 0x%08lX\r\n", (unsigned long)

Hi All, I am a newbie to STM32L432 boards. I am seeing that when i power the STM32L432 board with USB then everything is fine and my code runs and LED stays solid RED.But if i try to start the STM32 board with only VIN i.e. +7V then the RED led i.e. LD1 keeps blinking. I have checked that i followed this -   This procedure also works fine - 1) Power up the board using VIN of +7V and LD1 keeps blinking.2) Connecting USB then the LED LD1 turns to solid RED and then disconnect that cable after 5 seconds.3) Then continue to use this. I am guessing here that it is something to do with the bootloader not being able to run from Flash ? But how come just connecting the USB makes it run fine. Is this a known bug ? 

Hello Experts,I am looking for a solution in which we can create STM32 project with .ioc file and generate the code but cmake as build tool instead of make.I know we have couple of options while creating new project as follows:We can either create STM32 project which allows to have .ioc file and can generate code but that is make file-based project.If create CMake project, then it doesn't have .ioc and code generation feature.In past, I created STM32 project and on top of that added CMake list files but want to know is there any better option.Thanks in advance.

I'm losing my mind a little, because this seems like it should be a simple task. I have configured my I2C module to enable DMA and interrupts: I can confirm that my call to HAL_I2C_Master_Transmit_DMA returns OK. I can also confirm that the generated DMA1_Channel2_IRQHandler is called. That's where things start breaking down. Other modules in the HAL library give you a hook (e.g.HAL_GPIO_EXTI_Callback) signature that you can implement and have it be called by the HAL top-level ISR, but it seems like DMA has not implemented that. Instead, the HAL DMA module implements HAL_DMA_RegisterCallback, and you can successfully call it - but then those callback pointers are overwritten by ones in the HAL itself. OK... so then I tried copying some of the code from HAL_DMA_IRQHandler to (re-)determine which DMA flag applies: static void dma_states( const DMA_HandleTypeDef *restrict hdma, bool *restrict is_complete, bool *restrict is_error ) { const uint32_t flag_it = h

Hello ST community.Based on the content of this page, there should be ACIM example files for V/F and FOC motor drives, but after downloading both MCSDK 5.4.7 and 5.4.8, i found no ACIM example file for this topic in MC Workbecnch. Where shoud i get these files?Thank you for your time and support.