Solved

Hello,I am trying to run a touchscreen with STM32H7R7L8Hx and I am having multiple issues.This is the structure I used, I am using FreeRTOS and TouchGFX in the STM32CubeMX. Years ago I run a touchscreen with STM32H7A3RITx, it was easy because it was not asking project structure.When I add FreeRTOS it is adding both locations, I know I can simply exclude from build the top one but there are more issues. In the TouchGFX Designer it can't find the project file so it can't add include paths and source files correctly, so I have to make it manually. I think this is the most important problem, TouchGFX uses older version of FreeRTOS but STM32CubeMX adds newer version of FreeRTOS and I am not able to select FreeRTOS version.STM32CubeMX Version: 6.16.0TouchGFX Version: 4.26.0How can I solve these issues? Thank you.

I have been working on an IoT project using STMicroelectronics' STM32 microcontrollers, and I have encountered a unique challenge around power management. My system needs to run on minimal power to ensure long battery life in remote applications, but I am facing issues with inconsistent power consumption during sleep modes.Here’s the problem:Despite using the low-power modes like Sleep, Standby, and Stop in STM32, I am seeing unexpected power drain when the device is supposed to be in a low-power state.I have implemented HAL libraries and checked my hardware, but I still get around 10-20mA of current draw when the microcontroller is supposed to be in the Stop mode.Some potential solutions I have considered:Reviewing the clock configurations to ensure the system isn't inadvertently running unnecessary peripherals.Using the dynamic voltage scaling feature, but I'm not sure if I’m configuring it properly.Checking for interrupt handling issues that might keep the MCU active unintentionally

Hi,I’m trying to read internal temperature sensor on ADC1, but the ADC result is always 4095.I use STM32L471, and I know that the problem is not HW related, when I run a different bin it reads the temp ok.Tried to read VREFINT, raw value is also 4095.Attached below screenshots with clock tree configuration and code.p.s. also tested with different clock speeds and sample cycles with no luck.    

