Solved

HI,The driver file I downloaded from the official website is version 1.2.8.(stsw-img029)But when I downloaded the Demo(X-CUBE-TOF1), I found that it uses version 1.2.10.Should I use the latest one? Thanks

I'm using an STM32F446RE MCU on a custom board and I developed a custom bootloader. The bootloader starts at 0x8000000, while the application code starts at 0x8008000. Inside the bootloader I use timer 14 with interrupt and when I need to jump I use the following code: HAL_CAN_DeactivateNotification(&hcan1, CAN_IT_RX_FIFO0_MSG_PENDING); HAL_CAN_Stop(&hcan1); HAL_CAN_DeInit(&hcan1); HAL_TIM_Base_Stop_IT(&htim14); // Note this HAL_TIM_Base_DeInit(&htim14); // Note this HAL_RCC_DeInit(); HAL_DeInit(); SysTick->CTRL = 0; SysTick->LOAD = 0; SysTick->VAL = 0; uint32_t JumpAddress = *(__IO uint32_t*) (APPLICATION_ADDRESS + 4); pFunction Jump_To_Application = (pFunction) JumpAddress; SCB->VTOR = APPLICATION_ADDRESS; __set_MSP(*(__IO uint32_t*) (APPLICATION_ADDRESS )); Jump_To_Application();  Now inside the application code I need the same timer 14 and I also want to debug the application code. The debugger works perfectly until the execution reach

This is a warning listed under the "Problems" tab in STM32CubeIDE (1.1.0). I am seeing some strange behavior and am wondering if this is the cause.The strange behavior I am seeing is that often when I change something in the TouchGFX Designer and click "Generate Code" then do a Run > Debug in STM32CubeIDE, the change does not take effect. What runs on the target is some previous build (without the changes).Sometimes if I disconnect the target and reconnect it, the latest code is correctly running on the target.

Hello.Recently I've been trying to set up a multichannel ADC. The data of both channels are supposed to be transfered to memory through DMA. I've looked through many examples, read many discussions but none of them addressed my issue. In my CubeIDE CubeMX application I just can't see certain parameters for choosing and therefore cannot keep up with the tutorials. The picture below describes what I should be seeing what I see.  Any Help would be appreciated.

Hello,I want to do GPIO initialization for STM32F769I-DISCOhere, i am using those pins in my code: {GPIO_InitStruct.Pin = EV2_Pin|AF1_Pin|WF5_Pin; GPIO_InitStruct.Mode = GPIO_MODE_OUTPUT_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_LOW; HAL_GPIO_Init(GPIOF, &GPIO_InitStruct); } EV2_Pin for electrovane AF1_Pin for air-fani am connecting the STM32F769i card to relay card and i want to initialize relays to 0 value.I use this after declaration of pins { GPIO_ctrl_relay_AF1(GPIO_OFF); GPIO_ctrl_relay_EV2(GPIO_OFF); GPIO_ctrl_relay_WF5(GPIO_OFF); } Any Help or suggestion Guys ?

Hello ST, I am trying to integrate ThreadX into TFM_Appli-NonSecure project. Mostly I am able to integrate it and execute but to make a thread run, I have to comment _tx_initialize_low_level(); API in _tx_initialize_kernel_enter() function.This all work smoothly until I try thread context switching. My initial understanding assumption says pendsv_hander is not getting called.Could I get some more insight to resolve this issue as there is no direct example available for this.

Hi, I Have a custom board with stm32h743... I design a graph page with touchGFX and when D-cache is enable, system detect some hard faults specifically when I touch a button to change screens, some times it works and some times not, When I disable D-cache, system works fine, but graphic speed degrade dramatically ... Please help me ...

In my design I left the exposed pad in Stm32wb55rg VFQFN68 package. when I try to flash the device using st link , iam getting error "target not found". I am check the design and found i left the epad (69th pin) floating. Does this cause any issue ?. Please help me out here .thanks @Amel NASRI .

