Solved

Hi,I am using the stm32mp157-disco board and trying to mount one of my sd card partitions to my linux VFS at boot time with systemd. I have modified the file /etc/fstab, adding the following entry:# <file system>         <mount pt> <type>        <options>        <dump> <pass>/dev/mmcblk0p8        /boot            ext4          defaults,nofail            0 2but somehow systemd cannot mount the partition before the timeout. I've been unable to change the timeout for the disk mounting by adding x-systemd.mount-timeout under the <options> term of the entry. It seems that Openstlinux has been able to ignore the params in /etc/fstab.However, I can mount the same disk partition with command:mount /dev/mmcblk0p8 /bootafter the login. So I am not sure what I have missed. Can s

Greetings!Our team is planning a new product and we're looking into options for upgrading the pre-existing ST25R3911B based design with themST25R300. As I understand this is still a relatively new product in the portfolio - as such development kits are not commercially available for it yet. My question is - is the ST25R300 supported by either of the currently available X-CUBE-NFC software expansions, or are there any example codes available akin to the poller examples in case of the ST25R3911B? Thanks for the answer in advance! -mp

I'm using STM32L011F4P6 in CubeIDE. I toggle digital output pin PA2 hi/low every 10ms just to see if it works and it consumes 80uA when it runs. When I set another pin PA0 as analog input, the current consumption rises to 315uA. This is OK as I understand that it needs some energy to do ADC conversion. However I only need to measure analog input once and so I want to turn ADC off. I tried HAL_ADC_Stop(&hadc); HAL_ADC_DeInit(&hadc); however it does not returns consumption to 80uA only to 280uA, so something related to ADC is still on and consuming energy. I really want to go back to 80uA when I don't need ADC anymore. I tried enabling Auto Off it had no effect.  int x = 0; while (1) { // toggle digital pin every 10ms HAL_GPIO_TogglePin(GPIOA, GPIO_PIN_2); HAL_Delay(10); x++; // at 5s mark (10ms*500 = 5s) turn off adc if (x == 500) { HAL_ADC_Stop(&hadc); HAL_ADC_DeInit(&hadc); } } 

Hi to everybody and thank you in advance. I'm planning tu use the STISO620 as a function replacement for old-school optocouplers. STISO620 matches in every metric. My plan is use the part to interface an STM32 MCU.My application will detect falling edge pulses by interrupt, so I need a pullup on the MCU side to hold the high level on RX of the STISO620 while there is no excitation on the TX side.My question is: Will the adequate pullup hold the RX line high when TX states are X and power supplies well stablished?Best wishes, 

If this thread was not read only i would bring it to life again. @Jocelyn RICARD @EEdwa.1 @Bubbles @Arno1 @Denish_Ribadiya @cyril After succesfull compiling (NUCLEO-G474RE) SBSFU and uploading UserApp troguh (TERATERM) \en.x-cube-sbsfu-v2-7-0\STM32CubeExpansion_SBSFU_V2.7.0\Projects\NUCLEO-G474RE\Applications\2_Images I decided time to do the same in linux, the issue is teraterm doesnt work for linux.Trying to use minicom:Adding the simbol for minicom special compilation and recompiling SBSFUinstalling minicom sudo apt install minicom Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: lrzszminicom uses by default YMODEM lrzsz implementationThe FW update is VERY SLOW (for only 24K) and ends up with incomplete half update:  full update, it says incomplete: and the SBSFU console says FW too big======================================

Hello,We use the two products together for a Qi Transmitter (SWTBC86) and Qi Receiver (STWLC38) solution for a single product and it's accompanying charger board. The eval kits of both boards perform much better than our production design, particularly our TX board, and we're wondering why that is the case.Our designs were based off of the reference schematic of both ST products. The coils are the same.Some remarks:1) The transmitter overheats to > 100C in about 15 minutes2) Efficiency nears 45% even at a nominal distance of 2.5mm3) We send about 5.5W across the link and receive 2.1W (desired receive)4) Operational TX voltage is 12v (to try and meet our distance requirement - up to 6mm). Receive voltage is set to 5.0v, that goes into a 3.8v nominal (4.35v charged) li-ion battery charger5) Stock firmware for bothBecause this is for a consumer wearable, the efficiency needs to be better than a run of the mill desktop charger. It also need to keep cool. We've reached neither goal.Trans

I would need X-CUBE-STL for one of our project. The official website denotes a NDA to be signed for the package download. It would be helpful, if we could get the point of contact for the NDA procedure.

Hello,     I am using NUCLEO-WB55RG board to implement BLE and I got error when I was Upgrading my STACK Version currently which is v0.0.0.0 in STM32CubeProgrammers FIRMWARE UPGRADE SERVICE option, I select stm32wb5x_BLE_Stack_full_fw.bin with 0x080D4000 memory location for stack upgrade which is preferred by STMicroelectronics official documentation, I have post my Screenshot after multiple attempts no update in STACK Version.--> It is mandatory to upgrade STACK Version for implement BLE?--> Also want better suggestion & Guidance Documents for BLE implement from basic to advance?it would be grateful for any guidance!... Thank you.

