Solved

Congratulations. I have such a problem. I've made 1000 PCB prototypes and 30% don't want to enter DFU mode. If you try to turn the PCB back on multiple times, the part will go into DFU.I'm using a USB Type-C connector, could that be the problem? Also tried changing the USB cable, but that didn't fix the problem.I use a microcontroller STM32F405RGT6TR.What can this be related to?

I am working with the X-NUCLEO-IKS4A1 expansion board and NUCLEO-F401RE.I’ve successfully programmed and run the examples provided by MEMS Studio and those in the STMems_Finite_State_Machine/application_examples/lsm6dsv16x repository. Additionally, I’ve used .ucf files and AlgoBuilder to generate C programs.But I have no idea how to program my own FSM from scratch. I have read some of AN5882 but I am not sure if that is the right way to learn about FSMs. Are there any tutorials I am missing?How do I implement my own FSM from scratch based on my own requirements and application? I would like pointers to some good tutorials with examples which explain how to program the FSM.

I'm testing whether HAL_I2S_TxCpltCallback or HAL_I2S_TxHalfCpltCallback is called properly by setting i2s to normal and periodically calling HAL_I2S_Transmit_DMA. However, HAL_I2S_TxCpltCallback or HAL_I2S_TxHalfCpltCallback is called only once and not again. I want to use i2s in normal mode, not circular mode, so I'm testing like below. Is there something wrong?When I check the return value with status = HAL_I2S_Transmit_DMA(&hi2s2, audioBuffer, AUDIO_BUFFER_SIZE);, HAL_BUSY(2) is returned. while (1) { HAL_I2S_Transmit_DMA(&hi2s2, audioBuffer, AUDIO_BUFFER_SIZE); HAL_Delay(1000); } void HAL_I2S_TxCpltCallback(I2S_HandleTypeDef *hi2s) { dma_count++; } void HAL_I2S_TxHalfCpltCallback(I2S_HandleTypeDef *hi2s) { dma_count++; } 

Hi,   typedef struct { uint8_t Status; /*!< ResultStatus */ uint16_t Distance; /*!< ResultDistance */ uint16_t Ambient; /*!< ResultAmbient */ uint16_t SigPerSPAD;/*!< ResultSignalPerSPAD */ uint16_t NumSPADs; /*!< ResultNumSPADs */ } VL53L1X_Result_t; We have cases when the Sensor Status result is non zero.  When it is it is usually a 3 or 255: #define RANGE_ERROR_DISTANCE_BELOW_DETECTION_THRESHOLD 0x03#define RANGE_ERROR_OTHER 0xFF I asked about these in a different post but now I have a somewhat different perhaps more general question.  If the Status returns a non zero in any case should the Distance be disregarded -- in all cases? Or,  are there certain non zero Status conditions where we should "trust" the Distance versus not "trust" the Distance (reading) returned? As usual thank you, Will    

I'm adding Power-Down mode to my Listen Mode implementation, and have come across some unexpected behavior.I keep the chip in Power-Down, with the field detector set to automatic, and then see EON when a field is detected, as expected. The first time this happens, it behaves as expected (see first screenshot): the osc_ok bit was set automatically upon EON, then I set en and rx_en, and ~1ms millisecond later, the IRQ comes in. But the next time, 100-300ms after the previous emulation, it doesn't behave the same way. The osc_ok bit is set after EON, then I set en and rx_en, but the IRQ never comes in. This all the same logic as the previous cycle - so EON is definitely not masked, and should be coming in after ~1ms. Is there some logic/behavior here I'm missing?

Hi everyone,I am implementing the communication between MCU SPC582B and High side driver VN9D5D20F. SPI signals seem fine to me, see next image:Spi Clk frequency = 625kHz  (range is 0Mhz to 8Mhz)CS transaction time = 71usTime between bytes = 7usTransaction 1 = read CTRL (en = 1, parity = 1, GSBN = 1)Transaction 2 = read SOCR (all zeroes, GSBN = 1)Transaction 3 = GSB = 20h (SPIE = 1) On the third transaction, I can't understand why reading SOCR register cause the driver to throw the SPI error (clk count is adequate and SDI is not stuck.I can't figure out what I am doing wrong. Any help would be very much appreciated. Thanks,FP 

What is the Hex code to enable extended mode for the VL53L4CX please ??

MCSDK 6.3.1, FOC with STOPLL, EVSPIN32G4, this motor.We're using a custom board based on EVSPIN32G4 as a drone ESC in a traditional sensorless configuration. Naturally, in our application the motor starts up to a low RPM under idle load and then after FOC takes over it spins up and down within the whole range as commanded by the autopilot. The MCSDK is in the speed control mode.We have found an interesting fault condition (also recreatable with the original EVSPIN32G4): if the motor is held in place somewhat elastically, e. g. by hand, during startup, the following things might happen:Speed feedback fault flag is set ~45% of the time -- expectedStartup fault flag is set ~45% of the time -- expectedNo fault flag is set, the motor is not spinning (sometimes making noises), the indicated RPM jumps to very high negative numbers, followed by speed feedback fault after a few seconds -- unexpected, but easy to catch and handle, RPM flips are easy to see.No fault flag is set, the motor is

