Solved

Hello,I want to integrate a secure boot and secure software update (SBSFU) on a nucleo H753ZI board.I downloaded the software from https://www.st.com/en/embedded-software/x-cube-sbsfu.html and followed the steps to compile the three programs (SECore, SBSFU and UserApp) proposed in the "projects" folder using the 1-image version of the SBSFU.The next step was to program the SBSFU application on the board which I tried to do using STM32CubeProgrammer. However, the program has not been completely installed. The first image below shows the device memory after the introduction of the application and the second image shows what should have been programmed. You can observe that the code abruptly stops after the address 0x08000100 while it should continue. I suspect that something went wrong when I prepared the board and that the region after 0x08000100 has been mistakenly let as an area protected against writing.My problem is that since this incomplete code has been inserted inside the b

I am working with IAR EWARM 9.10.1 and STM32CubeMX 6.2.1 on a NUCLEO-H743ZI2.To reproduce:Create NUCLEO-H743ZI2 project in STM32CubeMXGenerate itStart IARDownload to target (compile & flash succeed)Change something in IAR, e.g. add a source file to project tree.Save project.Download to target (compile & flash succeed)Go to STM32CubeMX and generate again.HERE my git tool shows the change from ST-LinkV3 to ST-LinkV2Go to IARDownload to target (will compile, but fail to flash, as it is now falsely set to ST-Link V2)STM32CubeMX generation falsely changes the EWARM/<projectname>.ewd file, when working with modified EWARM project files. <option>                    <name>CCSTLinkProbeList</name>                    <version>1</version>   &

I have successfully build st-image-weston using Distribution-Package.Now I want to add libmodbus to st-image-weston.I refer to the wiki page below.https://wiki.st.com/stm32mpu/wiki/How_to_integrate_an_external_software_package​1)​ ​I checked the libmodbus recipe in the path below.And I am using the meta-oe layer containing libmodbus.But I can't find libmodbus in the target.Why doesn't rootfs include libmodbus?layers/meta-openembedded/meta-oe/recipes-extended/libmodbus2)I tried to add libmodbus by executing the command below.The following error occurs.how to fix it?echo 'IMAGE_INSTALL_append += "libmodbus"' >> ../layers/meta-st/meta-st-openstlinux/recipes-st/images/st-image-weston.bbappendbitbake st-image-weston -c cleanall bitbake st-image-westonNOTE: Started PRServer with DBfile: /home/osboxes/STM32MPU_workspace/STM32MP15-Ecosystem-v3.0.0/Distribution-Package/openstlinux-5.10-dunfell-mp1-21-03-31/build-openstlinuxweston-stm32mp1/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 35363,

I followed the series of video "STM32WB Getting Started" with my P-Nucleo-WB55 board. During the 5th video "Heart Rate Monitor", I flashed the BLE_HeartRate project into my board and since this I have this message :"Target no device foundError in initializing ST-LINK device.Reason: No device found on target"I'm on Linux but I tried to do the same thing on Windows and the same error occured. I tried with an other P-Nucleo-WB55 board and I did the same manipulation and the same error occured. I let you screenshot of my errorsNow, I can't flash and run a new code on my two boards. What can I do to reset the Firmware of the board or to solve my problem whereas I can't flash any code on it ?Thank you

Question for the Hardware-wise ones:When probing canH and canL with my isulated oscilloscope i get the following signal:different voltage levels inside the same frame??!.Notice how the ACKs are always higher voltage alsoIt doesnt happen always but every time is just half frame 600mv difference No idea of what is going on, im using exclusively ifx1050gvio transceiver, the bus has its proper EOL and is about 3m long, populated with 4 nodes and a master.

Hi all,I'm developping an application under system workbench for STM32. The compilation works fine, but when it comes to the Linker I get the following output : 16:08:46 **** Incremental Build of configuration Release for project Firmware **** make all Building target: Firmware.elf Invoking: MCU GCC Linker arm-none-eabi-gcc -mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -specs=nosys.specs -specs=nano.specs -T"../STM32F412ZETx_FLASH.ld" -Wl,-Map=output.map -Wl,--gc-sections -o "Firmware.elf" @"objects.list" -lm Src/main.o: In function `main': D:\dev\AEL_FW\Firmware\Release/../Src/main.c:119: undefined reference to `MX_USB_DEVICE_Init' Src/stm32f4xx_it.o: In function `OTG_FS_IRQHandler': D:\dev\AEL_FW\Firmware\Release/../Src/stm32f4xx_it.c:282: undefined reference to `hpcd_USB_OTG_FS' collect2.exe: error: ld returned 1 exit status make: *** [Firmware.elf] Error 1 makefile:43: recipe for target 'Firmware.elf' failed   16:08:47 Build Finished (took 981ms)I've tried to tra

