Solved

Dear ST,Could you please help me on that how can I solve the below issue?After updating the HALL firmware in teh Cube MX to FW F4 V 1.27.1 when i am regenerating the code. In the place where the FREE RTOS componens are created before a headline of the main.c is generated instead.Do you know is the Firmware update reset some settings?Thank you,David

Hello,I using STM32CubeIDE to create my Code with STM32CubeMX.With version STM32CubeMX V6.6.1 there where no problems.Now with the update V6.7.0 and the project migration all the freeRTOS initialization stuff will no more generated. Following code:/* Create the queue(s) */ /* creation of mailboxCanRx */ mailboxCanRxHandle = osMessageQueueNew (32, sizeof(CanRxMsgStruct), &mailboxCanRx_attributes);   /* creation of mailboxCanTx */ mailboxCanTxHandle = osMessageQueueNew (64, sizeof(CanTxMsgStruct), &mailboxCanTx_attributes);   /* creation of mailboxEemCmd */ mailboxEemCmdHandle = osMessageQueueNew (64, sizeof(EemJobStruct), &mailboxEemCmd_attributes);   /* Create the thread(s) */ /* creation of taskMain */ taskMainHandle = osThreadNew(osTaskMain, (void*) &taskMain_attributes.stack_size, &taskMain_attributes);   /* creation of taskWatchdog */ taskWatchdogHandle = osThreadNew(osTaskWatchdog, (void*) &taskWatchdog_attributes.stack_size,

I selected LDO power supplyBut frequency is still limited to 400MHz.

According note of page 27 of datasheet only is possible VOS2 and VOS3. But in STM32CubeMX is possible selections of VOS0, VSO1, VSO2 and VSO3.Thank you in advance

Using an STM32U575 on our own design. Aim is to put it into Stop2 Mode and wake up from three sources: a) GPIO pinb) Wake up timer (RTC)c) AlarmA (RTC) I have these three sources setup as interrupts and when the CPU is running (i.e. not stopped) these interrupts fire and are handled correctly. However, when entering stop mode, the device cannot be woken when any of these 'interrupts' occur - those of you familiar with this will recognise that while the interrupts don't wake up the CPU, these interrupt sources are used to wakeup the CPU when they occur after which the interrupt will be serviced. Debugging in low power mode is troublesome, so my best insight comes from using the STM32Cube Programmer, attaching in 'hot' mode and examining the SFRs. Here I can see the WUTF and ALRMAF are set, but still no wake-up. Frustratingly, I have used the examples referred to in this rather good tutorial and based on this I can (using a Nucleo board) enter Stop2Mode and exit is su

Dear ST HelloI am using timer 6 to calculate the time for timer interrupt triggering,I am using the example for the board from the cube BSP folder,\STM32Cube\Repository\STM32Cube_FW_F4_V1.27.1\Projects\STM32F429I-Discovery\Examples\BSP\SW4STM32\STM32F429I-DiscoveryIn this project, I disable some functions and want to add an interrupt using timer 6.I generated the code using another project for the interrupt and timer configuration and I integrated the hal timer and timer ex to build the project, I also defined the HAL_TIM_MODULE_ENABLED.here is the code: /* Configure USER Button */ //BSP_PB_Init(BUTTON_KEY, BUTTON_MODE_EXTI); MX_TIM6_Init(); /*##-1- Initialize the LCD #################################################*/ /* Initialize the LCD */ //BSP_LCD_Init(); /* Initialize the LCD Layers */ //BSP_LCD_LayerDefaultInit(1, LCD_FRAME_BUFFER); //Display_DemoDescription(); HAL_TIM_Base_Start_IT(&htim6);       static void MX_TIM6_Init(void) {   /* USE

If BLB2=1, hardware maps the System memory to address 0. The bootloader might've remapped it when it detects "valid code" in either bank, but it apparently does not do it, as witnessed by footnote to SYSCFG_MEMRMP.MEM_MODE description:1.When BFB2 bit is set, the system memory remains aliased at @0x0000 0000IMO, this should be added - maybe also as a footnote - to Table 5. Boot modes.The reason is, that the combination of default VTOR=0 and System memory mapped at 0 causes the users to complain of "my code crashes at 0x1fffxxxx", which we see here quite often.---SYSCFG_MEMRMP.MEM_MODE description is common for all three Cat devices; however, the BFB2 bit is present only in Cat.3 devices according to in which Flash chapter is it present at all. Shouldn't this fact be reflected in the abovementioned footnote?---Only Cat.3 devices are documented to have BFB2 in option bytes. However, factory-progrmmed value for Cat.2 and Cat.4 devices have the bit at this position set to 0, which is surpri

