Solved

I am currently implementing a UART communication on a STM32F1. As I understand from the manual, the ORE bit does block all further Rx until it is cleared but the other error flags (PE, NE, FE) do not block Rx when set.How is the behaviour of the UART error flags and the data register (DR) in the following 2 scenarios. (in both scenarios 2 bytes are received before checking the SR and DR).Scenario 1:** First byte contains an PE/NE/FE error** Second byte contains a correct byteIf I understood the manual correctly, all error flags (PE,NE,FE,ORE) are now set and DR contains the first (corrupt) byte. Is that correct?Scenario 2:** First byte contains a correct byte** Second byte contains a PE/NE/FE errorMy assumption is that the first byte is stored in DR but PE/NE/FE flags are set (because of the second, corrupt byte) and also the ORE. Is that correct?If both of my assumptions are correct, is it therefore true, that, if 2 bytes are received and all error flags are set, you cannot decide whe

Is there an OctoSPI sCommand configuration which will generate only 8 clock cycles and read the result from MISO via HAL_OSPI_Receive?I'm attempting to use Macronix code (MX25l2565G flash) tied to a single SPI bus channel via OctoSPI. That code uses GetByte() which performs a single byte read.I've tried several configurations, including setting InstructionMode and AddressMode to "None", adding/removing DummyCycles, but either I set an Instruction/Address mode and have an extra 8 clock cycles or HAL_OSPI_Receive fails. Thanks!Thanks!

I'm trying to attempt CAN on a STM32G473 MCU. While transmission seems to be fine, I'm not receiving any data back. The receive call back function is not triggering.Following is my setup:Below is the TxHeader and RxHeader initialization along with the call back function. I have a breakpoint in the call-back function which never gets triggered.FDCAN_TxHeaderTypeDef TxHeader; FDCAN_RxHeaderTypeDef RxHeader;   //uint32_t TxMailbox;   uint8_t TxData[12]; uint8_t RxData[12]; int indx = 0;   void HAL_FDCAN_RxFifo0Callback(FDCAN_HandleTypeDef *hfdcan, uint32_t RxFifo0ITs) { if((RxFifo0ITs & FDCAN_IT_RX_FIFO0_NEW_MESSAGE) != RESET) { /* Retreive Rx messages from RX FIFO0 */ HAL_GPIO_WritePin(GPIOB, GPIO_PIN_13, 1); if (HAL_FDCAN_GetRxMessage(hfdcan, FDCAN_RX_FIFO0, &RxHeader, RxData) != HAL_OK) { /* Reception Error */ Error_Handler(); } if (HAL_FDCAN_ActivateNotification(hfdcan, FDCAN_IT_RX_FIFO0_NEW_MESSAGE, 0) != HAL_OK) { /* Notification Error */ Error_H

by some mistake, we have a large batch of boards with LIS2DS12 sensor and STM32G030F6P6 mcu powered with 3.3 volts. but the maximum voltage for LIS2DS12 is 2.0 volts, and absolute minimum voltage for STM32G030F6P6 is 2.0 volts. so we tried to adjust on board power regulator down to 2.0 volt but we had boot problems with the mcu. so the question is 2.2 volt the absolute maximum of LIS2DS12 is safe for long term working condisitons ? because STM32G0 looks fine with 2.2 volts.also can we run LIS2DS12 with 2.5 volts (0.3 volts over the absolute maximum) i am asking this because we have a test batch and LIS2DS12 chips are working fine with 3.3 volts over weeks without single fault.

..

