Others: STM32 MCUs related

Hi,has anybody already implemented the LAN9253 via SPI?I´m trying since several month to implement the Software framework - without success...EtherCAT Software Framework User's Guide (microchip.com) Best regards, Achim

Hi thereI am working on a custom board with a s2-lp radio on it. The only difference to the STM generate s2-lp SubGhz project is that I use PA5 for radio_sck (see attached Project). After playing a while with my I-NUCLEO-S2868A2 shields suddenly the basic minimal p2p example does not work anymore. When I press the button is pressed I see a call to app_x-cube-subg2:c:Set_KeyStatus and the a packet is send in app_x-cube-subg2:c:MX_SUBG2_P2P_Process->AppliSendBuff(&xTxFrame, xTxFrame.DataLen);. However the software stays forever in app_x-cube-subg2:c:MX_SUBG2_P2P_Process in the SM_STATE_WAIT_FOR_TX_DONE e.g. I get no Interrupt from the Radio in the P2PInterruptHandler where  the xTxDoneFlag should set. You can check in the attached Project that the Interrupt should be triggered by the falling edge, Spi clock is 625kBps, I use 8 bit words for the bus. The explanation I have killed my radio, but this must be impossible!!!!

In this Getting Started Tutorial video we are going to dive into generating an audio I2S stream. We will be creating dual SINE waves (Left/Right) at 96 kHz sample rate. #STM32 #Tutorial #GettingStarted #STM32CubeIDE #STM32CubeMX #I2S #DMA #STM32Worldhttps://youtu.be/vOAf3xxGq_o

Lots of people dunk on my beloved C-preprocessor, but I find it to be my go-to hammer in my codebase. https://github.com/PhucXDoan/phucxdoan.github.io/wiki/Macros-for-Reading-and-Writing-to-Memory%E2%80%90Mapped-Registers Let me know of any mistakes that there may be in the article.

Hi all,I am using an STM32H563 (device ID 0x484).When attempting to update the MCU firmware using stm32flash 0.7, I am encountering the following error.=============stm32flash 0.7http://stm32flash.sourceforge.net/Interface serial_posix: Baud Rate : 115200, Data Bit : 8, Parity : E, Stop Bit : 1GET returns unknown commands (0x50)Unknown/unsupported device (Device ID: 0x484) I would like to know what the 0x50 command is and what content should be added to devices[] for the STM32H.The following is what I found through a search, but I don't know if it's accurate.=============const stm32_dev_t devices[] = {/* ID "name" SRAM-address-range FLASH-address-range PPS PSize Option-byte-addr-range System-mem-addr-range Flags *//* H5 *//* {0x474, "STM32H503xx" , 0x20004000, 0x20008000, x , x , x, x, , x , x , 0x0BF87000, 0x0BF90000, x}, *//* {0x484, "STM32H563xx/573xx , 0x20000000, 0x200A0000, x , x , x, x, , x , x , 0x0BF97000, 0x0BFA0000, x}, *//* {0x478, "STM32H523xx/33xxx , 0x20004000, 0x20

Hi Guys, for an internship I am making a dual channel datalogger. So for that datalogger, I am using DS1338 RTC. Now instead of doing I2C normally, I am doing Bit-banging. I am using Nucleo-F030R8 board for my prototyping and I am using PA0(SDA) and PA1(SDA).  After using DSO I was able to verify start condition, stop condition and slave address transfer. Also I tried to test ack by manually pulling the sda down and the output was as expected.  Now the issue is I am not able to write or read the RTC and I am getting FFFF while reading it. And there are no hardware issues as I have tested the RTC. This makes me think there is problem with my I2C read function. Following is the snippet of code I am using for this purpose -#define I2C1_SDA_HIGH() (GPIOA->BSRR = (1U << SDA1_PIN)) #define I2C1_SDA_LOW() (GPIOA->BSRR = (1U << (SDA1_PIN + 16))) #define I2C1_SCL_HIGH() (GPIOA->BSRR = (1U << SCL1_PIN)) #define I2C1_SCL_LOW() (GPIOA->B

