Solved

..

Hi, can someone refer to the above MCU reference. This is my first time using the STM32 MCU chip on my embedded system. My question regarding the power up/down phases concerning specifically on STM32L433CCT6 IC ... Is it a must and critical to use some kind of power sequencing/power management IC to perform the function ? My board consists just serial and CAN ports, relays, digital input circuits and few external memory ICs. - Any specific power management IC suitable for the job? - Thank you in advance

We are working on a couple ST25R3916B designs and would like to get some of the latest and greatest reference design, the x-nucleo-nfc08a1. Where can we buy these? I've been watching the distributors for a couple months and haven't seen any which is odd because the chip has been available a few times.Thanks,Derek

The stm32-mw-openbl project supposedly implements the system memory bootloader available in all STM32 MCUs.However, there are some missing functions:The GetChecksum command is missing, but it is documentend for example in AN4221 (I2C interface for the system memory bootloader)See also my issue here: Where is Get Memory Checksum command (i2c interface) · Issue #5 · STMicroelectronics/stm32-mw-openbl · GitHubI am posting here because it seems that nobody reads/replies to issues on the github project.Can you update the github library accordingly, so that it provides the full feature set?

Hi there, I'm starting developing on an STM32MP157F-DK2 kit, and I wanted to build my own distribution, starting from the distribution package (STM32MP1 Distribution Package - stm32mpu). At the first compilation, the bitbake st-image-weston takes reaaaally long time. I already used Yocto with older projects, using competitors' boards, and I never faced such a slow compilation time, which seems weird to me. Do you have any suggestions to speed up the process for your distribution? I tried already to modify BB_NUMBER_THREADS  and PARALLEL_MAKE parameters in local.conf file but I didn't notice any real difference. Other ideas? PS: I'm running my compilation on a virtual machine (running Ubuntu 20.04 lts OS), which has the minimum raccomandations that I found in some other thread here (sorry I don't remember where exactly): 6Gb of ram (ddr4 3200mhz) and 2 cores of physical CPU (intel i7-1165G7), totally not a bad machine in my opinion. Thank youSimone

Hello ST Community,currently I am thinking about how to ensure that different developers working on the same project are able to keep exact results. Building, linking, debugging and flashing process should be reproducible and identical for my purposes. Any recommendations on this?When using STM32CubeIDE I had the problem that the project files, which contain information about the toolchain etc., are very difficult to manage. (XML files containing absolute paths, .cproject, .project files etc. are changing on every startup of IDE).Currently I manage in a separate GIT repository tools like:- GNU ARM Embedded Toolchain- Make- STM32CubeProgrammer- OpenOCDThe firmware is in a separate GIT repository and relies on a Makefile build process. There are only relative paths to the toolchain repository in the Makefiles. This means that as soon as all developers consider the hierarchy of the firmware and the toolchain folder, it should always be possible to reproduce identical results. The Makefile

Hello everyone, I'm fairly new to Git and I'm trying to use it as my firmware version manager for an existing STM32 project. I set up correctly my project directory to work on my computer and with Bitbucket and everything works fine. I created a new branch before doing some big changes to the project, and I did a checkout towards this branch. The problem is that when I modify anything inside Cube IDE, the modification doesn't appear inside the "real" file that I find on my computer inside the directory : for example, if I add "//test" into main.c inside Cube IDE, and then I open main.c with VSCode, this line does not appear. I checked several times that the file path is EXACTLY the same (D:/__Git/MyProject/Core/src/main.c), but it does not work at all. Is it a problem with my setup, with Cube IDE, or with my understanding of Git ? Does anyone have a solution ? Best Regards.

According to the "known issues" post, importing an existing .ioc file from STMCubeMX is currently unsupported.I'm starting a new project and would like to use the IDE for this - but my engineer designed the product using CubeMX.Is there any kind of workaround for this?As I see it, my options are:1) manually recreate his work2) keep using the "old" tools (CubeMX & Keil compiler)Not sure which would be "better".Thanks.

We are migrating from ecosystem version 2.1.0 to 4.0.0. We have a custom board with STM32MP157C.After resuming from STANDBY the ADCs and DAC, used by M4, no longer work. They are initialized and started without error, but all ADC channel data reads 2048. For the DAC, the DOR1 register reflects the data written to it, but there is no output on the DAC_OUT1 pin.Additional information:The ADCs and DAC are used with DMA.The ADCs and DAC work fine after cold boot.On ecosystem version 2 the ADCs and DAC work both after cold boot and after resume from standby.We use trusted boot.

Hi,I have some questions about the latest ToF released VL53L8CA (only databrief released at the moment):Is the VL53L8CA footprint/pinout-compatible witth the VL53L5CX?Is the VL53L8CA on-board microcontroller RAM-based (like VL53L5CX)? If yes, what is the time (or size) to load the on-board FW at the initialization phase?Could you update the comparison between ToFs by adding the VL53L8CA?Thank you

I'm working on a ML project with X-Cube-AI version 7.3.0 with the STM32F4DISCOVERY board. I created the neural network with tensorflow, and the analysis went smooth, the network occupies 25 kb of flash and 8 kb of ram.This is the neural network summary;Model: "sequential_8" _________________________________________________________________ Layer (type) Output Shape Param # ================================================================= conv1d_10 (Conv1D) (None, 28, 16) 1456 batch_normalization_49 (Bat (None, 28, 16) 48 chNormalization) conv1d_11 (Conv1D) (None, 28, 32) 1568 max_pooling1d_25 (MaxPoolin (None, 14, 32) 0 g1D) batch_normalization_50 (Bat (None, 14, 32) 96 chNormalization) conv1d_12 (Conv1D) (None, 14, 64) 6208 batch_normalization_51 (Bat (None, 14, 64) 192 chNormalization) conv1d_13 (Conv1D) (None, 14, 64) 4160 max_pooling1d_26 (MaxPoolin (None, 7, 64) 0 g1D) batch_normalization_52 (Bat (None, 7, 64) 192 chNormalization)

If I set read protection (RDP=0xBB) on my STM32H7 MCU, it seems that both software reset and hardware reset commands stop working, e.g. I type:STM32_Programmer_CLI -c port=SWD sn=XXXXXXX reset=HWrst -hardRstand nothing happens. Also, the MCU will not reset after flashing if read protection is set to 0xBB. Is this expected behaviour?Edit. After some experimenting it seems that in the GUI STM32CubeProgrammer it is not possible to run the firmware by clicking Run button in MCU core view if RDB is set. I get "Error: Unable to run application"Edit. More experimenting: When I try to runSTM32_Programmer_CLI -c port=SWD sn=XXXXXXX --start -vb 3I get:RUNNING Program ... Address: : 0x8000000 STLink read from (0x08000000) returned: 0x00000020   2nd try fail!   STLink read from (0x08000004) returned: 0x00000020   2nd try fail!   w ap 0 reg 15 PC 0x000EFFFF w ap 0 reg 17 MSP 0x000EFFFF w ap 0 reg 16 xPSR 0x01000000 Warning: The core is locked up Start operation achieved success

..

Hello, I am working on vd6283 sensor to interface with NRF52 chip, I able to get data from the sensor, for ALS values and flickering extraction, but the problem I am facing is that I am unable to operate the sensor both for flickering frequency extraction and ALS values... at the same time.And unfortunately, I am unable to find an example pseudo-code that tells us how to use the sensor for both operations at the same time.Thanks.

..

I'm trying to make 2 DRP 100w ports but I can't find many related resources. Can anyone help by providing a sample code or related resources.

Hello! I have STiD135, but can't find actual documentation for this device on it's page on your site. Where can I find it?Thank you very much!

HiI have some wiedgets which are using the registerTimerWidget functionality.My software crashes with an assertion:*** assertion failed: timerWidgets.size() < MAX_TIMER_WIDGETS, file ../../../../framework/source/touchgfx/Application.cpp, line 585The MAX_TIMER_WIDGETS are defined as 32 in the file Application.hpp. Now I wanted to increase that number, but the crash still happens at 32 registrations.Now I assume that the library is precompiled with MAX_TIMER_WIDGETS = 32 and that your check does not check for the size of Vector<Drawable*, MAX_TIMER_WIDGETS> timerWidgets;Anything I can do to increase that number? @Martin KJELDSEN​ Thanks for your help./jimmii

..

Hello,I am developing a system using VL53L1X.Occasionally, when the host microcomputer is asynchronously reset, there is no response from the sensor after that.It can be detected that the sensor's SDA is stuck at Low. We can handle it.The situation I am encountering is that the sensor's SDA line is high, but I2C communication is not possible.Is there an internal state that ignores the start condition from the host microcomputer?If so, please tell me the transition conditions to that internal state.Best regards.

Hello,​I am developing a system using VL53L1X.Occasionally, when the host microcomputer is asynchronously reset, there is no response from the sensor after that.​I've never used the xshut terminal.If communication with the sensor becomes impossible, I'm thinking of using the xshut terminal to synchronize the host microcomputer and the sensor.Please let me know the setup time required to start I2C communication after setting the xshut pin to high level.​From the topic below, I think 10ms is enough, but I would like some information as a specification. Title:vl53l1x-xshut-pin​​Best regards.

Hi, I cannot debug stm32mp157-dk2 on macOS (stm32cubeide). I have those logs in the console:Does anyone know how to resolve it? :)

