Solved

Hi all, apologies if I am missing where this has been explained.  It seems a relatively common question, but I have not found a definitive answer.A legalistic reading of the datasheet says that there is no difference whether the pin is configured as digital I/O or analog input; FT_a still allows 5V (assuming the usual case of min(supplies) = 3.3V).On the other hand, various commenters here and elsewhere (but not ST employees) have insisted that when a pin is configured as analog input, the 5V tolerance no longer applies; i.e. no difference between TT_a and FT_a as far as input voltage tolerance is concerned.  See e.g. this thread:https://community.st.com/t5/stm32-mcus-products/maximum-allowed-voltage-on-stm32h755xih3-adc-pin/td-p/669693The problem is that this assertion seems to have no support in the actual datasheet.  Or if it does, I haven't been able to find it.  (I would appreciate someone quoting me "chapter and verse" in that case!)Would someone please clear

Greetings,I am very new to ST MCU development, but not new to embedded development. I've developed professionally on Microchip, Qorvo,,and Renesys for the last 20 years.  I am working on bringing up the kit in title. I was successful in generating compiled code for the ElectronicSpeedControl_ESC-G4 project in ST Motor Workbench 6.4. I am working with the latest tools from your website. I did use the stand alone Motor Profiler tool (v5.4) to run a profile on a drone motor successfully, but I quickly realized that it generated XML files for profiles. I figured out that the new version of MP was embedded in WB and produced JSON files. So I proceeded down that path. I could connect the kit to the newest version of MP, but it said I need a "Profiler" version of FW on my kit. I had downloaded the compiled non-Profiler version. This is where it went off the rails. When created a brand new project with the kit and a 24V motor selected from the default group of motors and I check

I am using a pcb4188_vd66g1 camera module with a Raspberry Pi 5.The system has been freshly set up with Raspberry Pi OS 64-bit, and I followed the official setup guide step by step.After completing the setup:The camera is detected correctly when running rpi-hello --list-cameras. However, when I run rpi-hello, no image is displayed (black screen), and an error message appears (see attached screenshot). Modified versions of the command do not work either The camera is also recognized at startup (dmesg as well), as confirmed by the output of v4l2-ctl --list-devices. I have also read through several forum threads on this topic and have already tried many of the suggested troubleshooting steps, but the issue persists.Could you please help me identify what might be causing the problem and how to resolve it? Additionally, I noticed the following behavior:During setup, I only ran sudo apt update but did not perform a full upgrade.After running a full system update/upgrade later, some Ras

Hi all,I'm using an STM32U5G7VJT6Q on a custom design PCB. From the application, I jump to the USART (UART1) system bootloader. I then try to connect to the bootloader via STM32CubeProgrammerCLI. The jump to the bootloader appears to be correct and the bootloader is starting ( connect and properly read chipID) . Unfortunately, communication with the bootloader shows some errors. Especially with some Flash locations like 0xBFA07A0. RDP is set to AA ( Level 0 - no protection )TZEN is not set -------------------------------------------------------------------STM32CubeProgrammer v2.20.0 -------------------------------------------------------------------Serial Port COM3 is successfully opened.Port configuration: parity = even, baudrate = 115200, data-bit = 8, stop-bit = 1.0, flow-control = offNo Init bits value is : 0Sending init command: #byte 0x7F sent successfully to targetWait ends after 1 loop, dataready = 1, delay = 2#ack Received response from target: 0x1fActivating de

Dear,For a given HDPL, how many 256-bit AHKs (Application Hardware Keys) can be stored in the option byte keys?And how many of those are:only usable by SAES?usable by software?The reference manual states the following:5.2 FLASH main features:"Up to 1 Kbyte of protected non-volatile option byte keys, readable either by software orusable as a secret AES key through SAES peripheral (as AHK keys)"It is unclear whether this is for just one HDPL, or whether this is a grand total comprising all three HDPLs that support option byte key storage (HDPL0, HDPL1, HDPL2).Suppose it is for just one HDPL, then this would be able to store 32 (= 1 K byte * (8 bit / byte) / 256 bit) 256-bit AHKs. This seems to be a reasonable assumption since if it were for all three HDPLs, this number would have to be divisible by 3, which it is not (32/3 = ~10.667).5.9.18 FLASH option byte key control register (FLASH_OBKCR):"OBKSIZE[1:0]: Option byte key sizeApplication must use this bitfield to specify

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.