I'm using a Nucleo-G474RE to measure a signal via ADC1.ADC measures are triggered by TIM2, then transferred via DMA1 into a large buffer (60KB).When the buffer is full an interrupt is generated and I give the DMA another 60KB buffer.After that, everything is stopped and I upload the buffers to the PC via LPUART1.Finally I check the result with a 100Hz sinusoidal input.So far so good, I can set TIM2 up to 3.86333MHz, but anything above will result in a sub-sampling output (between 2 and 3Msmpl/s).That's 44 cycles (clock is 170MHz on all buses). I was expecting to go higher, since I set the ADC measure time to its minimum (2.5 cycles sampling time, 8 bits, no filtering), so a measure should take ~11 cycles, plus the DMA transfer (1 byte of data), so maybe 20 cycles per measure.No transfer error or ADC overrun is reported, and nothing else runs during the measures.My question is: what could possibly eat up 24 cycles per measure, and how to maximize the number of ADC measures per second?

Hello all, We have multiple VL6180 sensors on a common IIC bus.Upon system start up, we are enabling one sensor via its GPIO0 / CE pin, initialising it, changing its IIC address, disabling it, and repeating these steps for all sensors on the IIC bus.We noticed that upon disabling the chips (GPIO0 / CE pin low) and enabling them again (GPIO0 / CE pin high) to take measurements, their address changes again to the default (0x29) and we cannot communicate with them using the newly-assigned addresses. Moreover, the sensors would need to be re-initialised before measurement (using the default address).So am I correct in saying that when low, the GPIO / CE pin completely shuts down the chip and any set registers (e.g. register 0x212 that holds the IIC address) are reset to their default address? Do you have to keep the chips enabled (GPIO / CE pin high) after address is changed? Thanks for your input! Brian   

Is it possible to execute features such as pedometer, activity/inactivity detection, tilt/tap, with same configuration of ODR, Full scale? How can I include all these features in a single program?Can someone explain this please

hello,i have few basic Question regarding accelerometer sensor.1. accelerometer data coming from imu sensor that is 2's compliment data, so should i receive this data in signed integer or unsigned integer? 2. i want to know whatever raw data is coming from this sensor resgistors of accelerometer that is mg/LSB or only g ? if it is mg/LSB then how i can covert into g (refer ±2g)?3. formula of convert g into (-180° to 0 to 180°) ?please refer below attached  code or screenshorts

Hello,I set ODR_XL target during inactivity(INACTIVITY_DUR XL_INACT_ODR_[1:0]), but when I read CTR1 ODR in inactivity mode, it doesn't change to the setting, why?

Hello,I am trying to transmit some data on my STM32F042F6P6. But my PC's serial monitor only picks up some of it. Here is the code and the serial monitor output:void readAllRegs(void){ uint8_t value; for (uint8_t addr = 0x00; addr <= 0x2E; addr++) { value = readReg(addr); printf("0x%x: 0x%x (%d) \n", addr, value, value); fflush(stdout); }}int _write(int file, char *ptr, int len){ CDC_Transmit_FS((uint8_t *)ptr, len); return len;}0x0: 0x29 (41) 0x1: 0x2e (46) 0x4: 0xd3 (211) 0x6: 0xff (255) 0x7: 0x4 (4) 0xa: 0x0 (0) 0xd: 0x1e (30) 0x10: 0x8c (140) 0x13: 0x22 (34) 0x14: 0xf8 (248) 0x16: 0x7 (7) 0x19: 0x76 (118) 0x1a: 0x6c (108) 0x1d: 0x91 (145) 0x1f: 0x6b (107) 0x20: 0xf8 (248) 0x23: 0xa9 (169) 0x25: 0x20 (32) 0x26: 0xd (13) 0x29: 0x59 (89) 0x2c: 0x88 (136) When I change the Tx buffer size from 128 bytes to 512 bytes, there is even more data loss:0090 5f040x00 f80230x07406 :(:(0210002(001xbCan someone explain to me what is happening here? I thought CDC was reliableThank you

Hi GFX Team,Could you possibly add access to colour of autogenerated __background gfx::Box please ?ThanksFerro 

Hi, maybe i ask this some years ago, but still not resolved. In designer now cant create defines list for use instead constant numbers. Then can be quickly managed all objects.Now for example i have designs with 150 labels and set some level of white color on every.After design presented boss say require more darker or lighter texts, then start hard job click on every object and change color, instead we need change one define.Exist any way to do it now, or is planned in next release ??

