Solved

Hello, I plan to make a 333V Battery using AEK-MCU-C4MLIT1 as the master, AEKSCOM-ISOSPIA as the translator and AEK-POW-BMS69EN as the slave BMS Boards.  So far, I have been using the Example "SPC58EC—AEK_POW_BMS63EN_SOC_Estimation_Single application for discovery" to connect the Master to a single slave and receive cell voltages and temperatures. That has worked well.  Now, the next step of the project is to connect the slaves in a daisy chain and get individual data. Since the battery modules are supposed to be connected in series, I can't connect the slave boards using the USB connection. Thus, I have only connected the ISOH & ISOL lines.  As per the support document, I can't directly use the same example when I have multiple slaves. I should use the following examples: "SPC58EC - AEK_POW_BMSWTX_SOC_Est_SingleAccess_CHAIN application for discovery" However, I am not able to get cell data from even a single slave if I use this example, even when I change the connec

Theres T1 T2 T3 T4 and QA. QA is unchecked. Assuming it means Quality Assurance. Should I be worried?

Hi community, I understand that users can encrypt and sign firmware using STM32CubeProgrammer. My question is about the first stage bootloader provided by ST. From my limited reading, it seemed that this 1st stage ST bootloader is only encrypted but not signed. Is my understanding correct? If not, please can someone point to me the document describing how does ST do the 1st stage bootloader signing and where the verification key is programmed on the MCUs? Thanks, and best regards James  

Hello, first time poster.I recently got a few NUCLEO-WL55JC2's for a research project.but other than the standard examples, I am unable to compile a project that I either made using my own ioc, or the one in C:\Users\%username%\STM32Cube\Repository\STM32Cube_FW_WL_V1.3.1\Projects\NUCLEO-WL55JC\Applications\LoRaWAN\LoRaWAN_End_NodeWhen I use either of these, this is the error message I get in CubeIDE, when hitting build. ../Core/Inc/platform.h:45:10: fatal error: stm32wlxx_nucleo_radio.h: No such file or directory 45 | #include "stm32wlxx_nucleo_radio.h" | ^~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. arm-none-eabi-gcc "../Middlewares/Third_Party/LoRaWAN/Mac/Region/RegionBaseUS.c" -mcpu=cortex-m4 -std=gnu11 -g3 -DDEBUG -DCORE_CM4 -DUSE_HAL_DRIVER -DSTM32WL55xx -c -I../Core/Inc -I../LoRaWAN/App -I../LoRaWAN/Target -I../Drivers/STM32WLxx_HAL_Driver/Inc -I../Drivers/STM32WLxx_HAL_Driver/Inc/Legacy -I../Utilities/trace/adv_trace -I../Utilities/misc -I../Utilities/sequencer

