Solved

after extract the zip file to the shortage path C:\st2\STSW_STUSB010_v1.3\Projects\STM32F072RB-Nucleo\Appli\usbpd\STM32F072_MB1303_DRP_2PORTSthen import the example with STM32CubeIDE. Then compile result was"Build Failed. 34 errors, 3 warnings. (took 16s.325ms)"not sure how to config the project to make it successful compile?Can anyone help me?Here is the compile result

Hello everyone,I write HAL_Delay(1000) or HAL_Delay(5000) on my code but it delays it by half. I checked SystickTimer it works fine. But HAL_Delay function gives me half delay time. I created another project with same board, same Cubemx features , it works fine.Where should i check at my code to find what's wrong with it (at debug mode)?

I am currently experimenting on stm32l562e-dk board, and I discovered that, in the secure world, non-secure flash cannot be read via a secure memory region (i.e. not covered by any of the SAU regions). To be specific, value of zero is read.I am wondering whether this behavior is architecturally specified or just STM32-specific.Thanks

A couple of questions.First there seems to be some conflicting comments. In the vl53l5cx_plugin_detection_thresholds.h file there is the following statement in regard to the mathematical operators for multiple checkers. "Please note that the first checker MUST always be a OR operation." Then in the file Example_9_detection_thresholds.c there is the statement " Please note that the first one must always be set with a mathematic_operation VL53L5CX_OPERATION_NONE." I've tried the example with both OR and NONE and it works either way.The seconds question is I can't seem to get the AND operation to work. I want it trigger when the distance is between 200 and 400 mm AND the SIGNAL_PER_SPAD_KCPS > 10. When I use the VL53L5CX_OPERATION_AND operator it never triggers. If I change it to look for VL53L5CX_TARGET_STATUS == 5 instead of VL53L5CX_SIGNAL_PER_SPAD_KCPS > 10 then it triggers, but none of the zones have a distance between 200 and 400 mm. Looks like it is triggering when the d