I'd like to raise attention of ST staff regarding the LPS28DFWTR pressure sensor and what I believe is a sensor design issue (I hope I'm wrong, because it is an amazing sensor nevetheless!).The original topic was here:https://community.st.com/s/question/0D53W00001r8PF1SAM/what-is-the-material-the-membrane-is-made-from-on-the-lps28dfwJust in case I copy-paste results of my quick research here:I confirm that LPS28DFWTR is not just sensitive to sunlight, it is sensitive to ANY light! It feels like some p-n junction on sensor's die is exposed to light through transparent silicone and it's confusing readings/I2C. I'm attaching video here:https://veed.io/view/a25b61dc-20d8-4442-998d-9bb3f83cf191It's a simple setup where I measure both pressure/temp using LPS28DFWTR and convert it to altitude (you can see current altitude and temp resdings on display).As you can see on the display, when I cover membrane and sensor to light - pressure readings are fine.When membrane is facing bright

Hi, I have an application that suggests the pressure sensors are very sensitive to sunlight. 1. I have noticed the same behaviour. Can anyone confirm if the sensor experiences a photo-electric effect that amplifies the signal current within the sensor?Images below are of a device with two LPS33HW sensors mounted in orthogonal directions being dipped in and out of water. In the first case this is done inside under ambient light, in the second it is outside in direct sunlight. 2. In some cases we have observed the sensor measurement circuit appears to lock up but the digital line continues to output the last known value. Can anyone confirm the following: I suspect the Analog circuit has experienced some overcurrent and has shut itself down, but the digital line remains powered and keeps reporting the last known value.Can anyone confirm this behaviour? 

HelloI have recently acquired a B-L475E-IOT01A2 IoT node, which has an integrated SMT32L475VGT6 MCU microprocessor.I have installed the STLINK V2 driver and tried to connect to it via a microUSB type B cable to the USB_STLINK port (CN7), with jumper JP4 on pins 1 and 2. So LED5 lights green and I proceed to load (in CubeIDE) a project previously generated with CubeMX. Then I receive the following error message: "No ST-LINK detected! Please connect ST-LINK and restart the debug session".Therefore, I try to connect through CubeProgrammer to the micro-controller but I am not able to. I have tried to update the STLINK driver firmware and I still can't connect. I have also downloaded and installed OpenOCD as an alternative. I have repeated the process on both Linux and Windows (because I have read in other forums that many users have had problems with the STLINK driver on Linux).So I've been at a loss and unable to transfer a project for a while now. I suspect it may be a bootloader thing,