Solved

I'm freezing on the following screen, is there anything I can do?TK

I have a question about the MEMS audio sensor MP23DB01HP. I think i already undertood that the output is a PDM, but my question is, how can I convert that to obtain a corresponding value in dB? Or some used unit? I have done the acquisitons, but know i don't know what to do with that values... Thank you in advance for your replies

I'm trying to make own dfu application on STM32F746G-DISCO board.I've already tested dfu function by using ST's DFU_Standalone demo example which is worked under USB device mode.Demo example is also provided upgradable sample application which is named as STM32746G_DISCOVERY_SysTick_0x08008000.dfu.I can upgrade this application by using DfuSeDemo.exe on windows 10 PC and It works well.But if i made a simple led toggle dfu application, It cannot run.In this case, i have used the same DFU bootloader. Just changed application.Below is what i modified for dfu application--------------------------------------------------------------------------------1. Changed app's flash location to 0x08008000 in STM32F746NGHX_FLASH.ld2. Changed VECT_TAB_OFFSET to 0x8000 in system_stm32f7xx.c.the board is always running in DFU mode even if there is no error by using DfuFileMgr.exe and DfuSeDemo.exeSo i checked flash's USBD_DFU_APP_DEFAULT_ADD(0x08008000) location by using STM32CubeProgrammer.It shows 0x200

Hi community,I have a problem that other people have also raised and I'd be grateful for help.I followed AN5361 and I watched this STM video on the same topic. First thing to mention is that the video and doc have different advice about whether the CM7 should Halt All Cores (Video advice) or not (AN5361 advice). Grrr!Now I've got that off my chest here's the problem in more detail.CM7 like this:  CM4: With that configuration when I launch CM7 first, then CM4, both pause as expected with CM4 in reset and CM7 ready to go. When I select both cores then click on the green go arrow, CM7 runs straight into this:Caused by the timeout expiring.If, alternatively, I configure CM7 like this:Then I can debug both cores, but they aren't doing a coordinated start as they should.I know that I could ignore the timeout error, but then the systems wouldn't be doing a coordinated start as they should.Any suggestions please?    

Dear ST Team,I am having difficulty finding the ULD library for the VL53L3CX chip. The complete library is too large for my chip's Flash memory, and the ULP library's ranging capabilities and accuracy do not meet my requirements. Could you tell me if there is a ULD library available for this chip, similar to the one provided for VL53L1? Thank you for your assistance.

I'm trying to use my NUCLEO-H753ZI board to send some message to my PC using UART. I read from the data sheet that USART3 is connected to the ST-LINK for the Virtual COM Port (VCP), and USART3 can directly transmit messages to the PC. However, in the configuration window, USART3 is greyed out and cannot be configured. Is this normal? If so, how can I send messages to my PC using this board?

Hello, I want to enable the secure connection key type as 'DEBUG' in STM32WB55 with my custom setup. The cube IDE does not allow this setting in the configuration of .ioc file. I followed this tutorial and added the following line in my code inside the definition of Ble_Hci_Gap_Gatt_Init() function, but it returns with error code 0x12 (Invalid HCI parameters). What am I missing here? static const uint8_t SC_KEY_TYPE_DEBUG = 1; static const uint8_t SC_KEY_TYPE_NORMAL = 0; ret = aci_hal_write_config_data(0x35U, 1, (uint8_t*)&SC_KEY_TYPE_DEBUG); if (ret != BLE_STATUS_SUCCESS) { APP_DBG_MSG(" Fail : aci_hal_write_config_data command - CONFIG_DATA_SC_KEY_TYPE_OFFSET, result: 0x%x \n", ret); } else { APP_DBG_MSG(" Success: aci_hal_write_config_data command - CONFIG_DATA_SC_KEY_TYPE_OFFSET\n"); }I am also following AN5270 for development, and the offset to set SC_KEY_TYPE seems to be correct. This is what I am seeing when I run the code: I made sure that CFG_