Hi,I'm working on stm32l496 and I try to write data to a custom flash section, in the .ld file I put new sector :/* Memories definition */MEMORY{[...]FLASH (rx) : ORIGIN = 0x08003800, LENGTH = 0x07B800config(rx) : ORIGIN = 0x0807F000, LENGTH = 2Kcommon(rxw) : ORIGIN = 0x0807F800, LENGTH = 2K}[...]PROVIDE(_config_page_start = ORIGIN(config)); PROVIDE(_common_page_start = ORIGIN(common));I set it like this to flash config or common page without touch my program section.I have no difficulty to read data from this pages. But when I use `HAL_FLASH_Program()` function to write data in 'common' section, I have an error.After reseach the error may be due to ASSERT checking if the address is whitin the flash range.This is my code :error_e mcu_flash_program_data(uint32_t start_addr, const void *data, size_t size) { HAL_StatusTypeDef hal_ret = HAL_OK; const uint64_t *ptr = data; for (size_t i = 0; i < size; i += sizeof(uint64_t)) { hal_ret = HAL_FLASH_Program(FLASH_TYPEPROGRAM_DOUBLEWORD, star

Hi, I have been working with the board for quite some time and everything was functioning normally. Last day, upon powering the board, I noticed that the board has entered reset mode. Also, I have been unable to establish a JTAG connection.Do you know the possible reasons behind this unexpected behavior, specifically the board entering reset mode? Are there some ways to restore boards functionality?Attached please find a picture of the board in its current state.

Hello,First time posting in this forum!I'm evaluting the STHS34PF80 sensor and went through these materials: Datasheet & AN5867.However, I could not find any information regarding the interpretation of the object temperature (after calculating the signed value of 16 bit (TOBJECT_L and TOBJECT_H), then divide by the sensitivity).My very first thought was that this represents the so-called absolute object temperature value, as the sensor is T-MOS based technology and its sensitivity is calibrated with a black body covering the full field of view. However, the function of f(TOBJECT_L, TOBJECT_H, SENS_DATA), doesn't give me that.Rather I have a feeling that it gives me the difference between the object temperature and the ambient temperature. I have attached an image to show you how the values changed when I have my hand approaching the sensor, to completely cover it, then get my hand off the sensor.I have tried with both the ST driver: https://github.com/STMicroelectron

I've written a fairly simple test case for using the system bootloader to boot from flash bank 2 on a STM32F429ZIT6U (developing on a Nucleo F429ZI board). With stdio redirected to a UART, I'm able to direct the code to:Mass-Erase Bank 2Copy the entirety of Bank 1 to Bank 2Set the BFB2 bit The function that sets BFB2 looks like this:void boot_bank_select(uint8_t bank_bit) { FLASH_AdvOBProgramInitTypeDef optionbits = { .OptionType = OPTIONBYTE_BOOTCONFIG, .BootConfig = (bank_bit) ? OB_DUAL_BOOT_ENABLE : OB_DUAL_BOOT_DISABLE }; HAL_FLASH_OB_Unlock(); HAL_FLASHEx_AdvOBProgram(&optionbits); printf("Waiting for option bit write...\r\n"); HAL_StatusTypeDef rc = HAL_FLASH_OB_Launch(); if(rc == HAL_OK) printf("Bank select completed.\r\n"); else printf("Bank select failed.\r\n"); }By placing a few strategic breakpoints, I can see that once the option bit write takes place, printf starts causing an endless reboot cycle. Code in main() executes up to the first place printf() is ca

