Solved

Hi to all,I managed to interface with the SD card through the SPI and the FaTFS library (thanks to https://01001000.xyz/2020-08-09-Tutorial-STM32CubeIDE-SD-card/) now I need to implement a USB mass storage device on the same hardware.i don't know how to modify usbd_stoge_if.c tin odero implement the functions:int8_t STORAGE_GetCapacity_FS(uint8_t lun, uint32_t *block_num, uint16_t *block_size)int8_t STORAGE_IsReady_FS(uint8_t lun)Have you any suggestions?Thanks.

Hello everyone. For some days I have been trying to solve a problem that occurs in CubeMX when generating the code for STM32CubeIDE. I state the following:1) The error occurs both when starting from a new project (from STM32CubeMX or STM32CubeIDE) and when importing an already made one.2) The error occurs only with the generation of the code for STM32CubeIDE, while with all the other IDEs the procedure is successful.3) The error occurs with the two attached pop-ups4) The Driver folder is generated incompletely and no Middleware and STM32CubeIDE projects are generated.Finally, just to complicate things:5) The error occurs on systems based on OpenSUSE Leap 15.3.6) The error does not occur on an Ubuntu 20.4.4 LTS machine.Some idea? Has anyone experienced the same problem?Greetings

As noted by @Community member​ in https://community.st.com/s/question/0D53W00001yEbUsSAK/stm32f7-eth-tcp-checksum-offload-fails :there's a documentation error in RM0410 which says CIC bits are 28..27 in [TDES1], page 1785Besides this, CIC bits are not in TDES1 but in TDES0, so that's second typo in the same sentence.I checked not just RM0410 rev.4, but also RM0090 rev.19, and it contains exactly the same two typos, so it will probably go across all RMs containing the ETH chapter.JW

I have a question about the value of `TICK_INT_PRIORITY` in a project for the STM32G070CBT6. I am not using FreeRTOS (which I think makes a difference here), and all projects have been created with the (default) `Targeted Language`: `C`, `Targeted Binary Type`: `Executable` and `Targeted Project Type`: `STM32Cube` options selected.I was trying to change the MCU used for a project from using an STM32G030C8T6, and couldn't find a way to do that without starting with a new project and bringing the older code into it. But between making the original STM32G030C8T6-based project and the new STM32G070CBT6-based one, I've gone through several changes in the STM32CubeIDE, too (and the old version has been migrated through these from the version it was originally created in).Something I noticed, as I was comparing files to make sure I'd moved all of the code and settings across), was that the value set for `TICK_INT_PRIORITY` in a `#define`, in file `stm32g0xx_hal_conf.h`, was `3U` in the new pr

I am aware there is a datasheet, but it does not contain the info I need. I am trying to configure timer triggered timers for my project, so I would like to know the internal trigger mapping for each timer. I am hoping to find something similar to the image below from the STM32F446xx reference manual. Any help is appreciated.