Hello, I am using STM32WB55 chip on my custom setup. I have configured my device in peripheral mode. I want to be able to accept / reject pairing requests initiated by the client device. I am following AN5270 for development. I have added code to set bit3 in SMP_MODE register to enable the generation of pairing request event. Although, the documentation says "SMP MAY generate the event". Why is that? The documentation also says that if I bypass the SMP, all the events that go to SMP will be transmitted to the application. However, what are the other events handled by SMP? I am not able to find a list of events handled by SMP. Is there any other documentation that I am missing? I also looked at an older thread in which the functionality to accept / reject pairing request did not exist. But since not it exists, do you have an example code where it actually works?Any help is appreciated!  Here's the old thread: https://community.st.com/t5/stm32-mcus-wireless/what-is-th

Hello, We would like to integrate LSM6DS3TR sensor.For that to happed we need SEE (Secure Execution Environment) framework drivers for Qualcomm based processors. Could you please supply drivers for that? It is urgent. Thank you.Best regards,Miha

Hi,I am using the ism330dhcx and lis2mdl and run the MotionFX  algo.the ism330dhcx data rate is 104Hz and the lis2mdl is set to 100Hz (sensor hub ODR set to 104Hz)should i run MotionFX  algo at 100Hz or 104Hz ?on ST examples, when the ODR is set to 104, the ALGO_FREQ is set to 100 !is this difference can generate wrong values on fusion algo ?i notice that if i run the magneto calibration at 104Hz, the calibration is never reachif i use 100Hz for magneto calibration and 104Hz (or 100) for MotionFX  algo it is workThank you,Sincerely.

HiI am not an IMU expert. My current task is to upgrade an old board which used LSM6DSL(gyro abd accelerometer ) and lsm303agr(Magnetometer) to caliculate orientation of a human head.As far as I can see LSM6DSV would be providing orientation data without gyro. So I dont need a magnetometer?When it comes to orientation data, what is the benefit of having a magnetometer? How does it come LSM6DSV is doing the job without magnetometer?

In the schematic for STM32N6 Vddcore power rail (attached), voltages of 0.81V and 0.89V are output from the SMPS using resistor dividers. I understand how the output of 0.81V was achieved using the 56K and 160K resistors and formula from the SMPS datasheet, but I'm not clear how the 0.89V output was achieved when the third resistor of 422K was added in parallel when the n-channel mosfet is used. Can someone please share the formula/how this was calculated?

Hi, I am working on OEMiROT bootloader for STM32H523. I have copied big parts of the ST OEMiROT example project from H533 example as this is the closest MCU to H523 from the flash memory layout perspectives. However, it is taking ridiculously too long time to refactor the security parts of the project as the H533 does have more hardware security peripherals than H523. I have cloned the STM MCUBoot and the ST Mbedtls repos in my project. I would love to know if there is an OEMiROT project example(s) for H523 and if you have any recommendation on how to process this faster as it has been taking forever to refactor and recompile the H533 example on H523 MCU. Cheers,Hani

On the wiki page:https://wiki.st.com/stm32mcu/wiki/STM32MotorControl:SDK_AC_induction_motor It says:""This article applies to the 5.Y.* versions series of the X-CUBE-MCSDK. ACIM motors are not supported in older versions of the X-CUBE-MCSDK (v5.4.* and before). They are not supported yet in X-CUBE-MCSDK versions 6.*." However, the latest v5 version I can download is 5.4.8. So, it appears that I would need to use version 6 to compile the examples, while full support comes later?       

I'm currently at schematic stage designing a board based around the STM32U5G9ZJT6Q. The PCB will be produced and assembled by JLCPCB, so I had a look for a HSE crystal they have in stock and found this:https://jlcpcb.com/partdetail/YangxingTech-X322516MLB4SI/C13738https://jlcpcb.com/api/file/downloadByFileSystemAccessId/8579709258350247936Calculations seem to check out OK (Gm_crit < Gm_critMax), I'm just a bit unsure about the Rext resistor and whether it is required for this part. I have put an 0603 0R resistor in for now, is there a way to calculate whether I will need some resistance there, or does it require measurements to be taken on the circuit, then adjust accordingly?Many Thanks,Anthony

