Solved

I keep getting warnings when using STM32CubeProgrammer_CLI that usb devices are still referenced: libusb: warning [libusb_exit] device x.x still referenced. This is a bit annoying.-------------------------------------------------------------------STM32CubeProgrammer v2.17.0-------------------------------------------------------------------libusb: warning [libusb_exit] device 4.7 still referencedlibusb: warning [libusb_exit] device 4.8 still referencedlibusb: warning [libusb_exit] device 4.6 still referencedlibusb: warning [libusb_exit] device 4.5 still referencedlibusb: warning [libusb_exit] device 4.1 still referencedlibusb: warning [libusb_exit] device 3.1 still referencedlibusb: warning [libusb_exit] device 2.1 still referencedlibusb: warning [libusb_exit] device 1.3 still referencedlibusb: warning [libusb_exit] device 1.2 still referencedlibusb: warning [libusb_exit] device 1.19 still referencedlibusb: warning [libusb_exit] device 1.20 still referencedlibusb: warning [libusb_exit]

Hi In the past 6 months, I created a project for an STM32H755. For middleware, I selected CMSIS RTOS v2 (using FreeRTOS underneath).I noted that the header file is cmsis_os.h, which at first seemed wrong. I (maybe naively) asked the "AI", and with it's usual confident tone, suggested I change them (however, this is hard to maintain if you change your .ioc file).Looking at past posts on these forums, and inside cmsis_os.h, I confirmed that cmsis_os2.h is indeed included within it (despite the AI not finding this).So, I challenged the "AI", stating what I had found. Of course, in it's somewhat complimentary way, it agreed with me, but still insisted that if I am using entirely v2 APIs, I should change the headers.Of course, such responses derive from human content written elsewhere, and I fear it may not backed by actual facts. I have left the headers as they are for now. I have a bad feeling about changing them as ST might have reasons to do things the way they have. So, is it

Hello, does ST67W61 module support pass-through mode?   I have an application based on a third-party IP stack and it would be a pain to rewrite it all with AT primitives. A far simpler solution would be replacing low-level calls to transmit and receive Ethernet frames over SPI link.   Alessandro

   Hello STMicroelectronics Support Team, I would like to make a custom wireless power transfer based project. I was trying to download the GUI (STSW-WBC2STUDIO). I am planning to use STEVAL-WLC38RX and the STEVAL-WBC2TX50. Please send me the software package asapThank you for your support. 

Hello, I am starting my project with CubeMX and CubeIDE right now and I am encountering massive time issues.For example it took almost 25 minutes to go from the IOC file to the generated code (throuh the autogenerating functionnality). It also took 3 minutes and 45 seconds to build a basically empty program (except for the inits).I'm running on CubeIDE v1.19 and CubeMX v6.15.My laptop is Windows 11, I have 32 GB RAM, 13th Gen intel Core i7-13700H.If you guys have any advice on how to work around it that would be great. Thank you very much !

Hello,  I was wanting to make my own camera board and I wanted to use the same camera that is on STM's Camera board MB1854 and I looked up that manufacturer part number (AS-BC538A3M6-63(1.02.A3265)) and nothing showed up, and when I looked up just AS-BC538A3M6-63 then the only result was STM's example schematic for the MB1854 camera board. I then tried looking up the company they listed on the BOM (HONGJIA) and still found nothing. Does anyone know how to find the board or even some contact info for that company?  ThanksCarson 

Reading STM32U5A5 Rev. ID returns 0x3003 using STM32Cube HAL API that is not listed in Reference Manual (RM0456). What is the revision of this product? The Reference manual lists only 0x3001 as revision X and 0x3002 as revision W.Thanks.

Hello, I'm using WinUSB and I'd like to program the flash memory at address 0x0800c0000 in 256-byte increments. This works fine the frame but every frame after this gets written to blocks in increments of 1024. It seems that if one needs to push more than 1024 bytes then I must use 1024byte pages. Does this sound correct? I'm testing this on a Nulceo H7A3ZI-Q

