Solved

Hello, I'm currently trying to develop a bare-metal ADC driver for my Nucleo STM32H7A3ZI-Q Board. I have done all the necessary steps in order to setup the ADC, however I still get random values from the data register, even though I have my PF11 (or A5) connected to the GND.Here is my current code:#define ADC1EN (1U<<5) #define GPIOFEN (1U<<5) #define ADC_CH2 (1U<<7) #define ADC_SEQ_LEN_1 (0x00) #define ADC_DEEPPWDEN (1U<<29) #define ADC_REGEN (1U<<28) #define ADC_LDORDY (1U<<12) #define ADC_PRESC_2 (1U<<18) #define ADC_CKMODE_SCLK_1 (2U<<16) #define ADC_ADCALDIF (1U<<30) #define ADC_ADCALLIN (1U<<16) #define ADC_ADCAL (1U<<31) #define ADC_ADEN (1U<<0) #define ADC_ADSTART (1U<<2) #define ADC_ADRDY (1U<<0) #define ADC_EOC (1U<<2) void pf11_adc_init(void) { // Configure the ADC GPIO pin RCC->AHB4ENR |= GPIOFEN; // Enable clock access t

I add CMSIS DSP over MX ioc in CubeIDE 1.7:0, but now in latest ARM software dont exist. Why?

Hi everyone,I'm encountering an issue with the STM32 Device Configuration Tool: it doesn't properly generate the global interrupt handler function for one of the UARTs in my project: The generated interrupt handlers for USART1 and USART2 include call of the default HAL interrupt handler (HAL_UART_IRQHandler(&huartX);) but the handler for USART6 is missing this line. /** * @brief This function handles USART1 global interrupt. */ void USART1_IRQHandler(void) { /* USER CODE BEGIN USART1_IRQn 0 */ /* USER CODE END USART1_IRQn 0 */ HAL_UART_IRQHandler(&huart1); /* USER CODE BEGIN USART1_IRQn 1 */ /* USER CODE END USART1_IRQn 1 */ } /** * @brief This function handles USART2 global interrupt. */ void USART2_IRQHandler(void) { /* USER CODE BEGIN USART2_IRQn 0 */ /* USER CODE END USART2_IRQn 0 */ HAL_UART_IRQHandler(&huart2); /* USER CODE BEGIN USART2_IRQn 1 */ /* USER CODE END USART2_IRQn 1 */ } /** * @brief This function handles USART6 global in

Moved from 'Feedback' forum - which is reserved for posts about the forum itself.I am simply trying to blink onboard LED on PC13. When I run without any breakpoints the stack looks as follows:I have 2 bluepill boards and the result is similar on both of them.

We are designing an STHS34PF80 into an occupancy sensor and the plan is to have an HDPE window to protect it.  To test the response in the actual product we purchased 1/16" (1.5mm) HDPE sheet and put it over the sensor.  The fresnel lens with the dev kit was removed.  Surprisingly the Tpresence triggers when the sheet is over the sensor, and so the device doesn't seem to be seeing through the HDPE sheet.My first thought is that the HDPE is doped or just wrong somehow but I thought I'd ask if anybody else has seen something like this.Thank you.

Hello,first of all, I would like to thank STMicroelectronics for their commitment to providing information and expertise to the public free of charge. Currently, I am working with a very competent study colleague to set up a test bench.We intend to operate a PMSM with the mentioned 5KW inverter. It seemed like a simple project at first...The motor identification was performed using an IHM08M1 setup. The electric machine spun wonderfully! :)Now we have set up a complete test bench with the mentioned board, the ICS current sensing board, and a Nucleo-F446RE.After generating QC and settings to make the machine spin, we cannot get the electric machine to run!After several hours, to be precise, we tried somehow to get the Motor Profiler running.Ultimately, we saw in the MC Workbench that this function is only possible when the current from all three phases is measured.The STEVAL-CTM008V1 "Current sensing board" was, of course, expanded for the third ICS, but in the board manager (JSON file)

Hi All,I have just started a project with STM32WL33CC1 MCU. To get started I am trying to run and debug the example MRSUBG_Chat project.The project builds fine but refuses to enter debugging.I can program the WL33 using STM32CubeProgrammer and STM32_Programmer_CLI.exe version 2.18. An earlier version of the STM32_Programmer_CLI.exeversion 2.14 that I had on my laptop did not work. I can debug using OpenOCD option but I can not seem to debug using the ST-LINK GDB server option. Is there something that I am missing?I noticed that the STM32CubeIDE calls the STM32CubeProgrammer_CLI.exe using the same command tool that works when ran manually. I noticed that if I ran STM32CubeProgrammer_CLI.exe with mode=HwRstPulse then the error I get is similar to what the STM32CubeIDE throws.As mention earlier I can manually use STM32_Programmer_CLI.exe to connect with the following C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin>STM32_Programmer_CLI.exe --connect

I try to build a rpmsg sample app by following this instruction : https://docs.zephyrproject.org/latest/samples/subsys/ipc/rpmsg_service/README.htmlThe example repository here: https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/subsys/ipc/rpmsg_serviceIt seems that the device tree overlay is missing for STM32MP157F-DK2, so I create one/ { chosen { /* * shared memory reserved for the inter-processor communication */ zephyr,ipc_shm = &mcuram2; zephyr,ipc = &mailbox; }; mcuram2: mcuram2@10000000 { compatible = "mmio-sram"; reg = <0x10000000 0x40000>; };It is not working, please advice if the device tree is correct or not? and Is there any relation with Linux device tree? thanks 

