Solved

I'm working on a stm32wle5c8 Lora project.  I have my own overrides of HAL_InitTick, HAL_GetTick, HAL_Delay and HAL_IncTick because I want to use SysTick as a high-resolution timer.  With this new project, a file Core/Src/sys_app.c is being generated that overwrites HAL_GetTick and HAL_Delay.  What's worse.. The generated ones don't even do anything.  HAL_GetTick does nothing unless the static variable SYS_TimerInitialisedFlag is set.  There is nothing in the code that actually sets it, so HAL_GetTick will always return 0.  HAL_Delay calls a function in another newly generated file Core/Src/timer_if.c which looks like this: void TIMER_IF_DelayMs(uint32_t delay) { /* USER CODE BEGIN TIMER_IF_DelayMs */ /* USER CODE END TIMER_IF_DelayMs */ } In essence, these files are overwriting functions that did something with functions that actually do nothing! So, it would be nice if neither of these files are generated, but I cannot find the magic inca

Created a new thread from STDRIVE101 PWM Output Jitter Inquiry here because it is a question about a completely different device.Dear Peter,Thank you for your explanation. That clarifies the behavior of the STDRIVE101.I have two follow-up questions:Does the STSPIN32G4 behave the same way regarding jitter?Does the STSPIN32G4 use an internal clock?I appreciate your insights.Best regards,Aji

Hi all,I am using the Nucleo-H723ZG board and I'm testing the consumption in stop mode, running the example from the ST repository NUCLEO-H723ZG\Example_LL\PWR\PWR_EnterStopMode.The code compiles without any warning and I use the stlink of the nucleo to program it.I removed the Jumper JP4 (VDD_MCU) and in its place I inserted a precise ammeter (HP34401A)The current measured at the moment of STOP is about 4mA!!Can anyone help me?Thanks a lot,Nicola

I have two NUCLEO-H755ZI-Q boards and I’m trying to run the SPI_FullDuplex_ComIT example on both.One board breaks here (whether the software is built for master or slave):The other board has no problem (whether the software is built for master or slave).Any ideas?

Hi,I'm using the CMSIS-DSP library for FFT calculation, using build-time configurable FFT lengths in the range 64 - 1024. The CMSIS-DSP documentation recommends that, when the FFT length is known, using an appropriate initialisation function such as arm_rfft_init_512_q15() for a 512-length real FFT is preferred over the generic initialiser arm_rfft_init_q15(), since the former allows unused tables to be removed by the linker.I can only find arm_rfft_init_q15() in the repository.I'm using STM32Cube_FW_H7_V1.12.1 but I can't see how to determine which version of CMSIS-DSP that includes (having searched include files for a define, which I'm sure must be hidden there somewhere!).Does anyone know whether those additional FFT init functions have been deliberately excluded from the H7's repository?Advice about how to check the CMSIS-DSP version would also be appreciated.Thanks in advance.

Hello community :)I need help using the EEPROM Memory 24LC1025.I've this address for the 24LC1025 EEPROM ( A0 = 0, A1 = 0 and A2 = 1). And I'm trying to write/read on the data address range 10000h-1FFFFh but I'm not able to, when I try to do anything in this sector it rollovers to the data address range 0000h-FFFFh and I haven't figured out why.Here's part of my code:I2C_HandleTypeDef hi2c1; uint8_t dataread[127]; int main(void) { HAL_Init(); SystemClock_Config(); MX_GPIO_Init(); MX_DMA_Init(); MX_I2C1_Init(); MX_USART6_UART_Init(); HAL_I2C_Mem_Read(&hi2c1, 0x54<<1, 0x0000, I2C_MEMADD_SIZE_16BIT, dataread, sizeof(dataread), 1000); HAL_UART_Transmit(&huart6, dataread, sizeof(dataread), HAL_MAX_DELAY); while (1) { } }I've modified the Mem_Read function incresing MemAddress from uint16_t to uint32_t because I wasn't able to reach one of the higher addresses.In the datasheet the method of accesing different blocks of memory or different sectors is by modif

I want to work with Lora FHSS. Resources on this subject are limited. \STM32Cube_FW_WL_V1.3.0\Projects\NUCLEO-WL55JC\Applications\SubGHz_Phy\SubGHz_Phy_LrFhss. ;I looked at the FHSS example you told me about. This example works in TX mode only. It only sends data using FHSS. I want to listen to this transmitted data with the same model STM32 Nucleo WLE5JC card. Is there an example of this? How can I configure the FHSS configuration to always listen?