We are using IAR embedded workbench for our compiler and debugger (I-jet). I am testing with a STM32H750B-DK board. Running the sample code of QSPI memory mapped. I realized that if I select board as STM32H750-DK, then everything works fine, but if I select STM32H750IB, then the flash reading was always 0x99. What is the difference between the two selections? Does the debugger load extra initialization code for DK board? The source code is exactly the same. Thanks for any help in advance.

I'm trying to talk to a string of WS2812C LEDs with an STM32C011J4M6. The timing requirements are:Here's the schematic. I populated R3 and removed R1:I'm hoping for the simplest hardware implementation, so I'm using the HSI 48MHz clock. This means that each clock cycle is 20.8ns, which means that, for a 0, the pin can only be high for at most 18 clock cycles. With that in mind, I tried to write the most efficient driver that also takes the same time for each bit.My problem is that, when I try to output a string of 1s, the timings vary despite the code being the same for each bit:I get 4 short pulses (840ns, good) followed by 4 longer pulses (1670ns, too long). Somehow, ~45 extra clock cycles are embedded in the long pulses, which doesn't make any sense since the code is the same for each bit.Is the microcontroller doing background tasks or something? Why is the timing different in such a predictable way?Here's my main.c:#include "main.h" #define NUM_COLOURS 3 #define LED_COU

STM32F411CEU6 Minimum System Board Microcomputer STM32 ARM Core BoardI'm unable to flash my board using USB DFU mode. When I enter DFU mode, Windows fails to recognize the device and shows a USB error. However, UART flashing works correctly using PA9 (TX) and PA10 (RX)- Hold the BOOT0 button- Pressed and released RESET button- Then released BOOT0- Windows shows a popup:_USB device not recognized. The last USB device you connected to this computer malfunctioned- Device Manager says "USB Device Descriptor Failed"- STM32CubeProgrammer and dfu-util do not detect the deviceAnd also I installed STM32CubeProgrammer, Drivers and more but still cant enter dfu mode On the other hand Im unable to flash board with UART which I dosent like Note- Im new to STM boardsI'd appreciate help in diagnosing and fixing the USB DFU issue on my STM32F411CEU6 Black Pill board. 