Hi,I have a board with an STM32U575 at the core.I'm attempting to set up SAI receiver in I2S mode, with 32-bit 48kHz sampling. See my configuration of SAI A below: I also want to receive the data continuously in circular mode via DMA (or GPDMA in the case of this MCU).Reading other sources, I've concluded that the following setup should be established: The audio DMA functions can be seen below. The Audio_Init() function is called once in the main function, and the CpltCallback functions are called by DMA interrupts.   static uint16_t audio_rx[AUDIO_BUFFER_SIZE]; static uint16_t audio_tx[AUDIO_BUFFER_SIZE]; void Audio_Init(){ audio_ready_flag = AUDIO_DATA_FREE; if(HAL_SAI_Receive_DMA(&AUDIO_RX_PORT, (uint8_t *)audio_rx, AUDIO_BUFFER_SIZE) != HAL_OK){ Error_Handler(); } if(HAL_SAI_Transmit_DMA(&AUDIO_TX_PORT, (uint8_t *)audio_tx, AUDIO_BUFFER_SIZE) != HAL_OK){ Error_Handler(); } } void HAL_SAI_RxHalfCpltCallback(SAI_HandleTypeDef *hi2s){ audio_ready_flag

  static uint16_t aDST_Buffer_1[BUFFER_SIZE] = {0}; static uint16_t aDST_Buffer_2[BUFFER_SIZE] = {0}; LL_DMA_LinkNodeTypeDef pNode1, pNode2; /** * @brief LPDMA1 transfer configuration * @PAram None * @retval None */ void BspLPDMA1Init(void) { /* DMA node configuration declaration */ LL_DMA_InitNodeTypeDef DMA_InitNodeStruct; LL_DMA_InitLinkedListTypeDef DMA_InitLinkedListStruct; /* Set node configuration ################################################*/ /* Set node type */ DMA_InitNodeStruct.NodeType = LL_DMA_LPDMA_LINEAR_NODE; /* Set node configuration */ DMA_InitNodeStruct.BlkHWRequest = LL_DMA_HWREQUEST_SINGLEBURST; DMA_InitNodeStruct.Direction = LL_DMA_DIRECTION_MEMORY_TO_MEMORY; DMA_InitNodeStruct.DestAllocatedPort = LL_DMA_DEST_ALLOCATED_PORT1; DMA_InitNodeStruct.DestBurstLength = 1U; DMA_InitNodeStruct.DestIncMode = LL_DMA_DEST_INCREMENT; DMA_InitNodeStruct.DestDataWidth = LL_DMA_DEST_DATAWIDTH_HALFWORD; DMA_InitNodeStruct.SrcAllocatedPort = LL_DMA_SRC_ALLOCATE

Im attempting to set up A/B partitioning on an STM32MP157d-dk1 board so that it can switch between partitions when updating. The board image is built using yocto, and I have used the meta-st-stm32mp layer, and am building a modified version of core-image-full-cmdline for the image.I have set up fw_setenv and fw_printenv using the following fw_env.config file:# Configuration file for fw_(printenv/setenv) utility.# Up to two entries are valid, in this case the redundant# environment sector is assumed present.# Notice, that the "Number of sectors" is not required on NOR and SPI-dataflash.# Futhermore, if the Flash sector size is omitted, this value is assumed to# be the same as the Environment size, which is valid for NOR and SPI-dataflash# Device offset must be prefixed with 0x to be parsed as a hexadecimal value.# On a block device a negative offset is treated as a backwards offset from the# end of the device/partition, rather than a forwards offset from the start.# Block device example

Hi everybody,I'm trying to implement into a custom board, the dynamic Qrcode generation algorithm.I'm using touchgfx 4.23.0, an SPI display with partial buffer strategy.I would like to draw the string "https://support.touchgfx.com" . Display seem to draw it correctly but when I'm try to read it using my phone, this one is not readle. it seems not valid..I'm using the following initialization sequence:   void Screen_QrCodeView::setupScreen() { Screen_QrCodeViewBase::setupScreen(); QR *code; sprintf( string, "https://support.touchgfx.com"); code = new QR( string ); qrCode.setXY(10,10); qrCode.setQRCode(code); qrCode.setScale(8); add(qrCode); }  display screenQrcode detailI don't understand the reason. If I change the size of QrCode using qrCode.setScale the result is the same.Is it possibile to change the resoltuion of the QrCode? Is the QrCode resolution too poor respect the modern APP algorithm?Does someone ahs the same issue? Please, Can someone try to

I am starting a product design tentatively using the STM32F072RBT6.I want to determine how soon the CTS input must go low to prevent the USART from transmitting the next byte.Even informed opinion would be appreciated; but a reference to documentation or direct experience would be  preferable.One note in the reference manual says, "For correct behavior, CTS must be de-asserted at least 3 USART clock source periodsbefore the end of the current character."  page 740, Reference Manual PDF [What about the first character?]  I assume that what they mean is "before the beginning of the next character"? Which clock is "USART clock source"?In this diagram from the reference manual the ultimate source clock seems to be Fck,  but the diagram seems to show that only the slower "Transmitter clock" is used for "Transmit control".Note that this diagram shows obvious incorrect or at least misleading info for the receiver clock. [So, can this diagram really