Solved

Hello all,I am working on the STM32H753 Evaluation board and I have a software architecture with an SBSFU running in the internal flash, that jumps to the External NOR flash to execute the user application (Download and Active slot in External NOR flash). My user application is FreeRTOS based. I am currently working on SBSFU v2.6.1 and have managed to customize the Nucleo H753's example project and my user application to execute successfully from the external NOR flash on my STM32H753 Evaluation board. But, in the process, I had to disable the Memory Protection Unit (MPU) in the SBSFU side due to the following couple of problems: Enabling the MPU causes the user application to hang at the RTOS thread creation and not proceed further. I see that this is not supported at the IOC level alsoThe Data Cache being enabled in the SBSFU side was corrupting the External NOR flash for some reason, causing the signature of the firmware to mismatch and causes critical errorAlso, I see in FreeRTOS w

I am designing a PCB for a self-powered industrial device with a USB port, and therefore need to use VBUS sensing. In the generic USB hardware guideline (application note 4879), it is stated that "Pin PA9, a five V-tolerant pin, is natively dedicated to VBUS sensing".What confuses me is that the STM32L433 datasheet doesn't mention this. In fact, nether the datasheet or the manual mentions VBUS at all, and PA9 doesn't seem to have anything to do with the USB port at all.So my question is this: Does anyone here have experience with VBUS sensing on the STM32L433? Does PA9 really work as VBUS sensing on these devices, even though it isn't mentioned in the manual or the datasheet?I had a look at the datasheet for the STM32L475, where the additional function for PA9 is listed as OTG_FS_VBUS. Is PA9 dedicated to VBUS sending only in OTG capable devices?

Hello,I am using the STM32H7B3I-EVAL evaluation board to develop an understanding on using a custom board that has an LCD display. I am dissecting the code and there is something inconsistent that I am trying to understand.My steps were as followed:1) Use CubeMX to bring up the code from scratch, adding the TouchGFX 4.20.0 software package. 2) Open the ApplicationTemplate.touchgfx.part file to generate the code for the UI.3) Made a basic display UI (one screen with a red background, just to test). The code works without issue, but I am looking through the TouchGFX folder to understand the code and there is a file created:TouchGFXGPIO.cpp ( I have attached it).It's claiming it's using 4 signals (VSYNC_FREQ, RENDER_TIME, FRAME_RATE, MCU_ACTIVE), which toggles the following pins:// VSYNC_FREQ - Pin PA4// RENDER_TIME - Pin PG13// FRAME_RATE - Pin PB15// MCU_ACTIVE - Pin PG12On the evaluation board, those pins are used for different features entirely.PA4 -

Hi I am using an STM32G071 Nucleo board and would like to know if it is possible to achieve the advertised current of 40nA in shutdown mode.I have no problems entering shutdown mode but the observed current with my nRF PPK2 is closer to 1uA. I have disabled the RTC.1) Is the current of 40nA possible on the Nucleo board?2) Are there any required steps before entering shutdown mode?Thank you

When I try too start debugging I get this message:I checked the drivers and the device is showing as a USB Composit Device and I have no alternative to change the driver.I installed en.stsw-link009 and successfully installed some drivers but they are not available in device manager.I uninstalled the device in device manager but still no change.I even installed the newest STM32CubeIDE 1.12.0 but still no change.Does anybody have another idea?

we use the timer capture for Hall inputs. we were able to program the XOR input using the filter and can geneate an interrupt, but I also want to read the individual inputs using the filter.feature. When I read the corresponding IDR it seems it is not the output of the filter.

