Solved

It is developing products using stm32f469i_Discovery.The stm32f469i_Discovery board is intended to be used with DS3231.It was connected to I2C1 for I2C communication.I2C1 initialization runs on MX_I2C1_Init();In this function, It is developing products using stm32f469i_Discovery.The stm32f469i_Discovery board is intended to be used with DS3231.It was connected to I2C1 for I2C communication.I2C1 initialization runs on MX_I2C1_Init();hi2c->State = HAL_I2C_STATE_RESET;I2C communication is not possible because it is in a state.Thus, after MX_I2C1_Init();, hi2c->State = HAL_I2C_STATE_READY; was added for use.What I want to know is why the status of HAL_I2C_STATE_RESET continues when I2C is initialized.For your information, I am working on it using TouchFGX. Init Code is Add..

In STM32CubeWB v1.10.0, the definitions of RCC_CR_HSEBYP (HSE bypass control) were removed from the CMSIS files for STM32WB5x MCUs. Also parts of the HAL that configure HSE bypass mode were removed. In the release notes it says "Remove RCC_CR_HSEBYP" but there is no further detail about this.I could not find any mention of HSEBYP in the latest errata for the STM32WB5x.What is the reason this definition was removed from the CMSIS and HAL, does this HSE bypass feature still work on STM32WB5x parts?

Hello I would like to use Mac802.15.4 with BLE included in the Wireless Stack. Is that possible? I was developing F/W using stm32wb5x_Mac_802_15_4_fw.bin for Wireless Stack, but now I need to support BLE as well. I wrote stm32wb5x_BLE_Stack_full.bin and stm32wb5x_BLE_Zigbee_FFD_dynamic.bin in the experiment, but MAC802.15.4 could not be initialized normally.

Hello, I have been having trouble getting CubeMX to generate a EWARM project that will compile in IAR Workbench. I looked at this thread so far, but I do not think it will fix my issue since I am currently used IAR 8.50.9. I do not know what is causing the error and do not know what additional debugging information I should post. If any one knows what could be causing this, please let me know. Thank you-U

Hello,I am using the LIS2DW12 accelerometer using Zephyr OS.Driver code is https://github.com/zephyrproject-rtos/zephyr/tree/master/drivers/sensor/lis2dw12 I configured the chip as follow: ODR is 12_5Hzlis2dw12_reset_set(ctx, PROPERTY_ENABLE); lis2dw12_reset_get(ctx, &rst); lis2dw12_block_data_update_set(ctx, PROPERTY_ENABLE); lis2dw12_full_scale_set(ctx, LIS2DW12_2g); lis2dw12_power_mode_set(ctx, LIS2DW12_CONT_LOW_PWR_12bit); lis2dw12_data_rate_set(ctx, LIS2DW12_XL_ODR_12Hz5); lis2dw12_all_on_int1_set(ctx, 1);     lis2dw12_act_mode_set(pLis2dw12->ctx, LIS2DW12_DETECT_ACT_INACT);Where the act_mode_set islis2dw12_read_reg(ctx, LIS2DW12_WAKE_UP_THS,(uint8_t*) &wake_up_ths, 1); lis2dw12_read_reg(ctx, LIS2DW12_WAKE_UP_DUR,(uint8_t*) &wake_up_dur, 1); wake_up_ths.sleep_on = (uint8_t) val & 0x01U; lis2dw12_write_reg(ctx, LIS2DW12_WAKE_UP_THS,(uint8_t*) &wake_up_ths, 1); wake_up_dur.stationary = ((uint8_t)val & 0x02U) >> 1; lis2dw12_write_reg(ctx, LI

..

..

..

..

..

..

..

..

..

..

Why is the new IIS2ICLX a 2-axis sensor only? It's complicated to compensate for cross axis effects and in horizontal orentation, the sensitivity still decreases when abs(angle) increases. A 3-axis sensor in ceramic would be awesome to be placed in 360° devices with arbitrary orientation like IMUs or so. Are there any plans for such a device?

..

..

..

..

..

..

..

..

..