I want to generate 6 PWMs using channel 1 of timers 1,8,2,3,4,5. All of them are set the same way except ARR, PSC and CCR1 registers. However, it turned out that timers 2 and 3 don't have PWM signal on their pins. The content of registers for those timers are the same (checked during debugging). I also tried to initialize timers by writing directly to registers, with no luck. MCU: STM32F103RCT6. Here is the the initialization for timer 3, for example: // ------------------------- PA6 settings ------------------------- // RCC->APB2ENR |= RCC_APB2ENR_IOPAEN; // Port A clock (PA6 - TIM3_CH1) GPIOA->CRL |= GPIO_CRL_MODE6; // PA6 speed MAX GPIOA->CRL &= ~GPIO_CRL_CNF6_0; // Alternate function Push-Pull GPIOA->CRL |= GPIO_CRL_CNF6_1; // ------------------------- TIM3 settings ------------------------- // RCC->APB1ENR |= RCC_APB1ENR_TIM3EN; // TIM3 clock TIM3->CCMR1 &= ~TIM_CCMR1_OC1M_0; // PWM mode 1 TIM3->CCMR1 |= TIM_CCMR1_OC1M_1; TIM3->

Hi,By mistake in our PCBA, ST 556D4 K148/B IC is used instead of M95256 EEPROM.now I am searching for ST 556D4 K148/B datasheet.Can you share the datasheet of this IC ?

In HAL_DACEx_ClearConfigAutonomousMode(), a test is surrounded by parentheses that are clearly unnecessary in code generated by STM32CubeMx.This is not very important... but it generates warnings that I check at each compilation...

Please help me add support for USB-UART converters of the CP210x and CH341 series on the STM32MP157F-DK2 board. I expect to see ttyUSBx, but no new devices appear after connection. I am using the Distribution Package, and in the kernel configuration, I have activated the following settings: # USB port drivers # CONFIG_USB_SERIAL=y # CONFIG_USB_SERIAL_CONSOLE is not set CONFIG_USB_SERIAL_GENERIC=y CONFIG_USB_SERIAL_SIMPLE=m # CONFIG_USB_SERIAL_AIRCABLE is not set # CONFIG_USB_SERIAL_ARK3116 is not set # CONFIG_USB_SERIAL_BELKIN is not set CONFIG_USB_SERIAL_CH341=m # CONFIG_USB_SERIAL_WHITEHEAT is not set # CONFIG_USB_SERIAL_DIGI_ACCELEPORT is not set CONFIG_USB_SERIAL_CP210X=m But when connecting a CP210x- or CH340-based converter to any of the four USB-A ports on the board, I only get the following in dmesg:  [1619.270102] usb 1-1.3: new full-speed USB device number 4 using ehci-platform At the same time, I can see my adapter when running lsusb: Bus 001 Device

I'm trying to figure out some unexpected behavior (that I've posted about before) after successfully implementing alternation between T2T Card Emulation and Reader/Writer such that they seem simultaneous to the end user.During device initialization, my code goes through the following series of events:Send Set Default commandDisable overheat protectionIncrease driver power for I2CDisable all interruptsClear all interruptsStart the oscillator and wait for it to be stableMeasure the voltage and set the power supply 5V or 3V3Send Adjust Regulator command (interrupts enabled within this step)Send Stop All Activities commandI've posted before about the difficulties I've faced with Adjust Regulators; it now works reliably with several layers of fallbacks. One of these fallbacks is to enable Tx/Rx beforehand; I don't know why, but it results in Adjust Regulators succeeding more frequently. However, when I do enable Tx/Rx beforehand (setting rx_en and tx_en), it results in an interrupt. So

I am trying to implement a neural network on the LSM6DSV16IS IMU using an X-NUCLEO-IKS01A1 board.The neural network was trained and exported from MATLAB in ONNX format. Subsequently, the model was quantized using ST Edge AI Developer Cloud, and I downloaded the generated library for the IMU.I referred to the following tutorials as guidelines:How to implement a neural network on LSM6DSO16IS and ISM330ISST MEMS ISPU GitHub repositoryHowever, I encountered some differences in my case and decided to download the template (I tried both template and template_stedgeai).I modified the main.c file in inspu/src/main.c, but it fails to compile. On the other hand, when I try to compile the file in inspu_stedgeai/src/main.c, the console outputs: "Nothing to build for project ispu_stedgeai".At this point, I am unsure how to proceed.My main questions are:Is it possible to use ST Edge AI Developer Cloud to directly obtain the three folders (lib, inc and src) that can be integrated into the project in

As discussed in here, im trying to use ST\s ROM bootloader, when i read AN2606 Page 280 shows the FDCAN1 rx and tx Pins   Those pins dont exist in stm32H743ZI@KDJEM.1 proposed "you can activate the FDCAN bootloader with only by PH13/PH14 pins." What does "activate" mean?, those pins dont exist 

Hello,I have a custom board with the STM32MP257FAK processor. I am having issues booting into u-boot from emmc. I can boot into u-boot fine using dfu-util over usb. But once I program in fsbl, ssbl, and meta data into the emmc and try to boot from it I get a error with the metadata partition. See log below.Any ideas what could cause this error?

