Solved

How do you know how big the preallocated static buffer should be when calling cmox_rsa_construct?Does this depend on the RSA key size that will be used?Does this depend on the Modular Exponentiation function that is selected (LOWMEM, MIDMEM, HIGHMEM)?Thanks!

We are using the STUSB4700 in our PD implementation as a source. We have encountered an issue where it seems like the output is constantly switched on/off/on/off with about 500ms on, 200ms off timing.Below is the schematic which connects to a USB type C connector and a SoM. Please note that we are aware that PD_1V2 should not be connected to the gates of the power FETs and we have patched this on the board we are testing with. Also, to make sure there is no interference from the SoM, the reset and alert line have been cut as well.So to summarize the behaviour:The input voltage is 5V and seems stable when no device is connected.We connect a USB PD enabled sink device through USB and see that the PD negotiation is working. The output is shortly as expected and device is charging.After about 500ms, the VBUS_EN_SRC is released which forces the fets to open and the output drops to 0V.After about 500ms this cycle repeats.The input voltage seems stable for the most part with about a 1.4V

I have designed a custom board using STM32H747 with external SDRAM (IS42S32800J) via FMC, copying a lot of the design from the STM32H747I-DISCO eval board. I am currently bringing up the board and testing each component before I implement a TouchGFX UI via MIPI.I am initialising the SDRAM as bank 2 as follows void FMC_Init(){ FMC_SDRAM_CommandTypeDef Command; HAL_StatusTypeDef status; Command.CommandMode = FMC_SDRAM_CMD_CLK_ENABLE; Command.CommandTarget = FMC_SDRAM_CMD_TARGET_BANK2; Command.AutoRefreshNumber =1; Command.ModeRegisterDefinition =0; status = HAL_SDRAM_SendCommand(&hsdram1, &Command, 0xfff); HAL_Delay(1); Command.CommandMode =FMC_SDRAM_CMD_PALL; status = HAL_SDRAM_SendCommand(&hsdram1, &Command, 0xfff); Command.CommandMode =FMC_SDRAM_CMD_AUTOREFRESH_MODE; Command.AutoRefreshNumber =2; status = HAL_SDRAM_SendCommand(&hsdram1, &Command, 0xfff); Command.CommandMode =FMC_SDRAM_CMD_LOAD_MODE; Command.ModeRegisterD

Hi,I'm new to STM32 tools.If I add a new component in STM32CubeMX, where can I find the documentation to the added sonftware modules?E.g. if I add DMA2D from the left pane software is added to the project.How do I know what this software offers and how to use it.All I get are references to the controller datasheet and reference manual on mouseover.Greets,Joerg

Hi,I've just installed CubeIDE 1.16 and without any change to code/source file, every press of Ctrl+B shows this dialog: Any idea why this message please ?   I did not have this with IDE1.14. Thanks

I ran the CubeMonitor-UCPD app on my MacBook Pro(M1 pro, MacOS Sequoia 15.0.1), but it didn't open properly.Does the app support MacOS 15?

Hi I was just wondering if someone could help point out where I could be going wrong with my implementation of write NDEF function. This is a very rough implementation but I believe I am following the correct message structure. I know my i2c mem write commands are working as I have tested the addresses. When I use the ST25 Tap app I don't see NDEF storage being populated. My implementation:HAL_StatusTypeDef write_ndef_pressure_message(int32_t pressure_mmHg_scaled) {HAL_StatusTypeDef status; // Create a buffer for the pressure message (e.g., "123.45 mmHg")char pressure_str[16]; // Max size for the pressure string (with decimals and unit)snprintf(pressure_str, sizeof(pressure_str), "%ld.%02ld mmHg", pressure_mmHg_scaled / 100, pressure_mmHg_scaled % 100); uint16_t message_len = strlen(pressure_str); // Ensure the total length doesn't exceed the memory limitif (message_len + NDEF_HEADER_SIZE > 32) {message_len = 32 - NDEF_HEADER_SIZE; // Limit to 32 bytes (adjust ba

Hi,ST-LINK/V2 ISOL plugged on STM32L072CZT6 (custom board, nReset pin on swd interface is pulled up)Reading with ST-LINK_CLI.exe works fine. (-r32 0x50000000 gives 0xEBFFFCFF) Tried the following in order to write :C:\Program Files (x86)\STMicroelectronics\STM32 ST-LINK Utility\ST-LINK Utility>ST-LINK_CLI.exe -c SWD -w32 0x50000000 0xEBFFFCF0STM32 ST-LINK CLI v3.6.0.0STM32 ST-LINK Command Line InterfaceST-LINK SN: 55FF70067871515314171267ST-LINK Firmware version: V2J40S7Connected via SWD.SWD Frequency = 4000K.Target voltage = 3.0 VConnection mode: NormalReset mode: Software resetDevice ID: 0x447Device flash Size: 192 KbytesDevice family: STM32L07x/L08x/L010Writing 0xEBFFFCF0 at 0x50000000... Error! I wonder whether there is any protection when trying a write access.Any idea where to look up? Regards,

I am currently working on the STM32F072RBT6 microcontroller and have developed a bootloader that successfully jumps to a specified location. The bootloader is located at address 0x08000000, and the main application is at 0x08006000. The bootloader is able to jump to the main application, but when the main application starts, it stops at the very first HAL_Delay() statement. Could you please help me troubleshoot this issue and suggest any possible solutions? Any assistance would be greatly appreciated.Thanks in advance!  below the mention function for jump bootloader to application code:static void goto_application(void){ void (*app_reset_handler)(void ) = (void (*) (void))(*(volatile uint32_t *)(0x08006000 + 4)); __disable_irq(); __set_MSP((*(volatile uint32_t *)0x08006000)); __enable_irq(); app_reset_handler(); }  

Hello, I want to download the program, STM32CubeProgrammer.Before log in, download tap was visible and connectable.However, After log in, download tap continues to load...I've been waiting a long time, but it doesn't stop!!! :(I also cleaned my cache data, but I can't see download tap.... I upload a captured picture.. Please Help me... ㅠ^ㅠ

I'm operating an Infineon F-RAM CY15B116QSN at the OctoSPI port of an STM32H735 MCU with 100 MHz clock (F-RAM devices is specified up to 108MHz). The F-RAM datasheet requires a CS high time between commands of at least 145 ns, which requires 15 clock cycles @100MHz. The CubeMX tool limits the CS high time up to 8 cycles (3 bits wide); the same applies to the STM32H7xx HAL driver, which asserts, if this value is outside the range 1 to 8. In contrast to these limitations, the STM32H73x reference manual allows a CS high time of 1 to 64 (6 bits wide), which would suffer our needs ! Actually I added a copy of the 'HAL_OSPI_Init' function with different name to my project to get around this limitation, but it would be fine, if this bug will be fixed in future versions - or am I wrong at some point ?Best regards, Heino  

 Is it possible to change the starting direction in open-loop control? Can I adjust the initial parameters based on the potentiometer value? Where can I configure this? 

Hi, Is there a reference design for a wireless charging system based on the ST25DV and the ST25R3916.The webinar :Webinar: NFC charging: the tiniest solution for wireless charging– STMicroelectronicsshows the boards in use but the ST Micro NFC website is very vague on specific details or if those boards are purchasable? Kind RegardsTom

I need your help to find out this obsolete item, which I'm attaching the Datasheet.L4970A - 1000 pcsCould you please let me have your best offer?

Hello Forum,I have an issue performing continuous conversions with the ADC on my STM Nucleo board. I want to continuously convert once the ADC is initialized and started and do something with the data afterwards (what is irrelevant to the problem). However, for some reason, if I place the HAL_ADC_Start_IT function call outside the while loop the HAL_ADC_ConvCpltCallback function is only called once. I would expect that in continuous mode I don't need to Start the ADC every time I want to make a conversion.Board: STM32 Nucleo F446RESTM32 IDE version: 1.14.0The main:ADC_HandleTypeDef hadc2; UART_HandleTypeDef huart2; /* USER CODE BEGIN PV */ uint16_t adc_val; uint16_t counter = 0; /* USER CODE END PV */ /* Private function prototypes -----------------------------------------------*/ void SystemClock_Config(void); static void MX_GPIO_Init(void); static void MX_USART2_UART_Init(void); static void MX_ADC2_Init(void); /* USER CODE BEGIN PFP */ /* USER CODE END PF

I have configured DAC in nucleol496zg board using an internal voltage reference of scale around 2.048V , it is 12 bit DAC so step size would be around 0.5mv but when i write HAL_DAC_Start(&hdac1,DAC_CHANNEL_1); HAL_DAC_SetValue(&hdac1, DAC_CHANNEL_1,DAC_ALIGN_12B_R,0);In multimeter it shows around 24.7mv-25mv for all the count values up to 25mv instead of step size DAC. Only if I give greater DAC count value (which produce above 25mv) it gives the correct millivolts in multimeter.

After using cubemx, I tested the single channel round-robin acquisition and there was no problem.After changing to DMA acquisition, as long as VREFINT and VBAT exist at the same time, the data of the first channel is wrong. The following is the correct code:uint16_t data[256]; void HAL_ADC_ConvCpltCallback(ADC_HandleTypeDef* hadc){ } int main{ ...... while(1){ HAL_ADC_Start_DMA(&hadc1, (uint32_t *)data, hadc1.Init.NbrOfConversion*2); printf("adc: %d %d %d %d %d %d \n",data[0],data[1],data[2],data[3],data[4],data[5]); HAL_Delay(1000); } } static void MX_ADC1_Init(void){ /* USER CODE BEGIN ADC1_Init 0 */ /* USER CODE END ADC1_Init 0 */ ADC_ChannelConfTypeDef sConfig = {0}; /* USER CODE BEGIN ADC1_Init 1 */ /* USER CODE END ADC1_Init 1 */ /** Configure the global features of the ADC (Clock, Resolution, Data Alignment and number of conversion) */ hadc1.Instance = ADC1; hadc1.Init.ClockPrescaler = ADC_CLOCK_SYNC_PCLK_DIV4; hadc1.Init.Resolution = ADC_RESOLUTION_12B; hadc1.Init.ScanC

 Hello, is there PAwR support for the STM32WB5MMG module? is there also any example such as for wb0?Thanks

Hi,St Community!I tried to use the RFAL library that provides support for ST25TV commands such as PresentPasword and WritePassword.However, it is still not possible to set a password for the user memory area on the card.My specific operation process is as follows.  The device I used is shown here(NFC08A1+stm32f401)First, my code is as follows(demo is based on NFC08A1 in NFC6 generated in CUBE MX): static void demoNfcv( rfalNfcvListenDevice *nfcvDev ) { #if RFAL_FEATURE_NFCV ReturnCode err; uint16_t rcvLen; uint8_t blockNum = 1; uint8_t rxBuf[ 1 + DEMO_NFCV_BLOCK_LEN + RFAL_CRC_LEN ]; /* Flags + Block Data + CRC */ uint8_t *uid; uint8_t reqFlag; uint8_t pwd[8] = {0x11,0x22,0x33,0x44,0x55,0x66,0x77,0x88}; uint8_t rxBuf_pwd[12]; #if DEMO_NFCV_WRITE_TAG uint8_t wrData[DEMO_NFCV_BLOCK_LEN] = { 0x00, 0x00, 0x00, 0x00}; /* Write block example */ #endif /* DEMO_NFCV_WRITE_TAG */ uid = nfcvDev->InvRes.UID; reqFlag = RFAL_NFCV_REQ_FLAG_DEFAULT;

I am working with an STM32D103C8T6 and I want to store some data on the flash memory.I have some idea on how to do It but not sure about some details.My procedure is the following:1- Add a new section in linker at a defined address near the end.I understand this is done so main program never overrides my data. If not please correct meex: .permament 0x800EA60 : { KEEP(*(.permament)) }>FLASH 2-  Unlock flash and option bytes with FLASH_CR and FLASH_KEYR registers.3- Clear page inside the area I destined for my permanent data4- Write my data in 16 bits packageseg: *(__IO uint16_t*)(addr) = data;  I have the following questions:Regarding step 1:Is this necessary? Does this guarantee I won't overwrite the main program or is it any other way to do it?Regarding step 2:Do I need to unlock option bytes or is this ?Regarding step 3:Where does a page start? Do I need to specify the addres in FLAS_AR register to the begining of a page?Regarding step 4:I

 Here's a corrected version of your text:Hi!I would like to ask the community if my design of the SDIO and USB bus looks fine. Previously, I was using a dev board (BlackPill STM32) to write data to an SD card, but I encountered some issues during the communication stage. The problem occurs when the SDIO protocol starts sending data at a 24 MHz frequency. When I try to write or read a block of data in common mode, without DMA and interrupt handling (IT), I always get a HAL_TIMEOUT error.After researching the issue, I found that some people suggest it might be caused by incorrect SDIO bus design, specifically related to impedance and trace length control.To address this, I redesigned the PCB. It now consists of four layers, with the top and bottom as signal layers, and the two middle layers as GND and VCC (which are not shown in the design). I hope you can review it and provide some feedback, whether positive or negative.I have tried several variations of the code and tested it on a

Currently I'm developing within the STM32CubeIDE for an STM32F373CC.I use the main.c as entry point into a wrapper and program all of the rest in C++. I generally try to keep any HAL code outside of simple classes that can be unit tested easily. Ideally my tests would still compile when data types and some definitions are used from the HW-related codes but I don't really need actual HW-code running within a test. I just want to test algorithms and basic classes. Any comments regarding the HAL or any other HW-related code would still be appreciated.When adding a class to my project the IDE suggests adding a unit test: So how exactly is this supported? The Foo_test.cpp is simply added to my project but I'm not sure how to proceed. Do I have to integrate a unit testing framework on my own? Is there a framework somehow included in the STM32CubeIDE? Is there support for test execution and visualization?Any resources and guides are appreciated! If non of this is supported, I'd still lik

Hi,Im trying to encryp using AES 128 CTR but i dont get the same result that online calculators.Im using this online calculator: https://cryptii.com/pipes/aes-encryptionMy code is the next:uint8_t IVKey[] = {0xDD, 0xF9, 0x11, 0xA6, 0xDD, 0xF9, 0x11, 0xA6, 0xDD, 0xF9, 0x11, 0xA6, 0xDD, 0xF9, 0x11, 0xA6}; AesDeInit(); // CTR AES hcryp.Instance = AES; hcryp.Init.DataType = CRYP_DATATYPE_1B; hcryp.Init.KeySize = CRYP_KEYSIZE_128B; hcryp.Init.pKey = (uint32_t *)AESKey; hcryp.Init.Algorithm = CRYP_AES_CTR; hcryp.Init.pInitVect = (uint32_t *)IVKey; if (HAL_CRYP_Init(&hcryp) != HAL_OK) { Error_Handler(); }and the AESKey is the next:const uint8_t AESKey[] = {0x44, 0x26, 0x44, 0x20, 0x45, 0x6C, 0x65, 0x74, 0x74, 0x72, 0x6F, 0x6E, 0x69, 0x63, 0x61, 0x20 };My AES function is the next:int16_t AesEncrypt(char *In,int16_t Len) { uint8_t Buf[16]; if (Len & 0x0F) Len+=16-(Len & 0x0F); if (HAL_CRYP_DeInit(&hcryp)!=HAL_OK) Len=0; else if (HAL_CRYP_Init(&

Hello, I continue my journey toward build a STM32 hardware emulator for the famous Apple II Disk II. I am implementing UF2 firmware management, USB drag & drag update. the new firmware is not starting, even if I see log of tinyuf2 passing to the appand I do not understand why I put the boot loader (tinyuf2) and I changed :- system_stm32f4xx.c and I add #define USER_VECT_TAB_ADDRESS#define VECT_TAB_OFFSET 0x00010000U I also changed : STM32F411CEUx_FLASH.ld with  /* ****************************************************************************** ** ** @file : LinkerScript.ld ** ** @author : Auto-generated by STM32CubeIDE ** ** @brief : Linker script for STM32F411CEUx Device from STM32F4 series ** 512Kbytes FLASH ** 128Kbytes RAM ** ** Set heap size, stack size and stack location according ** to application requirements. ** ** Set memory bank area and size if external memory is used ** ** Target : STMicroelectronics STM32 ** ** Distribut

I have an STM32H745 Kit with two processors: M7 and M4.I created graphics using TouchGFX and built several screens.I set up the M4 to work with the RTC, and I want to send information from the M4 to the M7 using OpenAMP.I modified the linker file and built the M4 file.The issue occurred when I tried to integrate OpenAMP into the HPP and CPP files for each screen. Errors appeared, and I don't know how to deal with them. 10:55:10 **** Incremental Build of configuration Debug for project STM32H745I_DISCO_CM7 ****make -j8 all arm-none-eabi-g++ "C:/TouchGFXProjects/noooooooooo/CM7/TouchGFX/gui/src/settings_screen/settingsPresenter.cpp" -mcpu=cortex-m7 -std=gnu++14 -g3 -DDEBUG -DCORE_CM7 -DUSE_HAL_DRIVER -DSTM32H745xx -DMETAL_INTERNAL -DMETAL_MAX_DEVICE_REGIONS=2 -DRPMSG_BUFFER_SIZE=512 -DVIRTIO_MASTER_ONLY -DNO_ATOMIC_64_SUPPORT -c -I../../../CM7/Core/Inc -I../../../CM7/TouchGFX/App -I../../../CM7/TouchGFX/target/generated -I../../../CM7/TouchGFX/target -I../../../Drivers/BSP/Component