When VL53L5CX Time-of-Flight sensor is in threshold detect mode, will it trigger only on what would be a Status 5 valid distance? Thanks! -Doug

Hello,I have an ultra low power application and must share SRAM2a with BLE. For power reasons, RAM1, and SRAM2b cannot be used. The CubeProgrammer refuses to re-program SBRSA to anything but 0xA.More details:I am using Full BLE wireless stack: 'stm32wb5x_BLE_Stack_full_fw.bin'. SBRSA is programmed to 0xA, which matches the 10K provided to RAM_SHARED from the linker file. I believe, that means SRAM2a is completely occupied by RAM_SHARED (10 KB) plus the Secure section (22 KB).I would like to shrink RAM_SHARED based on the map file, and push SBRSA up to make room for my application's data. I need about 10 KB, but it will be nice to get more.I basically have three issues:1) What is the procedure/tool to reprogram SBRSA as CubeProgrammer refuses to program anything but 0xA.2) How much actual memory Full BLE Stack take from the Secure section. All 22KB?3) Is there anything in RAM_SHARED that is not specified by the map file?Thank you in advance.

..

Hello,I'm design a new product based on STM32 and I'd like to use a H7 family. The main problem is that there is no stock on the market. I'd like to know is there is any possibility that H7 or even F7 will return on stock with a normal price on the 2023 (at the moment I can find just few F7 but the price is higher than normal), or if it is better use an F4 microcontroller.Kind regards,Riccardo

..

Hi!I'm using a x-nucleo-nfc08a1 board on a nucleo-g491re using mbed os, I'm trying to implement support for a tag which requires custom crc and parity on both tx and rx.I'm using the following flags RFAL_TXRX_FLAGS_CRC_TX_MANUAL | RFAL_TXRX_FLAGS_CRC_RX_KEEP | RFAL_TXRX_FLAGS_PAR_RX_KEEP | RFAL_TXRX_FLAGS_PAR_TX_NONE | RFAL_TXRX_FLAGS_CRC_RX_MANUAL with rfalStartTransceive, tx works fine but rx fails with a crc error (rfalNfcDataExchangeGetStatus() returns RFAL_ERR_CRC.rxRcvdLen gets set to 8192 and rxBuf is filled with 0s.I'm using a proxmark3 to debug the nfc communication and the tag responds fine as expected, but RFAL (or the transceiver itself) drops the packet.

Hi, I am trying to use an external frequency to drive my STM32F303RE, using a nucleo board (NUCLEO-F303RE). There is a lot of confusion going on right now. First of all, I was provided a nucleo board with an external oscillator that was already soldered on there. But to use the oscillator, I DISABLE the HSEBYP bit in my code. The reference manual states for this bit:0: HSE crystal oscillator not bypassed1: HSE crystal oscillator bypassed with external clockI would think I need to set the bit to 1 to see the external oscillator frequency (24 MHz) and not the HSE frequency (8 MHz). But when I set the bit to 1 (RCC->CR |= RCC_CR_HSEBYP;) I see the HSE is not bypassed and the microcontroller uses the provided 8 MHz clock. If I set the bit to 0 (RCC->CR &=~ RCC_CR_HSEBYP; ) is see the 24 MHz user external oscillator as a result.Also I noticed that the bit has no impact on a microcontroller on a nucleo board, where no external oscillator is soldered. According the the Nucleo Datash

..

..

Hi,​I am trying to flash the Starter_Package to SD card in accordance with the following wiki("6.2 Image flashing"). But fail.https://wiki.st.com/stm32mpu/wiki/STM32MP15_Discovery_kits_-_Starter_Package#Image_flashing​Unfortunately i am a complete beginner on these tools and don't understand what is happened.Thank you by advance for any help or advices.​​error log are...Error: failed to download Segment[0]Error: failed to download the FileError: Download partition 0x06 failedError: TSV flashing service failed​My environments are below,Bord:STM32MPU157F-DK2.Host PC: Windows10 64 bitSD card: ADATA 16GB​[Full log]   -------------------------------------------------------------------            STM32CubeProgrammer v2.7.0   -------------------------------------------------------------------​​​USB speed  : High Speed (480MBit/s)Manuf. ID  : STMicroelectronicsProduct ID : DF