Hello,Attempting to debug STM32F746G-Disco, it's been working fine for days. The debugger first started playing up when trying to pause execution during the program, it would not pause but no error message was thrown. Next it would download and launch but pressing the green play button to start the program would not run it. Finally, I've lost the ability to program the board altogether, it just sits on 95% configuring GDB.Running the program (not debugging) works fine as does programing and debugging other boards. Is it something to do with the GDB server? Do I need to reinstall IDE and (somehow) the GDB server? It's odd that it's only this board and only when debugging not launching.Cheers,MichaelCubeIDE version info (windows 11):      Version: 1.18.1Build: 24813_20250409_2138 (UTC) ST-Link Version:V2J46M31    

I am setting up my first m55 STM32 project using the NUCLEO-N657X0 dev board with the CMSIS DSP libraries. I have copied the CMSIS DSP libraries into my project and I have added the CMSIS-DSP include paths into my project, but I am receiving the following build error message, arm_vec_fft.h: error: incompatible types when assigning to type 'uint32x4_t' from type 'int32x4_t'Can you please provide a recommendation to resolve this error? Thank you.   

Hi ST members ！Did ST25R95 tested against FCC Rule Part(s) 15？If yes ，can you share FCC certification link ，thaks！Usually ，ST25R95 transmit power will under this limit？ 

..

Both of the machines are Linux; Computer1 is Pop!_OS 22.04LTS and Computer2 is Ubuntu 22.04LTSI have been tring to use rsync to copy my workspace from Computer1 to Computer2 so I can continue the work on the second machine.The problem is that when I try to access the workspace on the second machine, my project cannot be found.Here are the details.====On Computer1, my workspace is located on the main drive at this path:/home/AccountName1/workspaces/workspace1My project, named Blinky, which contains, among other things, the .project file, is located in workspace1:/home/AccountName1/workspaces/workspace1/Blinky/.project====On Computer2, my workspace is to be located on a 2nd drive at the following path:/media/AccountName2/Data/workspaces/workspace1I expect my project will be located there:/media/AccountName2/Data/workspaces/workspace1/Blinky====Here is how I rsync my workspaces from Computer1 (local) to Computer2 (remote):rsync -av --delete /home/AccountName1/workspaces AccountName2@Compu

