Solved

Hello I am trying to implement I²C slave on a STM32U385RGTxQ in non-blocking mode, on I2C2.To match I²C standard I tried to use the Address macthed interruption but the interruption is never trigged. I used the function HAL_I2C_EnableListen_IT(&hi2c2) to enabled it; My issue is, I don't reach neither the I2C2_EV_IRQHandler(void), the I2C2_ER_IRQHandler(void) or the HAL_I2C_AddrCallback() when sending the slave address.  Please found attached my project. And bellow some pictures of my I2C2 init, an oscilloscope capture and my I2C2 register when I am in debugger :         Best Regards Thibaud HABRAND      

Hello,I've just received my fresh new SMT32H747I-DISCO dev board and I wanted to try some samples.I have some experience deveolping on embedded Liuxes, but this is my second MCU (the first one was a Raspberry PICO, don't know if this counts). I am using a MacBookPro with Apple silicon (M3) and MacOS 14.4What I have done:read the specs, configured the board to get power and STLink from CN2 (as is by factory)installed every tool available:STM32CubeProgrammerSTM32CubeIDE (which also installed a SMTLink server nstall ,st-stlink-server.2.1.1-2, installed successfully ) even STM32CubeMXconnected the board to a USB-C port on my Mac via a USB-C to USB-B mini cable2 times out of three the main led (LD10?) starts red, then flashes red/green then stays green. The other times the board LED stays red. In either case, nothing on the LCD display. to me the board seems waiting.On the former occurrences, MacOS then asks me for permission to connectbut that's it. I wanted to install the Tutti Fruit