Hello,i am porting a relative old project which uses std hal lib v1.06 from stm32h750.Due to the market shortage, i am migrating this project to stm32h725igk6 ( bga version).The project is compiled trough CubeIDE with latest hal libraries ( v1.11).The adc uses adc1-ch3 and adc2-ch5 in regular simultaneous mode with DMA.External bypass oscilator of 25mhz is used,ADC clock is coming from PLL2 at 88MHZ, and divided by 4, to obtain a 2msps.The project itself uses alot of complex math, and it was originaly created under unix.After porting the code to cubeide, there are no compile errors.However i noticed the. function HAL_ADC_IRQHandler its never triggerd, and i wonder why?Both NVIC for ADC and DMA are enabled.By the way, what is the dma stream for reading ADC1 data register? is it DMA1 stream 1?I ask this because i have alot of hard time figuring all the data from the reference manual, and cubemx when generating the project does not autofill thisI already spent 2 days on this, trying to ex

Hi @OlivierK​ ,I am using openstlinux ecosystem release v3.1.1 and trying to use secure boot feature with yocto and as per https://wiki.st.com/stm32mpu-ecosystem-v3/wiki/TF-A_overview we need to set "TRUSTED_BOARD_BOOT=1".We need use "TF_A_SIGN_ENABLE=1" to use "TRUSTED_BOARD_BOOT=1" in meta-st-stm32mp.https://github.com/STMicroelectronics/meta-st-stm32mp/blob/dunfell-3.0.x/recipes-bsp/trusted-firmware-a/tf-a-stm32mp-common.inc#L84. https://github.com/STMicroelectronics/meta-st-stm32mp/blob/dunfell-3.0.x/conf/machine/include/st-machine-common-stm32mp.inc#L524.If TF_A_SIGN_ENABLE=1 then FIP_SIGN_ENABLE will get set as per ecosystem release v3.1.1 and which force to set FIP_SIGN_KEY_EXTERNAL FIP_SIGN_KEY FIP_SIGN_KEY_PASS and TF_A_SIGN_ENABLE as per https://wiki.st.com/stm32mpu/wiki/How_to_perform_Secure_Boot_from_Distribution_package.I do not want set FIP_SIGN_KEY_EXTERNAL FIP_SIGN_KEY FIP_SIGN_KEY_PASS at the time of build and want set after build seperatly with "cert_create". For

Hi,My 1st post here, so please forgive me if I'm posting this in the wrong category.2nd disclaimer, I'm predominantly a HW engineer, so I have a limited amount to SW experience.I've been trying to put together a OT border router application on a BeagleBone Black, using the P-Necleo-WB55 board programmed as a RCP.My intention is to build a border router (and other products) using the STM32WB5 modules.I followed the OpenThread instructions to setup the BBB Debian installation, with the only difference being that I interfaced the BBB to the RCP directly via a UART interface. Naturally, I am struggling to get it working.I've managed to see UART traffic from the BBB platform, but have not been able to get any UART communication with the STM32WB55.I also looked into this ST article on how to setup a border router, where the author comments that one can connect to the STM32WB55 board to a hyperterminal to view the RCP logs:Connect one HyperTerminal (ST_Link) to be able to get the RCP running

Hello Team,Please let me know the inductance value of the passive filter IC EMIF02-SPK03F2. In the datasheet, the capacitance value is listed but the Inductance value not showing.

In the ST25DV data sheet, I read:"Energy harvesting can be set even if ST25DVxxx is in RF disabled or RF Sleep mode, or in Low power mode. In all these cases, ST25DVxxx will deliver power on V_EH pin if RF field is present."However this is not what I am seeing.If energy is being harvested to power the MCU and it sets either RF_DISABLE or RF_SLEEP in RF_MNGT_Dyn via i2c ,the energy harvesting output disappears and the system dies.Is this an error in the data sheet or is there a way to disable/delay enabling RF communications whilst maintaining Energy Harvesting?I suppose that the possibility exists that the phone is switching off the field when RF communications are disabled, but this amounts to the same thing.I want to be able to delay RF communications until the MCU has written the NDEF record to the EEPROM, i.e. I want to power up from harvested energy with RF communications initially disabled.Thanks,Richard