Hello,I have been facing this issue of "No source available for "<signal handler called>() at 0xfffffffe"" on a nucleo-h753zi board. Following are few logs obtained from STMCube Programmer.1. Fault that is eesca;ated to a hard fault (forced)2. Faulty called function address: 0x1BB166083. Fault on instruction access (IACCVIOL)4. MMFAR: 0x05. R0,R1,R2,R3,R12: 0x0   SP:0xFFFFFFFC   LR:0xFFFFFFFF   PC:0xFFFFFFFE   XPSR:0x10000036. Debugger issue: As soon as disassembly is clicked, debug is stopped. Note: I am trying to test CAN communication between two nucleo-h753zi boards. Code works on one of the boards. Any help would be much appretiated.Thanks in advance

Hi!I use STM32CubeIde + FreeRTOS + LWIP and quite often, especially for debugging, I change features through CubeMX. It causes reloading of several files that I would like to patch before build.  Examples are LWIP->tcpip.c or LWIP->cc.h.I face an issue, that once they are reloaded, I need to apply changes manually. I looked into file templates, but it seems even worse idea to manipulate that. I know I could add my patched templates to the project, but it's some kind of CubeIDE feature I guess and could make it work properly. I'd like to just create a patch file and add "git apply" command to pre-build steps. However, it seems that reloading file from the Repository by CubeMX causes patch to be not relevant to the file since I get error that patch "does not apply". I used "git diff" for patch creation.Any idea how to patch Repository files before building my application and maintain CubeMX "rebuild" functionality? 

Hi, I need FIT rate for CL 60% and CL 90% for M24C02-RMN6TP please help me with this query.

Hello STM32 Community,I am working with an STM32F103C8T6 ("Blue Pill") Original Chip and interfacing it with a MAX31855 thermocouple amplifier over SPI1. I used a sample program generated by ChatGPT, which initializes SPI1 and manually controls the CS pin using MOSI (PA7).Programmer Used : Original STLINK-V3SET Hello STM32 Community,I am working with an STM32F103C8T6 ("Blue Pill") and interfacing it with a MAX31855 thermocouple amplifier over SPI1. I used a sample program generated by ChatGPT, which initializes SPI1 and manually controls the CS pin using MOSI (PA7).Problem Statement:The program works only on the first flash when I enter debug mode. As soon as i click on Play Button the board stops getting detected via ST-Link/V2 and cannot be reflashed anymore. I have tried with 2-3 different boards, but all of them stopped responding in the same manner.What I Have Tried:Checked Hardware Connections:MAX31855 Connections:SCK → PA5DO → PA6 (MISO)CS → PA7 (MOSI, manually controlled)M

I read in the doc for the G431:"The Flash main memory programming sequence in standard mode is as follows:1. Perform a mass erase. If not, PGSERR is set."So i can not do a single page erase??

HiI managed to read both accelerometer and gyroscope ISM330DLC in "polling" mode with INT1 pin with 3330 output data rate, but my goal is to reach peak data rate (6660 samples / s) so I need to use FIFO and this is where my problems start, I dont know how to set FIFO properly, results in FIFO are intertwined. Could you show me a problem in my configuration? I have some success with enabling FIFO but I have no clue how to configure it to reach my goal which is reading acc ang gyro via primary SPI with max data rate (6660 Hz) and with lowest latency (low set fifo watermark) My code   /* Header of application modules */ #include <sensors-board-app/logging.h> #include <sensors-board-app/ism.h> #include <sensors-board-app/ism330dlc.h> /* Header from CubeMX autogenerated code */ #include <main.h> #include <spi.h> #include <gpio.h> /* Constants */ /** @brief Timeout of ISM330 SPI interface */ #define ISM330_SPI_TIMEOUT_MS 100 /* Priv

HI, it seems to me that reading the LIS2MDL sensor only works correctly if I read first the X axis, then the Y axis, and finally the Z axis separately, each axis in a separate SPI transaction. My settings:- continuous measurement, output data rate set at maximum 100Hz- temperature compensation turned on- high resolution mode- low pass filter disabled, offset compensation disabled- i2c disabled, SPI 3-wire clocked 10MHz, BDU enabled- data ready interrupt on INT pin triggers enqueuing event into event queue, then main loop perform readout after some time (there are other higher priority tasks) My observations:1. Reading 8 bytes in one SPI transaction (from OUTX_L_REG 0x68 to TEMP_OUT_H_REG 0x6F) to read all data does not work at all, temperature data is broken, you need to split readout into 6 bytes of "axis data" and 2 bytes of temperature data2. In certain edge cases of my application when possible readout latency is high I have incorrect readouts of Z axis from time to time

hello, I'm currently developing an application that features more than 150 screens. However, I've encountered a significant challenge: once I build the code, the overall size exceeds the available flash memory. While I'm using external flash for images, I still need a solution to accommodate the large code base . What strategies or best practices can I implement to optimize my application’s size and ensure it runs smoothly? Any insights or recommendations would be greatly appreciated!

