Solved

When I'm using TOUCHGFX and FATFS together, I can create/write/read a file in my SD only if I do it before "MX_TouchGFX_Init();"f_mount(&SDFatFS, (TCHAR const*)SDPath, 0);f_open(&SDFile, "DIO.TXT", FA_CREATE_ALWAYS | FA_WRITE); //with TGFX this one gets FR_DISK_ERRf_write(&SDFile, wtext, sizeof(wtext), (void *)&byteswritten);f_close(&SDFile);f_mount(NULL, (TCHAR const*)SDPath, 0);Not sure if this can be helpfull but the only difference I notice it's that when I debugging:If there is MX_TouchGFX_Init();, after f_mount(), FatFs gets the value : 0x2000a6a4 <SDFatFs>In other case, FatFs is equal to the value : 0x2000a2fc <SDFatFs> Do you know if there is something I can do to make them working well after with the graphic application?Thank youEDIT: I resolve it. I suppose because MX_TouchGFX_Init() is written in C++ inside that the FATFS methods could not be read in C so I put it inside a task and it works!!! 

Hi everyone,I am trying to create a windows pc app to talk to the STM32WB board using the dongle.I want to run some scripts, e.g., write to characteristic, connect, read an etc.I saw that STM32CubeMonitor-RF can already run scripts via some text files. I wonder if it is possible to run the script text file from the CLI, or better talk to the dongle via some sort of .dll interface.  The second would the preferable way .Thanks

Hello everyone.When setup a fresh setup with fresh Ubuntu 20.04 Desktop or Windows 10 Pro and fresh STM32 CubeMonitor 1.3.0 or even 1.4.0, the Manage Palette is not availabe at STM32 CubeMonitor Editor.As workaround, install node-red with NPM and NodeJS according to NODE-RED website, fix this issue.This is an expected behaviour or I'm missing something during STM32 CubeMonitor installation? 

The impact of log4j vulnerabilities CVE-2021-44228 and CVE-2021-45046 for STM32Cube tools has been assessed by the development team, and the tools can be used without risk.STM32CubeMX,STM32CubeIDE,ST-MCU-FINDER-PC The log4j version used is not impacted by CVE-2021-44228No risk of remote code execution using CVE-2021-44228STM32CubeMonitor-RF, STM32CubeMonitor-UCPD, STM32CubeMonitor-PWR The log4j version is impacted by the CVE-2021-44228 (log4j version 2.8.1)There is no internet and no remote access for this tools, so attacker would have to be logged on the computer and need to have access to tool GUI to inject data in log4j. No risk of remote code execution using CVE-2021-44228STM32CubeProgrammer,STM32CubeMonitor :log4j is not used for this toolsNo risk of remote code execution using CVE-2021-44228

Console displays error [warn] OS priority setting: SystemError [ERR_SYSTEM_ERROR]: A system error occurred: uv_os_setpriority returned EACCES (permission denied)Within the application these errors occur hen pushing start:Bad parameter (7)Bad parameter (7): startWhen run with sudo, error does not appear and monitor works as it shouldUbuntu 21.04 installed from deb file

{  "variablelist": [    {      "address":"0x200004a0",      "type":4,      "value": "{{payload}}"    }  ],  "accesspoint":0}

i had used used cubemx 5.5 and in 'System Core' => 'SYS' configurated the 'Time Source' as TIM7 and enabled the option 'Enable Full Assert'On running the project a had an assert that fails over the Preempt Priority value for the timer (TIM7)The PreemptPriority value for the HAL_NVIC_SetPriority variate from 0-15, but when the HAL_RCC_ClockConfig function is called is this value 16. (max 4 bits long) .The reason comes from the File STM32F4xx_hal.c where uwTickPrio is defined as follow:uint32_t uwTickPrio  = (1UL << __NVIC_PRIO_BITS); /* Invalid PRIO */In main.c with the function HAL_Init() is the PreemptPrioity value correct but with the SystemClock_Config() function is the PreemptPrioity value overridden by the uwTickPrio  value.The issue comes from the WEAK function HAL_InitTick in the weak function is the uwTickPrio  initialized, but the HAL_InitTick is overridden in the stm32f4xx_hal_timebase_tim.cSo the only possible solution i had found is to

Hello, I'm using the demoboard B-U585I-IOT02A with a STM32U5 microcontroller. Today, I'm using a RTC with an external battery placed before VBAT. But in order to reduce current consumption, I'm currently working on using shutdown mode in order to just update RTC without using CPU.My question is the following : If I lose power for Vdd, so only remains Vbat for the RTC (based on the external battery), does the microcontroller go into shutdown mode automatically? Or do I have to do it manually by detecting a power failure just before losing power for the CPU ?Thanks in advance,

