Solved

Hello,I am connecting STM32V2 debugger at following pins.  This supports SWD. I want to use JTAG pins and want to use STM32V2 debugger as a JTAG connection for debugging purpose. can you support me how to connect or which pins to be used and what is the procedure to change from SWD to JTAG mode? Regards,Nikhil  

hi all I testing lora tow nucleo-073 pingpong test.(STM32CubeExpansion_LRWAN_V2.1.0\Projects\NUCLEO-L073RZ\Applications\SubGHz_Phy\SubGHz_Phy_PingPong)But it happen rxtimeout txtimeout .  Let me know why... Thanks

When changing the timebase source in CubeIDE from Systick to any peripheral timer (TIM6 in my test case), the timer is set up in HAL_InitTick() called from the HAL_Init() function, which is the first function that is called in main().HAL_InitTick() uses several calls to get the clock configuration from RCC in order to set up the timer.However, the clocktree is configured only AFTER the timer has been initialized, since SystemClock_Config() is the second function called in main().This should mean, that the peripheral timer that provides the system clock is based on uninitialized clock settings. The simple solution is to swap SystemClock_Config() and HAL_Init() in main(), so clocks are configured first and the timer afterwards.Am i missing anything, or is this a bug? Setup:STM32F427VGTxCubeIDE 1.16.0STM32Cube FW_F4 V1.28.0Selected Timer for System clock source: TIM6My .ioc file is attached.

Hi,I'm trying to create a wrapper for STM32CubeProgrammer_API.dll.The program crashes on trying to use the obDisplay API. I've tried using STM32CubeProgrammer_API.dll versions 2.10 and 2.15. Is there something I'm missing?Thank you very much.

My group want to start a project about capturing image by OV7670 and display it with STM32F429  but don't know where to start, any tutorial or suggestion?

Hi all,When I wake up from Standby mode and reinitialize the pins and peripherals, they still don't work. Below is my STBY_SysHwRestore() routine, where I reinitialize clocks, pins and peripherals, but the rest of the code does nothing when they accessing the pins and peripherals. I have looked into the BLE_HeartRate example and copied the CPUcontextSave and CPUcontextRestore from the start up file. What confuses me on the BLE_HeartRate example is that it doesn't need to reinitialize clocks when leaving the standby mode, while on my application it needs, otherwise it get weird behaviour. QUESTION 1: What is the correct way to reinitialize pins and peripherals when waking up from standby mode?QUESTION 2: After waking up from standby mode due to a wake-up timer (registered on the hw_timerserver.c module), if I start a task on the sequencer directly from the wake-up timer callback, the CPU hangs for some reason. This stuff is really h

Hello, I would like to report a bug on USB CDC middleware generated from CubeMX 6.11. When I use it in Debug build, everything works as expected. Once I switch to Release, the compiler optimizes out the serial number.  I use official VScode extention with Cmake to build the FW.Without a serial number at USB device, Windows fails to recognize that anything is connected. It works in Linux only. I have the same issue happen at STM32F411 and STM32L433. The solution was to add initalization to 3 lines in USB_DEVICE\App\usbd_desc.c uint32_t deviceserial0 = *(uint32_t*)DEVICE_ID1; uint32_t deviceserial1 = *(uint32_t*)DEVICE_ID2; uint32_t deviceserial2 = *(uint32_t*)DEVICE_ID3; I hope this helps someone and the STM may fix it. No support is needed.Thanks.

 Is my settings true?