Hi all,I recently purchased an STM32H723VGT6 breakout board [https://github.com/WeActStudio/WeActStudio.MiniSTM32H723] (not a NUCLEO) and a VL53L5CX sensor breakout from Pololu [https://www.pololu.com/product/3417], and, as I'm a beginner and struggling to navigate all the literature as it relates to STM32, I was wondering if anyone here could give me a step-by-step guide on what documents I need to read in order to set up this custom hardware before I design a similar setup myself with an STM32H523 instead of an STM32H723.I've already went through the user manual, quite a few YouTube videos, and some more stuff, and I'm confused, since I can't seem to find documents on working with X-CUBE-TOF1 and custom hardware.The main issue I have is the fact that I only want just that two pin I2C connection between the MCU and the sensor and nothing else due to the space constraints of my upcoming custom design [PB10 = SCL, PB11 = SDA]. Therefore, I have done the same in the prototype with the of

I am using the STM32WB15CC and encountered an issue when my program exceeded 112KB (0x1C000), causing the flashing process to fail. I noticed that the memory region starting from 0x0801C000 is set as a secure flash area.I would like to know if it is possible to modify this secure flash area. If so, could you please provide guidance on how to make the necessary modifications?

Good day,I've been working on getting an external adc on the nucleo H755ziq to work at max speed. The adc can reach up to 1 million samples a second with a clock cycle time of 10ns. Problem is that it's only seeming to go at a speed of 60ns per clock cycle. Spi is set at 200mhz with a /2 prescaler on an external 48mhz crystal. Any idea why it's getting this 60ns speed instead of 10ns? Ive set the GPIO for spi to very high speed as well encase that was the issue.

Hi,I am developing AC-DC flyback with HVLED815PF controller.Using application note AN4350 I managed to have a CV output for 6W max.At high load, everythings good and functioned as expected.I got 25% iTHD and 0.96 PF.However at 2W and below its suddently getting worse.After checking it out, it turns out the controller operating in burst mode and normal mode alternately.I have checked all pins and did not found anything out of the ordinary, except that COMP pin is below 1V that triggers this burst mode operation which is my questionWhat could be the reason for this? and how to mitigate this?Its too early to enter burst mode at just 30% load. 

Hi,I'm trying to get the FTM examples from the STSW-ST25R-LIB to work on a ST25R3916.I am using the following hardware:-Mikroe NFC 4 Click Board with a ST25R3916-STEVAL-25R3916B (I only use the reader/antenna board STEVAL-D25R3916B without the Mcu board)-Nucleo L476RG microcontroller board (as it is the one used in the sample projects from the library)On the software side I am using the FTM examples from the X-NUCLEO-NFC06A1 (for 3916 on Mikroe board) and X-NUCLEO-NFC08A1 (for 3916B on Steval board) folders in the lib. The programs seem to be identical, only the global definition for the HW/reader selection is different.When I use the NFC08A1 program with the Steval, the reader works fine. But when I use the NFC06A1 example with the Mikroe board it doesn't work. When I try to read the chip ID in the initialisation process, it always reads zero. I have checked this interaction with a logic analyser in both examples and have attached the screenshots. I have tried both SW examples on

Hello! I'm looking for a BSDL file for the SPC560D40L1BxE0.Is it available somewhere?Kinds regardsJacob

In my setup, I’m using Comparator 6 (COMP6) on the STM32G474 microcontroller. The non-inverting input of the comparator is connected to a burden resistor from a current transformer, which measures current flow. The inverting input is tied to a fixed 1.5V reference created by a voltage divider. The goal is for the comparator to disable all PWM signals (generated by HRTIM TimerA) when the burden resistor voltage reaches 1.5V, indicating an overcurrent condition (e.g., 10A).Issue: Despite the burden resistor voltage hitting 1.5V at 10A, the comparator does not trigger, and the PWM remains active.

Best SPI Routing Method for Double-Sided 16×128 LED Matrix Using STP24DP05Project OverviewI am designing a double-sided 16×128 RGB LED matrix display using STP24DP05 LED drivers. The LED drivers are controlled using a single SPI bus from the MCU. Since the display consists of both a front and back panel, each panel consist of 16 STP24DP05 LED driver. I am considering two different approaches for routing the SPI and error signals and would like recommendations on the best solution.Approach 1: Split SPI and Error Signals Using BuffersIn this approach, I use buffer ICs (74LV244) to split the SPI bus and drive both the front and back panels independently. Additionally, the error signal (ERR) from the STP24DP05 drivers is also split and handled separately for each panel. Each panel consist with 16 LED driver. SPI Control: The SCK, MOSI, MOSI and CS signals are buffered separately for the front and back panels.MCU Control: The MCU enables/disables the SPI buffers using GPIOs, ensuring t

I'm trying my hand at a LoRa project and settled on using the STM32WLE5JC chip on Seeed studio's Wio-E5 module. I've read through the bootloader manual and Seeed studio has their own set of instructions for wiping their pre-existing code which I have gone through, but my question is in regards to after I have successfully flashed code similar to the ping-pong examples in subGHz. Specifically, is it possible to upload code using an ST-Link without access to the BOOT pin?For reference, the module gives access to SWDIO, SWCLK, and NJRST, which I have broken out these pins along with GND and PWR, but the BOOT pin is not accessible. In my past experience using STM32, I flashed through UART which did require the bootloader and hence boot pins were the easiest way to go. From what I have read online, it seems that flashing through ST-Link doesn't require the system to be put into bootmode but would appreciate some confirmation on this. Seeed's factory firmware appears to have made a different

I was looking at STM32N6, and it says it has 1G networking. Problem is, chip used is 100M. So how can they say that development kit supports 1G ?LAN8742A-CZ-TR chip used inside both devkits:Same goes to HR timer, it says on datasheet, it does support high resurrection timer, while no mention anywhere about itIs there nay more information regarding timer and does devkit support 1G ? I was hoping it could, since I could make IP camera or something similar. 

I want to use the motionfx library in the x cube mems1 package for my flight control card and ahrs project, my aim is to obtain roll pitch and yaw values with sensor fusion, but I have not come across an example code for using motionfx. Can anyone help?

Hi,I am using the latest version v1.16.0 STM32CubeIDE with stm32g071cb.It is not possible to use ADC1_IN16 (PB12). I have created also a new project  to test this condition.Changing the sequencer disables IN16 or makes error condition.I need PA2 -PA3 and PB12 pins (IN2-3-16 channels to ADC sampling)Below attached screen view and the ioc file generated via STM32CubeIDERegardsMurat   

Hello,in the datasheet of LPS22HBTR the absolute pressure accuracy is between 0. and 1 mBar in the range of 0°C and 65°C .Please have more information about the absolute pressure accuracy in negative temperature ? because i will use it betwen -20°C and 0°Cthanks 

Heyho, just checked the build analyser in STM32CubeIDE for my L031 project and found "impure_data" in the RAM list.Can anyone please explain what that is? Google didn't really help... Just curious, RAM size is not a problem for this project (32kB flash is a problem when debugging with UART...).Thanks!

I've been using B-WB1M-WPAN board with a modified example of motion service from BLE_HR_p2p_Sensor. but with IMU readings with a steval-mki217v1 shield connected with SPI. I already have the CRC checked from CubeMX generation.   So far I have been able to read IMU data (polling) and send it through a BLE notifiacation service. but when I try to setup a MotionFx server it mulfunctions. void ssfusn_setup(void) { /* Check if statically allocated memory size is sufficient to store MotionFX algorithm state and resize if necessary */ if (STATE_SIZE < MotionFX_GetStateSize()) { // Error_Handler(); while (1) { /* code */ } } /* Sensor Fusion API initialization function */ MotionFX_GetLibVersion(lib_version); MotionFX_initialize((MFXState_t *)mfxstate); MotionFX_getKnobs(mfxstate, &iKnobs); iKnobs.acc_orientation[0] = 's'; iKnobs.acc_orientation[1] = 'e'; iKnobs.acc_orientation[2] = 'u'; iKnobs.gyro_orientation[0] = 's'; iKnobs.gyro_orientation[1] = 'e'; iKn

Can anyone confirm that the Build Analyzer in the CubeIDE works when using the CMake toolchain? For compatibility reasons I'm currently stuck at IDE version 1.16.1. I created a fresh CMake Project for a Nucleo board (U545). It creates the elf and map files just fine but the Build Analyzer stays empty. (Yes, I tried the refresh button...)If someone could confirm that a newer IDE version does the job, I'll try to convince the project team. Or what I could do to make it work in 16.1. Thanks!

Hi all, I got trouble with updating firmware on Nucleo f103rb board (ST-Link/V2) I used STM32CubeProgrammer to update firmware.  First of all, I checked connection between PC and board by clicking the green "Connect" Button, and the connection was good.(ST_LINK configuration section showed serial number)  Then I click Firmware upgrade Button and clicked "Open in update mode" in ST Link UPgrade tool. Every time I click "Open in update mode" to update firmware, the tool says "Device [mydeviceNo] not found, No device connected." And LD1(on Red LED the board) starts blinking.LD1 was not blinked Before Open in update mode. (The red light was just ON without blinking)  Please Help me with this problem.. 

It is shown that some updates are available in my STM32CubeIDE version 1.18.0... But when i started that update, it is stopping at 12 percent... Help me with this  

@MM..1  @Tesla DeLorean Hi! I am getting this error and not being able to find out why. I've looked online and haven't found an answer either.I have some #defines in my header file and for some reason I it is like my source file can't see these definitions. I've done just the same for all my other files and all of them work, however this one gives me: Type 'Button' could not be resolved.I checked if there is a type, but everything seems to be correct. Any chance someone could help me? Thank you!! (I am using STM CUBE IDE)

We are planning to use an external flash memory connected via QuadSPI to the OCTOSPI peripheral of a STM32H735 (at a later stage that would be STM32H733).This will be used to run firmware and store downloaded firmware updates with SBSFU. For that we will need the OTFDEC peripheral to ensure date is encrypted for storage.What I need to know is whether the Quad SPI interface of OCTOSPI will be able to work with OTFDEC in memory mapped mode? The memory also does not support HyperFlash.It is my understanding (from AN5050 and AN5281) that OTFDEC and OCTOSPI are independent peripherals in operation but where OTFDEC comes in between OCTOSPI and the AXI bus so it should be possible.

Hi there!I have two UART devices connected to STM32U575 that run at 1.8 and 3.3V and 115200 baud rate. I am trying to get USART1 working on STM32U575 on PG9 (TX) and PG10(RX) that uses VDDIO2 reference 1.8V and UART4 on PA1(RX) and PA0(TX) that uses main VDD 3.3V as reference voltage.I have an LDO that uses 3.3 to get 1.8V and its enable pin (pulled LOW and disabled by default) is controlled by STM32U575 GPIO - PE4, so controlling the timing of 1.8V is possible.Problem: After enabling 1v8 power and initializing USART1, the UART4 interrupts stop working but UART4 is able to still print. However, if I enable 1v8 power and I don't call the function MX_USART1_UART_Init(), UART4 interrupts works as expected.I've tried enabling the VDDIO2 before initializing the USART1 but no luck. Below is the code that shows this behavior. void console_thread_entry(void *argument) { char tRxedChar; HAL_UART_Transmit(&huart4, (uint8_t *)"Hello!\r\n", strlen("Hello!\r\n"), 100); HAL_PWREx_D