I'm working on an iOS app that can read and write to st25 type 5 tags . While writing, i am able to write only 4 blocks at a time using writeMultipleBlocks() method. NFCError occurs if I write more than that.mISO16593Tag.writeMultipleBlocks(requestFlags: [.address,.highDataRate], blockRange: blockRange, dataBlocks: dataBlock){error in      if let error = error as? NFCReaderError {        print("\(error.localizedDescription)")      }      else{        print("write successfull")      }       self.semaphoreFunctionSignal()    }I tried using stm's NFCTap App, it is also giving me an 'invalid response error' if I write more than 4 blocks of data.Can someone help to me to understand why this is happening in iOS. The writing works perfectly f

I found this deceder STA020DJTR and I would like to know if it is possible to replace.

I have working code for an STM32L0 device that uses Alarm A of the RTC to wake / interrupt at the desired minute interval. I now require the ability to wake / interrupt at the desired hours AND minutes time. Previously all masks were masked except for the Alarm A minutes mask. Now all masks except for the Alarm A minutes AND hours masks are masked. I believe it should work as before only now the alarm needs to see a matching hours AND minutes value in order to cause the interrup. Is my understanding correct ? So, for example, if the current time is 0 hrs and 0 minutes and I set AlarmTime.Hours = 1 and AlarmTime.Minutes = 1 then I would expect a single interrupt 61 minutes from now.

Hello ~I'm studying IWDG concept. (STM32F769-EVAl)First picture is the block diagram of IWDG at reference mannuals (stm32f76xxx, stm32f77xxx). Second picture is IWDG parameter setting using Cube MX. Window register doesn't exist in block diagram. Is this wrong? If Window register enable in IWDG, is this the same system WWDG???Thank you, any help might be useful.

Hello,there are so many topics out there about "stuff not working after CubeMX / CubeIDE update", so I wonder how that could impact my "workflow".I'm using CubeMX only as a starting point, and as soon as I have some basic stuff running (usually UART for debugging), I won't use CubeMX again. Except, I sometimes add peripherals by using CubeMX only with a new project and the same setup as the existing one, so my existing source will not be overwritten, as I don't like that /* USER CODE BEGIN / END */ stuff (and I'm a little bit psychic about the ugly indentation...).That said, updating CubeMX should not be a problem for me.But what about updating CubeIDE ?Would that somehow change my project's source files when I'm using HAL stuff (I replaced a lot with direct register access, but some stuff is not that important - or I was too lazy to replace) ?Or would a CubeIDE update only affect projects that were created with the CubeMX from "within" CubeIDE ? Which I hope is like that...

Dear Sir I'm getting start ST25R3916-EMVCO . and i would like to know EVK can support TFT .

We're using STM32 MCSDK to control a high torque BLDC motor. The motor is equiped with hall sensors. Due to high torque at startup, we start the motor in torque mode. When running, we would need the speed control mode.But if we change the control mode on-the-fly from torque mode to speed mode (when reaching a certain speed), the motor stops immediately after executing MC_ProgramTorqueRampMotor1() and ramps up from zero speed.Furthermore: how can I switch from HALL sensor mode (main sensor) to sensorless obserer (auxiliary sensor) on-the-fly?Any help/hints/tips are welcome :)

I've been testing the internal temperature sensor on STM32 Nucleo-L452RE.Therefore, I am using the internal Macors as well as a self-build function to calculate the temperature. Both yield the same value, thus the same constant negative offset of roughly -6°C.The offset appears over the whole temperature range of -40°C to 85°C. I have verified the temperature set in the climate chamber with several other sensors. I have checked everything I can think of. Maybe some of you can find the mistake I keep making in my code, which explains the strange behaviour.Thank you in advance!Best regards,Jan#include "main.h" #include <stdio.h> #include <stdlib.h>   ADC_HandleTypeDef hadc1; UART_HandleTypeDef huart2;   void SystemClock_Config(void);   static void MX_GPIO_Init(void);   static void MX_USART2_UART_Init(void);   static void MX_ADC1_Init(void);   #define TEMP_CAL2 110  #define TEMP_CAL1 30  #define TS_CAL1 ((uint16_t*) (0x1FFF75A8UL)) #d

HiI'm using the Random Number Generator in interrupt mode and am getting HAL_RNG_ERROR_SEED errors. I'm not getting clock errors. I use HAL to drive the rng.The errors are quite infrequent, I don't have stats but probably 1 in 100000.Are these errors to be expected or am I potentially doing something wrong?I am running the CPU at 280 MHz. The clock settings are implemented by HAL and I haven't changed these.The problem I have is that to clear the error you have to restart the rng which take up to 200 ms.The entropy of the numbers isn't critical in my app as I'm only using the rng to purterbate test data around a mean. So I am thinking that I could just let the rng run without resetting it.RegardsRob