Hi, I am running the vscode extension on ubuntu 22.04, and am getting the following error when trying to start a debugging session: "Could not find the path to "ST-Link_gdbserver". Ensure STM32CubeIDE is installed.". I have tried reinstalling the latest version of STM32CubeIDE but nothing changed. I have installed all the required programs (CubeMX, CubeCLT, MCUFinder).The error prompt gives you a button to edit the launch.json to change the debug configuration, but i'm not sure what I'm supposed to change in order to get it to work. Thanks.

hi st expert​I am porting openstlinux for my robot board, I found that the system froze after uboot selected the extlinux file, and then rebooted after a while，the uart log :Do I have any debugging means to analyze where the current problem is? thanks advance!my extlinux.conf context:

I am struggling to find working examples to work with FreeRTOS in an interrupt mode.I use the function HAL_I2C_Slave_Transmit_IT() This enables the interrupt as well as setting up the data.It works to a point, then the remote Master send a Nak and 8 bytes which then fires the Error interrupt.However the Write address and the Subaddress is sent there is an issue. The top trace in the waveform below indicated where the interrupt fires. What is most notable that the second firing is a result of a RXNE bit being set. As this bit is never cleared by a read from the data register in the HAL library the interrupt fires again about 200 times until a read address is received.I feel that is an issue with the stm32f4xx_hal_i2c.c library?There doesn't seem to be a wealth of slave I2C examples for the STM32F4 series. I think I know what I am doing wrong, but either way this behaviour is not ideal. The byte should at least be read and an error indicated in some way.

Any chance STM32 MCUs will adopt native i3c support any time soon? Many new devices, including some from ST (like the LPS22HH), support it. It's a compelling (new-ish) standard.

Hello,I have a custom STM32 board which has basically only the needed components to flash and use an STM32F103RET6 on board. This means, there are only a few capacitors for voltage stability, an 8MHz quarz + circuitry, and a few connectors on it.I have the SWDIO, SWCLK and NRST lines connected through a 100 Ohms resistor exposed so a connector, so I can use them to program the device. Now the problem ist, that I cannot connect to the device via STM32CubeProgrammer, nor the CLI, nor my IDE of choice (Keil uVision).When I use my ST-LINK V2, connect it to the board and my pc, and then press "connect" in the program, I get the error "DEV_TARGET_CMD_ERR".There is literally no explanation of this error anywhere, other than "hardware issues". I then proceeded to try out the CLI and it didnt work either. My Keil uVision just throws the error "Internal Command Error". So I set up a logic analyzer and found out, that the device is actually communicating with my ST-LINK.It is basically doing this

Hi allI'm trying to distinguish between the interrupt sources in the NMI handler on a STM32G031 - particularly the RAM parity error.I have everything in place and I can provoke a parity error. The NMI ISR is called as expected, but if the SYSCFG_CFGR2_SPF is checked in the ISR it is never set (and neither are the other 3 potential NMI sources).Am I not understanding correctly how this works? Is this flag getting automatically reset upon entry into the ISR (The manual is not totally clear here. For the other flags it explicitly mentions that they need to be cleared manually)?Thanks for any pointersA

Hello,I am in the process of making my own circuit board and using an f767 with 144 pins. I have integrated a QSPI and a 40-pin FPC for an 800x480px display. The LTDC is in RGB565. Unfortunately, I don't have any pins left for the SDRAM. So the question is, do I need the SDRAM? Can the QSPI replace it?

After download TFA, USB DFU device is marked as "UNKNOWN":#dfu-util -a 1 -D tfa_v4.stm32 && dfu-util -a 0 -e && sleep 2 #dfu-util -l   dfu-util 0.9   Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2016 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to sourceforge.net/p/dfu-util/tickets/   Found DFU: [0483:df11] ver=0200, devnum=58, cfg=1, intf=0, path="1-1.5", alt=5, name="UNKNOWN", serial="UNKNOWN" Found DFU: [0483:df11] ver=0200, devnum=58, cfg=1, intf=0, path="1-1.5", alt=4, name="UNKNOWN", serial="UNKNOWN" Found DFU: [0483:df11] ver=0200, devnum=58, cfg=1, intf=0, path="1-1.5", alt=3, name="UNKNOWN", serial="UNKNOWN" Found DFU: [0483:df11] ver=0200, devnum=58, cfg=1, intf=0, path="1-1.5", alt=2, name="UNKNOWN", serial="UNKNOWN" Found DFU: [0483:df11] ver=0200, devnum=58, cfg=1, intf=0, path="1-1.5", alt=1, name="UNKNOWN", serial="UNKNOWN" Found DFU: [