So I create a simple custom container containing just a box. Then I create 3 instances of this custom container in Screen1. I modify the custom container class to detect single click. But how to detect long press > 1s on any of these 3 containers?Attached is the partially done of the project, it is able to detect single click but not long press. Can someone give me some pointer or maybe complete the project?So the final objective is for function onLongPressHandler() in CustomContainer1 class called when there is long press.

I'm using an event to update indication statuses in my screen. There are four independent events that update the screen in the same fashion (with different images toggling for active/inactive). I added in another indication to show that when any of the events are registered it would indicate the 'global' status as well as the individual statuses.The individual statuses all indicate properly, and debugging shows the program is reaching every one successfully. However, in my global status, only the fourth event (zone4heatcallstatus) indicates the global indication.The code is identical (except numbers) for all. Any idea why this could be happening?void MainMenuView::setHeatCallTextStatus(uint8_t status) { if(status == 0) { textHeatCall_Active.setVisible(false); textHeatCall_Inactive.setVisible(true); textHeatCall_Active.invalidate(); textHeatCall_Inactive.invalidate(); } else { textHeatCall_Active.setVisible(true); textHeatCall_Inactive.setVisible(false); textHeatCall_

The HAL RTC initialization routines for the STM32F476 unconditionally reset the clock toJanuary 1, 2000. I have a battery backup for the clock and do not want the clock reset on initialization.Has anybody found a way to do this within the CubeMX framework?

I am going to use STM32G473 for my application. Most of peripheral interfaces need in 1.8v power (QSPI, I2C, GPIO, etc.) but i need in USB device functionality too.There is a requirement form data shhet (DS12712 Rev3 p174) to power USB tranciever from 3.3v. Does it mean that when I need in USB whole chip should be powered from 3.3v?

Hello Everyone, I have a STM32F401RE and the version of STM32IDE is 1.6 . I have been told that after naming a project, the STM32IDE pops a massage asking if want to set the peripherals into default mode. But for some reason my version NEVER shows me this question. What can I do? is there any other way to set the peripherals in default mode? thanks in advance.

I am trying to use the Eclipse Cube MX plug-in to create a project, generate code, write my application code and run and test it on my board.I have installed STM32CubeMX (v5.1.0) plug-in in Eclipse (v4.19.0).The STM32CubeMX is visible in my perspectives but I am unable to use it to create any projects using the tool. I have attached a screenshot of how the window looks when I open the CubeMX perspective. The "File" tab is missing. Have I missed anything during the installation or are there any versioning constraints that the MX tool is only compatible with certain versions of Eclipse?Looking forward to your support.

Hi ,I am using the STM32L072Cz LoRa discovery Board and I am doing the flash erase by using the HAL function "HAL_StatusTypeDef HAL_FLASHEx_Erase(FLASH_EraseInitTypeDef *pEraseInit, uint32_t *PageError)"I given the Start address 0x08000000 and No of pages to be erased to be 400 .then only page one has got erased and other pages didn't erased !!!for testing i have given random page address and No of pages to be 1,then this function has erased.please suggest me here why this function is not able to erase the more pages ???

..

Hi, I would prefer to use my segger jlink debugger with the discovery board io using stlink. I see there is an unpopulated header with 3V3 , SWCLK, GND, SWDIO on the left side of the board, and there is an NRST pin on the back connectors so I think i have all the signals I need for debugging. Will this work or will there be a problem with the integrating stlink debugger also interfering on these lines ?RegardsBram

I am using a custom board with STSPIN32F0A microcontroller. After assigning pins in the Motor control workbench, I am generating the code. Then I dump the code to the MCU by IDE.After that 12VReg starts.To test the motor, I go to Motor control Workbench--> Monitor section. Then I initiate UART communication and the device gets connected.But here the "Under Voltage fault always persists. Please check the image attached below."Note: I apply 12V input to run the Motor. Motor Used : Bull Running BR2804-1700kvPlease help me solve this problem. I have been stuck over here for more than 20 days.THank you Ritul Shah

Has anybody noticed this? Last activity time in old threads is updated and they raise up in "most recent activity" sorting order. For example this thread: what happened there on June 1 to update its activity time? 