Hello, I have been trying to make the AEK-MCU-LNK work with my SPC56 discovery board with OPENOCD (I reached a dead end trying to make the .cgf files). So I have two questions:1.- I understand that the AEK-MCU-LNKU works with this SPC56 family using UDE. Is that true?2.- I saw in another post (https://community.st.com/t5/automotive-mcus/stellarlink-vs-spc5-udeskt/td-p/64794) in the last answer, that AEK-MCU-LNK with the UDE driver should work with SPC56 family. Can you please confirm this?Thanks,Agustín

Sir can i use the stm32 cube ide for the commercial in free of cost. is there any limitation pls tell me

We have a query regarding STM32U375 PKA peripheral.As per datasheet, the peripheral is available for this variant. Under the "STM32Cube/Repository/STM32Cube_FW_U3_V1.2.1/Drivers/STM32U3xx_HAL_Driver/" we can also see that stm32u3xx_hal_pka.c and stm32u3xx_hal_pka.h driver files are available. However, the ST official product page - does not seem to mention this peripheral as a part of STM32U375 series.    Also, we cannot see this peripheral in graphical configuration .ioc. Please let us know if this is available as part of STM32U375 series and how to use it.We also need STM32U375.svd for debugging support, please share this file.

I have a project which runs fine using CMOX_PQC_ML_DSA_44_DET_SIGN_LOWRAM_ALGO but I would like to see how much faster I can get with CMOX_PQC_ML_DSA_44_DET_SIGN_ALGO. When I use it, cmox_pqc_dsa_sign returns 0x9000c, which apparently means "Not enough memory".I am also wandering what kind of memory we are speaking about because it does not seems to request heap memory and I don't expect it to detect if stack is large enough at runtime.I am going to have exactly the same question for CMOX_PQC_ML_DSA_65_DET_SIGN_ALGO and CMOX_PQC_ML_DSA_87_DET_SIGN_ALGO.Perhaps a more general question: is there a documentation for the cmox_pqc library ?

I want to use ILID9341 screen on STM32F407G-DISC1 without any libraries, just spi protocol. However, while the screen turns on, I can't draw anything on it. Why is this the case?This is SPI configuration.I have checked the physical wiring, and it seems to be correct.This is the code that is relevant for the LCD screen (there is also a code for functions for reading values from accelometer, which is probably not relevant).#define RST_GPIO_PORT GPIOD #define RST_GPIO_PIN GPIO_PIN_9 #define DC_GPIO_PORT GPIOB #define DC_GPIO_PIN GPIO_PIN_14 #define SET_ROW_CMD 0x2B #define SET_COL_CMD 0x2A #define SET_COLOR_CMD 0x2C void Reset_Screen() { HAL_GPIO_WritePin(RST_GPIO_PORT, RST_GPIO_PIN, GPIO_PIN_RESET); // pull low HAL_Delay(10); HAL_GPIO_WritePin(RST_GPIO_PORT, RST_GPIO_PIN, GPIO_PIN_SET); // release reset HAL_Delay(120); } void Write_Rectangle(uint16_t row_lower, uint16_t row_higher, uint16_t col_lower, uint16_t col_higher, uint16_t color) { //16 bit/pixel color order (R:5-bit,

Hello. I try to start a new project with two non-listed motors in Workbench. I use two gimbal 3-phase BLDC motor with encoder AS5048A https://cdn.sparkfun.com/assets/d/6/b/5/8/27477_27478_Datasheet.pdf Based on the motorShinano.json file, I built my own JSON file, please see below. However, I have the following questions. What to write in the compatibility: "sixStep"? The motor has the encoder. Hence, should TRUE be for HasHallSensor? I use a Pololu power board (voltage regulator) https://www.pololu.com/product/5576 and two Sparkfun 3-phase BLDC motor drivers https://www.sparkfun.com/sparkfun-brushless-motor-driver-3-phase-tmc6300.html . Therefore, what to write for pwr_board? What to write for foc_rate? What to write for acceleration and max_speed_startup? Thank you. {"id": "motorSparkfun","label": "Sparkfun DM3505/3505EC","hardwareFamily": "MOTOR","description": "Outer rotor type - 11 poles pairs - brushless DC motor with encoder", "compatibility": ["FOC", "s

do the example of LPGPIO,why show this error.Getting started with LPBAM - stm32mcu 

I am trying to connect the STM32MP257F-EV1, following the  guide on the wiki. Followed the LInux preparation. At startup, I get a blinking RED LD1 and steady green LED When start the laptop on windows, the device manager shows a DFU device a. But when booting up LInux, no device in DFU mode is detected by CubeProgrammer 2.210, either through the GUI or the CLI interface.Having tried several possible workarounds—such as changing cables, reinstalling drivers and VMs, and reinstalling CubeProgrammer and the supporting software The board seems to be working as when I reconfigure the boot switches, the display and camera work OKCould someone suggest what I might be doing wrong or if there is a known solution?Linux shows this:T: Bus=01 Lev=01 Prnt=04 Port=02 Cnt=01 Dev#= 11 Spd=480 MxCh= 0D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1P: Vendor=0483 ProdID=df11 Rev=02.00S: Manufacturer=STMicroelectronicsS: Product=DFU in HS Mode @Device ID /0x505, @Revision ID /0

I have just spoken with an ST sidekick, and I was informed that STM32CubeMX is currently not supported on Windows ARM64.Thank you for the clarification.  

Greetings,I am trying my hands on STM32WLE5CCU6 and want to encrypt variable length data using inbuild encrypt hardware or feature of the controller. I am generating a byte array of variable length. Is it possible to encrypt that array ? In an example i have seen an array of 32bits but not 8 bits. Please guide me.

HI,I'm using the VL53L4CX and in an enclosure and thus have a cover glass over the sensor.i've been doing some simple calibration, but have noticed that this requires a strict procedure and preferably a good setup to perform the calibration.I therefor want to make a box to perform the calibration in. This should remove any variables and make sure that calibration is handled the same every time.I know i should be able to copy the calibration data from one device to the other, but due to it being a lorawan device, and my current provisioning/flashing steps, it's easier for me to calibrate the sensor afterwards.I posted the same question here: https://community.st.com/t5/imaging-sensors/vl53l4cx-refspad-caliberation-no-target/m-p/869701/highlight/true#M6277 but that's a fairly old topic, so i'm starting a new one. My current idea for a wooden calibration box is:Wooden (probably MDF) box with an internal height from sensor to top of 60cm, probably 40cm wide.Matt black paint

helloI want to use your api to speed up the developpment of a driver based on spi communication, this function seemed appropriate in your stlink-v3-bridge-v1-2-0:Brg_StatusT Brg::ReadSPI(uint8_t *pBuffer, uint16_t SizeInBytes, uint16_t *pSizeRead)unfortunatly I found this comment:* In #SPI_DIRECTION_2LINES_FULLDUPLEX dummy data are sent while receiving.and i check with a scope that it is the case (data written are '0'),this is a pity because read/write are frequently simultaneous in spi,is there a possibility to send data instead of dummy in the mean time we are reading ?regardsBenjamin

Hi all -    I am building an isolated power converter using a three phase forward converter topology.  Each phase has a half bridge driving a transformer primary w.r.t. Vin/2 (split Vin).  The transformer has a mid-tap secondary, rectified effectively acting like a buck regulator at 2x the primary frequency.  I am using the HRTIM hardware to drive this.So far it works great - I have my three phases A/B/C programmed like so (each has high-side 1, low-side 2):A resets on master update, A1 set on A update, reset on A cmp1, A2 set on A cmp2, reset on A cmp3.B resets on master cmp1, B1 set on master cmp1, reset on B cmp1, B2 set on B cmp2, reset on B cmp3.C resets on master cmp2, C1 set on master cmp2, reset on C cmp1, C2 set on C cmp2, reset on C cmp3.The master cmp1 and cmp2 are set at phase angles 60, 120.  The maset compares and all three cmp2 are fixed, while the cmp1 and cmp3 are all set by the feedback code.   Works perfectly.For continuou

Hello all.  Tasked to replace an old 128Kx8 EPROM, but the folks paying the bills want me to decode the ICs manufacture date code for QA reasons.  Does anyone know of any URLs?  The ST first data book I found was created long before this IC existed.  The key details are below: Below quartz window of die with 2 banks x 1  Row 1: ST logo B88HARow 2:9231E5SRow 3:M27C1001Row 4:        -20F1My best guess is the 128Kx8 (confirmed by reading manufacture code on the programmer and prior EPROM knowledge and abuse) STMicro EPROM 200 ns with 0 to 70 C temperature range. Guessed at date of 1992 week 31.  No idea about where it was made or what the E5S means or what the B88HA translates to in locations.Also I have another EPROM withBelow quartz window of die with 4 banks 2x2 matrixST logo B88GA9227MC27C1001          -20F1Just want to be sure I can explain the die differences if anyone asks about counterfeits. 

hello, I have a can bus with 2 node (one STM32G0B1 with SN65HVD1050DR  transcriver and one esp8266 with MCP2515 module) that comunicate over canbus at 1Mbps.I am trying to add a third node, it is a blue pill STM32F103C8T6. The chip onboard looks genuine (i have also tested the usb double buffer on it and it works) but who knows...Transcriver attached to STM32F103 is a SN65HVD1050DR, as for the G0B1.The problem is, whith STM32F103 i see only messages coming from STM32G0B1 (and not from the other node on bus), and it looks like it is not sending messages (other nodes on the bus don't receive also if they are accepting from any id). My ideas are: 1- fake chip, so canbus will never work properly, 2 - bad code.Here are relevant code parts for STM32F103, do you see errors (i am quite new to C programming)?With this code, the main loop run for some seconds (circa 10) than it enter in Error_Handler function, if i activate the AutoRetransmission it happen

I've tried this evening to download STM32CubeIDE on 2 different accounts, 2 different computers, a phone, and have reset my computer and also deleted my cookies but still will not download. Nothing happens after I accept the terms and conditions. I have also tried to download as a guest the link from the email still just takes me to the download page but it won't download.

Dear ST members,My application is using the EEPROM emulated library (X-CUBE-EEPROM) with an STM32WB microcontroller. I noticed that, when I update a variable, the page can be padded with random zeros. Attached are screenshots of the page before and after two variables were updated.I initially thought this could be unused variables, since we need to define the NB_OF_VARIABLES. Even reducing its value to match the number of variables I am using, the random zeros are still added to the page. The AN4894 says there is a wear levelling algorithm but this is the worst I have ever seen on an emulated EEPROM implementation. This makes it difficult to calculate the erase cycles I will need for my application. Can you clarify where these random zeros are coming from and if I can get rid of them? Regards

Hi,// WM8904.c int32_t WM8904_Init(WM8904_Object_t *pObj, WM8904_Init_t *pInit) // ... if ((WM8904_CurrentDevices & WM8904_OUT_HEADPHONE) == WM8904_OUT_HEADPHONE) { ret += WM8904_SetVolume(pObj, VOLUME_OUTPUT, (uint8_t)pInit->Volume); } // ... /* Store current devices */ WM8904_CurrentDevices = (pInit->OutputDevice | pInit->InputDevice); in line 4, WM8904_CurrentDevices is still 0, so the gain is not set.I'd change the line this way: if ((pInit->OutputDevice & WM8904_OUT_HEADPHONE) == WM8904_OUT_HEADPHONE) { ret += WM8904_SetVolume(pObj, VOLUME_OUTPUT, (uint8_t)pInit->Volume); }  

Hi STM Community, I’m currently working with the NUCLEO-G491RE board and need some guidance regarding DFU (Device Firmware Update) mode. According to the documentation, CN2 is marked as the DFU connector. Based on that, I have soldered 4 pins on CN2. I also have a USB Type-C female breakout board, and I’d like to connect it properly to CN2. USB Type-C Female Breakout Board. However, I’m a bit confused about the following points: CN2 pin mapping Which pin on CN2 corresponds to GND, D+, D-, and 3.3V / VBUS? Entering DFU mode What are the exact steps to put the NUCLEO-G491RE into DFU (Device Firmware Update) mode? Do I need to configure BOOT0, jumpers, or any CubeMX settings for this? At the moment, when I connect the board to my PC using the USB breakout, the device is detected as an “Unknown USB Device”, so I assume I’m missing something in either the wiring or configuration. I would really appreciate it if someone could: Clarify the CN2 pinout, and Explain the cor

Hey, our team is working with TouchGFX Designer (4.19.1) and IAR IDE.TouchGFX assets include 50 MB of images, videos, fonts and texts.We are trying to find a way to change the app without touching and flashing TouchGFX assets.The TouchGFX should stay constant while only the app code itself changes.Meaning compiling the code without compiling TouchGFX assets again to get a smaller hex file to flash/store, and current TouchGFX assets that are stored in the external memory will work, so basically we want to exclude all TextFlashSection, ExtFlashSection and FontFlashSection files from compilation.The main goal is to store a backup version of the code inside the internal flash for cases of software updates, so we want to compile only the app code.Is it related to the linker file or some other configuration file?

Techsupport ignored my request, so I have to come here. The part is ECMF02-2AMX6. It is CM choke plus ESD surge protector for USB2. Here's the question: in the datasheet from June 2011 Doc ID 17815 Rev 2, this is the recommended layout is shown (see the image).As can be seen, pins 3&4 are connected to GND (3 VIAs are being used).However the Pin 4 is declared "NC". In the text this is not addressed. My request to the support was not answered.THis is fairly important. If the pin i named "NC", it means "No Connect" unless the opposite openly explained in the text of the datasheet.Waiting for an answer.   

I'm currently looking at something like thisSTM32N657A0But they sell a non AI accelerator version STM32N655A0Is there any benefits to using the non AI version of the chip.  Other then saving a few dollars on the chip?