Solved

Hi everyone,I am a beginner working with the VL53L1X sensor on an STM32F103C8T6 using the STSW-IMG009 (Ultra Lite Driver). I am trying to implement a calibration routine, but I am encountering two specific compilation errors inside my VL53L1X_calibration.c file:The errors:1. 'VL53L1X_ERROR_TIMEOUT' undeclared (first use in this function); did you mean 'HAL_DMA_ERROR_TIMEOUT'?2. implicit declaration of function 'VL53L1_WaitMs' [-Wimplicit-function-declaration]I have checked the driver files but cannot find their declarations.I have not changed any of the driver files. Am I missing something? Any help is appreciated. Thank you!

Greetings!I am trying to establish a connection between STM32F439IIH6 (Slave) and a customize board (Master) through SPI DMA application. The customize board has its own built-in driver with SPI application. The communication between STM32F4 and customize board eventually broke down after few thousands of cycles. Through some investigation, I found out that the SPI_WaitOnFlagUntilTimeout() hangs inside SPI_DMATransmitReceiveCplt(). It sutcks inside the else statement of SPI_WaitOnFlagUntilTimeout(). The clock used in customize board (Master) is 80Mhz with clock division 4/** * @brief This function handles SPI Communication Timeout. * @PAram hspi: pointer to a SPI_HandleTypeDef structure that contains * the configuration information for SPI module. * @retval HAL status */ static HAL_StatusTypeDef SPI_WaitOnFlagUntilTimeout(SPI_HandleTypeDef *hspi, uint32_t Flag, FlagStatus Status, uint32_t Timeout) { uint32_t tickstart = 0; /* Get tick */ tickstart =

Hello everyone. I am running into a USB Host <--> Device connectivity issue. I have 2 STM32L496 MCUs, one as Host and other as Device. I cannot get the CDC connectivity to work for some reason. The connections are as follows: D+ <> D+, D- <>D-, GND<>GND.I have VBUS, SOF and NOE disabled. CubeMX forces to set Drive_VBUS as well over a GPIO, however, I am not using that in my circuit. Even though it is a recommendation in USB connectivity in AN4879, I believe it is possible for a simple connectivity without it as well. Would this be a wrong assumption (and hence the culprit)? As a connection stability, I tested both MCUs individually as Devices, connecting to my PC and it sent data over USB just fine. The attached code has NucleoL496 as the host. Would appreciate your support.

Hi everyone, I'm working on a prototype, which is using a PM8805 to classify connected PoE types. However we are running into an issue, where neither T0, T1 or T2 are giving us any signals (giving always 1 on their open drain signals, making .the LEDs stay off). Suspecting an issue with our prototype, we went on to get a STEVAL-POE001V1, which is showing the same scenario: With our different PoE, PoE+ and PoE++ injectors (Both Ubiquity and TP-Link brand), the T0, T1 and T2 LEDs are remaining off. The PGD LED is however on in those tests. We tested with and without a load on the output (for example 5kOhm) to prevent the injectors going into standby mode. We checked and according to datasheets the TP-Link TL-POE160S is an active 802.3af/at compliant injector. Is my understanding correct? With the CLS 1 resistor at 36.5Ohm and the CLS2 resistor at 51.1Ohm, the T0, T1 and T2 signals should, as an example, be 0, 1, 1 respectively for a

..

I have enabled USB with the following settings:Following USB middleware is enabled like so:In the linker script I have moved everything from DTCMRAM to RAM.Additional section is specified like so.dma_buffer : { *(.dma_buffer) } >RAM_D2And used like so:/** Received data over USB are stored in this buffer */ __attribute__((section(".dma_buffer"))) uint8_t UserRxBufferHS[APP_RX_DATA_SIZE]; /** Data to send over USB CDC are stored in this buffer */ __attribute__((section(".dma_buffer"))) uint8_t UserTxBufferHS[APP_TX_DATA_SIZE]; At this point USB device enumerates but looks like no descriptors are transferred to the host.I also tried to enable MPU like so:But that did not do the trick.However, when RAM region base address (0x24000000) is used instead of RAM_D2 (0x30000000) for MPU, device enumerates correctly:and there is no need for:__attribute__((section(".dma_buffer")))on rx and tx buffers anymore.Now the question. How to correctly place only the USB related stuff to

Hi.I'm using an STM32G051 and would like to use 12 ADC channels which are not sequential. I have thus set up the ADC for 'sequencer set to not fully configurable' as show below:Ignore for the moment that IN9 is red, I think I was trying something with one of the comparators to see if that helped.I'm using the DMA to kick off a new conversion and the callback reports back raw values which I print out as seen below.If I enable IN0, IN9 or IN10 then I get bad data from the ADC (possibly mixed up channels) as seen below where the VREF+ is being reoprted as over 5V when it should be 3.3V.VREF+: 5362 mV.CPU Temperature (STM32): 1870.0 °C.Sample Temperature: 0.0 °C.LED feedback current: 0 mV.raw vref ADC value: 0x3a5.raw DET0 ADC value: 0x184.raw DET1 ADC value: 0xfff.raw DET2 ADC value: 0xffe.raw DET3 ADC value: 0xffd.raw DET4 ADC value: 0xfff.raw DET5 ADC value: 0xffe.raw DET6 ADC value: 0x5e4.raw STM32 temp value: 0xffe.raw LED feedback current value: 0x00e.If I disable IN8, IN9 and IN10 (

Hi,I am new to ST platform, i am facing an issue as below.C:/Users/Yuvaraj/Desktop/Test/1/Middlewares/Third_Party/LwIP/src/apps/http/fs.c', needed by 'Middlewares/LwIP/apps/http/fs.o'. StopI am opened the project from examples codes.Can anyone help ? How to resolve this? Regards,Yuvaraj V

Locking the controller (NUCLEO-C562RE - RDP level 2 with OEM key) works fine with J-Link / ST-Link (SWD). E.g.stm32_Programmer_CLI.exe -c port=JLINK -lockRDP2 0x11111111 0x11111111 0x11111111 0x11111111 -ob RDP_level=0x72 ------------------------------------------------------------------- STM32CubeProgrammer v2.22.0 ------------------------------------------------------------------- Connecting to J-Link/Flasher Probe Device=Cortex-M33 Device ID : 0x44E Voltage : 3.29V Frequency : 4000 KHz NVM size : 512 KBytes Lock RDP2 password successfully done UPLOADING OPTION BYTES DATA ... Bank : 0x00 Address : 0x40022050 Size : 112 Bytes ██████████████████████████████████████████████████ 100% Bank : 0x01 Address : 0x40022098 Size : 8 Bytes ██████████████████████████████████████████████████ 100% Bank : 0x02 Address : 0x40022070 Size : 8 Bytes ██████████████████████████████████████████████████ 100% Bank : 0x03 Address : 0x40022080 Size : 8 Bytes ███████████████████████████

Heyho,playing with the L073, partitioned the flash for bootloader "BL" (bank 1) and application (bank 2).No writing of app yet, just testing jumping back and forth.I just added a no-init variable for communication between BL and app, mainly to tell the BL to not jump back to app if the app requested so.at power up / reset, the uninitialized variable "u32AppRqstBootloader" is 0, so the BL jumps to the app, and just for checking: before the jump the BL sets u32AppRqstBootloader = 0xB0072ABBin the app u32AppRqstBootloader is printed via UART, and it shows the expected 0xB0072ABB, the printf is done immediately and takes ~ 2 ticks (1 tick = 1 ms)now I let the app jump to BL, before the jump the app sets u32AppRqstBootloader = 0xABB1B007 so the BL does not jumpSo far so good...But when the BL now jumps back to the app, all of a sudden in the app there's a ~ 1 second delay before u32AppRqstBootloader is printed - everything else is working fine - or so I think... (the next pri

Hello,I have some sort of experience working with linux on RPI.I wanted to increase my embedded linux experience with STM32MP.So I wonder, should I buy STM32MP2 because its newer, or STM32MP1 because it will probably have more support and more reference because its been here for some time now?Also, for STM32MP257F-DK, the debug port and the power supply are shared on the same USB-C, how can i do both at the same time? because I don't think the PC can supply it with enough powerWould I need anything to start other than the external USB-C power supply?Any other recommendations are welcome

If I don't enable RX line inversion, everything works fine. But when I enable inversion, I constantly get frame errors. The DMA operates in cyclic mode, without interruption. It's just like a ring buffer. In normal mode, everything works without problems. The signal source itself was tested on another device with a purely hardware signal inverter, and everything was fine. It's unclear why enabling inversion causes the problem. Perhaps someone can give me a hint as to what might be causing this? Thank you.

Hi SupportI have experience in STM32 with Zephyr but I am trying out AMP for the first time.So I am trying out OpenAMP example from STM32CubeIDE. I can compile the example but cannot flash the same.I have the following errorThe ST-Link device is present as shown below I have tried other boards like NUCLEO-G431RE with some simple UART example and work well.I have problems only with AMP board, I am not able to flash M4 and M7 core. My dev environmentUbuntu 22.04 and STM32CubeIDE ver1.1.8.1 Could anyone please help me understand the same?  

CubeMX Project Manager has a bug, where when I accidentally cleared the "Project Location" field and moved the cursor away CubeMX complains that project location cannot have special characters and cannot be empty. But this popup does not go away and gives you no chance to correct your mistake. Screenshot attached. Host OS: Ubuntu 24.04.4 CubeMX version: 6.15.0  Edit: Turns out there was a new version of CubeMX (6.17.0) where this problem disappears. You click 4-5 times on OK and the dialog disappears. Should I delete the question in this case?

Since the 210 reader seems to be cheaper and smaller (in non BGA package) than the 3916b we are currently using, while delivering comparable output power, I am naturally intrigued.  But the wakeup mode figures don't quite impress, even though it is advertised for situations "where each µA matters".Wake-up mode for the ST25R300, ST25R500, ST25R501 and ST25R210 - Application notegives a 75.17 μA figure for 200ms scanning (using 250mA Amplitude)Wake-up mode for ST25R3916/16B, ST25R3917/17B, ST25R3918, ST25R3919B, and ST25R3920/20B devices - Application notegives  a 43.74 µA figure for 200ms scanning (using 200mA Amplitude)Even adjusted for the amplitude difference, that would give >35% more power draw for the 210. Is there a way this is compensated through higher sensitivity, so actually we need less Amplitude on the 210, or should I really expect a regression in low power card detection?

Hello,In the STPMIC datasheet, the BSTOUT continous current  is specified as being greater than 1.1 A when 3.3 V < VIn < 5.5 V.If the voltage Vin is greater than 4.5 V, does the  BSTOUT continous current  increase?I assume so, since the inductor's peak current limit (IBSTLIM) is 3.3 A and the short-circuit current (IBSTSH) is 4 A, but could you confirm this for me?If so, what is the BSTOUT continous current  when Vin>4.5 V?Best Regards.Sylvain 

For the past week or so, pasting images directly into posts seems to have broken.I used to be able to just take a screenshot, or copy an image and paste it straight into the editor, but that no longer works.I press 'paste', and nothing happens - no error messages or anything.I am now having to save the image locally, and then use the 'Insert Photos' button to import it. There is history with this, but now it seems to have just broken completely. Using Chrome Version 145.0.7632.109 (Official Build) (64-bit) on Windows-11 Pro

I am using STM32H743VIT6 with USB3300 to develop a HS USB Device.But the program is always trapped in USB_CoreReset() at  do  {    count++;    if (count > HAL_USB_TIMEOUT)    {      return HAL_TIMEOUT;    }  } while ((USBx->GRSTCTL & USB_OTG_GRSTCTL_CSRST) == USB_OTG_GRSTCTL_CSRST); I am using a VCP example generated by CubeMX for testing without any other code.  environment 

Hi,When I downloaded a .hex file to my STM32H563VGT6 (1MB Flash) using STM32CubeProgrammer v2.20.0, I encountered an issue where it would erase the wrong sector. For example, as shown in the image below, it was supposed to erase sectors (76..91) and sector 115, but I found that the contents of sector 27 is erased.I also try to "Erase selected sectors" (76..116) manually, but sector 27 still be erased.However, I did not have this problem when downloading the same .hex file using an STM32H563ZIT6 (2MB Flash).

Hello everyone, I am working on a design based on the STM32H7 MCU and I am evaluating storage options.I came across the Micron MTFC128GBCAYAL-AIT device, which is described as a USF NAND / eMMC memory. I would like to know:   1, Can MTFC128GBCAYAL-AIT be directly interfaced with an STM32H7 MCU? 2, Does STM32H7 support this device via SDMMC, FMC, or any other peripheral? 3, If direct interfacing is not possible, what is the recommended alternative (raw NAND, SD card, QSPI/OctoSPI flash, etc.)?   My goal is to use soldered non-volatile storage (similar to eMMC) for data storage or filesystem purposes. Any clarification, reference manuals, or practical experience would be appreciated. Thank you.

 Between Last Day to Last Year, doesn't show users. Only All Time shows users.     

I want to disable the AGC and use supply manual attenuation values.Disabling the AGC is pretty straight forward, I just set the AGC_EN bit in AGC0CTRL to zero.This works fine, but the gain/attenuation is fixed at the reset value and I'd like to use a custom value.To set manual attenuation values, I suppose I need to write them to the AGC_ANA_ENG register.However, i noticed something weird: This AGC_ANA_ENG register is not present in the driver files. Its not mentioned anywhere and in the MRSUBG register definitions it is listed as "Reserved". The "Description of STM32WL3 HAL and LL drivers" pdf (UM3438) even lists a couple of LL-functions to modify it, such as LL_MRSubG_SetAgcForceGains, but they exist nowhere in the driver files.Why is this register not mentioned in the official driver files and why dont the LL-methods exist?

Hi together, I have been developping a simple BLE application (that I can attach eventually) on the STM32WB55RG P-Nucleo This application combines BLE + USB Device (FS) But after I upgraded the BLE stack firmware from: FUSVER:1.2.0.0STKVER:1.13.2.2STK@:80CF000FUSOP:3.1.0 To: FUSVER:2.2.0.0STKVER:1.24.0.2STK@:80D0000FUSOP:3.1.0 Then I can no longer get any BLE connection nor bonding to my board, using a smartphone.  I'm very suprised of that.

Hello ST community!Currently i'm working on a project based on the stm32 NUCLEO-N657X0-Q which should be delivered very soon .I followed this article https://community.st.com/t5/stm32-mcus/how-to-build-an-ai-application-from-scratch-on-the-nucleo-n657x0/ta-p/828502 step by step with the same versions of software mentioned but without any results .I tried using X-Cube AI and the new tool Stm32Cube AI studio but i ended up with a lot of confusion and errors .I'm planning to stick for now with x-cube ai since the new tool has a lot of bugs to be fixed .My questions is what are the right versions of the software to use to get a computer vision (Yolo like) to work on my board ?Thnx!

Hi,I'm using TouchGFX to make a simple screen with just one slider. This to prove my graphics work and i can use touch to move the slider.I started with a CubeMX project this time but i got stuck somewhere.I enabled DMA2D and touchGFX.I see the DMA2D IRQ's passing by and My frame buffers are swapping when i touch the screen.I see that I get calls to HAL_LTDC_LineEventCallback so I think hltdc is working as well.But i see that my images that should be drawn on my screen are not there. I see the global layout of the slider but it is not the correct image.Steps to reproduce:1) start a new TouchGFX 4.26.0 project2) disable all frameworks in config page3) Set a Box with a specific color (not black)4) Add a simple slider to the canvas5) run the simulator  In the simulator i now see the same issue I see on My device. When I re-enable the Config->FrameworkFeatures. I get a working simulator but on my embedded device the images stay wrong.I have tried everything and check