I've spent some time recently trying to prototype a small project based on the STM32H503 which would need to have the ADC and DAC running simultaneously with multiple channels of analog I/O via DMA. I was able to get this all coded up but discovered that sometimes on reset the DAC outputs were not as expected. Cycling power or asserting NRST would sometimes fail and sometimes operate properly. A quick look through the H503 errata revealed that this is a known issue - "2.2.21 Invalid DAC output voltage for several DAC kernel clocks".The problem is that the DAC requires both a bus clock and a kernel clock, and likely because of a synchronization issue between them the kernel clock and bus clock must be the same. Ordinarily this wouldn't be a huge problem except that the DAC and ADC share their kernel clock and the ADC is limited to a maximum 125MHz for its kernel clock. This results in the derived requirement that the AHB bus clock cannot exceed 125MHz when both the DAC and ADC are used

HiIs it possible to configure the interrupt function for free-fall with normal XYZ polled operation, or is it better to use the interrupt in low power mode and performing the free-fall via normal XYZ programmatically in normal operation?Thanks! 

After solving my issue with reading the USER1 button (thanks to everyone who helped me on this forum :folded_hands:), I am now trying to handle USER1 button detection using interrupts.My project is running in FSBL mode, so I’m using NVIC FSBL. I’m trying to configure the USER1 button (EXTI13) with a pull-down in CubeMX. …but unfortunately without success.what is wrong ? in my configuration in CubeMX ?  Cheers Emmanuel my code stm32n6xx_it.c :   with void EXTI13_IRQHandler(void)/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file GPIO/GPIO_IOToggle/Src/stm32n6xx_it.c * @author MCD Application Team * @brief Main Interrupt Service Routines. * This file provides all exceptions handler and * peripherals interrupt service routine. ****************************************************************************** * @attention * * Copyright (c) 2024 STMicroelectronics. * All

I am planning to have my application interface with the service API of the X-CUBE-ST67W61 Software package. How does the shell utility interface with the Service API? Is the communication interface through a queue?

Hello everyone! I'm working on an application using AzureRTOS and FileX, however, I'm getting a hard fault that I can't pin down.Here is a screenshot of the variable states when entering _fx_directory_search (in middleware fx_directory_search.c) which causes the hard fault. It seams to occur as the function is called. (Not sure why the resolution is bad but don't think there is anything I can do about it I'm sorry!)I'm seeing a lot of 0x0 in the function arguments.media_ptr FX_MEDIA * 0x0 name_ptr CHAR * 0x0 entry_ptr FX_DIR_ENTRY * 0x0 last_dir_ptr FX_DIR_ENTRY * 0x0 last_name_ptr CHAR ** 0x200012a8 <fx_byte_pool_buffer+408> i ULONG 4025479151 n ULONG 1627389952 found UINT 134272988 status UINT 4025479151 v UINT 134276061 j UINT 10 cluster ULONG 536875464 next_cluster ULONG 4025479151 directory_size ULONG64 2305863900471563680 And a screenshot of the states before entering the above function: I take note of:name_ptr CHAR * 0xffffffff <error: C

The last few lines of  StMicro’s ST25DV-I2C  low power application note (high lighted) are ambiguous. Does “ST25DV-I2C” have the ability to read/write EEPROM without power applied between pins VDCG and GND? (YES/NO)  Our desired application needs to read/write EEPROM via RFID when microcontroller's battery is dead.   StMicro Literature (see attached *.pdf)Ultra-low power stateTo save power, the ST25DV-I2C is completely shut down most of the time. In that state, the GPIO connected toST25DV-I2C’s VCC pin can be either forced to low-level output, in high impedance mode. The GPIO connected tothe ST25DV-I2C’s LPD pin can be in any state, high or low output, or high impedance without any influence onpower consumption.If the ST25DV-I2C is powered by the RF field, it can receive and answer from any RF command and can sendan interrupt signal on its GPO pin to the microcontroller. The VDCG pin needs to be permanently powered. I2Ccommunication is not working. In

