Solved

Hello,We are currently working with the STM32MP257F-DK development board and encountered an unexpected behavior while accessing the Ethernet DMA Mode Register (ETH_DMAMR), located at address offset 0x1000 as per section 92.11.2 of the reference manual.According to the documentation, the reset value of this register should be 0x00000000. In particular, Bit 0 (SWR: Software Reset) is defined to be cleared (0) after the reset operation is completed.However, upon reading this register after system initialization, we consistently observe the value 0x00000001, indicating that the SWR bit remains set. This suggests the software reset is still ongoing or not completed, which is contrary to the expected default state after a successful system boot.We have verified that all required PHY clocks and Ethernet clocks are active .Could you please advise if this is a known behavior or if there are additional initialization requirements that need to be met to ensure proper reset deassertion?Best regard

Hello,We have an issue with the VL53L7CX. We are using 2.8V for both IOVDD and AVDD. We have 4x TOF sensor on the same I2C line. We set the LPn for 3x of them to low to disable the i2c comm. We are only using 1x TOF for now with it's LPn set to High for testing purpose.We are able to finish the initialization OK using the ULD API https://www.st.com/en/embedded-software/stsw-img036.html. However, when we reach the while loop (using the polling mode) to check for the : uint8_t vl53l7cx_check_data_ready(VL53L7CX_Configuration *p_dev,uint8_t *p_isReady) p_isReady is always false and We hit this particular return line:status |= p_dev->temp_buffer[2]; /* Return GO2 error status */ What is the G02 error values ? i cannot find any definition for it.Any help is welcome to investigate this issue.  --From file VL53L7CX_api.c:uint8_t vl53l7cx_check_data_ready( VL53L7CX_Configuration *p_dev, uint8_t *p_isReady) { uint8_t status = VL53L7CX_STATUS_O

Hello,I'm working with the STM32N6570-DK board and trying to merge two example projects provided by ST:Project 1 (DCMIPP):https://github.com/STMicroelectronics/STM32CubeN6/tree/main/Projects/STM32N6570-DK/Applications/DCMIPP/DCMIPP_ContinuousMode Project 2 (USB CDC):https://github.com/STMicroelectronics/STM32CubeN6/tree/main/Projects/NUCLEO-N657X0-Q/Applications/USBX/Ux_Device_CDC_ACM While merging, I added the following files from Project 1(DCMIPP) into the Project 2(USB CDC) project in Keil: 1 . libn6-evision-awb_keil.a 2 . libn6-evision-st-ae_keil.aHowever, I’m encountering the following build issues:Build target 'Ux_Device_CDC_ACM'armclang: warning: ../../../../../../Middlewares/ST/STM32_ISP_Library/evision/Lib/libn6-evision-st-ae_keil.a: 'linker' input unused [-Wunused-command-line-argument]armclang: warning: argument unused during compilation: '-mfloat-abi=hard' [-Wunused-command-line-argument]armclang: warning: argument unused during compilation: '-mcmse

Hi, I would like to use an external signal to trigger camera capture with the STEVAL-EVK-U0I board. I am using a promodule (CAM-56G3), and looking at the document: how-to-integrate-and-configure-the-vd56g3-vd66gy-and-vd16gz-devices  (p.g. 22 section 1.3), I know it should be possible to do this by using the gpio 0 pin, and setting the first 2 bits of the VT_CTRL  register to EXTERNAL_SYNC. However, it is unclear to me if the STEVAL-EVK-U0I board exposes the gpio pin I need or if there is another way to go about this with the STEVAL-EVK-U0I board and a promodule.Thanks

 以上就是我配置的所有内容。您能指出我的配置有任何问题吗？根据上述配置，我的设备现在在开机时无法在计算机的设备管理器中检测为 USB 设备。Edit: That's all I have configured. Can you point out any issues with my configuration? With the above configuration, my device is now not detected as a USB device in the computer's device manager at boot time.

Thanks.

