Solved

   Hello, I would like to ask about a question regarding “STM32N6570-DK for gesture recognition control applications.”I have downloaded the official example x-cube-n6-ai-hand-landmarks-main and reviewed the DataBrief of the development board. Since the board itself does not contain internal Flash, the file _htmresc/FSBL.PNG in the example clearly indicates two possible solutions:User APP programmed into SRAM (address: 0x3400 0400 ~ 0x3418 0000)User APP programmed into external Flash (address: 0x7008 0000 ~ 0x7FFF FFFF)Following the instructions in README.md, I executed the following steps:~make -j8~ Program the Firmware in the External FlashAfter building the application, it is necessary to add a signature to the binary file:~STM32_SigningTool_CLI -bin build/Project.bin -nk -t ssbl -hv 2.3 -o build/Project_sign.bin~ After obtaining the signed binary file, I manually programmed it to address 0x70100000.(The files ai_fsbl.hex, hand_landmark_data.hex, and palm_det

Environment: STM32L4 + 32.768K LSEFunction: Wake up and work once every hour, then enter stop2 mode. During the one-hour sleep, wake up every ten minutes to feed the external watchdog.Problem: The device resets directly when waking up every ten minutes.Current known information: The device was tested in the company for over twenty days without any issues (including restarts, freezes, etc.). After the prototypes were given to customers, problems started to occur in about 10 to 20 days. Currently, there are two failed devices. After power cycling, the devices did not return to normal. External reset also did not restore them to normal. Re-flashing the devices allows them to operate normally, and they are currently under continuous pressure testing to see if the issue will recur.Current debugging progress: When the device restarts, the nRST pin has a low-level time of less than 1ms. The 3.3V power supply pin of the MCU is stable as observed by the oscilloscope. The TP5010_DONE_Pin has a 4

I am trying to deploy encoder only transformer model on STM32 by converting pytorch model to onnx format first and then using STM toolchain (STM32 CubeAI). However, I am constantly getting this error when I analyzed the model:TOOL ERROR: cannot reshape array of size 0 into shape () I tried to debug my model but couldn't find any issue in it. Any guidance will be appreciated. Thank you.

Hi there!I already configured LwIP package and make it work on a NUCLEO-H755ZIQ following @Adam BERLINGER gude in the Knowledge base section:https://community.st.com/t5/stm32-mcus/how-to-create-project-for-stm32h7-with-ethernet-and-lwip-stack/ta-p/49308 Well, trying to move the LwIP heap memory to a larger memory location I experienced a n unexpected issue:When I locate the heap in the DTCMRAM of the M7 core, communication will no more work at all(no ping, no tcp connection...).Locating it in D1 (AXI RAM) or D3 RAM all work as expected.I checked also the MPU configurations ad all seems correct, it seems that in DTCMRAM there is a different behavior. Just for my comprehension, there is something wrong in locating such heap into the DTCMRAM?Thanks in advance! iTTy 

Reporting that this bug is sitll present in CubeMX v6.16.1Solved: We found a bug while using Hardware JPEG. - STMicroelectronics CommunityStill JPEG_SWAP_RG, not JPEG_SWAP_RB.I wish there would be user defined section in jpeg_utils.conf.h to workaround it.And there's another bug:Every time I regenerate code, CubeMX erases Utilities/JPEG folder. So the package code has to be manually restored.

I’m working with TouchGFX in STM32CubeIDE. After creating a new project and copying over the IOC file and pin configuration from the verified design used for my custom PCB, I’m now running into errors. Some components fail to build, and I’m getting “file not found” errors for certain header files—even though the files clearly exist and I can open them in the IDE.Do you have any suggestions for fixing include paths or linker settings to resolve this?  

Hi,I want to kick ADC1 IN5 with the Timer TIM2. I'm working with CubeIDE.I select:ADC1 -> ADC_Regular_Conversion_Mode -> External Trigger Conversion Source  -> Timer 2 Trigger Out eventTIM2 ->  Trigger Output (TRGO) Parameters -> Update EventBut ADC1 does not run, Data Register is constant.If I kick ADC1 by software everything is fine, I get some noisy numbers.TIM2 is running, the count register is counting.Why does TIM2 not kick ADC1 by the TRGO event?This setup used to work fine on STM32F303. What do I miss on the STM32F429?THX CheersDetlef 

In rm0316 rev 10 for the stm32F303x, the documentation for the ABRQ bits in the CAN_TSR transmit status register states: Setting this bit has no effect when the mailbox is not pending for transmission. I am finding on my STM32F303 that setting ABRQx when the mailbox is empty will actually clear the RQCPx and TXOKx status bits in the CAN_TSR. This effect is important to note, because if you're using the TXOKx bit to determine if the message was transmitted or aborted and ABRQx was set after the mailbox finishes its transmission and becomes empty, you will think the message was successfully aborted (because TXOKx is cleared by the late abort) when it was actually transmitted. Even if you disable interrupts and check the mailbox status immediately before setting the ABRQx bit, it seems like there is still a race condition where the mailbox transmission could complete between the read and write operations, which could occasionally cause the abort to be late.  Is there a way to do this

Hi everyone,I am trying to train a large dataset in NanoEdge AI Studio, where each class is around 500 MB in size.Totally 5 class.However, I am facing limitations related to the data structure, memory usage, and training workflow in NanoEdge AI Studio. I would like guidance on:Recommended data structuring or segmentation methods for very large datasetsBest practices to handle or reduce large data sizes (windowing, feature extraction, downsampling, etc.)Any tool limitations or configuration settings to be aware ofPossible alternative approaches if direct training with such large data is not supportedIf anyone has experience training large datasets with NanoEdge AI Studio, your guidance or references would be greatly appreciated.Thank you in advance for your support.Best regards,Vijepradeepan

hi, ive noticed that hand landmarks pre built binarys uvc output does not work on the C02 revision NUCLEO-N657X0-Q but does work on the c01 rev, could anyone guide me on how to get this demo up and running ont he c02?

Hello, I was writing some code and one day a handler_reset() appears in the debug panel It is said that appears because it give the opportunity to the user to debug from the very begining. But why? if there is already the ability to set the breakpoint in the main...  I cannot assign a value to a variable.  And the other things is the fact that since it has appear I cannot longer debug and the variables make no sense. What causes all that and which is the solution??Thanks.          

Hi,I am currently facing an issue while connecting to the STM32 board using STM32CubeProgrammer. The tool consistently shows the error: "Unable to read device ID from ROM table."I have already tried the following troubleshooting steps:Performed a hardware/software/core reset using the RESET buttonVerified that all required supply voltages are correctChecked the hardware connectionsDespite this, the programmer is still unable to establish communication with the M7 core via ST-Link. It appears that the device is not being detected properly, and at the moment the board has become unusable.Could you please guide me on possible causes or additional steps I can take to resolve this issue? I would be happy to provide any further information if required.Thank you for your support.Best regards,Prathiksha

Heyho,I just changed a big PCB (1st revision working) with a H733 and added a micro SD cardholder and connected it to the SDMMC2 peripheral.Only to find out later that this #2 does NOT work with the extra IDMA controller.SDMMC1 is out of the question because I absolutely need I2SCKIN for the SAIs, and I didn't want to change the complete pin-out and PCB design (Altium says: Components on board: 1015).I'm pretty sure I've checked the RM, but maybe I oversaw something...So, is there any way to use another DMA with SDMMC2 ?Thanks in advance!

Hello Team,  I am using stm32f769 controller. I am using timer 1 channel 4 for pwm output, and my APB1 clock is 180MHZ here I am taking prescaler : 17999 and ARR=1999 and ccr=1000 for this values I can see output of pwm by generating 5hz pulses. But when I want to generate 486 pulses where my psc:17999 , ARR=19, ccr=10, I cant see any output pulses, my pwm is not responding.  (ARR+1)(psc+1)=180MHZ/frequency (ARR+1)(psc+1)=180MHZ/486 (ARR+1)(psc+1)= 370370 ARR+1=370370/18000 ARR+1=20 ARR=19   for some values upto ARR= 40 i am getting output over pwm but from values ARR=20 i am not getting output could you please help me   Thanks vamshi kumar

Dear all, I would like to connect a camera to my Nucleo F756ZG board, with the goal to send images via the ethernet port. However, this board doesn't feature a 30-pin ZIF connector nor a 22‑pin FFC connector....Apparently, the STM32 F756ZG has a "DCMI". Is this accessible on the Nucleo board as well?Which module/camera do you recommend for the Nucleo F756ZG?Would you recommend Arducam? They seem suspiciously cheapThe B-CAMS-IMX is not compatible, right?Many thanks

Title edited - part number added (not an ST part)After commencing debugging with the JLink, these faults persistently occur after approximately 30 seconds. However, this JLink functions correctly when debugging IAR. What might be the cause?The actual chip used is the STM32F407VET6.JLink keeps disconnecting from CubeIDE for some reason. Debugging frequency SWD=500kThe ST Community moderator has edited the post to comply with the forum language guidelines. The language of the Community is English. For more information, see: ST Community Terms and Conditions

I am trying to get wake-up from HALT mode working on the STM8L151 using the RTC, but without success. I tried two approaches:using the RTC wake-up counter to wake the device after 10 seconds andusing the RTC alarm to wake it up every minute.Neither approach was successful — once the MCU enters sleep, it no longer wakes up. I have the feeling that the issue is not so much directly in main and in the CLK + RTC configuration, but rather in the ISR, IQR handling setup. At this point, however, I’m not sure what to add, what to check, or in which files (stm8_interrupt_vector.c, stm8l15x_itc.c,....).I would be very grateful if someone could advise me on what belongs where, so that I can understand the entire interrupt chain and which additional files in the Inc directory need to be adjusted. In parallel, I also have several related follow-up questions:I am using STM8L15x_StdPeriph_Driver (downloaded from ST as STSW-STM8016 version 1.6.2) — is this version up to date?In the examples, there are

I am developing with STM32CubeMX and generating initialization code for an STM32N6 device. In my FSBL (First Stage Boot Loader), I use USART10 to connect to the ST-LINK V3’s Virtual COM Port (VCP). However, it seems that CubeMX does not correctly generate the peripheral clock initialization code for USART10.After a series of investigations, I found that when generating USART10’s clock initialization code, only the kernel clock for USART10 is set to IC14, but the PLL source and divider for IC14 are missing. This happens with both LL and HAL libraries. For USART6, there is no such problem — its clock configuration is generated correctly.This behavior is very strange. During debugging, I also encountered an issue where PLL2 was not initialized, but that problem disappeared later.To work around this, I manually added IC14 configuration code for USART10 following the pattern used for USART6, setting IC14 = 96 MHz. After that, USART10 worked normally at the maximum baud rate of 12 Mbps.Has a

So as the title suggests, I have been trying to get the LCD screen to work on the STM32F469i-DISCO board. Currently I just want it to turn on at all. I found the BSP drivers in this link as well as the OTM8009A drivers in this other link  When I run the code however, it gives me the following error:../Drivers/BSP/STM32469I-Discovery/stm32469i_discovery_lcd.c:402:5: error: too few arguments to function 'OTM8009A_Init'402 | OTM8009A_Init(OTM8009A_FORMAT_RGB565, orientation); I noticed that the function prototype for that function is int32_t OTM8009A_Init(OTM8009A_Object_t *pObj, uint32_t ColorCoding, uint32_t Orientation);so I am not sure why the lcd drivers call the function in that way. Are there better/newer drivers that I should be using instead?

We are operating ASM330LHH with ODR set at 3333Hz, but the actual measured output is about 3570Hz.This is not stated in the specifications, but is this within the range of the specifications?

When using stm32n6 and enabling both GFX and AI models, the runtime continuously reports errors:"Epoch controller error interrupt: EC_IRQ = 0x00000008 Epoch controller opcode counter: 0x00000000 Epoch controller tag: 0x00000000 ATON_STD_IRQHandler()@851: irqs=0xlx Assertion '0' failed: file 'E:/TouchGFXProjects/AR_Glasses/Middlewares/AI_Runtime/Npu/ll_aton/ll_aton_runtime.c', line 855, function: __LL_ATON_RT_IrqErr"What could be the possible cause of this? Is it related to the XSPI2 bus? both GFX and cubeAI utilize XSP2.The model used is the official demo program: st_yolo_x_nano_480_1.0_0.25_3_st_int8.tflite from STM32N6-GettingStarted-ObjectDetection-main.I sincerely hope that st can help me solve this problem. Thanks

I want to use DMA with SPI in slave receive mode with words longer than 8 bits :I launch the DMA with the function: HAL_SPI_Receive_DMA( &HSPI_ADS, (uint8_t*)ads_dma_buffer, ADS_BUFFER_MAX_SIZE );Unfortunately in this function the following test fails:  /* Packing mode management is enabled by the DMA settings */ if (((hspi->Init.DataSize > SPI_DATASIZE_16BIT) && (hspi->hdmarx->Init.DestDataWidth != DMA_DEST_DATAWIDTH_WORD) && \ (IS_SPI_FULL_INSTANCE(hspi->Instance))) || \ ((hspi->Init.DataSize > SPI_DATASIZE_8BIT) && (hspi->hdmarx->Init.DestDataWidth == DMA_DEST_DATAWIDTH_BYTE))) { /* Restriction the DMA data received is not allowed in this mode */ errorcode = HAL_ERROR; __HAL_UNLOCK(hspi); return errorcode; } Because the structure "hspi->hdmarx->Init" is never initialized. It is not initialized, but the structure associated with the nodes is indeed initialized.In the case where the data size is 8 bits, the test i

HiI have been messing around with VL53L4CD for the last few months, and I recently realized that my readings differ significantly, depending on the target color/texture.Here is my setup: The sensor is set on its side, and directly in front of it, at the 20cm mark, I place a few different gray-level cardboard boxes, ranging from black to white, mostly gloss-textured.The sensor readings vary by about 10mm (222 shortest, 233 longest) depending on the box.Performing offset calibration helps to have an accurate reading on a gray target, but the error persists for other colors.I have tried performing cross-talk calibration, although I don't have a cover glass for this test, but that doesn't seem to help either.My question is - do we have to know the target reflectivity in advance and calibrate for it? Am I wrong to expect more consistent readings against various targets?Thanks!

ST‑LINK Mini V3E not detecting STM32H7 (Core ID error, high current when VTARGET connected)I’m debugging an issue with a custom STM32H7 board and an ST‑LINK Mini V3E. The setup includes a main PCB and a separate power PCB. So far:Power & Basic Checks3.3 V and 24 V rails are correct.Board current consumption is low when powered from either an 8 V or 24 V supply.Connections between the ST‑LINK Mini V3E and the main PCB have been verified.ProblemWhen I connect VTARGET from the ST‑LINK to the board’s 3.3 V rail, the current spikes and something starts to smell hot.STM32CubeProgrammer shows no target voltage, no device ID, and fails to read the core ID.The ST‑LINK is detected by the PC normally.Additional TestsTried a second main PCB and a different ST‑LINK Mini V3E, powering only through the ST‑LINK (no external supply). Same result: STM32CubeProgrammer cannot detect the STM32H7.I’m aware that VTARGET on the Mini V3E is an input, so I’ve tied it to the board’s 3.3 V rail as required.Ne

 Dear sirs. I'm connecting an ISM330DHCX with an IIS2MDC and I need to know if the connections scheme is okay to operate in MODE 2Then I need to know if pullups are needed for i2c bus coming from SCx and SDx, and if pulldowns are required for INT lines as in the provided schematic.I'm based on the ISM330DHCX and IIS2MDC datasheets and X-NUCLEO-IKS02A1 board manualThe routing jumpers are there just in case we need to route one magnetometer to tha main I2C bus Thanks in advanceIgnacio