Hi,I am developing a device which uses CAN interface. My code is 'bare metal'. I am using arm-none-eabi combined with cmake and vscode. Assembly and CMSIS are taken from cube generated project.The problem is that immediatly after setting RCC_APB1ENR1_FDCANEN bit the FDCAN_IR_ARA bit is set by hardware. The code is very simple:void main(){  RCC->CCIPR &= ~RCC_CCIPR_FDCANSEL;  RCC->CCIPR |= RCC_CCIPR_FDCANSEL_1;  RCC->APB1ENR1 |= RCC_APB1ENR1_FDCANEN;  FDCAN1->CCCR |= FDCAN_CCCR_INIT;//here the FDCAN1->IR ARA bit is setted  while ((FDCAN1->CCCR & FDCAN_CCCR_INIT) != FDCAN_CCCR_INIT)    ;  FDCAN1->CCCR |= FDCAN_CCCR_CCE;  FDCAN1->CCCR |= FDCAN_CCCR_DAR;  FDCAN1->CCCR |= FDCAN_CCCR_PXHD; // Protocol exception handling  FDCAN1->NBTP = 0x100403;}I was not able to reproduce this error in STM32CubeIDE. I've pasted same lines to the empty project and it worked. Therefore i must by not doing something th

Hi,​I upgraded the image for our custom board to 4.1 last week. After fixing the sw issuesconcerning the recipe syntax changes i have now problems to boot the new image.​Info: Our board does not use PMIC but static voltage configuration:​/ { model = "DEWETRON NEXDAQ tf-a"; compatible = "st,stm32mp157f-nexio", "st,stm32mp157";   aliases { serial0 = &uart4; serial1 = &usart1; serial2 = &usart2; };   chosen { stdout-path = "serial0:115200n8"; };   /* Supply Voltages */ vddcore: vddcore { regulator-name = "vddcore"; regulator-min-microvolt = <1200000>; regulator-max-microvolt = <1350000>; regulator-always-on; };   vdd: vdd { regulator-name = "vdd"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-always-on; };   v3v3: v3v3 { regulator-name = "v3v3"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-always-o

About reading tags via USB UART by ST25RU3993 without ST25RU3993 Reader Suite GUI.To initial and start reading tags automatically after plugged in and print them on serial terminal (ex: Tera Term) via USB UART (not the UART LOG pin) by ST25RU3993 without ST25RU3993 Reader Suite GUI, I want to know how should I edit for ST25RU3993 EVAL firmware, thanks a lot.

..

On running the SBSFU project on STM32F769I-DISCO board, will the boot ROM evaluate the integrity and authenticity of Secure boot. So that, the user will be sure that his/her Secure boot not replaced by others.

Hello guys, I am working with an STM32L071CBT6 MCU. I want to have a cycle of 10 minutes, where MCU works for 1 minute before entering to standby mode during 9 minute.Using RTC, I want to have an interrupt every 1 minute(60 s); but I don't want the interrupt to wakeup the MCU. I want to use a different RTC event to do so.Is it possible to implement? Please any suggestion on how to go with this would be appreciated

Can ST please provide a guide for bringing up a custom board without using the STPMIC? We are extremely space constrained and unable to fit the PMIC. For our use case we just want simple LDO's with bucks as required.There is no material I can find that outlines what the device tree should look like for TF-A, U-Boot and Kernel when STPMIC is omitted.

i am having a problem trying to add a source code to my project, even though CUBE IDE already added it but the source codes of TOUCH GFX are not receiving, i see people using Makefile to add it but i am having trouble towel when using it.I would be very grateful if you could help me in this matter  

During testing to see what happens if power is interrupted during various parts of firmware update, I removed power from my test board while updating FUS. Now, when I connect via SWD using STM32CubeProgrammer, it shows the following: When I try to update FUS in this state (writing FUS v1.2.0 to 0x080EC000), I get an error, "FUS_STATE_ERR_UNKNOWN".Is it possible to recover from this state?

Here are the memory assets when I have the project configured for internal flash...and here is how the linker script is configured of course../* Specify the memory areas */MEMORY{ FLASH (rx)   : ORIGIN = 0x08020000, LENGTH = 2048K - 128K DTCMRAM (xrw)  : ORIGIN = 0x20000000, LENGTH = 128K RAM_D1 (xrw)  : ORIGIN = 0x24000000, LENGTH = 512K RAM_D2 (xrw)  : ORIGIN = 0x30000000, LENGTH = 288K RAM_D3 (xrw)  : ORIGIN = 0x38000000, LENGTH = 64K ITCMRAM (xrw)  : ORIGIN = 0x00000000, LENGTH = 64K EXTFLASH (r)  : ORIGIN = 0x90000000, LENGTH = 8M}   FontFlashSection : {  *(FontFlashSection FontFlashSection.*)  *(.gnu.linkonce.r.*)  . = ALIGN(0x4); } >FLASH TextFlashSection : {  *(TextFlashSection TextFlashSection.*)  *(.gnu.linkonce.r.*)  . = ALIGN(0x4); } >FLASH ExtFlashSection

Hi,I'm using STM32F429 to talk to TI BQ40Z50 via I2C, and I ran into an issue I have no clue.First of all, the code simply reads registers, and it works on TI BQ20Z95. The same code doesn't work on BQ40Z50. The HAL library always returns HAL_BUSY, and the error code is 32 (timeout). However, the logic analyzer doesn't have any waveforms. Both SCL and SDA are held high the entire time. The most puzzling part is that if I disconnect the BQ40Z50, let the STM read registers (reads nothing obviously) several times, and connect the chip back. It works like a charm. any suggestions I can try?The I2C is running at 100KHz, with internal pull-up registers.Thanks!

..

I have successfully configured the adc watchdog. But i am a bit dissapointed of the accuracy. I set the bounds to 1000 and 3000, but when i read the values of the adc from the watchdog interrupt, i get also values from within the window (up to 1025/2975).The signal is 10Hz Triangular. I already measured the time from beeing outside of the window until the interrupt is executed (4us). So there is no timing issue.In the manual it says: The analog watchdog feature allows very precise monitoring of the converted voltage of one, some or all selected channels. An interrupt is generated when the converted voltage is outside the programmed thresholds.25 of 4096 at 3.3V is 20mV... I would not call that very precise, not even precise....Is it a safety margin?I could compensate this, but i wonder if it could change somehow (temperature etc.)?I made a diagram, to visualize it and added a cap to smooth out the signal: x-axis shows the value from the ADC, and the y-axis is the number of measure

I have Nucleo G0B1RE.I had add 3V battery to VBAT.I had change to use LSE for RTC.I had add RTC_BKP_DR to keep time before reset so RTC time reg was not cleared after reset but It was re-initial while booting.But RTC don't count while power off and RTC_BKP_DR was cleared after reset.So I don't know what my mistake?This is my system clock configvoid 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);   /** Configure LSE Drive Capability */ HAL_PWR_EnableBkUpAccess(); __HAL_RCC_LSEDRIVE_CONFIG(RCC_LSEDRIVE_LOW);   /** Initializes the RCC Oscillators according to the specified parameters * in the RCC_OscInitTypeDef structure. */ RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI|RCC_OSCILLATORTYPE_LSE; RCC_OscInitStruct.LSEState = RCC_LSE_ON; RCC_OscInitStruct.HSIStat

Hi everyone!I use 8 MHz external oscillator for my MCU. For TIM1 there is no prescaler in CUBE, so I expect this timer to tick with pure 8MHz frequency. And therefore I expect to see 0.125 us * 2 * 2 = 0.5 us period of signal. But actually I have 24 us period duration. What does slow down my DAC output? How can I achieve 0.5 us period for my pulse signal?Thanks.

As titles, ​are there any debugger products from ST that can connect daisy chain of JTAG?(without J-link from Segger)

IRET returns to nowhere from wakeup timer ISR as soon as programmable alarm interrupt is active!Here is the STVD screen where programmable alarm and wakeup timer interrupts are enabled and wakeup timer ISR is just about to end. In the memory window at the bottom centered you can see a nonsense address stored in stack (highlighted with yellow).Next is the screen of the result of IRET instructionAnd a screen with programmable alarm disabled where MCU exits correctly from the ISR What is it?  Any clues?

Hi, I'm using an STM32H755ZIQ Nucleo and migrating an old project in CubeMX 6.8.The RCC > supply source > PWR_DIRECT_SMPS_SUPPLY option has been removed from CubeMX, which was the default previously. I tried the two available options (External / LDO), both lock up the board and require full chip erase to continue.I have read this knowledge article which suggests that the solution is to "Make sure that you fixed the power-supply configuration in your project". However the only available options do not work. If I manually put int the SMPS option again, it works.I've read many posts relating to this issue, mostly about how to revive the board, but I haven't found an explanation for why the option is removed form CubeMX and why I (presumably) shouldn't be using that option any more. If anyone can shed some light on how I'm supposed to configure the project so that the Nucleo is powered properly, that would be great.Thanks, Matt

..