Hi Guys,I'm on windows 11, i installed all the drivers needed (STSW-IMG501_v.1.1.1) that contains InstallCx3Driver.exe and EVK GS_1.1.1_win64.exe  I have connected the steval-56g3mai module to steval-evk-u0i.I'm trying to run the script vdx6gx_example_open_cv.py from STSW-IMG507_56G3_v.2.0.2.zip What i noticed is that for some image sizes (like 600x600) the camera can acquire correctly and i see the image displayed with openCV, but if i increase the size to for example 800x800 or more i get this error from the script:c:\tmp\windows>python vdx6gx_example_open_cv.pyLoading st_brightsense_sdk_vdx6gx.dllIMG platform version 305 loaded :)Boards connected: (0,P4405C-00A#0219)No board id was specified, selecting board 0.Initiating CCI communication at address 32No sensor on interface 0, checking interface 1Sensor detected on interface 1.CSI reconfigured with 2 lanes at 1500 Mbps, 1116x1356 pixels, 8 bits per pixel, 160.8 MHz pixel clock1119IMG_PLAT error (1):

Hi, Is anybody use IAR with STM32H750B-DK board? I am new to STM32H750 and the discovery board. I am trying to run the FreeRTOS_ThreadCreation sample code using IAR embedded workbench with I-jet debugger, with configuration of XIP_QSPI_InternalSRAM.  I first load the boot code from ExtMem_boot project to the internal flash memory. Then load the project of FreeRTOS_ThreadCreation to QSPI flash memory at 0x90000000. The code was loaded correctly, and I was able to step into the code at beginning. But the code always crashed at SystemClock_Config() -> HAL_RCC_ClockConfig() -> tickstart = HAL_GetTick(). After that the CPU cannot stopped.  But after all these steps, if I power down and power on the board, I actually saw the LEDs blinked as they are supposed to, so code in the QSPI flash memory is running correctly.  What is wrong with the I-jet then? Thanks for any ideas, thoughts, suggestions.     

Hello,I'm encountering an issue with the ST1S12G18R DC/DC regulator. I've attached the reference schematic from the datasheet and my PCB layout, created in Altium. As you can see, my design matches exactly with the reference schematic provided by ST.According to the datasheet, with approximately 5V input and the recommended reference schematic resistor values, I should obtain 1.2V at the output (56k ohm resistor used for both feedback resistors). However, I'm consistently measuring around 4V instead of the expected 1.2V.Because I specifically need a 3.3V output in my design, I adjusted the feedback resistors to 150 k ohm and 33.2 ohm. Still, the output voltage remains stable at approximately 4.3V when the input voltage is in the range of 4.5V to 6V. Only when the input voltage drops below 4V does the output voltage start decreasing accordingly. This behaviour indicates to me that the feedback loop may not be actively controlling the output voltage as intended.To further investigate, I

Am I seeing this right? According to the datasheet, the STM32F413xG/H only maps USART3_RX to PB11, PC5, PC11, and PD9. All four happen to not exist in the STM32F413CG/H variants with the UFQFPN48 package!Bit weird this doesn't seem to be noted anywhere. I guess this 10 UART chip is really a 9.5 (or fewer?) UART chip in the 48 pin package? Extra keywords: STM32F413C STM32F413CH

Hello,Is there a trick to get the Build Analyzer to produce data every time the code is compiled?   It seems like the only way I can get it to update the window is if I change something in the linker script file and recompile again.   Is there an easier way or a setting that needs to be set?thanksMatthew 

I have Nucelo-F303RE but needed easy access to the pins and needed to keep track of their names, but so just sharing a pic of what I came up with: Note you will need two socket headers with long pins of size at least 1x19 (in my case I used 2x20 cause I didn't have any 1x19 ones) that will access the outer columns. The pins unfortunately don't quite line up perfectly into the breadboard like this, so the socket headers are slightly non-vertical, but at least it works and gets access to outer columns over the breadboard.  And make sure you have a good fine-point pen for writing the pin names small and legibly onto the sticker or tape.  I wish they included such a set of pre-labeled stickers with the board.

Hallo,for security reason I have to stop HRTIM generating 3-phase signal for PMSM motor.It works as described in RM0433 (37.3.23) with DBG_HRTIM_STOP = 1: when debugger stops MCU predefined "FaultLevel" appears on outputs as expected. HRTIM goes into STOP mode. So far very good but... The problem is: "This is permanently maintained even if the MCU exits the halt mode."How can I leave FAULT state of HRTIM on leaving debugger halt without writting debugger script?

In continuation of debugging the Ethernet ping test (from this thread)  @Andrew Neil @bouazizm Main issue:When debugging the project, everything works well and i am able to ping the MCUWhen flashing the project, the ping test failsHere are the details of my stm32 cube environment.Operating system: UbuntuSTM32cubeIDE version details:Firmware version : 1.17.3I have attached the project for your reference.Main configuration changes for the project for a successful ping:In the ethernet module: RX and TX descriptors addresses are 0x2007c000 and 0x2007c0a0 respectively.In LwIP  , Under General Settings, DHCP is disabled and static IP(192.168.1.125) and mask(255.255.255.0) are providedIn LwIP , Under Key options, MEM_SIZE is 16000 Bytes and LWIP_RAM_HEAP_POINTER is 0x2007c140In FreeRTOS module, the default task stack size increased to 3000 words.In the linker .ld file add .lwip_sec .lwip_sec (NOLOAD) : { . = ABSOLUTE(0x2007c000); *(.RxDecripSect

Hello, I am writing a mobile application to interact with a STS25DV04KC-I chip. I am encountering problems when trying to write to to user memory on this chip from iOS using the ST25 framework.I want to write a byte array into area 2, and to modify the NDEF records stored in area 1.  I have successfully integrated the ST25 SDK on Android to fulfill these needs. When using the Android version of the SDK, I could successfully read and write bytes transparently with no issue (using the methods writeBytes and writeNdefMessage on the discovered tags).My problem with the iOS SDK is the following: when writing data, there are extra, undesired bytes with the value 0x02  that are inserted into the data written to the chip. Example: I want to send the values [0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0a, 0x0b, 0x0c, 0x0d, 0x0e, 0x0f, 0x10], but the values written to memory are [0x02, 0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0a, 0x02, 0x0c,

Is it possible to use RFAL with ST25R200/R100 without utilizing the additional IRQ / EXTI Line? So just the SPI connection?

I'm using the STM32U031C8U6 with STM32CubeIDE 1.19.0 and can't figure out how LPTIM1 works.I created a new project and enabled LPTIM1 in Device Configuration Tools (Mode: Counts internal clock events). In the NVIC Interrupt table tab, I enabled the interrupt.In Clock Configuration, I enabled LSE clock (32768 kHz) and selected it on the LTPIM1 Clock Mux.I generated the code and modified the main() function as follows:int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_LPTIM1_Init(); HAL_LPTIM_TimeOut_Start_IT(&hlptim1, 320); while (1) { HAL_PWR_EnterSTOPMode(PWR_LOWPOWERREGULATOR_ON, PWR_STOPENTRY_WFI); } }HAL_LPTIM_TimeOut_Start_IT() enables the timeout function, sets compare register CCR1 = 320 and starts the timer in continuous mode.I expected the HAL_LPTIM_CompareMatchCallback callback to be called every 10 ms (320 / 32768 kHz), waking up the micro.This callback is actually triggered every 2 seconds according the value of the ARR register (by default

Hi, I try to create a GATT server with a NUCLEO-WB15CC.I'm a beginner with STM32WB MCUs so I followed the Getting Started Series video and particulary : "STM32WB Getting Started Series: Part 12b, Lab. Receiving data from the phone" When its came time to test the firmware my device was not detected in ST BLE ToolBox mobile AppI tried to upgrade the BLE stack Firmware with "stm32wb5x_BLE_Stack_full_fw.bin" but nothing changed. Then I tried the example Firmware BLE_p2pServer and it's work.It's seems to be a problem links to STM32WB15. Indeed in the video they used a STM32WB55 and in the comment of the video other persons has the same problem when using a STM32WB15. Does anybody had this problem and knows how to fix it?Thank you

Hello all,I am a newbee, and so far I finally did successfully in creating my first prog with STM32CubeIde.I am able to produce .bin, .elf, .hex files for my project with CubeIdeI am able to read and produce a bin file of the program in flash in my board with the CubeProgWhen I want to flash back to the board using DFU mode, I noticed that bin file doesn t have any segment starting address, elf file instead, have a starting address 0x800000If I load a bin file, do I have to specify the correct programmer address I mean 0x800000 in cubeprog, because it doesn't itself :( 

 Hi everyone,I'm currently working with the ST25R3916B and trying to detect two NFC (ISO15693) tags simultaneously in the RF field.I'm using two ST25TV02KC tags and placing them close together above the antenna.However, my current implementation only ever returns one UID, even though both tags are clearly within range.I’m using RFAL and currently calling the following flow:  rfalNfcvPollerInitialize(); HAL_Delay(5); rfalWorker(); // or rfalNfcWorker() in some other attempts HAL_Delay(5); rfalNfcvInventoryRes invRes[16] = {}; uint16_t devCnt = 0; ReturnCode err = rfalNfcvPollerInventory( RFAL_NFCV_NUM_SLOTS_16, 0x00, nullptr, invRes, &devCnt );I tried increasing discConf_.devLimit = 5 and enabling only techs2Find = RFAL_NFC_POLL_TECH_V, but it had no effect.My questions:What is the correct RFAL call sequence (including delays, state machines, etc.) to reliably detect multiple NFC tags (ISO15693 tags) at the same time?Are there specific settings or steps to enable

I am experiencing issues with the VBAT pin on the STM32H753ZI Nucleo board. Specifically, the VBAT pin is not responding properly. I am using a CR2032 CMOS battery for RTC backup, but it is not maintaining the date and time as expected. When the power supply is off, the RTC does not hold and run correctly, but it resumes running once the power supply is restored. battery positive connected to VBAT and negative to GND. i have removed SB52. I have attached the IOC and main file for your reference.

Hello,in all examples for the STM32H7S78-DK - including the TouchGFX applications - the frequency for the external APS256XXN-OBR-BG PSRAM is set to 200 MHz:extmem_list_config[1].PsramObject.psram_public.FreqMax = 200 * 1000000u; But in the datasheet for the APS256XXN-OBR-BG, seehttps://www.mouser.at/datasheet/2/1127/APM_PSRAM_OPI_Xccela_APS256XXN_OBRx_v1_0_PKG-1954780.pdfit says that the default maximum read and write clock is 133Mhz, see page 16 and 18:It also says:"Write latency, WLC, is default to 5 after power up. Use MR Write to set write latencies according to writelatency table. When operating frequency exceeding Fmax listed in the table will result in write data corruption." Could the be a potential bug in the memory configuration of the STM32H7S78-DK board, which could lead to RAM corruption? Thank you and best regardsrk_iot 

I'm trying the new VS-Code extension 3.5.1, but I end up in the HardFault_Handler function during the initialization, in the "MX_USBX_Device_Init" function. The same project works correctly when using the "cortex-debug" plugin (separate VS Code profile to avoid conflicts).It's a very simple project where I did the very minimal config to enable USBX, and "UX Device HS -> Device Class HS -> HID -> MSC" on my STM32U5A5AJH6Q. The IOC file is attached.It crash in the function "USBD_FrameWork_MSCDesc", at line /* Append Endpoint descriptor to Configuration descriptor */ __USBD_FRAMEWORK_SET_EP((pdev->tclasslist[pdev->classId].Eps[1].add), (USBD_EP_TYPE_BULK), (uint16_t)(pdev->tclasslist[pdev->classId].Eps[1].size), (0U), (0U)); 

 Hello everyone,in my current project, I'm working with a Nucleo H743ZI2 (with an STMH743ZIT6). My goal is to read audio data from MEMS microphones using DMA and DFSDM filters. The ultimate aim is to build an 8-microphone array, but for the first step, I only want to read data from a single microphone. And this is exactly where my problem lies: currently, no data is being saved in RAM. I suspect the problem is with DMA, as I've observed the following:DFSDM:The following bits are set in the DFSDM control register: DFEN (DFSDM_FLT enabled), RCONT (continuous mode), and RDMAEN (DMA channel enabled to read data for the regular conversion).The value of the RDATAR register changes continuously => data is being read by DFSDM.In the ISR register, REOCF (end of regular conversion) is set, followed by ROVRF (regular conversion overrun) => REOCF should be cleared by DMA (it might be cleared and set again, which goes unnoticed during debugging, but i don´t think so as the DMA is not sta

Hi,  I'm struggling to monitor the debugging values on the MEMS studio. setup1. MEMS studio 2.1.1 (latest version)2. Sensor PRO Tile Box + STEVAL-MKI229A(LSM6DSO16IS)3. ST Official ispu-example GitHub, normhttps://github.com/STMicroelectronics/ispu-examples/blob/master/ism330is_lsm6dso16is/norm/output/norm.json4. ispu-examples/ism330is_lsm6dso16is/norm/output/norm.json    loading this json to the board through MEMS studio5. I can see the entire blank on the "Data Monitor" Page with checked "ISPU Output".6. Toggle the "ISPU Output" to the un-checked state, everything can back to the normal.