Hello,I'm currently working on a project where I want to use both the NFC08A1 expansion kit and the RVA35HI display kit along with the U575ZI-Q development board. When I try to include the X-CUBE-TOUCHGFX software package in STM32CubeIDE, I get the following message in the software packs component selectorI understand that there are pin conflicts between the two software packs. I have tried reassigning all the pins of the X-CUBE-NFC6 such that there are no conflicts, however even after doing so I get the same warningAny idea on how to go about from here?Cheers

Currently I'm using some of the vl53l5cx api functions along with some custom code. I plan to have multiple ToFs used and noted, via o-scope, that the initialization function vl53l5cx_init (looks to be blocking code?? correct me if I'm wrong) takes about 2.5 seconds to complete (at 400Kbps I2C) to configure a single ToF. This means with the current initialization it would take more than 10 seconds alone for initialization to complete. Unfortunately, I am working in constraints that prevent me from accessing the watchdog to circumvent the issue. Are you aware of any ways of overcoming this? I wasn't sure of the initialization sequence was one that could be split.

Hi, Apologies in advance for my ignorance.  I have a NUCLEO-G491RE and want to use it as a USB CDC. Unfortunately I haven't had any success getting it to work. My problem is that doesn't even appear to show as a device on the host. I have looked at several other posts which seem similar. On the one post, they seemed to fix it with a resistor and some extra wiring, but apparently that is only for F series? I also tried increasing the stack and heap size to 2048 as suggested on another post - but still the same. I know the cable and other USB stuff is working, because the on-board stlink shows up - and I can use a serial port through that. To make sure it wasnt some conflict with the stlink, I disabled it by adding the JP1 jumper. And still nothing showed on the host. The code is using the generated STM HAL code and drivers and freeRTOS. It is calling the MX_USB_Device_Init();       void StartDefaultTask(void *argument) { /* init code for USB_Device */ MX_USB_Device

Hello,   These are the scripts available for the L4 series, Can the same scripts be used for H7 series MCUs. If not, are there any specific scripts/commands needs to be followed.     Regards,Devank J

Hi, I am using STM32H503 controller and wanted to understand if SWDIO pin can be used to flash the code.

I have a circuit card that uses the M48T18-150PC1 Timekeeper SRAM, and the battery died. I replaced the part but the settings did not save once power was cycled. A second part was used with the same result. Looking at the date stamp, (412) tells me I'm possibly at the limit of the battery's life. I tried measuring the voltage (Vcc to Vss), but have no reading at all. The replacement units integrity are questionable, so I'm wondering if I'm measuring something wrong. Is there a latch I'm not aware of that prevents me from measuring this voltage? Any help would be appreciated. In the meantime, I have placed an order for new parts hoping this will solve my problem. Regards,Bob

Hello everyone,I would like to know the technology node (i.e. 180nm, 90nm, etc.) of the STM32 microcontroller STM32F103C8T6. I can not find this information.Thanks in advance.Best regards.Marco 

I'm missing the FATFS supporting library files after adding SDIO SD card support and FATFS support in the CubeMX code generation tool within STM32CubeIDE. The funny thing is that those files are present in the project folder, just not in my project's folder structure in STM32CubeIDE.What I am doing wrong here? I was under the impression that the CubeMX tool was supposed to add/link these files to the project automatically. 

Dear sir, dear missis,I'm working with an STM32L053r8 on a step by step know-how. My interface with the bootloader runs fine, and I am able to cover the main features provided through this interface. The issues I try to cover now is the right understanding , how the Cortex M0+ runs at assembly level.  I done several tests without results today, I can continue to test with an iterative methodology; I can also use the debug port (SWD pin).I developped an interface to do that, but at this time I didn't received any answer from the debug port. This one is built following Cortex architecture protocole (IHI0031G Debug interface architecture V5.2 architecture specification).The only thing I can say, to define an hardware protocol at this level is a very important effort, and therefore I missed may be, some details. Or in short my best efforts, were insufficient to translate by hardware, this design document. What seems unclear to me is the specifications at the hardware level, my interfa

Hello, I'm trying to create a smart device to connect to my Home Assistant network using Zigbee. So far, I've been able to connect to the network and control a light (turning it on and off), which works perfectly. The issue I'm now facing is rejoining the network. If I cut the power to my STM32WB55 and turn it back on, the device won't reconnect to Home Assistant. The only way to reconnect is by enabling "Permit Join" in Home Assistant, which starts the device interview process again. I suspect the problem lies in the function shown in the picture below, where I set startupControl to ZbStartTypeJoin. Perhaps I need to set this to ZbStartTypeRejoin, but I'm unsure if this is indeed the issue. Additionally, how can I create a function that allows the device to join the network when, for example, a button is pressed for 3 seconds? Thanks, Hessel Jilderts 

Hello everyone! First post here. I'm a grad student in Computer Science and Engineering and I'm looking to learn Machine Learning on MCUs. My professor suggested I use the STM32 Nucleo development boards for this. I was wondering if anyone had a rough guideline and perhaps links to some resources which you found really useful on how to get started with this topic. I would be really grateful for any help. Thank you!

I am using this dev board: NUCLEO-F411RE for developing SPI communication protocol considering it as a SLAVE device. My firmware will receive data over SPI sent by Host machine and acts on it.I have following requirement:How to transmit data packets via host PC to MCU using SPI to test whether my firmware working correctly or not ?Option A: To use Raspberry Pi as a Host machine device and send data over SPI to MCU :-> This one so far seems best option for me as I can easily write test python application using open source spidev package python-spidev and easily connect Raspberry Pi and NUCLEO board as both supports SPI interface.Option B : I have also found this USB-SPI-bridge converter to directly connect Host PC (Windows, Linux) to Nucleo-Board based on SPI interface pdf: FTDI-MULTI-SLAVEAlso found this Adafruit-FT232H for same USB-to-SPI bridge converterIs thee any other similar dongle available which are cost effective and easy to use

When working in remote connections, such as WSL or docker the STM32 extension can not be activated with the following error:"Cannot activate the 'STM32 VS Code Extension' extension because it depends on the 'C/C++ Extension Pack' extension, which is not loaded. Would you like to reload the window to load the extension?"But the C/C++ extension is loaded and working.Is there any Work Around available?

Hi I have an application inquiry...'m looking into remote mounting a ToF sensor (i.e. VL53L4EDV0DH/1) in order to observe the environmental limitations of the sensor in a more difficult envorment...are there any guidelines or application history for this kind of optical adaptation?  (not as straightforward as a simple cover glass)   thanks, Jason

I bought the STEVAL-ETH001V1 kit on digikey. I also downloaded the firmware for the servo drive. However, when I build this project using keil c, the "TrajCtrl.h" library is missing and this library is not provided in the firmware.I would like to ask where I can find this library or can someone help me?

Hello Everybody,MCSDK:6.3.0CubeMX: 6.3.0Workbench : 6.3.0Motor Pilot : 1.2.9I am running on a IHM08M1 with STM32G431, The control is FOC Observer+PLL(sensorless) with 3 shunt.I want to test the open-loop function of FOC. I have already checked the "open loop" option under "Debug Settings" in the "Drive Settings" page of Workbench. However, when I run Motor Pilot, the "Open Loop - Voltage" control option does not appear in the control menu. Is there anything else I need to configure??

I'm kind of stuck. I have USB_CDC running, data appears on the Kitty-Terminal in Windows10 via USB, presented as COM6:  serial device in Windows. Sending data vis USB_CDC  is easy:   ret = CDC_Transmit_FS( buffer0, sizeof( buffer0 ) ); if( ret != USBD_OK ) { /* errors during sending ? .....   Receiving however doesn't work. That should be interrupt driven, not?The interface code allocates one buffer. And AFAIK there is a callback routinestatic int8_t CDC_Receive_FS(uint8_t* Buf, uint32_t *Len) Callback would mean it gets called automatically "by the system" (acutally the ISR) when there is data.Apparently I've to modify that routine into a non static version (correct?) and shovle away the *Len bytes at Buf(USB_CDC ring buffer) into my application buffer, waiting for me.However I think the callback never gets called. I type away at the terminal but nothing happens.Thus there are some fundamental questions:- is receiving via USB_CDC done interrupt driven?- do I have t