Could not verify ST device! Please verify that the latest version of the GDB-server is used for the connection.Open On-Chip Debugger 0.12.0-00024-gc3ff39f8b (2023-06-26-16:51) [https://github.com/STMicroelectronics/OpenOCD] Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : Listening on port 6666 for tcl connections Info : Listening on port 4444 for telnet connections Info : STLINK V2J43S7 (API v2) VID:PID 0483:3748 Info : Target voltage: 3.308456 Info : Unable to match requested speed 8000 kHz, using 4000 kHz Info : Unable to match requested speed 8000 kHz, using 4000 kHz Info : clock speed 4000 kHz Info : stlink_dap_op_connect(connect) Info : SWD DPIDR 0x0bb11477 Info : [STM32F030F4Px.cpu] Cortex-M0 r0p0 processor detected Info : [STM32F030F4Px.cpu] target has 4 breakpoints, 2 watchpoints Info : starting gdb server for STM32F030F4Px.cpu on 3333 Info : Listening on port 3333 for gdb connections Error: [STM32F030F4Px.cpu] clearing lockup af

I had used STM32CubeMX generated ADC with STM32H750VBT6:ADC_REG_InitStruct.TriggerSource = LL_ADC_REG_TRIG_EXT_TIM1_CH1;ADC_REG_InitStruct.SequencerLength = LL_ADC_REG_SEQ_SCAN_ENABLE_2RANKS;ADC_REG_InitStruct.SequencerDiscont = ENABLE;ADC_REG_InitStruct.ContinuousMode = LL_ADC_REG_CONV_SINGLE;ADC_REG_InitStruct.Overrun = LL_ADC_REG_OVR_DATA_PRESERVED;LL_ADC_REG_Init(ADC1, &ADC_REG_InitStruct);->but ADC not working.My modify:ADC_REG_InitStruct.TriggerSource = LL_ADC_REG_TRIG_EXT_TIM1_CH1;ADC_REG_InitStruct.SequencerLength = LL_ADC_REG_SEQ_SCAN_ENABLE_2RANKS;ADC_REG_InitStruct.SequencerDiscont = LL_ADC_REG_SEQ_DISCONT_2RANKS;ADC_REG_InitStruct.ContinuousMode = LL_ADC_REG_CONV_SINGLE;ADC_REG_InitStruct.DataTransferMode = LL_ADC_REG_DMA_TRANSFER_UNLIMITED;ADC_REG_InitStruct.Overrun = LL_ADC_REG_OVR_DATA_PRESERVED;LL_ADC_REG_Init(ADC1, &ADC_REG_InitStruct);-> Issue had'nt fixed.I change to HAL lib with ADC1hadc1.Instance = ADC1;hadc1.Init.ScanConvMode = ADC_SCAN_ENABLE;hadc1.

I'm using stm32flash (https://sourceforge.net/projects/stm32flash) as my host on a raspberry pi. It's connected to the STM32H750 using I2C.Steps:Upload the code onto the STM32./stm32flash -a 0x4E -w stm32-blinky.bin -v -R /dev/i2c-1   stm32flash 0.6   http://stm32flash.sourceforge.net/   Using Parser : Raw BINARY Size : 15612 Warning: Not a tty: /dev/i2c-1 Error probing interface "serial_posix" Interface i2c: addr 0x4e Version : 0x12 Device ID : 0x0450 (STM32H74xxx/75xxx) - RAM : Up to 128KiB (16640b reserved by bootloader) - Flash : Up to 2048KiB (size first sector: 1x131072) - Option RAM : 1b - System RAM : 122KiB Write to memory Erasing memory Wrote and verified address 0x08003cfc (100.00%) Done.   Resetting device... Reset done.Obviously the same result can be achieved withst-flash --serial $SPI_BOOT_DUT --reset write build/stm32-blinky.bin 0x08000000   st-flash 1.7.0 2021-12-07T15:51:38 INFO usb.c: Unable to match requested speed 1800 kHz, using 1000 kHz

I have setted max current = 1 A and in RevUp table 0.6 A. In Waveforms below, I am getting current around 0.05. Is this in Amp? Only this much small current is driving the motor? I tried increasing/decreasing the speed but value is almost this.Also, Can I somehow just make x axis as time in (seconds) ?      

Hi,   I'm discovering the STM32MP13 Bare metal project. I'm following example given by the STM32CubeMP13 Package. Everything works fine except for the fact that I'm disappointed by the performance. Indeed, if my theory is correct, the following code should change the pin status every second.       void testCPUFreq(){ GPIO_InitTypeDef GPIO_InitStruct = {0}; uint32_t i; __HAL_RCC_GPIOH_CLK_ENABLE(); GPIO_InitStruct.Pin = GPIO_PIN_6 ; GPIO_InitStruct.Mode = GPIO_MODE_OUTPUT_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_VERY_HIGH; HAL_GPIO_Init(GPIOH, &GPIO_InitStruct); while(1){ for(i = 0; i < CPU_FREQUENCY; i++){ } HAL_GPIO_TogglePin(GPIOH, GPIO_PIN_6); } }       I made my measurements using a logic analyzer connected to the pin in question. When I run the test on an STM32F7 target running at 200MHz, the pin status changes every second (which is the expected result). When I run

Hello dear All,On STM32G0B1 I'm trying to capture PORTD[0-7] value with DMA on EXTI0 event (PD0 falling edge)(Read PORTD value in EXTI0 interrupt is too slow for this application -> PORTD change value before entering IRQHandler())I configure EXTI and DMA2_Ch3 in MX but PORTD value is NOT trasfered in my destination variable on event.However, by using HAL_DMA_Start_IT(), function DMA1_Ch4_7_DMA2_Ch1_5_DMAMUX1_OVR_IRQHandler() is called.Could you please help me to do a well configuration in order to transfert PORTD->IRD value in my destination variable "u8_tst_1" with DMA on PD0 falling edge event ? :| Let see source code below.My Environment:STM32CubeIDE v1.8.0STM32CubeMX v6.4.0-RC4STM32Cube_FW_G0_V1.5.0NUCLEO-G0B1REWindows 10 Pro 21H2/* Private variables ---------------------------------------------------------*/ DMA_HandleTypeDef hdma_dma_generator0; /* USER CODE BEGIN PV */ volatile uint8_t u8_tst_1; /* USER CODE END PV */   /* Private function prototypes -----------------

          Hello! I dont know where to find received data after HAL_I3C_Ctrl_Receive_IT progress.          I set I3C of my H563 as master and sent ENTDAA and master read , the slave answered both command. The interrupt of slave reflects that master read is done and the data in tx-fifo is transferred correctly. But when i read RxBuffer of the HAL_I3C_Ctrl_Receive_IT i find nothing but 0.          Can anybody help me?Thanks!

Hello,I have configured a DMA channel to perform a memory-to-memory transfer triggered by EXTI. I would like to automatically re-arm channel at the end of every completed transfer so that it is ready to process the next EXTI trigger event without any CPU intervention. What are the possible avenues to achieve this goal?Thank you very much for your assistance,P-M

I currently have a BLUENRG-M2SP connected via SWD to my STLink-V3PWR.The issue is while my flasher can connect to the device it then cannot read the bootloader sector or flash the address memory.Here is the log:16:34:35.247: Waiting device to read bootloader (device connected by ST-Link) ->Device Connected16:34:35.437: Device Identification -> BlueNRG-216:34:35.620: Read Bootloader Sector -> FAILED16:34:36.038: Device Disconnection -> SUCCESSMy set up is:PSU supplying the board with 3V9.STLink-V3PWRBLUENRG-M2SPFour wires connected from the board to the programmerSWDIOSWCLKVinGndIn addition to this, I also have the boot pin connected to another PSU that would supply it with 3V6. I heard/read via the datasheet that at times it is neccessary to force the boot pin high. This forces the chip to go into the bootloader and ensuring that the SWD debug pins are open for connection.So I have three questions.Any insight as to why I would be able to establish a connection but not

MCU : STM32F411CEU6 Hello everyone. I have an application in which I want to get image end address from linker. Here is a full context of what I want to do, I have a struct living in start of my image, which basically tells the bootloader usefull info, if bootloader want to inspect the image, the struct looks like this (BTW this struct is not yet implemented and this feature I made for when working with TI CC series so I am trying to replicate it for STM as well)  const imgHdr_t _imgHdr __attribute__((section( ".image_header"))) = { .imgID = OAD_IMG_ID_VAL, .crc32 = DEFAULT_CRC, .imgCpStat = DEFAULT_STATE, //!< Image copy status bytes */ .crcStat = DEFAULT_STATE, //!< CRC status */ .imgNo = 0x1, //!< Image number of 'image type' */ .imgVld = 0xFFFFFFFF, //!< In indicates if the current image in valid 0xff - valid, 0x00 invalid image */ .len = INVALID_LEN, //!< Image length in bytes. */ .softVer = SOFTWARE_VER, //!< Software version of the i

I'm trying to see what's possible in terms of a bootloader in a custom application of an stm32f722. We have an external 2-megabyte flash chip on the QSPI bus, along with the internal 512-kilobyte flash.  I'd like to make the bootloader stored on internal flash as tiny as possible; the best way to do this is to make it evaluate the image stored on internal flash as well as external, and simply jump to whichever one passes this evaluation.  I'd then put the code to handle USB DFU mode, SPI download mode, UART download mode, etc., all on the external flash, and run it from there only if needed. This requires being able to write that code into the external flash using SWD (further upgrades can be done over any of the protocols above, but for the first time we need to use SWD as the code isn't on the device yet to do the other protocols).  What I can't tell is whether the SWD implementation on this chip allows writes to flash chips mapped on the external QSPI bus --

Hi,I have read datasheet of STM32F103VCT6, it does not mention anything about code read out protection. Does STM32F103VCT6 has this function? (a security function to protect STM32F103VCT6 from reverse engineering)Thank youDavid Kean 

We managed to successfully run TFM_SBSFU example for the IOT02A board. We are using latest STM32Cube_FW_U5_V1.2.0.The problem is that we do not have access to PSRAM from NonSecure application when in memory mapped mode.We implemented PSRAM init by importing drivers from BSP package into TFM Example, and initializing PSRAM imidiately in main, adter COM_Init(). For the test, we tried without changing GTZC_TZSC_MPCWM and SAU registers from secure app.As expected, we are getting Secure Failed handler, with the information that we tried to access protected memory. All as expected.Than we implemented memory area unprotection in TFM_Appli_Secure, by adding next line of codes in function:fih_int sau_and_idau_cfg(void) { . . . . for (i = 0; i < ARRAY_SIZE(sau_init_cfg); i++) { SAU->RNR = sau_init_cfg[i].RNR; SAU->RBAR = sau_init_cfg[i].RBAR & SAU_RBAR_BADDR_Msk; SAU->RLAR = (sau_init_cfg[i].RLAR & SAU_RLAR_LADDR_Msk) | (sau_init_cfg[i].nsc ? SAU_RLAR_NSC_Msk : 0U) |

Hello.My STM32CubeMX version is 6.12, and I have chosen to create the project through the CMake toolchain.But when I make the project directly, I encounter the problem that target CPU does not support ARM mode. How can I solve it?I didn't change anything in CMakeLists.txt 

Good afternoon everybody,I bought an STM32H747I-DISCO, and installed the TouchGFX demo software.When I turned on the board, the demonstration ran perfectly on the LCD display, but after a few seconds, the images on the display started to show problems, as shown in the photos.If I disconnect and connect the USB cable, the problem continues, but if I disconnect and wait a few minutes, and turn it on again, the display starts perfectly and after a few seconds the problem appears again.I'm using St-Link v3 USB power.Has anyone had this problem?Thanks! 

Hi, We are using 54AC164245 device for our onboard application. We have connected VDD1 as 5V and Vdd2 as 3.3V. As per datasheet the side A side max input voltage allowed is <=Vdd2. In the case when the device will be in disable condition (Isolation) and also direction of the device will be side B to side A (so the device A side is configured as output and the device is in isolation state), can 5V signal connected to side A cause any harm to the long term reliability of the device?

Hello community,I'm looking for materials to learn STM8S programming.I searched on the internet but I couldn't find anything. Can you recommend me any documents or links to learn, please?Thank you all!