Hello, Having an issue with STM32G031K6Ux MCU. Below added function that checks Options bytes, and if needed - makes changes (power re-cycle is needed after it).This function CheckOptionBytes() works OK on several MCU's. But on this MCU we have an is...
Hi everyone.I am working on SMBus communication and i want to calculate PEC (packet error code) value. PEC value is using CRC-8 checksum with 0x07 polynomial. I want to use CRC peripheral in STM32G031F6 for PEC calculate. Cubemx settings are below.An...
Hi ,I have to use IAR IDE to develop SBSFU function , But I found that after "2_Images_SECoreBin" compiler success, I try to compiler "2_Images_SBSFU" as below picture. It's seem show post build fail.Dose anyone find this issue and some suggest? (but...
Hi!Can someone explain to me why this code:// Is FLASH_CR register locked for writing? if (FLASH->CR & FLASH_CR_LOCK) { // Unlocking FLASH_CR register FLASH->KEYR = KEY1; FLASH->KEYR = KEY2; } // Unlocking FLASH option register if (FLASH->CR & F...
Hi,I am trying to run the CRC calculation with the STM32G031 but the results do not match. The result of the CRC16_CCITT_FALSE should be 0x29B1 according to http://www.sunshine2k.de/coding/javascript/crc/crc_js.html but I get 0x277F.You can find my i...
Hi I am trying to get the the SBSFU v 2.5.0 package to work on NUCLEO-G071RB I am getting the following error after the compilation of the User App and during the preimage execution step (this is all occurring within CUBE-IDE): ---------------------...
Hello,with a new never programmed stm32g031 chip I get different values for PCROP if the same chip is read with ST-LINK or with bootloader+UART.The CubeProgrammer version is 2.7.0Which is the reason for that?Thank you
Hello everyoneSo I've managed to adapt and build my custom user app. Flashed it into the device.But it fails on startup somewhere between gpio and timers initializations in main().Console shows the following text:= [TEST] write 8 bytes @ Isolated cod...
HI, I am trying to port one of ST's security hands on labs for firmware protection that targeted v3.1.3 of the CryptoLib package, to v4.0.1 of the CryptoLib package. It seems like the "legacy" v3.1.3 interfaces for SHA256_Init() / Append() / and Fini...