Hi,App note AN2606 says I should use FDCAN1_Rx pin PH14 (similary Tx pin) to be able to use FDCAN bootloader but selected package UFBGA169 doesn't have such pins.Can I use default FDCAN Pins to work with bootloader?

I use a STM32H750 chip and I would like to use the emdedded bootloader with the FDCAN1 interface. AN2606 specifies pins PH13 and PH14 for this version. However, the package I use (STM32H750VBT6 LQFP100) doesn't have these pins exported. Does it mean that there is no FDCAN bootloader option for the 100-pin package?Thank you in advance for your answer,Dorian Bignet

 HAL_SPI_Transmit(&hspi1, NULL, 0, 0); uint32_t error = HAL_SPI_GetError(&hspi1); HAL_SPI_StateTypeDef spiState = HAL_SPI_GetState(&hspi1); above lines of code i expect error = error codespiState must be error state , but i still gets  error  = 0, spistate = Ready anyone knows the reason?

Hello, community. I have a task to transfer a value from the buffer of 64 values in memory to 7 GPIO by DMA every 1us. I solved it by setting a TIM2 timer Channel1 to Output Compare mode and TRGO to Update event. Then, I mapped the DMA request to TIM2_UP and set the mode to Circular so that I could use HAL_DMA_CallbackIDTypeDef to copy new data to half of the buffer while transferring another half. The challenge is that I must perform this on two separate STM32H7 MCUs with precise timing. To achieve this, I have a VSYNC signal that's essentially a basic PWM with a 64us period and a 5us pulse width.So, for every rising edge of VSYNC, I need to start transferring the data buffer of 64 values. One value for 1us. And start transferring another 64 values right at the start of the next sync pulse.I was trying to Enable Synchronization in DMA Request Synchronisation settings and set the Sync signal to EXTI (which is my PWM VSYNC) but it doesn't work as I expected. Is there any other

Hi ， we had a problem with ST25R95 NFC solution， it looks OK to detect Mifare4  card  at 10mm range， but have not any response to Mifare7 and Felica card.this is due to NFC antenna match？ 

Hi, I am going to run a simple external Interrupt excercise on Nucleo-G0B1RE. The push button (PC13) works correctly but the ISR is not working on this pin!  The sample code is attached. What is the problem with the Interrupt? #include "main.h" void SystemClock_Config(void); static void MX_GPIO_Init(void); int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); while (1) { } } void SystemClock_Config(void) { RCC_OscInitTypeDef RCC_OscInitStruct = {0}; RCC_ClkInitTypeDef RCC_ClkInitStruct = {0}; /** Configure the main internal regulator output voltage */ HAL_PWREx_ControlVoltageScaling(PWR_REGULATOR_VOLTAGE_SCALE1); /** Initializes the RCC Oscillators according to the specified parameters * in the RCC_OscInitTypeDef structure. */ RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSE; RCC_OscInitStruct.HSEState = RCC_HSE_ON; RCC_OscInitStruct.PLL.PLLState = RCC_PLL_ON; RCC_OscInitStruct.PLL.PLLSource = RCC_

Hi, I have been trying to implement the functionality to change the currently active screen on TouchGFX using a hardware button with no luck so far. I'm using an STM32H743zit6. Here are the resources I've looked at but haven't managed to get working: https://www.youtube.com/watch?v=ufvJ5bcesL8 https://www.youtube.com/watch?v=QgEDSjvGAlk https://support.touchgfx.com/docs/development/scenarios/example-gpio https://support.touchgfx.com/docs/development/board-bring-up/how-to/10-physical-buttons https://support.touchgfx.com/docs/development/ui-development/touchgfx-engine-features/screen-transitions https://community.st.com/t5/stm32-mcus-touchgfx-and-gui/hardware-button/td-p/640357   Any help would be greatly appreciated, Thanks.

Posted on April 21, 2014 at 05:45 Hi Everyone, I'm using the CR95HF to access the DESFire card. Everything was going fine up to RATS and PPS. However when I tried to send the GetVersion Desfire command (0x60) using the Half-duplex block transmission protocol with PCB, CID, INF...  as below:   0x04, 0x04, 0x0A, 0x00, 0x60, 0x28 header, len, PCB, CID,   INF,    control byte   I only received 0x87 0x00. The same happened with Authenticate (0x0A 0x00) command. So I think I it must be something wrong with the EDC (CRC) code.   Could anybody shed some light on this?   --------------------------------------------------   Edited: According to the datasheet, the CR95HF only supports 14443-3 not 14443-4, is that correct?   #desfire #cr95hf

Hello everyone:         I encountered a problem when importing the ONNX model and using the X CUDE AI tool for analysis. I have tried many solutions but couldn't solve it. I hope someone here can help me. The specific problem is as follows:      ST Edge AI Core v1.0.0-19894      NOT IMPLEMENTED: Only step=1 is supported for each axis: [2]        This is a problem that occurred after adding the SPDConv module to the YOLOv5 model. Before that, the model could be imported and analyzed smoothly.