Hi, on my board i`m running bootloader in internal flash of stm32h750 together with 2 QSPI NOR chips that store main program.Bootloader starts and jumps to main program in QSPI, howeverit get`s tricky when this function is called:SystemClock_Config();Inside of it we can see HAL_RCC_ClockConfig function that causes hard fault if FLASH_LATENCY is set to default value (4). By trial and error I`ve figured out that it works with values that are >= 7.void SystemClock_Config(void) { . . .   if (HAL_RCC_ClockConfig(&RCC_ClkInitStruct, FLASH_LATENCY_4) != HAL_OK) { Error_Handler(); } }Now the problem is that since HAL_RCC_ClockConfig function is autogenerated I would need to update this setting everytime I make some changes in .ioc file, setting it in user code won`t help because mentioned above function sets it back to default value.HAL_StatusTypeDef HAL_RCC_ClockConfig(RCC_ClkInitTypeDef *RCC_ClkInitStruct, uint32_t FLatency) { . . .   /* Increasing the CPU frequency */

Hello everyone. I have a question. I am using the stm32h723 processor in a project. I keep my image data in octoSPI external ram correctly. When I show OCTOSPI_BASE_ADRES to LTDC peripheral, the screen is distorted, but when I keep the same image in my flash memory, the image is fine. What would be the reason?.Could it be a sync problem between ltdc and octospi?

The data sheet for this family of parts mentions a Quad-SPI, butaccording to the datasheet the QFPN32 package does not appear to have QUADSPI_BK1_IO0 exposed to a pin (see picture). The Quad-SPI configuration in 1x/2x/4x IO mode all appear to require the IO0 signal. Is it possible to use Quad-SPI in this package?

..

I have a structure, that came from the hardware manufacturer for an encoder. The data is in most cases 16-bit words. Some times it is a 16-bit word with a bit field, sometimes it is a 32-bit variable and sometimes it is a 48-bit variable or a 64-bit variable. So I built the structure, it should be 44 16-bit words or 88 bytes. When I checked the size it was 100 bytes. That indicated it was inserting bytes in the structure. Fortunately there is such a thing as __packed attribute. I inserted the __packed attribute and I got warnings that the packed attribute was being ignored. Then I realized I had to say packed everywhere. So I put it everywhere I could think of, and I got no more warnings!Unfortunately that did nothing. The structure is still 100 bytes not 88 bytes.So I concentrated on the first place it gets off.Here is what the code looks like:typedef __packed union { uint8_t byte; __packed struct { uint8_t start_address:4; uint8_t end_address:4; }; } OEM_COMP_MEMORY_STRUCT; &

If I open cubemx using the terminal., I can find log messsge like: ThirdPartyUpdaterWithRetryManager:70 - Updater plugin not ready yet. [12/15]. Finally, cubemx reports IntegrityCheckThread:98 - exiting critical section [integrity check]. And It was stuck on the cover of cubemx.PS: I using Apple M1 Pro on macos 13.0.1 (22A400)

Looks like serious regression from 1.10.1. Steps to reproduce: Select STM32F401 or F411 MCU, Enable FreeRTOS. The generated main() function in main.c file does not contain the section creating the FreeRTOS objects (task, queues, etc.). Instead, the comment from the beginning of main.c is repeated where this section should be. CubeIDE 1.10.1 (also 1.9) with 1.27.0 F4 package generates the correct project.

..

Is there a Windows PC app that can read/write ST25DV04KC memory using a generic ISO15693 USB reader such as the Omnikey 5022? I've tried wakdev nfctools, it can see the tag but can't read memory. ST25PC-NFC uses an expensive Feig reader, I'm looking for a low cost solution for our field engineers.Many thanks

PM0056, Rev 6, page 105, Table 33. STM32 core peripheral register regions,Nested vectored interrupt controller;twice ?0xE000E100-0xE000E4EF Nested vectored interrupt controller0xE000EF00-0xE000EF03 Nested vectored interrupt controller 

Hiya, I'm a bit of an NFC newbie, looking for advice on which NFC Reader IC to use, ST25R3911B or ST25R95.We have a product that uses a ST25DV04KC tag for config data, and I'm designing a handheld tool for configuring these products. Pretty basic stuff, the tool will read and write the ST25DV04KC eeprom. However we're also hoping to do firmware updates of the target (product) micro via NFC, I guess using a bespoke bootloader in target, and ST25FTM library code. The tool's micro is STM32F412, target product STM32G030, sw dev using STM32CubeIDE etc.. Just wondering which reader chip will be the easiest to get up and running? I'm looking at the ST25R3911B just cos I have the X-NUCLEO-NFC05A1 board. But the ST25R95 looks simpler, cheaper and more widely available. STSW-ST25R-LIB appears to support both.Any advice gratefully received, I'm on a steep learning curve ;)

For everyday work I use ST-LINKs. Recently a customer gave me a JLINK for a board with a new QSPI flash chip, for this chip I could not find a ready external loader.Nevertheless the J-Flash software can program this chip, knowing only the the MCU and QSPI pins.It does this probably by decoding the built-in parameters table of the flash.Can CubeProgrammer do the same?Or is there already a smart QSPI flash programmer that works with ST-LINK?

Hi! I am working with STM32F722VET which has 3 i2cs in total. But in the HAL file \STM32F7xx_DFP\2.15.1\CMSIS\Driver\I2C_STM32F7xx.c there are function calls related to I2C4.For example, on line 1153: else /*(i2c->reg == I2C4)*/{ __HAL_RCC_I2C4_CLK_ENABLE(); }The __HAL_RCC_I2C4_CLK_ENABLE() macro is not defined in stm32f7xx_hal_rcc_ex.h so the project cannot be compiled.I'm using Keil with its device package manager and classic configuration (no cubeMX). Maybe I should include something to solve this problem?