I am working with STM32L010C6T6 MCUs. I need a way to consistently and uniquely identify each MCU with as few bytes as possible. The 96 bits "Unique device ID" register seems ideal but what is the minimal number of bytes I need? Are all 96 bits mandatory to fulfil my needs? At a first look, the answer seems to be no as 4 bytes seems to be enough but I am not sure.In Reference Manual RM0451, section 25.2, page 730-731 the 96 bits "Unique device ID registers" are described as follows:[23-0]: LOT_NUM in ASCII code[31-24]: WAF_NUM in 8 bits unsigned number[63-32]: LOT_NUM in ASCII code[95-64] Unique ID bitsHere are my assumptions. We have 3 distinct fields:LOT_NUM: An ASCII string represented by 56 bits => 7 chars/bytes. I assume that only the 7 LSB bits of each byte are significant (standard ASCII code represented on 7 bits) and this string may be common among MCUs of the same Lot.WAF_NUM: A Wafer number represented by 8 bits => 1 byte. I assume that all bits are significant and thi

HelloI am trying to implement low power mode with STM32WLE5 MCU (as a part of RAK3172-SIP).However, the current consumption is unreasonably high.I measure around 200uA with 3.6V and around 150uA with 3.3V.Did many tests with different configurations, checked the RF switches. I use TXCO, but even if I run with internal clock - no changes. Debug mode is disabled.How can I debug it further?I even tried to go into Stop2 mode directly before HAL_Init() - still the same 200uA (at 3.6V) consumption. So even before all periphery is initialized I cannot get the lower consumption.I did similar test with Wio-e5 module just to check that the HW is not an issue, and there I 've got around 300uA (at 3.6V). So I have no questions to HW.Regarding the HW, there I have one 100k resistor to BOOT0 to GND and one 100k pullup to nRST. The rest is caps and inductors for supply lines, nothing else is connected to the module.I was thinking this is because of SMPS - but I checked that it is not running in

The board is set up as follows, and USB of ST-Link V2-1 is connected to Host PC.   when using Linux host pc , /dev/ATM* devices not recognized.So I used a Windows PC, but it is not recognized either.Do I need to install a special driver to recognize the Uart serial?Or is there a problem with the Jumper setting?

Can we connect D1+ to DN and D1- to DP (same for the connector (D1+CON to USB_D_N))

I think there is an error in the PM0214 Programming manual "STM32 Cortex® -M4 MCUs and MPUs programming manual". The multiply and accumulate instruction is called "vlma" throuout the whole document. Other programmin manuals (e.g. for STM32H7) as well as the assembler say this must be "vmla" instead.

Hi!STM32MP1 provides a real-time core, and we use it for the hard-real time. But additionally, we would need the application running on the two fast cores to also be real-time. (with softer constraints but still better than standard scheduling on Linux).For this, I added to the yocto project, at (not the best place, but just trying to make it to work for now):Layers/meta-st/meta-st-openstlinux/conf/distro/openstlinux-weston.confPREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" COMPATIBLE_MACHINE = "(stm32mp1)"But then, I get the following errors:ERROR: Nothing PROVIDES 'quilt-native'quilt-native was skipped: incompatible with machine stm32mp1 (not in COMPATIBLE_MACHINE)ERROR: Required build target 'st-image-weston' has no buildable providers.Missing or unbuildable dependency chain was: ['st-image-weston', 'quilt-native']