Solved

I made a change to my project (using an STM32H7S3L8 part), saved the results, and a few days later tried to reload the project, but got a "Not a valid ioc file" error message.  Here is the output of the log file:```2025-02-17 10:59:38,352 [FATAL] ProjectFactory:568 - Exception caughtjava.lang.NumberFormatException: For input string: ""at java.lang.NumberFormatException.forInputString(NumberFormatException.java:67) ~[?:?]at java.lang.Long.parseLong(Long.java:719) ~[?:?]at java.lang.Long.valueOf(Long.java:1157) ~[?:?]at com.st.microxplorer.mcu.memorymap.MemInfoExtractor$ETHInfoExtractor.onETHEnable(MemInfoExtractor.java:4561) ~[STM32CubeMX:?]at com.st.microxplorer.mcu.memorymap.MemInfoExtractor.completInit(MemInfoExtractor.java:252) ~[STM32CubeMX:?]at com.st.microxplorer.mcu.memorymap.MemoryMapService.MMTActivated(MemoryMapService.java:1259) ~[STM32CubeMX:?]at com.st.microxplorer.mcu.memorymap.MemoryMapService.loadConfigV3(MemoryMapService.java:2578) ~[STM32CubeMX:?]at com.st.microx

Hello,(previous post was marked as spam - I don't know why, so I'm posting again...)I've been working on Provisioning my STM32H563 and after 3 weeks of not touching it, I am unable to perform Full Regression or Debug Authentication on my password-provisioned Nucleo Board. I tried using the generated bash scripts from CubeIDE/MX (which are using STM32_Programmer_CLI) and also STM32CubeProgrammer GUI.I remember before the vacation, I could open and close the Board at will. I always used the same password.bin.Provisioning always happened using the generated provisioning.sh script.Here is the Output of STM32CubeProgrammer (I found it has more info than dbg_auth.sh), after trying Discovery and Full Regression:  17:21:34 : Start Debug Authentication Sequence 17:21:34 : SDMOpen : 609 : open : SDM API v1.0 17:21:34 : SDMOpen : 610 : open : SDM Library version v1.1.0 17:21:34 : open_comms : 501 : open : Asserting target reset 17:21:34 : open_comms : 505 : open : Writing magic number 1

I'm using a NUCLEO STM32F303K8 board attempting to use FreeRTOS, and I have a halting problem when I use CMSIS V2. I found this out by just trying to toggle the built-in LED using HAL using one statically allocated task and observing that the LED only toggles once.(I have OSdelay of 500, so I should be able to observe it). When I run into the debugger, it gets stuck in the default_handler. I then tried using CMSIS V1 and it toggles just fine. My question is is there any documentation on this? I've tried looking around, but haven't had any luck.  I've used FreeRTOS on other STM32's/NUCLEO boards and I haven't had a problem using CMSIS V2. Just to clarify, I don't mind using CMSIS V1. I was just wondering if others knew the problem or experienced the same issue.

Hi,About rfalST25xVPollerFastReadMultipleBlocks and rfalNfcvPollerReadMultipleBlocks。I use st25r3916 to read NFCV tag.The farthest reading distance of my reader can reach 70mm.When I use the command RFALNFCVPoller Read Multipleblocks, I can successfully read data between 0-70mm, but when I use RFAL ST25XVPoller FastTreadmill Blocks, when the amount is between 55 mm and 70 mm, I will fail to read, and the returned error codes are mainly 04, 09 and 21. There is no problem with tag. I can read it with other competing products in this position. How can I determine what the problem is, the software configuration problem? Or is there not enough energy after the RF field is far away?Do you need any other configuration to use fast reading?I hope you can help me answer it. Thank you.

When using DMA to do a SPI transmit, I found a strange behavior. The problem is, that the communication to the DAC works for a few seconds, depending on the used frequency. After the few seconds only 1 byte instead of 3 bytes are sent and the NSS Pin (Hardware regulated) stays low. You can even see these two data items to transfer in S1NDTR (NDT). I used the approximately same code with Software NSS without any problem.I also get a DMA FIFO Error (FEIF) directly after starting the DMA stream, even when using DMA circular mode. Not every time but over 50% of the times when the communication is working I get the FEIF. When the communication is not working anymore, I do not get the FEIF anymore. I found these factors influencing the error:- Using DMA normal mode/ circular mode -> no difference- Enabling DMA FIFO -> no difference- Increase frequency of sending values to the DAC: communication breaks very fast- Decrease frequency of sending values to the DAC: communication does n

Hello,I'm using a STM32H743 and IS42S32160 SDRAM.  The SDRAM is in bank1, and I followed the instructions on how to setup the external memory from this guide:https://community.st.com/t5/stm32-mcus/how-to-set-up-the-fmc-peripheral-to-interface-with-the-sdram/ta-p/49457i can read/write the entire bank (64Mbytes) one word at a time, but then when I run a memory test, where it uses a pattern (incrementor) at each location the memory test fails.  Also, in debug mode, when I step through the program and watch the memory window, i noticed weird things happening.  Before this memory tests starts, the entire 64mb is initialized to x80000000 as shown below:Now the first write happens to location 0xc000_0000 <= 0000_0001, which seem to write there, but it also writes or reads  from addresses:  C000_0020, C000_0080, C000_00A0Something similar happens to the next memory locations:  .... etc... it does that through out the entire memory space.  I check

Given an MCU (say an STM32H755ZIT) and a function (say SPI2_MOSI), how can you find which pins may be configured as SPI2_MOSI, short of clicking on every pin in the Pinout View of the MX Device Configuration Tools?

I'm using the STM32H753ZIT6 NUCLEO Board. For some reason the User LED's are on by default even without any code on it. I tried to press the reset button but it would just blink the led's. I read on another forum to short the BOOT0 and Vdd pins but was hesitant to try that. The board works fine sometimes but it tends to give random/no outputs some times. 

Hi, I’m working with the IIS3DWB accelerometer to acquire single-axis data (Z-axis) using the following setup:Full Scale: ±16gSPI Mode 3 at 10 MHzTarget ODR: 26,667 HzI have attempted different methods to read the Z-axis data. First, I tried reading the Z-axis high (0x2D) and low (0x2C) registers using a timer with auto-increment. I also tried using 1AX_TO_3REGOUT mode and reading all 6 registers (0x28 to 0x2D) using a timer with auto-increment.I then configured the sensor with the following register settings:write_register(IIS3DWB_CTRL1_XL, 0x00); // Power Downwrite_register(IIS3DWB_CTRL6_C, 0x03); // Single Axis Mode (Z-Axis)write_register(IIS3DWB_CTRL1_XL, 0xA4); // Power On, Full Scale 16g, 26.667 kHz ODR write_register(IIS3DWB_CTRL3_C, 0x44); // BDU and Auto Increment Enabled write_register(IIS3DWB_CTRL8_XL, 0xF4); // High-pass and Low-pass Filterswrite_register(IIS3DWB_CTRL4_C, 0x01); // 6 Consecutive Single Axis Valueswrite_register(IIS3DWB_CTRL5_C, 0x20); // Wraparound Rounding

Since upgrading to 1.17.0 compile times have went from a pleasant time to wow, that is slow.  Anyone else experiencing this?Basic project from template: 22:45:47 **** Incremental Build of configuration Debug for project CompileTimeTest **** make -j4 all arm-none-eabi-size CompileTimeTest.elf text data bss dec hex filename 11996 9 1644 13649 3551 CompileTimeTest.elf Finished building: default.size.stdout 22:47:00 Build Finished. 0 errors, 0 warnings. (took 1m:13s.194ms) I've tried 32 cores to just 4 and the time difference is in a few seconds.  All build times are now in minutes when they used to be less than 20 seconds.

Hello,I would like to configure PA11 as an EXTI pin. I know that there exists the hardware limitation that there cannot exist two pins with the same pin number in different ports configured as an EXTI pin (I.E., I could not configure both PB11 and PA11 as EXTI inputs). PB11 is already configured as a UART RX pin. Will there be any conflict if I now attempt to configure PA11 as an EXTI input pin, I.E. a low bit being received by PB11 triggers the EXTI interrupt on pin 11? Or does this conflict only occur when two pins of the same number are both configured as EXTI inputs? 

Hi,I am using the STM32H7R7I8T6 in combination with the Macronix MX25L12833F on a custom board. As I understand it, I need to configure the External Memory Manager and the XSPI interface in STM32CubeMX and after initializing the flash via SFDP, the bootloader should jump into the application if the External Memory Loader is configured correctly. Am I right? It is not necessary to write a separate library for the flash and put it in memory mapped mode? When debugging the External Memory Manager, the error message EXTMEM_DRIVER_NOR_SFDP_ERROR_SFDP is returned at step “4 - Analyze SFPD structure to get driver information”.Does the External Memory Manager support all SFDP flash memory or is there something to consider? Also, I am wondering if the flash memory needs to support XIP (Execute in Place) in order for me to use the flash memory?

From my research, I've read that LwIP is written with FreeRTOS, but can be altered to support any OS. Since ST has made an effort to support/encourage LwIP and ThreadX, are there any resources/examples that we can reference?I am doing my evaluation with the STM32H753ZI and I want to utilize LwIP and ThreadX. I have played with the STCubeH7 LwIP examples on GitHub, but again, none are with ThreadX. If someone could also point me to a tutorial or documentation that explains the different components LwIP needs, that would also be helpful. As I've noticed some examples have different req files that the use needs to provide: ethernetif.h/c, app_ethernet.h/c, and net_conn.h/c, ethernet_perf.h, etc.

I am using the STEVAL-C34KAT2 with the STEVAL-STWINBX1 which is running the software FP-SNSDATALOG2 V3.0.0.Do I need to change anything in the FP-SNSDATALOG2 V3.0.0 software ?Or does the software automatically detect the STEVAL-C34KAT2 board ?Does anything need to be added to the device_config.json file ?I have read the user manual for the STEVAL-C34KAT2, it explains how to connect the board but there's no explanation on how to use it in terms of software.  Is it just plug and play or are there extra steps required ?  

Good day Folks,I am hoping you are able to shed some light on this odd XSPI clock behaviour.  I have connected XSPI2 to a W25Q64 Flash in QSPI mode.There are 'preamble' clocks present prior to the NCS being asserted. I've noticed that the number of preamble clocks depends on the frequency of the bus. The least I have seen is 150 clocks. As you can see below it's 641 clocks, prior to the NCS falling.I am guessing the clock is used internal by the XSPI peripheral, however the 'noise' on the bus certainly is undesirable.This prevents me from using a NCS other than the dedicated NCS pin. Other than that it looks like it creates additional delays in the XSPI transaction, with the reads maxing out about every 30us.This is with a XSPI read being done in a while(1) loop.The data is being correctly read when the NCS is low, expected Byte of 0x16:When the SCK preamble clocks are present I can see the data lines (e.g. IO0 below) go high impedance and rise to the external pullup, until t

Hello,When generating code via CubeMX, the main code does not contain the configuration for the GPIO pins I need to be using.I have checked other solutions and seen that the pins need to be assigned to the core (in this case it would be the M3). The option to do this doesn't seem to be available; is there any hidden menus I need to be looking for? Thanks

I want to create and application on a STM32H745XI-DISCO. I am not using M7 core only M4.Reference manual says that upto 864kB of SRAM  and 2MB of flash are available.I will receive the application sw via Can. My bootloader will save it RAM and after checking CRC etc., It will write this to internal flash. App code is around 300 kB. So 256kB of flash and 512 kB of RAM would be sufficient. After writing to flash sw will jump to application.The application sw will receive data which is arund 730kB via can and it will save it to flash.Here is a part of ST generated linker for bootloader;   /* Entry Point */ ENTRY(Reset_Handler) /* Highest address of the user mode stack */ _estack = 0x10048000; /* previously = 0x10048000, end of RAM */ /* Generate a link error if heap and stack don't fit into RAM */ _Min_Heap_Size = 0x200; /* previously = 0x200, required amount of heap */ _Min_Stack_Size = 0x400; /* previously = 0x400,required amount of stack */ /* Specify the memory areas

Dear Gfx TeamIn addition to current implementation, could you please implement changing the parameter also1  using the keyboard arrow up/down keys and the mouse wheel in popup list.2  by hovering over the parameter and scrolling the mouse wheelThank you

Hello everyone  New STM32 user here, more specifically STM32 U545 RE-Q. I am kind of new and i would like to start acquiring some data with the STM32 ADC, triggered by a timer, and send the data to the DMA so that i can use the CPU for other stuff. Do you guys have any projects that involve this functionality? Any recomendations on where/how to start?  I am aware that i can use some other projects and theres one for the U575 that involves the ADC with the DMA.However, i have not been able to configure it for my nucleo successfully ... Any advice will be welcomed ... Thank you  Marc

I have the below code, which is supposed to update DAC with sinewave via SPI3 bus. It was configured and working fine via discrete command, but when I used timer7 to generate an event and update DAC16 via SPI3 via the HAL library, it went to hard fault. I have never seen this before. What caused the hard fault to occur?I use Nucleo STM32L476 and updated IDE and drivers.Note I have not included the /CS code (yet) because I was trying to figure out what caused the hard fault. I use optimization -Ofast.  #define DAC16_CENTER (32768) bool FID_DAC16_Timer7_Sinewave_Event(void) { volatile static uint16_t DACSine_Pointer=0; //-------------------------------------------------- zFID_Obj *zFIDObj = (zFID_Obj *)zFIDHandle; // assign the object (local) utobj-> //-------------------------------------------------- uint16_t dacdata = FID_SineWaveTable[DACSine_Pointer]; if (DACSine_Pointer >= FID_SinewaveSise) { DACSine_Pointer= 0; } else { DACSine_Pointer++; } //---------------------

As mentioned in the topic subject, I would like to implement I2C Slave device which will simulate the BQ769x2 device. For development I'm using STM32F4 Discovery board, but the final product will be deployed on STM32L0.Master device is first trying to detect if slave device is present and after that some functions will be called in no exact order nor the functions have same length. Therefore I was thinking interrupt mode would be appropriate to implement here for greater control.For testing purpose I have written small Master device program for Arduino (running on Arduino MKRZERO).With this example one can send scan or probe command over serial to run the procedure.  #include <Wire.h> #include <stdarg.h> #define PRINTF_BUF 80 // define the tmp buffer size (change if desired) String inputData; void setup() { Wire.begin(); Wire.setClock(100000); #if defined(WIRE_HAS_TIMEOUT) Wire.setWireTimeout(300 * 1000 /* us */, true /* reset_on_timeout */); #else Wire.se

I selected the processor in CUBE IDE to see how much space the sd card and h264 codes will take up in ram and memory on the STM32N657Z0HxQ processor, but I got the error “The target device ‘STM32N657Z0HxQ’ is currently not supported by STM32CubeIDE”. What should I do? 

Hello community,I am using AEK-AUD-C1D9031 board and I want to play 2 audio files one after other. What should I change in the code?

Hi, I am using an STM32G0B1CBT and using the example shown in the following video to implement a USB-C PD sink with TRACER_EMB and UI_INTERFACE utilities for debugging. https://www.youtube.com/watch?v=-vsJhNIaHxEAfter compiling and running the code, I noticed that the function BSP_GUI_LoadDataFromFlash at line 80 is trying to read from flash address 0x803F800, which is outside the memory region of 128k for the STM32G0B1CBT MCU. What can be the issue?Thanks