Messieurs,I am using the ST NUCLEO-F303RE together with an X-NUCLEO-IHM08M1 and the ST Motor Control Workbench (STMCW) to drive a BLDC motor using ST code.In addition, my company has designed its own motor control board for driving two BLDC motors using the same STM32F303RET6 processor. I hope, for prototype purposes, to use some of the ST motor control code in the company motor control board.However, I may have an issue with the ST code because of the ADC allocation.In the X-NUCLEO-IHM08M1 the inverter currents are measured by bridge leg shunt resistors and fed to operational amplifiers with a gain of 5.18.The STMCW allows for selection of the ADC channels with the NUCLEO-F303RE board for measuring the inverter shunt currents, for example :-Ch phase U      ADC1_IN1 (A0)Ch phase V      ADC12_1N9 (C3)Ch phase W      ADC12_IN8 (C2)What is apparent is that the choice of ADC channels is as follows&nbs

Trying to measure consumption of a sub-GHz radio device, and I keep getting this error:It always seems to happen at the time of a Tx.This is a really unhelpful message, as it gives no clue at all as to what the issue was - therefore is no help at all in resolving it.:pouting_face: The only thing mentioned under 'Troubleshooting' in UM2269 is USB overflow, with the suggestion being to reduce the acquisition frequency. So I reduced it to minimum (100Hz) - but still the problem persists.So I tried using the basic terminal interface instead of the GUI - and I get this:1578-06 2086-06 1146-05 1130-05 7516-05 end   error: Overcurrent >59mA, dynamic acquisition stopped   summary beg 0000-10 7516-05 summary endSo there is actually no "connection issue" at all - it is an error report from the board!Surely, the GUI should be able to handle such reports, and present them to the User - instead of sending us on a wild goose chase looking for non-existent "connection issues" ?:pouting_f

I need some clock synchronization between M4 and A7 cores. So I need steady clock values from A7 and M4 for single time point

I am using my stlink (chinese clone) from last one year for STM8. It was working fine till last week. But when I upgraded its Firmware( to version- 2J37S7) from CUBEIDE then it started misfunctioning for STM8 . Only sometimes it is detected by ST visual programer. Also using visual programmer, program get uploaded but then it automatically get disconnected . It is working fine for stm32 but not for STM8. It all started after I upgraded its firmware 3 days back. Debugging in STVD stop working at all. I ordered new stlink but it too came with new firmware and has same problem. I downgraded the firmware to 2J16S4 but still it is not working.Following is the error in stvpError : Cannot communicate with the device !Check the SWIM cable connection and check all the needed pin connections on the SWIM connector.If the application code uses Swim Disable and Reset pin as Output or has disabled SWIM Clock Divider:Try Now to SWITCH OFF and ON the application Power Supply while NRST Reset pin is fo

I have a screen and two buttons. With one I change the value, e.g. uint8_t sec. The other one changes the screen. How to set that when sec = 0 it is impossible to change the screen. It could be changed with other sec values. greetingsAndrzej

Hi, I am using ST25DV04k Tag and I can see an external tool can write to my Tag over RF.I am trying to read RFA1SS, LOCK_CCFILE, LOCKFILE registers over I2C but always getting values as zeros. even if I write LOCK_CFG=1, LOCK_CCFILE=0x03, RFA1SS=0x0C, still external tool can write or erase user area 1 data. please suggest me why all my system configs are reading as zeros and why I am unable to write or change the register values to lock/block RF write?Thanks Rakesh

Hello everyone,I am currently trying to calibrate VL53L1X sensors which are covered by a 4mm thick glass.I am using the ULD from ST to calibrate the offset and xtalk.I achieve a better result with calibration, but I still don't get further than 70-80 cm.According to the user guide the ranging curve with calibration should look like this.But in my case it looks more like this:So basically just like the ranging curve without xtalk calibration, only now the deviation starts a little further away.In the calibration process I also noticed that the XTalk calibration distance (XCD) determines the achievable range of a sensor after calibration.For example, if the XCD of a uncalibrated sensor is at 85cm, the range to which the sensor can produce acceptable results after calibration is also around 85cm.But the above picture found in various user guides shows that after calibration the sensors should also produce good results for ranges bigger than XCD.Am I doing something wrong? Is it the cover

I'm putting an STM32L4S into DFU bootloader mode by holding the BOOT0 pin high at power-up.That causes it to show up in WIndows 10 Device Manager under "Universal Serial Bus devices" as "STM32 BOOTLOADER". (It shows up under "Ports (COM & LPT)" as "USB Serial Device (COM4)" if the BOOT0 pin is low at power-up)However, when I run DfuSE Demo (v3.0.6), I see nothing under "Available DFU Devices". I've tried launching DfuSE Demo both before and after powering on the device in DFU bootloader mode. Also, I've got other interfaces like I2C /UART/SWD disconnected, just in case they might interfere with entry into DFU mode over USB.Am I missing some obvious step here?