Hi there,I have found an issue in code generation where there is a mismatch between a variable declaration in tsl_user.h and its definition in tsl_user.c.The bug can be reproduced by following these steps:Create a new project using the board selector tab and select "NUCLEO-L152RE".Enable TS and TOUCHSENSING in the .iocIn TS, allocate 8 of the 10 groups for one sampling cap and one pad each.In TOUCHSENSING, set TSLPRM_TOTAL_TOUCHKEYS_B to 8 and select the corresponding keys below this parameter. Upon code generation, the tsl_user.h header file contains:extern CONST TSL_TouchKey_T MyTKeys[];and the tsl_user.c source file contains:/* TouchKeys list (ROM) */ CONST TSL_TouchKeyB_T MyTKeysB[TSLPRM_TOTAL_TOUCHKEYS_B] = { { &MyTKeys_Data[0], &MyTKeys_Param[0], &MyChannels_Data[CHANNEL_0_DEST] }, { &MyTKeys_Data[1], &MyTKeys_Param[1], &MyChannels_Data[CHANNEL_1_DEST] }, { &MyTKeys_Data[2], &MyTKeys_Param[2], &MyChannels_Data[CHANNEL_2_DEST] }, { &am

Hello All, I am developing a design based on STM32N647A0 and have limitation on the number of pins to accommodate 16 data lines. The PSRAM used in STM32N6DK board is APS256XXN-OBR-BG and is based on 16 data lines. So, can i use APS6408L-3OBM-BA, PSRAM that has 8 data lines because of the limitation of number of pins. This will help me to stay with the STM32N647A0 part number? Please suggest on this.  Also, I understand the data rate may be compromised by using APS6408L-3OBM-BA, but I want your suggestion, if the STM32N647A0 device will be compatible to work with 8 data lines PSRAM. Please share your valuable suggestions on the concerned issue. Best Regards, Sakshi       

Hi ST team,We are encountering an intermittent issue while using the TOF L3 module in a mid-range distance measurement setup. Below are the details: TOF frame rate: 30ms. Readout rate: 50ms. Distance mode: Medium range.Issue Description: When a stable target is present within the TOF field of view, it measures correctly. However, if a hand is moved quickly back and forth between the TOF and the target, an error frame occasionally appears. This frame has:Distance status: 255Distance value: 8191mmThe following frame typically reports:Distance status: 12A valid distance value (matching the original target)Observations and Questions:All frames with status 255 appear on odd-numbered frames (i.e., those with smaller pulse intervals);These frames have abnormally high ambient light count rates (around 6x normal), even though the histogram data appears almost identical to normal frames;We suspect this high ambient count rate might be causing the signal to be discarded by the internal processing

I was using the CAD resources files from ST for the symbol & footprints of STM32N657B0H3Q & STM32647A0 but could find some pins missing in symbols and footprints as given in the discovery kit. So can anyone check and guide on this..I'm attaching the screen shots of symbols from the discovery kit and the symbol downloaded from the CAD resources.The symbol downloaded from the ST CAD resource for STM32N657B0H3Q (For instance PB1, PB2... pins are missing,) similar is the case for the STM32647A0 CAD files from ST CAD resource. The below attached screenshot is of STM32N657B0H3Q discovery kit having all pins of MCU. 

Hi all, Is there a Modbus tcp/ip Server (Slave) and client (Master) examples for STM32 Nucleo F429ZI board or any other similar boards?  Thanks,

Recently I have encountered a strange issue I cannot really explain...I have a firmware that manages serial UART communication with a callback that has a state machine with 3 states.In the first state, UART is set to perpetually expect 1 byte of data until a specific value is received. If the value is received, another byte is set to be read via UART_Receive_IT and SM proceeds to the next state.In the second state, the received byte is considered message length and UART_Receive_IT is set to read the expected amount of bytes.The third state is supposed to happen when the expected amount of bytes is received and all parsing is done... however, it is never triggered when the serial data is longer than 49 bytes.I am sending data with RealTerm. Short messages work just fine, but then I need to send 147 bytes. In the debug, I can see from the state of huart2 handler that RxXferCount starts at 147 and decrements until 98. Then, UART_RxISR_8BIT is never called again, the state remain

Hello,       I would like if anyone had to use X-NUCLEO-NFC08A1 expansion boards with NUCLEO-U083RC and could reuse successfully the examples for NFC08A1? I see there are a few, but for other MCUs Thanks,      Mihai 

 Without this feature, you can't generate task files and launch files with one click like before to handle code downloading and debugging. Now you have to write the configurations yourself—it's just way too much hassle!

Each time the debug function is used, there will be one more item in the STM32cube registers tree of the debug interface

Hello,Trying to achieve wakeup system at every 60 sec or more using LPTIMER1 in STOP2 mode.Observation:1. STOP2 = enable and LPTIMER = 60 sec --> Wakeup not work2. STOP2 = disable and LPTIMER = 60 sec --> Wakeup work3. STOP2 = enable and LPTIMER = 2 sec --> Wakeup work4. STOP2 = disable and LPTIMER = 2 sec --> Wakeup work void enterLowPowerMode() { HAL_UARTEx_EnableStopMode(&hlpuart1); HAL_SuspendTick(); HAL_PWREx_EnterSTOP2Mode(PWR_STOPENTRY_WFI); HAL_ResumeTick(); Reset_SystemClock(); HAL_UARTEx_DisableStopMode(&hlpuart1); }Using LPTIMER1, below is the configuration, static void MX_LPTIM1_Init(void) { /* USER CODE BEGIN LPTIM1_Init 0 */ /* USER CODE END LPTIM1_Init 0 */ LPTIM_OC_ConfigTypeDef sConfig1 = {0}; /* USER CODE BEGIN LPTIM1_Init 1 */ /* USER CODE END LPTIM1_Init 1 */ hlptim1.Instance = LPTIM1; hlptim1.Init.Clock.Source = LPTIM_CLOCKSOURCE_APBCLOCK_LPOSC; hlptim1.Init.Clock.Prescaler = LPTIM_PRESCALER_DIV64; hlptim1

  Hello everyone, I am having a problem with a simple program. My board is a STM32-U575ZITxQ.Using only the USART1 interface, if I try to print the string: "USART1_READY" on my laptop's serial port, I have no problem. However, as soon as I also enable the USART2, I cannot print anything. Whether with only the USART2 enabled, or with both USART1 and USART2 enabled, if I try to print the string with USART2, I cannot. I checked all the settings of the USART1 and USART2 and they are the same (in GPIO, in Parameter setting, etc.)./* USER CODE BEGIN PV */ char USART1 = "USART1_READY:\r\n"; char USART2= "USART2_READY:\r\n"; /* USER CODE END PV */ /* USER CODE BEGIN 2 */ HAL_TIM_Base_Start_IT(&htim4);//ready for trigger at 1 seconds /* USER CODE END 2 */ void HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef *htim) { if(htim->Instance == TIM4) { //HAL_UART_Transmit(&huart1, &USART1, sizeof(USART1),HAL_MAX_DELAY); HAL_UART_Transmit(&huart2, &USART2, sizeof(U

Hello ST Community,I'm developing a simple bootloader for the STM32U599 that requires USB serial communication (CDC class) for firmware updates.Current Situation:STM32CubeMX only offers USBX middleware for STM32U5 series.We have an existing, working USB driver implementation based on the classic STM32 USB Device Library (CDC class)Questions:Is it possible to use the classic STM32_USB_Device_Library with STM32U5 series instead of USBX?Can we port our existing USB CDC driver  to STM32U5 without major architectural changes?Are there any STM32U5-specific examples using the classic USB Device middleware for bare metal applications?Requirements:Bare metal implementation (no RTOS)USB CDC Virtual COM Port functionalityMinimal flash/RAM footprint for bootloader useCompatibility with existing USB driver codebaseI've seen references to the STM32U5 Classic CoreMW package on GitHub, but wanted to confirm the best approach for our use case.Any guidance or examples would be greatly app