Hi,I am trying to implement the BLE OTA firmware upgrade to an existing BLE project. However before I have even looked at integrating the functionality to an existing project I am focusing on the example projects.So first up I have successfully used the BLE_Ota and from this via the ST BLE android app have been able to upload the BLE_Heart_ota binary file to the nucleo board, everything works as expected.From this I move to the second part of work and this is to use the non_OTA BLE_Heartrate example and give it the OTA functionality. The steps to do this should be (I believe)- Replace the linker file STM32WB55RGVX_FLASH.Id, this is editing the flash address (0x08007000) and adding in the OTA region (magic key related) of the two sections TAG_OTA_START and TAG_OTA_END ).- Remove the update of SCB->VTOR in the file system_stm32wbxx.c - set BLE_CFG_OTA_REBOOT_CHAR to 1 in ble_conf.hWhen I make these changes to the default BLE heartrate application and upload the hex file (I am getting

It looks like STM32L496xx.h does not have the hash peripheral definitions in it. e.g. The STM32Cube_FW_L4_V1.16.0 examples for STM32L496 HASH peripheral are all configured to use the STM32L4A6xx. Does ST have a plan to update STM32L496xx.h?, or Is it ST's accepted solution to define the L496 MCU as STM32L4A6xx?

Hi all,I have been working on a Nucleo 68 board to develop firmware for my project. I have been working in parallel on two projects - one was purely hardware control - read/write to/from various peripheral devices (UART with IT and I2C DMA and External Interrupts). I am very happy with that side and it works perfectly. The other project was pure BLE application, which I have now written and on its own it works perfectly. It is a BLE client that simply gets the data out of a peripheral sensor.I am however now stuck trying to combine the two projects together. I have seen a similar post https://community.st.com/s/question/0D53W00000dOycq/integration-of-an-existing-project-into-the-sequencer-utilseq however it did not solve the issue. And actually in that post @Christophe Arnal​ suggests that interrput handlers should remain unaffected by the addition of the sequencer into the project.These are my observations:1/ Both projects on their own work perfectly - the same configuration file

Looking at the STM32H753xI datasheet, I'm curious to better understand the meaning of the cited "max" power consumption for each condition. Hoping to design a power subsystem that will provide sufficient current to give the STM32H753 its full range of performance. Based on this table, I'm predicting that a dedicated 1.8V power line with peak current of 600mA will be sufficient for most applications as long as the junction temperature is kept below 105C. I am also assuming 600mA is a reasonable maximum due to the absolute maximum 620mA input current to all Vdd pins on the H753. Are these assumptions correct? Does the maximum rating describe peak power during the test?Thank you!

I'd like to develop USB host application with Audio and/or Video class.Is there any working example project or code snippet?I checked STM32 HCD driver file - -ux_hcd_stam32_periodic_schedule.c, but it always generates EP_TYPE_INTR packet. How can I send audio/video ISOC packets?Regards,

I tried to program the demo .hex file into a B-U585I-IOT02A by STM32CubeProg, and got this:https://ibb.co/GJ1mHqnIt was prompted, there was flash protection, how to remove it?

I was trying to upgrade the FUS and wireless stack version on my STM32WB55 Nucleo board via ST-LINK using STM32CUBE Programmer GUI tool when I came to this issue. I first managed to delete the wireless stack by clicking on "Firmware Upgrade Service -> Firmware Delete" and it was successful.After that, I tried performing a FUS upgrade with "stm32wb5x_FUS_fw_for_fus_0_5_3.bin", as acquired from Release .12.1: STM32CubeWB/Projects/STM32WB_Copro_Wireless_Binaries/STM32WB5x at master · STMicroelectronics/STM32CubeWB · GitHub. However, it failed and gave me the following error information:16:11:30 : Old Firmware delete ...   16:11:30 : Warning: Option Byte: nSWboot0, value: 0x0, was not modified.   16:11:30 : Warning: Option Byte: nboot0, value: 0x1, was not modified.   16:11:30 : Warning: Option Byte: nboot1, value: 0x1, was not modified.   16:11:30 : Warning: Option Bytes are unchanged, Data won't be downloaded   16:11:30 : Succeeded to set nSWboot0=0 nboot1=1 n

Hello, I am working with a costumer board using STM32F105. There are some LED drivers working I2C1 and I2c2. Configuration for serial interfaces is:void MX_I2C1_Init(void){ /* USER CODE BEGIN I2C1_Init 0 */ /* USER CODE END I2C1_Init 0 */ /* USER CODE BEGIN I2C1_Init 1 */ /* USER CODE END I2C1_Init 1 */ hi2c1.Instance = I2C1; hi2c1.Init.ClockSpeed = 100000; hi2c1.Init.DutyCycle = I2C_DUTYCYCLE_2; hi2c1.Init.OwnAddress1 = 0; hi2c1.Init.AddressingMode = I2C_ADDRESSINGMODE_7BIT; hi2c1.Init.DualAddressMode = I2C_DUALADDRESS_DISABLE; hi2c1.Init.OwnAddress2 = 0; hi2c1.Init.GeneralCallMode = I2C_GENERALCALL_DISABLE; hi2c1.Init.NoStretchMode = I2C_NOSTRETCH_DISABLE; if (HAL_I2C_Init(&hi2c1) != HAL_OK) {  Error_Handler(); } /* USER CODE BEGIN I2C1_Init 2 */ /* USER CODE END I2C1_Init 2 */}/* I2C2 init function */void MX_I2C2_Init(void){ /* USER CODE BEGIN I2C2_Init 0 */ /* USER CODE

Hi all,I am trying assign DMA to USART3 channel on STM32MP1.I assigned it appropriately in the CubeMX but it looks like it was not able to auto-generate any code regarding the DMA assignment to the USART3.The device-tree bindings look pretty confusing to me. How can I assign it correctly? I checked option use MDMA in the CubeMX and I can see a mdma block generated which is empty. So any directions on how to assign dma to USART3 will be really helpful and appreicated.Thanks.

HiIn my application we need to read the last rest status, whether its a POR or WDOG      ret = ioctl(wdog, WDIOC_GETBOOTSTATUS, &status);looks like this support is not available in drivers/watchdog/stm32_iwdg.ccan anyone tell me how add a patch in stm32mp1 board ?

Hello,I am using the X-NUCLEO-NFC06A1 board to test the NFC functions, and to develop our prototyp NFC reader. I write the Firmware with other micro controller, and find it is really difficult to understand the ST25 Embeeded NFC library (STSW-ST25R16_v1.3.0). The codes are complicate and are not possible to use in my controller. So read some other Q&A and try to use direct commands and set the registers and to realize the NFC read and write. The following is the current code. ST25R3916 can read and transmit some bytes, because the main interrupt register shows start of receive, end of receive and end of transmission. But it can only receive 2 Bytes like 0x0008.  My question is How can I read the UID and complete data of tag? and how to write data to the tag correctly. Can anyone give a help? Thank you very much.ST25R3916_Init(void){ ST25R3916_Set_CMD(0xC1);//Set default ST25R3916_Set_CMD(0xDF);//Measure power supply ST25R3916_Set_Register(0x00,0x07);//Diffe

 Whether there is a bare - machine routine for MP1?

we need to blink led for our command we are using stevalmks1v1b box

Hi all, I'm developing our application which requires high speed SPI. Currently I'm using the Nucleo-G070 for development and my peripheral device is connected to the Nucleo SPI pins with 6" jumper wires.I was trying to see what clock the peripheral can handle and ran into some issues. At 4MHz, we have a nice clean square wave. At 8MHz, it's pretty much a sine wave but it still works fine. At 16MHz the amplitude of the sine wave is 1/2 of what it was and is shifted up by about 1V.Now I know my setup with fly wires is definitely not ideal. But I noticed that even when I disconnected everything from the Nucleo and just probed the header, the SPI clock still looked the same. Does this mean it's just not possible to use SPI that fast with the Nucleo? Is this because the layout wasn't done with high frequency applications in mind? Are there any other mitigations?

..

Hello Community,I want to port my project which is using ThreadX v2.1 to either STM32L4 or STM32F4. For that I tried to find the example code for the above MCUs. But, could not find any example for the ThreadX. However I came to know that H4 and L4 series do support ThreadX.Please let me know, From where I can find the sample example project.Thanks,Hiren Bhuva

I am having trouble trying to output data via USART1 on my STM32H7B3I-DK. According to the doc (UM2569), USART1 is a virtual com port connected to the USB STLINK (CN14). So I should theoretically be able to use USART1 to output to my serial console via the Mirco-USB connected to my laptop? But for some reason my serial console isn't outputting anything at all. I have already checked that the settings for USART1 in STM32CubeMX and serial console match, so I am assuming it has nothing to do with my serial console's settings. Here is a code snippet of my main loop and USART1. The code was essentially generated by STM32CubeMX after I selected the correct discovery board in 'board selector'.int main(void) { /* USER CODE BEGIN 1 */   /* USER CODE END 1 */   /* MCU Configuration--------------------------------------------------------*/   /* Reset of all peripherals, Initializes the Flash interface and the Systick. */ HAL_Init();   /* USER CODE BEGIN Init */   /

Hi !I'm used to working with F4 and F7 devices, and I've always made '.bin' files to distribute the firmware upgrades, which can be flashed via a custom bootloader, directly on the board, from an SD card.With my current project however, on a STM32H743BI, the generated '.bin' file is almost 700MiB in size!My two questions are:How come this is so big ? Does this have to do with the H7 memory mapping ?What reasonable options do I have ? Can '.hex' files be as easily read and written to FLASH memory ? Should I rather generate several '.bin' files to split sections ?Here's my linkerscript for reference:ENTRY(Reset_Handler) STACK_SIZE = 0x8000;   /* Non cacheable RAM for DMA This can be adjusted as needed */ DMA_RAM_SIZE = 32k; MIN_HEAP_SIZE = 0x2000; /* required amount of heap */ BOOTLOADER_SIZE = 256k; FLASH_ORIGIN = 0x08000000;   /* Specify the memory areas */ MEMORY { bootloader (rx) : ORIGIN = FLASH_ORIGIN, LENGTH = BOOTLOADER_SIZE FLASH (rx) : ORIGIN = FLASH_ORIGIN + BOOTLOA

Going over the application notes, I see that VCC provides many option but with minimum of 8V (default). I need 5V to supply my encoder and the line driver.Should I just use a voltage divider to VCC and get my 5V out of it? Sorry if I am answering my own question, but I want to make sure. Should I also filter the power with capacitors? Any suggestions will be appreciated.

hi i have a problem with the F103 the adc reading is jumpy and all over the place too much noise while reading i tried to filter it by summing some and deviding by it but its still jumpy

Hello,I'm testing the SPI peripheral through a simple PDM mic. The problem is the SPI doesn't start at all. The CSTART bit (that is the one that start the transfer) remain cleared, even right after I SET the bit.Now, I noticed that just after I've done the SET_BIT in the SR register happen to be set the EOT bit which indicate the (End Of Transfer). The problem is that I didn't get any data, nor in the buffer and nor in the registers.I thought the problem could be the transfer do start, but it is stopped immediately by the rise of the EOT.Didn't know If I am right, and more I didn't know how to solve the problem.Thanks for all your help guys.