I am looking for an interrupt based replacement for HAL_I2C_IsDeviceReady. I am implementing a EEPROM library for M24256 I2C Serial EEPROM in a FreeRTOS application.  The call HAL_I2C_IsDeviceReady relies on polling for many milliseconds to perform this function. Is there a version written to use interrupts?

Hi. I have some strange error when debugging code at my STM32F103C8T6 BluePill board.When I start debugging, everything seems fine (the debugger connects to the target, erases it, downloads firmware, and verifies it successfully). But instead of jumping to the int main() function body - the debug is in the HardFault handler. Also, my second stm32f103c8t6 board has exactly the same issue. Another strange thing - I have a third stm32f103c8t6 BluePill board that works correctly. Debug starts from int main and everything is fine.Is it a problem with my two boards? Or did I miss something important?I've already fully erased all 3 boards in STM32CubeProg. But nothing changed.

I am using STM32F103C8 Blue Pill Board. I am trying to communicate with ATH20 Temperature & Humidity sensor from past One week. Configured STM32F103 Blue Pill - System Clock As (8mHz * PLL8 )= 64mHz and APB1 as 32mHz.I have Trouble wit START bit, When i try to START I2C and waits for SR1_SB bit it remains LOW.Please check my code here and give me some suggestions to work done...uint32_t read_reg = 0;   void Sys_Clock_Config (void){ RCC->CR |= RCC_CR_HSEON; while (!(RCC->CR & RCC_CR_HSERDY)); RCC->APB1ENR |= RCC_APB1ENR_PWREN; FLASH->ACR |= (1<<1)|(1<<4); RCC->CFGR |= RCC_CFGR_HPRE_DIV1; RCC->CFGR |= RCC_CFGR_PPRE1_DIV2; RCC->CFGR |= RCC_CFGR_PPRE2_DIV1; RCC->CFGR |= ((RCC_CFGR_PLLSRC) | (RCC_CFGR_PLLMULL8)); RCC->CR |= RCC_CR_PLLON;   while (!(RCC->CR & RCC_CR_PLLRDY)); RCC->CFGR |= RCC_CFGR_SW_PLL; while((RCC->CFGR & RCC_CFGR_SWS) != RCC_CFGR_SWS_PLL); } void I2C2_Pin_Config(void){ RCC->APB1

Where I can find longevity data for RF LDMOS eg. PD55003, PD55008, PD55015, PD55025, PD55035STR1-E?Thank's

So I have seen several people say they used the Cube IDE to program the RA-08 from AI-Thinker. They say it was super easy and I love CubeIDE. but for the life of me I don't understand how they did it. Please help?

Hi everyone,I'm trying to configure LWIP for a custom board using stm32h730 and ksz8863mll PHY.Unfortunately within CubeMX there is no advanced settings tab in ETH and in LWIP on Platform Settings tab there is nothing but LAN8742 selectable.As far as found in other posts I should be able to select something like userPHY.Am I missing something or is this just another bug in CubeMX?I'm aware I'll probably have to implement some custom code for the ksz8863mll but I would really like to tell CubeMX not to basically revert all my changes whenever I press generate...

I use ADC 12 bit in STM32L03 and cannot find where CubeIDE defines which reference voltage the ADC should have. ADC_Init() is auto-generated. Is it the default used and what voltage is it?The processor is fed with 3.3V and has VDDA connected to that voltage.

We were using TIM16 to count and monitor if a button is pressed for more than 2 seconds. If pressed for more than 2 seconds, an interrupt will be generated and a flag will be set. This was successfully implemented when used as shown below:void HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef *htim) { if (&htim16 == htim) { __HAL_TIM_CLEAR_FLAG(&htim16, TIM_IT_UPDATE); __HAL_TIM_DISABLE_IT(&htim16, TIM_IT_UPDATE); if (device_C.is_in_use == NO) { device_C.is_in_use = YES; device_C.in_use_state = DEV_INIT; } }}After incorporating some other changes, now the timer stops generating intterupts(it seems as if the counter does not overflow). The followings were the changes being made. Are the above changes having any significant effect?Also i have tried to enable the IRQ forcefully by using HAL_NVIC_EnableIRQ(TIM16_IRQn); in the HAL_GPIO_EXTI_Falling_Callback() and vice versa (HAL_NVIC_DisableIRQ(TIM16_IRQn); in the HAL_GPIO_EXTI_Rising_Callback()).I noticed that it ent