I am not able to erase a section of internal flash of the NUCLEO-H633RE.Using the debugger I see the Flash is all 0x00 before I try to erase.  I verify that Flash is not locked i.e.if (*FLASH_NSCR && LOCK) { *FLASH_NSKEYR = 0x45670123; *FLASH_NSKEYR = 0xcdef89ab; }then I try to erase a section of Flash i.e./* ************************************************************************* */ /* */ /* EraseFla - Erases 8K page of Flash, Waits for Flash not busy. */ /* Inputs: uint32_t page holds the page to erase. */ /* Outputs: None */ /* */ /* ************************************************************************* */ void EraseFla(int EraPage) { while (*FLASH_NSCR && BSY){}; n = *FLASH_PRIVCFGR; // just testing n = EraPage >> 7; if (n && 0x0800) { n &= 0x07C0; n |= 0x80000004;} // BKSEL and SER else { n &= 0x07C0; n |= 0x00000004;} *FLASH_NSCR |= n; *FLASH_NSCR |= STRT; while (*FLASH_NSCR && BSY){}; }  With the debugg

Hey!Does anyone recognice this part?It`s marked with C306 (ST- Sign) FRO169.It looks like a transistor or diode in SOT-229 package.Thanks!Frank

Hello,The latest version of STM32CubeMX no longer lists x-cube-spn5 as an available package.Could someone help me how to use a X-Nucleo-IHM05A1 expansion board with the latest tools please? 

Good morning everyone, I have this Mini STM32F103C8T6 CH340 board which supposedly has the original chip (photo), I configure it as suggested in a post I saw here but it gives an error (attachment).Does anyone have a solution?Edited to place Images in-line for easier viewing:  

Hi everyone,I'm experiencing a very specific bus/clock issue on a custom board using the STM32U5G9ZJ (and also tested on STM32U5F9ZJ).The Problem: My display (320x240, RGB565 via LTDC) only works if the HSPI1 peripheral is enabled in CubeMX. As soon as I disable HSPI1 (which I need to do to free the PH9 pin for power management reasons), the screen turns grey, even though the LTDC settings remain unchanged.Key Technical Details:Data Location: All assets (images/fonts) are stored in Internal Flash memory. The HSPI/OctoSPI bus is NOT used during the display process.Memory Status: In Debug mode, I can confirm via the Memory Browser that the Frame Buffer (located at 0x20025800) is correctly populated with pixel data.LTDC Behavior: Despite the RAM being correct, the LTDC fails to output data to the panel when HSPI1 is OFF.Configuration: Pixel Clock (PLL3R) is at 200MHz, GPIOs are "Very High Speed", and the Frame Buffer is placed to avoid conflicts with the RTOS (ThreadX) heap.The Mystery: W

Hello!I have implemented one of the key parts of a speech recognition system on the STM32N6 without using the cloud. I would like to describe my results in more detail, but it seems to me that the “New Message” section is not the right place for that. Could you please advise me where it would be better to share this? 

For our product we use sliders to set parameters in our software. Some parameters effect the range of others at runtime. Sometimes the allowable range of the values is limited to a single value. In such a case min equals max. This leads to an assert error in the simulator and undocumented behavior on the target.We would like to see support for min=max. One way to implement it is to show the Indicator Image in the center (or left),  disable sliding, and set the value=min=max. This would simplify our firmware since we wouldn't need to handle it as a special case.I also added the tag bug-report since undefined behavior on the target is unacceptable.

Hello, I am experiencing an I²C communication issue between my MPU6050 sensor and an STM32F429I-DISC1 board. The sensor is properly powered at 3.3 V, and I have already verified its operation with an ESP32 board (communication is successful). However, with the STM32, no communication is established. Actions performed: Configured I²C1 on the STM32 (tested in fast mode at 400 kHz and standard mode at 100 kHz) Verified the MPU6050 address (default 0x68, AD0 pin connected to GND) External pull-ups: tested with and without 4.7 kΩ resistors on SCL and SDA Checked physical connections (SCL to PB6, SDA to PB7 for I²C1 on the board) Configured the LCD screen Observed behavior: The I²C scan does not detect any address Blocking point: The same sensor, using the same basic I²C code, works perfectly on the ESP32. Therefore, the sensor is not the cause. The issue appears to be related to the I²C configuration on the STM32 or a hardware detail. Question: Has anyone encountered this behavior with

Hello,I currently need to transfer ADC data from a nucleo-n657x0Q to a PC. I've configured the stm32n6 using ST's example on GitHub, but I still don't know how to use the `ux_device_class_cdc_acm_write` function to transfer the data.Can anyone guide me on how to transfer data using this USB HS?

Hi,This is my first time using an STM32N6 without internal flash, and since I am right before handing over files for artwork, I would appreciate it if you could check if the power lines and XSPI memory connections are correct.I have searched around a lot, but since it is my first time, I feel a bit nervous, so please let me know if everything is correct.>I looked it up and found that to boot via Nor-Flash (quad), I need to connect XSPI1 to XSPIM_P2. Also, since I try to connect the 16-bit PRAM in DTR without DQS mode, I connected it as XSPI2->XSPIM_P1. Is this correct? I really need to BOOT via Nor-Flash and use PRAM after that. (swapped mode? in CubeMX)>This is the power line. It operates at 1.8V, and an STM employee told me to connect all CSI/USB lines to ground if I am not using CSI/USB. Is this the correct way like this all? I won't be able to fix it if the power section is wrong, so I would really appreciate it if you could let me know.  

Hi, You know, there are some strict requirements about MCU used in optical module or production,  which include1. Size and package2. Internal resource3. IO amount, especially  ADC and DAC with >= 12bit resolution which be used to monitor signal and control4. Power efficiencyCould you please recommend latest ST MCU which are used widely in ultra high-speed optical module such as OSFP and NPO? or, share me roadmap about ST MCU series used in optical production? Thanks in advance!Best regards!Jason

I have this Riverdi board with a STM32H757XIH6 microcontroller. I have been using it consistently and loading touchgfx programs on it.  Today I was trying to use the 40 pin header and program one of the gpio pins on it to act as a gpio output. I put an led on a ground and the PA4 pin, which was the pin I was using on the 40 pin header, to verify the toggling code was working.  Nothing happened and so I tried to load a basic program onto the board using stmcubeMX and selecting the  STM32H757XIH6 microcontroller.   I selected the PA4 pin on the .ioc file and generated the code.  However, when trying to run the program I get this error, . Not sure if it was that program or touching the multi meter to certain pins that cause a hard fault or something.  I would not think a multi meter could do anything like that, but I'm trying to figure out why all of a sudden I am unable to upload a program to the board when I have been consistently.&nbsp

Software Versions: - STM32CubeMX: 6.15.0 - MCU: STM32G474QET6 - Firmware Package: STM32G4xx HAL Library V1.6.1 Bug Description: CubeMX 6.15.0 generates incorrect HRTIM deadtime prescaler macro definitions. These macros do NOT match the register bit definitions described in the STM32G4 reference manual (RM0440). This is a code generation bug in CubeMX, not a HAL library issue.  Old Correct Macros (Previous Version): #define HRTIM_TIMDEADTIME_PRESCALERRATIO_MUL8 (0x00000000U) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_MUL4 (HRTIM_DTR_DTPRSC_0) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_MUL2 (HRTIM_DTR_DTPRSC_1) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_DIV1 (HRTIM_DTR_DTPRSC_1 | HRTIM_DTR_DTPRSC_0) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_DIV2 (HRTIM_DTR_DTPRSC_2) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_DIV4 (HRTIM_DTR_DTPRSC_2 | HRTIM_DTR_DTPRSC_0) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_DIV8 (HRTIM_DTR_DTPRSC_2 | HRTIM_DTR_DTPRSC_1) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_DIV16 (HRT

..

STM32CubeProgrammer has a C++ API which allow to create program compiled using qt creator. Is it possible to compile for linux os and run in rasperry os which is debian based?

..

We want to use the Sensor TileBox pro to measure temp pressure and acceleration in structures.   We have been using some of your boards the MKI versions and they will run at a maximum of 1400 time steps per second when configured for about 2000.   I have the tilebox pro exporting on the USB and picking it up with a new C# program.   See below.  It is reading at 18 cycles per second, I need to adjust the freq output, I thought I had a higher rate.  it is really easy to use, but I have the Android Program setting 75 from pressure and temp and 480 for acceleration and getting 18 time steps per second.  Is this your board's limitation on exporting via the USB cable.   Where am I supposed to post this?  

Hi everyone,I am working on a custom PCB designed , but I’ve run into a hardware design constraint and would appreciate some architectural advice on the best way forward.The Setup:Main MCU: STM32L476 (Programming via STM32CubeIDE / HAL)Coprocessor/WiFi: ESP32-WROOM (Intended to handle AWS IoT connections)The Constraint: The PCB designer connected the STM32 and ESP32 exclusively via an I2C bus. There are no physical UART traces connecting the two chips.The Original Goal: The initial plan was to use the STM32 to write firmware directly to the ESP32 over UART, or to use a UART software bridge, and then use UART for passing sensor data to the ESP32 for AWS publishing.The Dilemma: Because the ESP32 ROM bootloader requires UART0 (TX0/RX0) for flashing, I realize a software bridge from the STM32 over I2C to flash the ESP32 is physically impossible.My Questions for the Community:The Initial Flash: Aside from tack-soldering temporary wires to the ESP32's TX0/RX0 pins to perform the initial flas

Hello,I am planning to use STM32H562RGT6 in my product to communicate and update my firmware via CAN FD.To plan that, I am using STM32CubeMX 6.17.0, the datasheet and the AN2606 (Rev 70).And I would like to use only one CAN FD to communicate and to update my firmware in this MCU. But it is impossible to do this in STM32CubeMX. I have only access to FDCAN1. And there are no FDCAN2 on the pins.So, is it a problem in STM32CubeMX ? Or should we use FDCAN1 to do firmware updates via FDCAN for this MCU ?PS: it is the same problem with the MCU STM32H562VGT6 (and maybe other similar MCUs) 

Title edited to flag that it's a clone ST-LinkI’m trying to flash an STM32G431CB on a B-G431B-ESC1 ESC board for a reaction wheel-based attitude control system. So there’s three ESCs each. For every one, I soldered 4 wires to the J4 SWD pads (SWDIO, SWCLK, 3V3, GND) and connected them to an ST-LINK V2. Just to clarify on my end, the wire colors don’t really follow any convention, so the red wire isn’t 3V~ I followed the schematic image where the actual pinout left to right is SWDIO, SWCLK, 3V, GND, which matches the correct J4 order. STM32CubeProgrammer is not detecting the chip. The error reads: UR connection mode is defined with the SWrst reset mode; but I am getting a target voltage at 3.25V (power is fine), but SWDIO/SWCLK don’t seem to be communicating. All target fields show dashes.I’ve confirmed that the wiring order matches ST-LINK V2 pinout, tried different connection speeds in CubeProgrammer, change the stlink v2 pinout, even changed my ESC (!) and I have the same i

I'm trying to use a Soracom SIM to experiment with the ST87M01 on the plan01s. Its not clear how to set the APN using the ST87M01. I tried AT+CGDCONT=1,"IPV4V6","soracom.io", but kept getting an +CME ERROR: 4.Any advice?  

I have followed the datasheets and tried to calculate my reference voltage. I am supplying steady 3V on Vref+ pin but I wanted to confirm this because I have some troubles with the ADC precision.So I read the internal voltage both on my card and on a nucelo-C092rc. This is my results: My board:Vref+ = 3.0 * 1659 / 1805 = 2.755Nucelo board:Vref+ = 3.0 * 1665 / 1641 = 3.043However I am quite certain that the nucelo boards are using 3.3 V as reference and my board are using 3 V as reference.So if I swap the 3.0 V from the datasheet into 3.3 V I get the following:My board:Vref+ = 3.3 * 1659 / 1805 = 3.033Nucelo board:Vref+ = 3.3 * 1665 / 1641 = 3.348Which match more my expectations, can someone confirm or deny this typo?I add my adc init function:u16 uiDelay = 0; ADC_CFGR2.CKMODE = 0x0; // Clock mode set to ADCCLK ADC_CCR.PRESC = 0x2; // ADC prescaler set to 48MHz / 4 = 12MHz ADC_CFGR1.RES = 0x0; // Set 12 bit resolution ADC_SMPR = 0x07; // Sampling time set to 1,5 ADC clock cyc

Hi there, I want to flash a HEX file using a Raspberry PI. So I followed the steps described here.But if I run this line:$> ./SetupSTM32CubeProgrammer-2.13.0.linuxI get the message:bash: ./SetupSTM32CubeProgrammer-2.13.0.linux: cannot execute binary file: Exec format errorHas someone an idea why this is not working?Im running Raspbian GNU/Linux 11 (bullseye)