I've followed all the steps from:https://wiki.st.com/stm32mpu/wiki/STM32MP15_Discovery_kits_-_Starter_Packagehttps://wiki.st.com/stm32mpu/wiki/PC_prerequisiteshttps://wiki.st.com/stm32mpu/wiki/STM32MP1_Distribution_PackageCreating openstlinux-5.10-dunfell-mp1-21-03-31 distribution installation,with bitbake st-image-weston, error rises:(..layers/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-extended/mozjs/mozjs_60.9.0.bb:do_compile) failed with exit code '1'Tried:bitbake -b mozjs -D -f bitbake mozjs -c cleanall bitbake mozjs -c compilebut the same error occurs.Also tried these solutions from the forum, without any success (the error is the same):mozjs60.9.0.bb returens error while compile (st.com)mozjs_60.9.0.bb:do_compile failed with exit code '1 (st.com) This is my 3rd attempt with a fresh Virtual Machine (Ubuntu 20.04.2.0 LTS), i'm pretty sure I've followed all the steps.For the Virtual Machine I have the following specs:Cores: 6Ram: 4.5GBDisk Space: 300

I am using HAL_I2C_Slave_Receive_DMA() function and am putting flags in each of the Callbacks which I have redefined in my code from the weak ones in stm32g0xx_hal_i2c.c. I have also tried putting breakpoints in the callback functions to see if it foes there. There is no indication that it is.My HAL_UART_Transmit_DMA() function is working. And it is calling the HAL_UART_TxCpltCallback(UART_HandleTypeDef *huart) function. So I know interrupts are turned on. I did not have to enable anything in the interrupts the HAL took care of that. I went into stm32g0xx_hal_conf.c and modified the line #define USE_HAL_I2C_REGISTER_CALLBACKS  1uSo it used all the callbacks. Looking at the hi2c1 structure, there are valid addresses in each of the callback pointers. Right now I cannot verify whether they are using the default weak ones or mine. But according to the documentation if I define them they should override the weak ones. When I use the HAL_I2C_Mem_Write_DMA() in the master STM32G031K

The readme.txt file for BLE_HeartRate_ota contains the following:@note This application is not supported by CubeMx but has been copied from the project BLE_HeartRate generated by CubeMx with some modifications in order to be able to download it with the BLE_Ota application. The steps to be done to move from the BLE_HeartRate application to the BLE_HeartRate_ota application are : - Copy the full folder BLE_HeartRate - Replace the linker file stm32wb55xx_flash_cm4.icf by stm32wb55xx_flash_cm4_ota.icf ( this adds the placement of the two sections TAG_OTA_START and TAG_OTA_END ). - Remove the update of SCB->VTOR in the file system_stm32wbxx.c ( The VTOR is already set by the BLE_Ota application and shall not be changed to a different value) - set BLE_CFG_OTA_REBOOT_CHAR to 1 in ble_conf.hHowever, comparing the two source directories I see many more differences and find it difficult to identify and merge all of the required modifications. BLE_HeartRate_ota does not appear t

arm-none-eabi-gcc -o "Uart_Ring_Buffer.elf" @"objects.list"  -mcpu=cortex-m4 -T"C:\Users\User\STM32CubeIDE\workspace_1.8.0\Uart_Ring_Buffer\STM32F429ZITX_FLASH.ld" --specs=nosys.specs -Wl,-Map="Uart_Ring_Buffer.map" -Wl,--gc-sections -static --specs=nano.specs -mfpu=fpv4-sp-d16 -mfloat-abi=hard -mthumb -Wl,--start-group -lc -lm -Wl,--end-groupc:\st\stm32cubeide_1.8.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.10.3-2021.10.win32_1.0.0.202111181127\tools\arm-none-eabi\bin\ld.exe: ./Core/Src/main.o:C:/Users/User/STM32CubeIDE/workspace_1.8.0/Uart_Ring_Buffer/Debug/../Core/Src/main.c:50: multiple definition of `huart2'; ./Core/Src/UartRingbuffer.o:C:/Users/User/STM32CubeIDE/workspace_1.8.0/Uart_Ring_Buffer/Debug/../Core/Src/UartRingbuffer.c:15: first defined herecollect2.exe: error: ld returned 1 exit statusmake: *** [makefile:64: Uart_Ring_Buffer.elf] Error 1"make -j8 all" terminated with exit code 2. Build might be incomplete.

I would like to develop a battery-less NFC strain sensor using an ST25 chip using mobile phone to read.Similar to this video: https://www.youtube.com/watch?v=C3YMzW_v8SsWhat components/hardware/software that I need to buy?Thanks and Regards,

..

..