I'm in trouble using dll with c# for using the mailbox.Can someone help me?Please @Ulysses HERNIOSUS , my friend, help me! I'm pain too! Here is the code: private void TxRxNBytes_Click(object sender, EventArgs e) {//This is a button click event handler    sbyte[] rx = new sbyte[512];    //Here following is the reversed uid byte sequence compared to the one reported from software ST25PC-NFC    byte[] uid = [0x61, 0x92, 0x74, 0xD0, 0x01, 0x24, 0x02, 0xE0];        ee = ST25R391x_Dll.iso15693Select(Handle, uid);    // ee=NoError    sbyte[] tx = { 0x10 , unchecked((sbyte)0xAA) , 0x02 , 0x06 , 0x01 , 0x02 , 0x03 , 0x04 , 0x05 , 0x06 };    ee = ST25R391x_Dll.iso15693TxRxNBytes(Handle, tx, 10, rx, ref uRxDim, 1);    //    ee=NoError... // ... but microcontroller hosting ST25DV04K doesn't receve the GPO signaling.//  

[EDIT 03/04/25 09:15:35 AM] Well, it appears that, as usual, the real issue was sitting right in front of the keyboard… and could have been solved with a good old ‘Read The Freaking Manual.’ My deepest apologies for this classic case of user error! :grinning_face_with_sweat:Sensor_ID inversion (0x01 and 0x02) I'm struggling with programming the ISM330DHCX on a sony spresense. By following the documentation I write my register with these values:CTRL1_XL: 0b01001000CTRL2_G: 0b01001100FIFO_CTRL1: 0b10010000FIFO_CTRL2: 0b00000000FIFO_CTRL3: 0b01000100FIFO_CTRL4: 0b00000110FIFO_CTRL3C: 0b01000100The I read the FIFO (SPI) with this kind of code :    void ISMSensor::read_FIFO(uint8_t *buffer, uint8_t ism_watermark) { uint16_t transferSize = (ism_watermark * 7) + 1; uint8_t tx_rx_buffer[transferSize]; tx_rx_buffer[0] = ISM330::ISM_REG::REG_FIFO_DATA_OUT_TAG | 0x80; for (uint16_t i = 1; i < transferSize; i++) { tx_rx_buffer[i] = 0x00; } bus-&gt

Would it be possible to connect and send sensor data to a Pi Pico W from the STEVAL-MKBOXPRO? I’m looking for a way to connect them together via Bluetooth but a wired connection would be alright too. I have connected a Pico to the sensortile box via Bluetooth already but I do not know how I can gather sensor data from this. Also is there any official or unofficial documentation on any similar endeavors? I’ve found this link which seems promising but the implementation is not very detailed https://community.st.com/t5/mems-and-sensors/how-to-create-a-custom-gaming-controller-using-sensortile-box/ta-p/597296. 

Hello,I have a GPIO pin that is owned and used by the M4, i.e. Pin Context Assignment.  But on power-up, I'd like the M7 to do some work with it, toggle the state, before it starts the M4.  Is it possible for the M7 to programmatically take ownership of the GPIO pin, then transfer it back to the M4 just before it starts the M4?Regards,Robert 

Hello, I am working on a project that includes HTTPS communication, peripheral communication via LIN, and a graphical user interface. I am using the STM32H745I_DISCO board. I have already tested and successfully implemented the HTTPS and LIN parts.Yesterday, I started investigating how to get the GUI up and running. I downloaded an image with TOUCHGFX 4.24.2, and it displayed correctly. Then, I followed the example from this link to configure it via CubeMX, but without success. The strange thing is that when I tried downloading an image or a demo to the board again using TOUCHGFX 4.24.2, artifacts started appearing. I tried erasing all the memory areas visible in STM32CubeProgrammer, but after loading an image or demo, the artifacts persisted. The last thing I tried was loading a blank GUI. I am attaching an image of what appears on the screen: vertical red stripes and pixels randomly turning on and off in red. It seems like a RAM read issue, but I can't understand why it per

Hello ST,I'm developing a USB CDC communication project on an STM32L452RE microcontroller using STM32CubeIDE.I can successfully receive data from a PC using the Hercules SETUP utility by HW-group.com.I'm facing a challenge with transmitting data back to the PC using the CDC_Transmit_FS function.Environment:MCU: STM32L452REIDE: STM32CubeIDECUBEMX: STM32CubeL4 Firmware Package V1.18.1USB Configuration: Configured as a CDC Virtual COM PortOS: Windows 11USB Interface: Hercules 3.2.8Issue Description: Data reception from the PC works flawlessly. However, when attempting to transmit data back using CDC_Transmit_FS, the function seems to never complete. The code gets indefinitely stuck waiting for hcdc->TxState to reset to 0, which, based on my understanding, should happen via an interrupt once the transmission completes.Troubleshooting Done:Create a new ST board project using this video USB tutorial:https://www.youtube.com/watch?v=92A98iEFmaA&t=212sConfir

Hi,I'm developing a bare-metal project with the SR5E1Ex (E3 and E7), and need to determine the current core ID at run-time.Could you please confirm if there are any registers that can be read to determine the current core ID? The only multicore examples I can find for the SR5E1Ex chips use different restart locations to determine the current running core, but if there are any registers that can be read with the core ID, that would be preferable.Regards,Steven Daglish

So I'm having this issue with a Nucleo STM32H563ZI board regarding the USART3 that connects to the VCP ST-Link port.If I enable the USART3 at 115200 baud rate, and keep all the default parameters and, in the clock configuration, if I do not change any clock parameters, except to configure the HCLK to 250Mhz, then the USART3 Clock Mux will use PCLK1 and also will output a clock frequency of 250Mhz.So basically all defaults without too much changes except the HCLK.In this situation, the USART3 works just fine, meaning that I can see correctly the data that is output by the USART with a terminal program. So far so good.Nevertheless if I change the main clock source to the 24Mhz crystal, hence use the HSE and still keeping the HCLK at 250Mhz, the USART Clock Mux will still also be at 250MHz (still using PCLK1), BUT this time the USART output is just garbage meaning that the baudrate calculation is just wrong.If I drop the USART clock mux to 4Mhz, for example everything just starts to work

Hello ST Community,I was successfully working with my STM32WB55RG Nucleo-64 and had FUS (Firmware Upgrade Service) and the BLE stack properly uploaded and running initially. However, after attempting to modify some register values in the Option Bytes, I encountered a serious issue where FUS and the wireless stack appear to be corrupted.Now, when I try to upgrade or reinstall the BLE stack, I am facing errors, and FUS is no longer functioning properly. FUS Version is now corrupted and shows invalid values (attached screenshot).FUS upgrade is failing – attempting to reflash FUS results in errors.BLE stack cannot be reinstalled due to the corrupted FUS state.Attempts to start FUS fail with FUS_STATE_ERR_UNKNOWN.Steps Tried to Fix the Issue:1. Attempted to Reinstall the BLE Stack (stm32wb5x_BLE_Stack_full_fw.bin) → Failed due to FUS corruption.2. Tried Deleting the Wireless Stack in STM32CubeProgrammer →  Did not resolve the issue.3. Performed a Full Chip Erase → FUS corrupt

Could you tell me the differences between the IIS2DLPC and LIS2DW12?According to the reference URL, are there any differences between these two devices other than product longevity and guaranteed parameter values? I am particularly interested in whether there are any differences at the wafer level.From a business continuity perspective, we would like to evaluate both the IIS2DLPC and LIS2DW12. However, it would be a waste to evaluate the same hardware twice. If it can be confirmed that there are no differences, we would like to evaluate only the LIS2DW12. Reference URL:https://community.st.com/t5/mems-sensors/iis2dlpc-vs-lis2dw12/m-p/179418