I have two custom STM32WB55 boards that I initially started with the P2P_Client/Server projects.  I have the two devices communicating with each other.  Once the communication is established, the notification characteristic is enabled from the P2P_Client, and data starts flowing from the server to the client.  Next step is to try and disable/enable the notification programmatically from the P2P_Client.  I see in the p2p_client_app.c file, there is an event handler for, APP_BLE_ENABLE_NOTIFICATION_DESC and APP_BLE_DISABLE_NOTIFICATION_DESC.Can anyone point me to the correct process for either setting the status somehow so that the event handler is utilized or what is the recommended process for enabling/disabling a notification programmatically from the P2P_Client?Kindest regards.

Hello, can someone point me to where there are some demo programs for working with GPIO as individual pins and creating a bus from a number of outputs. I am also looking for a demo program with general s/w based timers, for example, in mbed which is what I am porting from, you would dothread_sleep_for(1000);  // 1ms timer or delayand to create a busBusOut select_drv(dp11,dp4, dp5, dp6, dp9, dp10); //creates a bus called select_drvthanksAndrewR (I attached the code) 

Hi, I have Grove-Wio_E5, A Lora module based on STM32WLE5JC. I am trying to use STM32CubeIDE for debugging purposes. However, I can not seem to make it work. My resources are: J Link : Firmware: J-Link V9 compiled May 7 2021 16:26:12Hardware version: V9.10License(s): GDB STM32CubeIDE: version 1.17.0 I'm able to connect to JLink and MCU with JLink Utilities. Here is the J Link commander's response: But With STM32CubeIDE, I can not seem to figure out the issue. Here is my JLink interface settings in STM32CubeIDE. The error I get is the following:   I have been trying to resolve this for 2 days. I tried many things (As suggested by users on the internet), > Changing Ports of GDB Server (Although my Jlink is connected via USB) > Uninstalling/re-installing all the tools (J Link, CubeIDE, etc.) > Tried with STM32CubeProgrammer (It never worked for me, it detects Jlink but never MCU and gives an error some database file with id 0xFFF is missing). I saw other users having the

Hello community, I have this difficult task of powering an STM32G0B1 from a pin that was really not tasked for that (because the connector I have to plug onto provides no supply pin). In short, I can't draw more than 500µA current at any time or I risk lowering the voltage too much for MCU.I have tried so far to reduce clock and use low power run mode. I get a power consumption around 300µA, which is good enough for me. The problem is that the current drawn at boot before entering low power mode is around 1mA for about 30ms, as you can see on oscilloscope below (1mV=1µA) Is it possible to start program directly in low power mode without ever entering "normal" mode?

Hello Team    I am looking at how i can buy the reference for evaluation board STEVAL-ISV002V1  or the and the gerber files if possible.  any assistance would be appreciated.    regards joshua   

We purchased the STM32WL55JC Long Range Module board for a project. This board includes the LoRa E5 HF module. We are considering using LoRa FHSS in our project. Can this motherboard support LoRa FHSS? Does it support? I couldn't find much information about this on the internet. Please let me know if LoRa e5 supports FHSS.

Hi,when I increase the size of the ThreadX trace buffer above 30k the RTT output is not working anymore (Below 30k RTT works fine). static uint8_t trace_buffer[1024*64] __attribute__((section(".trace"))); My guess is that the RTT viewer can't find the RTT control block anymore. I can't explain myself why this is the case.When checking the map file I find the control block near the end of SRAM1, which should not be a problem I think?Anyone some idea, how to fix the RTT output? Any help is appreciated :)Thank youRegardsJohn   

Hi, I have problem. I have idea: my STM32H745 must read GPIO state as quickly as possible. FCPU = ~400MHzI wrote the program in assembler for M7LED_ON()ldr r2, [r3, #IDR]ldr r2, [r3, #IDR]... ~650xLED_OFF()...only read, IDR, no write (no record yet)And when I measure with an oscilloscope the led output is on for 25us -> one LDR 15 cycles clock CPU. When I read from RAM it takes about 12us, but GPIO 25us. This is too slow for me. I tried all the tricks and combinations of LDR; STR ... LDR LDR STR STR ... LDR AND LDR STR AND ... Minimum is 25us. LDR gpio and STR ram are without comment at all. Some astronomical values ​​come out that can be obtained from AVR or DSPIC. I tried FMC to read and it was even worse. What is the fastest way to read the state of a ~40MHz pin? 

Hello Team,I am planning to use the STDRIVE101 to develop an ESC, and I would like to clarify something before proceeding.Does the STDRIVE101 introduce any jitter in the PWM output? If so, what is the typical jitter value?Thank you for your help.Best regards,Aji

What are the differences between LPTIM and TIM, also doesTIM1,TIM2,TIM16,TIM17 work when the device is in STOP2 mode?