Hello All,I am using STM32F103C8T6 dev board and implemented UART code with RX idle line interrupt. I tested using USB to TTL converter it working as expected. But when I connected this UART to the Bluetooth module, it did not get interrupt if the command length was more than 1 byte.This behavior is very wired because it works when connect USB to TTL and not work when want to actual hardware with Bluetooth module.My working simple code isHAL_UARTEx_ReceiveToIdle_DMA(&huart3, Serial3RxData, UART3_RX_MAX_LEN); void HAL_UARTEx_RxEventCallback(UART_HandleTypeDef *huart, uint16_t Size) { // printf("UART SERIAL REC:%s\r\n", Serial3RxData); isSerialAvailble = 1; HAL_UARTEx_ReceiveToIdle_DMA(&huart3, Serial3RxData, UART3_RX_MAX_LEN); } //when isSerialAvailble is set trigger the function and execute RX command.Is there any external pullup or pulldown for Rx line required? What could happen when send more than 1 byte length and then not receive interrupt? Thanks in advance

Hi everyone, I'm having some strange issues with my ws2812b neopixels, and can't quite figure out what's causing them. Some color settings work perfectly, while others trigger this odd behaviour. Even weirder, certain fixes just seem to shift the issue to different color settings instead or resolving it entirely. And to make things more confusing - it doesn't happen every time. When I send color data to my ws2812b, certain colors cause the first led to appear much brighter with an excessive amount of green. This happens only on the first led. No matter how many leds are in the chain, the rest display the correct colors. I've tested multiple ws2812b rings and strips, but the issue persists. To rule out voltage level problems i added a level shifter to shift both, supply voltage and data line voltage to 5 volts. The problem remained, just brighter :) I can't quite put my finger on whats happening because it's just so bizarre. I am using the nucleo stm32C071RB board. It works at 48MHz. I

Hello, I am working on a home made board featuring an STM32G474QE in 128 pins and multiple relay drivers (MAX4896 : MAX4896 - Space-Saving, 8-Channel Relay/Load Driver)If I understand it well, the principle is fairly easy, sending a flow of data consisting of 8 times the number of MAX. Once that is done, driving the Chip Select to LOW will drive the outputs of the relay drivers depending on what the value of each bit is.In my case, I have 9 relay driver daisy-chained so that would be 72 bits to send in one data flow. I have two questions regarding this. First off all, what mode should I put the SPI in, I coulnd't find this information in the MAX datasheet.My second question is more of a code issue, would anyone have any example of how to code something of this sort.Thank you very much for any help

Lars Thomsen of the excellent https://stm32world.com has been creating hands-on, no non-sense tutorials about the STM32 family.Check out the complete list at https://stm32world.com/wiki/STM32_Tutorial_Videos

Hello,I am currently trying to use the EMW3080 Wi-Fi chip on the B-U585I-IOT02A over SPI. I am using the Keil µVision IDE and I am trying to use a bare-metal approach without a HAL. I am trying to send data over to ThingSpeak from the temperature and humidity sensor that is built on the board. I have been having significant issues communicating with the EMW3080 over SPI. If anyone is able to provide some guidance, that would be very helpful. I am not able to get the SPI clock to generate. I do not know what SPI mode the Wi-Fi chip is, and I do not know what protocol I need to use to communicate with the chip. I have attached my main.c file.Thanks for any help.

Dear Community,I am currently working on managing IGBT switching in the frequency range of 20 kHz to 60 kHz. My setup involves directly applying a PWM signal to a pulse transformer, which successfully drives the IGBT. However, I am encountering an issue where the IGBT occasionally burns out at random intervals. After reviewing some documentation, I suspect this is due to hard switching, and I understand that soft switching could improve efficiency and reliability.From my research, I learned that soft switching may involve applying a short pulse to the IGBT to initiate an LC tank oscillation, then detecting the zero-crossing point (ZCD) to synchronize the next pulse. However, I am uncertain how to implement this in a half-bridge configuration. Specifically:Implementation Method: Should I configure a PWM with complementary outputs, or can I achieve this by manually toggling two GPIOs with a controlled delay?Oscillation Synchronization: How can I effectively read the ZCD signal

Hi,I am using Tower Pro SG90 servo motor interfaced with STM32F401. Timer 2 is used for generating PWM and timer 5 is used for generating the delay. I tried multiple code changes by myself and also took help from internet, but the servo jitters a lot, gets heated and gives the incorrect angle. Can anybody check my code and help me out?#include <stdlib.h> #include <stdint.h> #include <stm32f401xe.h> /*************This structure defines the registers for general purpose timers 2 and 5*************/ typedef struct{ volatile uint32_t REG_CR1; uint32_t RESERVED0[2]; volatile uint32_t REG_DIER; volatile uint32_t REG_SR; volatile uint32_t REG_EGR; volatile uint32_t REG_CCMR1; uint32_t RESERVED1[1]; volatile uint32_t REG_CCER; volatile uint32_t REG_CNT; volatile uint32_t REG_PSC; volatile uint32_t REG_ARR; uint32_t RESERVED2[1]; volatile uint32_t REG_CCR1; uint32_t RESERVED3[8]; }TIM_REG_DEFINES; /*************This structure defines the registers for GPIO****

I got my custom stm32F746 PCB Working!  It is based on the STM32F746G-DISCO.  So, for the first revision I used the same capacitive touch lcd used on the Disco.  So that all works!  But I need a resistive lcd, so I designed in a TSC2046IPWR controller.   I just want to connect a resistive panel and get it to function.   Not really sure best way to proceed to disable the capacitive control and add the resistive?   Any insight would be appreciated.

Hi,I am trying to create a binary image that can be run from either 0x08010000 of 0x08044000 in a STM32L476 Processor using the Keil MDK-ARM 5.42.0.0 Development environment with the armclang 6.23/6.19/5.06 (Options I have tried) compiler.I am unable to find detailed documention on how to make this work.I have found a trivial project guidelines that does not really include any of the sections needed in the scatter file.here is the trivial example: https://developer.arm.com/documentation/100748/0624/Mapping-Code-and-Data-to-the-Target/Bare-metal-Position-Independent-Executables?lang=en However, this is not detailed at all and does not describe what is and what is not supported in Compiler 6.23/6.19/5.06 Here is what I have tried with 6.23:C/C++(AC6) flags: -fbare-metal-pie,Asm flags: -fbare-metal-pie <--- argument ununsed during compilationLinker flags: --bare_metal_pie.When I do this, I see the following linker warnings/errors: linking....\OBJ\ELSA-16T_Application.axf: Warning: L608

Hi everyone,I'm currently working on an obstacle-avoiding robot using the STM32F407 Discovery board and I'm running into issues with testing my HC-SR04 ultrasonic sensor.Hardware setup:TRIG connected to PA0 (configured as push-pull output)ECHO connected to PA1 (configured for TIM2_CH2 input capture mode)Using TIM2 to measure pulse width via input capture on Channel 2Running the code bare-metal (no HAL or CubeMX)The issue:I tried having Chat walk me thru how to use UART but that didn't work, so I tried testing the sensor by debugging it and see if the value for my distance changed in the expression window.When I tried running it, it wouldn't work, so I tried stepping over to see where it broke, and its stopping on line 118-119, right after the while loop. I had this issue earlier with the for loop on 113, but GPT was able to help me thru that one, but so far I am stuck on this part. I am doing this solo with GPT walking me thru it, so I am open to any and all pointers/advice.Apprec

Hi,I want to control a 4-pin DC fan (9RA1212P1K001). I need to run 3 identical fans at the same time and at the same speed. In this case, what is the difference between using 3 different channels of the same timer and connecting each to the PWM input of each fan, versus using only one channel of the timer and connecting the PWM pins of all 3 fans to that single channel?I should note that I'm powering this DC fan with an external power supply, and there's a MOSFET (AO3400) between the STM32 board's PWM-generating pin and the fan.BR

Is official rust support on the roadmap for st, or contributing dev time to open source libraries like embassy-stm?

Hi all, I'm working with a STM32 Nucleo-F439ZI board and using MATLAB Simulink (Embedded Coder + STM32 support package) to generate code and deploy to the target. I’m trying to set up serial communication (USART) between the STM32 Nucleo-F439ZI and my PC using MATLAB R2025a + Simulink + Embedded Coder. I am using the onboard ST-Link virtual COM port via USB. I’ve tried using the Serial Transmit and Serial Receive blocks in Simulink, mapped to USART3. However: No data is being received on the PC using a terminal (TeraTerm, PuTTY). I have also switched to other UARTs like USART2. Still it is not working. Are there known issues or required initialization steps when using Serial blocks in Simulink with STM32 targets?Any working example models or documentation for basic serial I/O using Simulink and STM32 boards? Thanks in advance for any help or pointers!

Hello,I made a simple USB HID keyboard with a STM32F042 in bare metal (no HAL, no LL). Everything works great. Including LEDs and media key support. The only strange thing I am observing is that windows and linux are both sending the LED report twice in a row (the second one comes directly after the minimum poll ~10ms later). The first report is always 0x01 and the second one is the actual state of the LEDs. Now I could implement a "filter" but I was wondering if this is normal behavior? Or could I have an issue in my descriptor?Thanks Kind regards

Hi everyone,I’m working on a design using an STM32H7 MCU communicating with a GPS/GNSS module over UART. Unfortunately, during board routing, the RTS and CTS lines were connected directly (RTS↔RTS, CTS↔CTS) instead of crossed.I understand that for proper hardware flow control, they should be:STM32 RTS → GPS/GNSS CTSSTM32 CTS ← GPS/GNSS RTSAt this stage, I can’t modify the hardware or rework the PCB, but I’d still like to maintain some form of flow control or transmission reliability if possible.

After some time I found the tool displaying an error of sort, I think something regarding inactivity.Following that I can't close the sampling window. I can't move it or minimize it , or press any button in its GUI.  All buttons are unresponsive.I can open a new instance of the STM32CubeMonitor-Power, and I can move to other Windows apps.But the windows is still there. Stuck.