Hi,I'm using an STM32H7 microcontroller and need to get the RTC working.I set RTC_OUT to 1Hz and set the LSE to a 32.768Hz crystal, and inserted the CR2032 battery.When the microcontroller is powered (VDD 3V3), I see the waveform oscillating at a frequency of 1Hz.My question is: should the signal on the RTC_OUT pin remain when I remove the power?Thanks

Hello everyone We successfully designed a custom board using the STMCSDK V6.4.1 and here is its specifications:MCU: STM32F030K6T6POWER BOARD: Based on STEVAL-IPM10Bwe successfully got a motor running and its nominal values are as follows:Pole Pairs: 5Vbus = 400V, Current = 2Amps, Speed = 1500rpm.We used the same board with another motor:Pole Pairs: 40Vbus = 400V, Current = 2Amps, Speed = 500 rpmThe First one runs smoothly and everything is fine, but the second one is making some annoying audible noise inside the motor. We tested it with a commercial board and its totally fine, so the motor isn't the problem.I have taken these steps so far and none of them have worked:1: decreasing and increasing the pwm frequency 2: decreasing the pi coefficients for the PLL3: decreasing the G2 coefficient for the observer 4: decreasing both kp and ki for torque and flux control loops5: decreasing and increasing deadtime for switching 6: decreasing and increasing the sampling cycles

The goal of my program is to:          1. Set low power time that runs off HSI for 10 seconds          2. Enter stop2 WFI           3. Wake up from low-power interrupt          4. Advertise for 5 seconds            5. Stop advertising          6. Repeat StepsDuring stop2 at the beginning of program my system is using ~ 74uA (which seems high but is reasonable), and when I wake up to start advertising and call aci_gap_set_discoverable(). This raises the current to ~3.4mA while advertising but when I call aci_gap_set_non_discoverable() it only lowers the current draw to ~3mA.I would expect the system to go back to the ~74uA it was drawing before advertising was turned on but it is not. I am able to connect to the chip over bluetooth successfully just want to know what needs to be done to get the power draw wher

I have a powerSTEP01 driving a stepper motor with the coil current set to 2A. However, the current flowing in the coils is unstable when it is flowing in one direction:Sorry about the image quality - I have an old 'scope, so had to use a photo ;)The image shows the coil current as the motor steps. The current is stable at 2A when the coil is energised in one direction, but not in the other.Any ideas what can cause this?