Dear Sir,In st25r3916 datasheet, VDD and VDD_TX is not connected togather.But in X-NUCLEO-NFC06A1 circuit schematic, it seems that these twopins are connected togather, but there is a X sign in schematic as shownin attached figure. could you like to confirm this connection for us? VDD and VDD_TX should be connected or not for normal application?best regardsDai Sai

Reference manual RM0453 and AN5457 - Rev 2 give some info on optimal PA and TxParm settings but the data is incomplete and appears to be inconstant. For example, Table 2 of AN5457 says for RFO_HP, +14dBm set paDutyCycle to 0x2 and TxParms to 14. The ref manual Table 35 says for RFO_HP, +14dBmset PaDutyCycle to 0x02 and Txparms to 0x16 (dec 22)So do I set Txparms to 14 or 22?paDutyCycle for +15dBm RFO_LP are also inconsistent. The ref manual says 0x7 and the ap-note says 0x06.Further the tables are incomplete. For example, under HP only settings for output powers of 22,20,17,14 are provided. I tried to interpolate between values but had issues there. And guidance for power lower the 10 (LP) and 14 (HP) dBm are missing.Is there a document or guidance with more complete information? Which tables should I believe? The Reference manual or the Ap-Note? What settings should I use (for example) for LP at 5dBm or other powers below 10/14 dBm. Maybe for powers below a certain value just set paCo

Hi,i am using macOS to flash an STM32F411RE.It is recognized, the mass storage shows up, but whenever i try to flash it using ArduinoIDE, it exits with code 3: STM32F411RE not found.Does anyone know how to fix this?Thanks in advance.

I have 11 boards of our prototype with the STM32L4A6AGI6 (i.e. 169 BGA) assembled. 5 of them work fine. The other 6 eventually loose debugging connection. It doesn't happen immediatelly i.e. I'm still able to run a few lines of code but then it resets unrecoverable for the debug session (i.e. I have to restart the entire debug session. Soft reset doesn't work).I can also measure the NRST (Pin H3) line that is pulled down caused by any internal mechanism (Unhandled interrupt?).To investigate what line of code is causing the eventually occuring reset I started to place a "while(1);" and checked, if I still can pause and then run again without the debbugger loosing its connection.This lead me to the following code section:core_cm4.hSysTick->CTRL = SysTick_CTRL_CLKSOURCE_Msk |     SysTick_CTRL_TICKINT_Msk |     SysTick_CTRL_ENABLE_Msk;  Removing the "SysTick_CTRL_TICKINT_Msk" my "while(1);" after that line will continue to

NUCLEO-U575ZI-Q  is based on a STM32U575ZIT6Q in LQFP144 package. A diagram on page 98 of the datasheet shows PC5 (pin 45), PB12 (pin 73), and PC4(Pin 44). None of these I/Os are exposed on the connectors of the NUCLEO-U575ZI-Qhttps://www.st.com/resource/en/datasheet/stm32u575zi.pdfSchematic diagram of the NUCLEO-U575ZI-Q doesn't even show these three I/Os:https://www.st.com/resource/en/schematic_pack/mb1549-u575ziq-c03_schematic.pdfFurthermore, schematic of the NUCLEO-U575ZI-Q shows STM32U575ZIT6Q with several pins labeled incorrectly. For example, Pin 33 is labeled PA0, while the datasheet of the IC shows PA0 at pin 34. There are several problems like this.

Today I attempted to update ISM43362 WiFi module firmware on my new B-L475E-IOT01A board.I downloaded this firmware update utility, dedicated for my board from ST site and followed the steps in the README file. The process uses Cube Programmer CLI and has three stages:Programming the bootloader passthroughErasing the Inventek WiFi firmwareProgramming the Inventek WiFi firmwareThe first stage completed OK, but the second and the third stages failed.ISM 43362 WiFi module is no longer recognized.What is alarming is that at the second stage wrong Cortex core and ChipID is detected. See the attached scrsht. It seems like ST published the wrong bootloader, meant to be used for STM32F2xx MCU, instead STM32L4xx.Please help, I am screwed :\

We don't use PMIC so we remove vmmc-supply = <&v3v3>; in device tree.what should be in vmmc-supply if we connect SD_VDD constantly to 3.3V, no pmic? Many thanks