I would like to ensure that I can use HAL_FDCAN_GetRxFifoFillLevel() function in  HAL_FDCAN_RxFifo0Callback() like this: void HAL_FDCAN_RxFifo0Callback(FDCAN_HandleTypeDef *hfdcan, uint32_t RxFifo0ITs) { if (RxFifo0ITs & FDCAN_IT_RX_FIFO0_NEW_MESSAGE) { // used loop to read all messages from FIFO while (HAL_FDCAN_GetRxFifoFillLevel(hfdcan, FDCAN_RX_FIFO0) > 0) { can_msg_t rx_msg = {0}; if (HAL_FDCAN_GetRxMessage(hfdcan, FDCAN_RX_FIFO0, &rx_msg.hdr, rx_msg.data) != HAL_OK) { break; } rx_msg.data.data_len = (uint8_t)dlc_to_bytes(rx_msg.hdrDataLength); // put rx msg to queue osMessageQueuePut(rx_queue_handle, &rx_msg, 0, 0); } } } When I googling more whether I can use HAL_FDCAN_GetRxFifoFillLevel() in ISR CalIback I got:HAL_FDCAN_GetRxFifoFillLevel is not guaranteed to be ISR-safe because it's a read operation on a peripheral register that doesn't automatically handle atomic operations, which are required in interrupt contexts to preven

I designed simple board around STM32C011J6 MCU (SO8 package). I'm using fresh-from-packaging parts, ordered from Element14 (Farnell). When I try to connect to MCU (via SWD, using ST-LINK/V2 ISOL), I get "Can not read memory! Disable Read Out Protection and retry" error:13:05:51 : Connected via SWD.13:05:51 : SWD Frequency = 0,9 MHz.  [I've tried frequencies between 400kHz to 4MHz, same result]13:05:51 : Connection mode : Connect Under Reset.13:05:51 : Device ID:0x44313:05:51 : Device family :Unknown device13:05:51 : Can not read memory! Disable Read Out Protection and retry.Chip Erase doesn't work either, which suggests RDP2 (if indeed enabled). Is there some issue I concerning board layout/setup have managed to miss (SWDCLK for instance is used to control a FET in main application, but that should not interfere here; SWDIO and NRST are not shared), or has someone delivered me bogus parts (as I suspect)?I am not seeing any activity on any of the MCU pins when disconnected fro

Hello ST team,I’m evaluating AEK-POW-BMS63EN with the AEK-POW-BMSHOLD. I’m seeing a bring-up problem where the pack voltage is correct but the board appears “dead” (no refs, no LEDs, SPI values = 0/NaN).SetupBoards: AEK-POW-BMS63EN (2 units available; this post is about the connection/reading behavior).Battery holder: AEK-POW-BMSHOLD.Cells: 18650 “INR 18650 MJ1”.Population: progressed from 6S to 14S (final VBAT ≈ 50 V).MCU/comms: AEK-MCU-C4MLIT1 + AEK-COM-ISOSPI1; UART 115200 to PC.Firmware: AutoDevKit example reading cell/temperature; balancing disabled.Power-up: mate the full holder connector once, with MCU unpowered; then power MCU and start SPI (no pin-by-pin hot-plugging).Measurements (board powered by pack)VBAT at the holder/connector: ≈ 50 V (matches cells).VREF, VCOM and other reference rails on the BMS board: 0 V (some readings slightly negative).LED indication: none (docs suggest at least one LED when VBAT > ~9 V).SPI: V1…V14 = 0.000 V, T1…T14 = NaN (make sense since

Can't connect to new board: NUCLEO-N657x0-Q Error: No STM32 target found

Title and content edited: modified MPU by MCU. There is a big differenece between MPU and MCU products Hi,   we are currently selecting an STM32 MCU.   We need a dual core M7+M4 and so we've spotted STM32H757, so far so good. Unfortunately we (lately) found out that even if its timer(s) are stated as HRTIM they do not have the DLL feature implemented and do not support high resolution PWM. So the question is "Is there any ST MCU fullfilling both requirements, M4+M7 and HRTIM with DLL?"   Thks  

Hello We are preparing the following modes for the authentication test. 1) Unmodulated signal continuous output (typo corrected!) 2) Modulated signal continuous output 3) Adjust each signal output dB   1 and 3 have been resolved, and we are having difficulty outputting 2 modulation signals. So far, RFAL functions cannot output modulated signals continuously, and the driver code for ST25R3916 must be configured, but it has not been successful yet. (1, 3 are implemented as RFAL functions)The way I want to use it is "Start function call -> modulated signal continuous output" and "Stop function call -> output end". What I've tried now is that I've been working with rfalNfcWorker()  For "RFAL_NFC_STATE_POLL_TECHHDETECT", we fixed "gNfcDev.state" to "RFAL_NFC_STATE_LISTEN_TECHHDETECT" instead of "RFAL_NFC_STATE_STATE_DISCOVERY". Is this the right way?  

Hello All, I'm usin SR6P3 ARM mcu. I have to implement a simple SPI communication with StellarSDK. When send/receive starts the communication stucks in a while cycle where the code checks Tx queue busyness. while (queue->tx_busy == SPIQ_QUEUE_TX_BUSY) {                 ; }   Never comes out from this while. The clock is 1MHz. But if I set the clock lower like 50kHz, then the communication is good. This is the pin configuration: /*===========================================================================*/ /*                              SPIQ 0                                       */ /*===========================================================================*/ /* SPIQ0  CLK - PJ12 */ #define SPIQ0_CLK siul2_iopack(SIUL2_PORT_J, SIUL2_PAD_12) #define SPIQ0_CLK_