STM32 MCUs

Hi, [PN]: B-G431B-ESC1[VERSION]: MCSDK 6.3.0[TOOL]: STM32CubeIDE 1.16.1, MotorControl Workbench 6.3.0[DETAILS]:I am designing a custom motor controller based on the B-G431B-ESC1 board. I have modified the power stage and current sensing hardware to support higher current and voltage ratings (targeting 100A and 100V). I am using MCSDK-generated firmware with FOC (Field-Oriented Control). However, I am having difficulty identifying which sections of the firmware or configuration files handle the over-current and over-voltage protection thresholds.[EXPECTED BEHAVIOUR]:Update the firmware so that the current, voltage, and protection ratings match my modified hardware specifications (100A

HiWe are currently working on a new board with a STM32H562. As part of the design, we want to measure the temperature of the MCU. In the Datasheet of the STM32H562 I see the “Analog temperature sensor” (as I know it from other STM32) connected to the ADC and a (maybe a new) “Digital temperature sensor (DTS)”. A few questions regarding the two sensors:Why are there two different temperature sensors?Is there a difference between the sensors, if it comes to the measured temperature?Are they places in different positions on the die?Is there a recommendation, when to use which of the two sensors?Thanks and RegardsMarco

Hi,I am trying to check if a button is pressed for 3s continuously using a timer which is started through an interrupt. The code for the same is attached below. The issue I am facing is the interrupt is immediately called when I press the button after reset, but it works fine for the consecutive times. void EXTI1_IRQHandler(void) { if (__HAL_GPIO_EXTI_GET_IT(RESET_Pin) != RESET) { __HAL_GPIO_EXTI_CLEAR_IT(RESET_Pin); // Clear the interrupt flag if( HAL_GPIO_ReadPin(RESET_GPIO_Port, RESET_Pin) == 0){ //FALLING Edge HAL_TIM_Base_Stop_IT(&htim2); }else{ //RISING EDGE if(!(TIM2->CR1 & TIM_CR1_CEN)){ __HAL_TIM_SET_COUNTER(&htim2, 0); HAL_TIM_Base_Start_IT(&htim2); } } } } void HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef *htim) { /* USER CODE BEGIN Callback 0 */ /* USER CODE END Callback 0 */ if (htim->Instance == TIM8) { HAL_IncTick(); } /* USER CODE BEGIN Callback

Hello everyone,I've been struggling with the ADC of a STM32G474QE on a custom board for some while now. I initially saw a discrepancy between an onboard NTC thermocouple and its measured ADC value. The measured Value (calculated to mV) was off by an average of 50mV over three boards. The impedance of the NTC circuit is reasonable low with 500ohm, which should result in no issues with this rather infrequent measurement with a a high sampling time. I then started seeing more of that behavior with other ADCs and their respective channels. There was always some offset in the measurement. To be able to quantify the offset, I ran a test, where i applied a dc voltage to the other channels, measured the voltage at the pin and compared it to the ADC values. (see attachment meas offset.png). I had very similar behavior on several boards. I then looked into ways to compensate this and started to implement measurements to Vrefint as injected samples after rerunnin

I am currently implementing FreeRTOS on the STM32F407 MCU board and integrating it with the RC7620 Cellular Modem. However, I am facing issues with the UART configuration of USART2 for transmitting and receiving AT command responses from the RC7620 modem. I already have the FreeRTOS source code available and would like to share it with you for your support in making the USART2 configuration work correctly. Best regards,Manjunath E. L.  

I am working on a STM32N6570-DK board, and I am wondering how to start the MPU of the N6 core, when I start a touchgfx project, it can't work successfully. I hope that some additional information and some courses can be provided.

I am working on a STM32N6570-DK board and I noticed that the CN7 of the board can be modified as digital I/O pin or an ADC. So I want to make sure that when I use the A1 port of CN7 for example, and I want to use this port as a usart_tx. Then I can directly enable the PC10 as a usart_tx and disable the PA9 right? And I want to make sure that the modification don't damage the ADC function of PA9, since the MCU actually accept 0-1.8V and the 3.3V is too high.

Hello , everyone. I am currently working with the STM32N657X0H3Q device on the NUCLEO-N657X0-Q board.Following the official Template_FSBL_LRUN example, I successfully generated and signed both FSBL and Appli binaries using STM32CubeIDE and STM32_SigningTool_CLI v2.19.0. In DV Mode (BOOT1 = High), I programmed:The trusted FSBL binary to address 0x70000000The trusted Appli binary to address&nbsp

Hi, I am using STM32F446RE Nucleo and a Peak CAN Usb to test the CAN functionality of the microcontroller. I have connected the Microcontroller to a CAN Transceiver (TJA1050) and added a 120ohm resistor between the CANH and CANL line. I have attached the config of the CAN hardware below   hcan1.Instance = CAN1; hcan1.Init.Prescaler = 42; hcan1.Init.Mode = CAN_MODE_NORMAL; hcan1.Init.SyncJumpWidth = CAN_SJW_1TQ; hcan1.Init.TimeSeg1 = CAN_BS1_2TQ; hcan1.Init.TimeSeg2 = CAN_BS2_1TQ; hcan1.Init.TimeTriggeredMode = DISABLE; hcan1.Init.AutoBusOff = DISABLE; hcan1.Init.AutoWakeUp = DISABLE; hcan1.Init.AutoRetransmission = DISABLE; hcan1.Init.ReceiveFifoLocked = DISABLE; hcan1.Init.TransmitFifoPriority = DISABLE;   When I transmit a message using the Peak CAN, I get  "Frame stuff error (Rx)". I have already attempted to Change the baud rate Remove the resis

Dear colleagues, hello! Question about LWIP. I have two network interfaces, one on the QCA 7000 chip via SPI, the second on LAN 8742, installed on the debug board. I use the Socket API. The problem is as follows: The server is running on one interface, the client on the other. When they are not running at the same time, everything works fine. But if you enable them at the same time, sometimes the outgoing packet on the QCA 7000 interface gets stuck in the LWIP library for about 210ms. And this time interval is always the same. Please tell me which way to look to solve this problem

Dear STMicroelectronics Support, I recently purchased two STEVAL-SPIN3201 boards. I initially attempted to connect them to my PC using a regular USB cable. The PC recognized the boards, but I encountered the following error when trying to program them: "ST-LINK not found target." To address this, I purchased an external ST-LINK debugger. After connecting it and trying to upload a test provided from ST MC Motor Workbench, I received a memory access error. I performed a chip erase which resolved the memory issue. However, I am now facing problems with UART communication. In Motor Pilot, I get the error: "No ST-LINK found", even though the debugger appears to be connected. I also attempted to connect the board via USB to TTL, but on STM32CubeProgrammer, I receive an error suggesting a problem with UART communication and asking to "Check Boot mode." Additionally, after the chip erase, the board is no longer recognized by the PC when using the regular USB cable, and I constantly get No S

Hi guys,I'm working on a pretty simple cable replacement client/server program to exchange data form one device to another.When I enable traces in CubeMX for the WPAN/BLE part, my STM32WB5 is visible (I can see it from my phone or using a Nordic USB Dongle, connect to it and exchange data). All traces go to USART1.Then, since everything works, I disable traces (CFG_HW_USART1_ENABLED to Disabled, CFG_DEBUG_* to Disabled, BLE_DBG_APP_EN to Disabled, etc.). At this point, I can't see anymore my device in the phone list even tough aci_gap_set_discoverable returns 0.I don’t understand how disabling traces can prevent the rest of the BLE stack from running.Any help on this would be appreciated.Thx !

HelloI am new to the STM32U5 and have problems with I2C communication via GPDMA.My transmit buffer consists out of ten messages that should be send.Strangely, only two write commands are written to the bus. However, this includes the first and the third buffer content of the Tx buffer - the second buffer content is not transmitted. After a new I2C start condition, no further content is written to the bus except the write address.This is the configuration of the GPDMA:In the case of using a falling or rising edge as the TriggerPolarity, only the starting condition is generated and readable on the bus. The behavior described above applies to the Masked polarity configuration as shown in the code.void DMA_memoryToPeriperhalInitSTC(uint8_t *I2C_RxDatabuffer,uint8_t *I2C_TxDatabuffer) { uint32_t I2C4_PeriperhalTxAddress = LL_I2C_DMA_GetRegAddr(I2C4, LL_I2C_DMA_REG_DATA_TRANSMIT); uint32_t MemoryS

I am confused about the limits of the FT pins on this MCU. I think I understand the maximum voltage on an FT pin except FT_c is Vdd + 4V as long as no pulls are enabled. So with 3.3V Vdd the max voltage on most FT pins will be 8.3V is that correct? Its a bit confusing where that footnote is placed.Beyond that, given the voltage limit is 8.3V how does it matter if the positive injection current limit is 0mA? That means I need an infinitely large resistor to prevent any injection current when the voltage is over Vdd. Or does N/A mean there is no current limit so long as the voltage is not exceeded?Thank you.

Hello,I have a problem with the operation of my firmware in "closed" state of PRODUCT_STATE. When my device is in "open" mode (ED code) my firmware works perfectly fine, but when i do provisioning procedure and change state to closed (72 code), my firmware works for a second and then hangs. In that state i cannot attach a debbuger to see what going on, so I have no idea why it doesn't work. My device has trust zone disabled, it is a custom PCB with STM32H523CET6.Thanks in advance for any help.

Is the internal bootloader on the STM32H723 DO-178 certified?   It just dawned on me that the whole line of CPUs might be disqualified for aircraft use because the bootloader code "flies" with the aircraft and all such code must be certified to the level declared by the system (DAL levels A-D).   Do you have avionics customers that use these?  Can the bootloader be erased?Regards,Mark

Hallo all:I want to implement a generic counter to count the number of impulses on an input, but after debouncing.I guess that mechanical switches for human interface purposes need a debouncing in the milliseconds range, say 1 ms to 20 ms. My Systick interrupt runs every millisecond, so I can sample the input there (with an appropriate prescaler implemented in software), which should take care of debouncing.If the input comes from a clean, high-speed signal, I can use a hardware timer like TIM1 in order to count impulses on input TIM1_CH1. I can do some level of debouncing with its built-in hardware input filter, but if the signal is clean, then probably no debouncing is necessary.The trouble is at mid input frequencies. I am thinking of some signal source which is faster than switches typical for human interfaces, but not completely clean (with some bouncing). Is that a plausible scenario at all?I am using an STM32F407. I have set APB1 to its maxi

Hello All,i want to implement bootloader in stm32g431rbt6 microcontroller using uart, I am looking for guidance and I would appreciate it if anyone could share useful resources, example projects, application notes, or tutorials specific to this MCU or closely related STM32G4 series chips.Thank you in advance!Best regards,

Hi,I have a piece of CRC calculating code that I nicked from somewhere a couple of decades ago. I've been wondering about a few lines: *CRCVal ^= (*CRCVal << 8) << 4; *CRCVal ^= ((*CRCVal & 0xFF) << 4) << 1;(CRCVal is a pointer to a uint16_t variable.)What I'm curious about is the slightly weird left-shifting notation. Shouldn't it give exactly the same result if it was written like this? *CRCVal ^= (*CRCVal << 12); *CRCVal ^= (*CRCVal & 0xFF) << 5;Does anyone have a hunch why the shifts are split up like this? Could it be something related to a specific compiler or device that handles half-byte shifts in a certain way?By the way, it would be great if this forum had a "General programming" board. I prefer to ask questions here, as I think that the community has a nice vibe.

Hello.I have problems turning BLE on and off on STM32WB55.Many examples with BLE start with the linesMX_APPE_Config(); MX_IPCC_Init(); MX_RF_Init(); MX_APPE_Init();I do the same, and it turns on right away. I don't know how to initialize the sequencer and timeservers by themselves without BLE, so for now, I found a workaround. I turn it off using the RTC timer using the code the esteemed @FilipKremen provided mestatic void BLE_exit() { tBleStatus ret; if (BleApplicationContext.Device_Connection_Status != APP_BLE_IDLE) { ret = aci_gap_terminate(BleApplicationContext.BleApplicationContext_legacy.connectionHandle, 0x13); if (ret != BLE_STATUS_SUCCESS) { APP_DBG_MSG("aci_gap_terminate(), Failed \r\n\r"); } else { APP_DBG_MSG("aci_gap_terminate(), Successfully \r\n\r"); } } ret

Hello,I'm having trouble establishing a working SPI connection between an STM32U585 and a sensor (LIS3DHH). The transaction looks great on an oscilloscope: Clock, CS, MISO, and MOSI are behaving as expected.This leads me to suspect that the MCU isn't receiving the data correctly. I'm using the low-level driver, but I've reproduced the same behavior with the HAL driver. It's important to note that I want to use DMA mode for performance reasons.I suspect a bug in my DMA or SPI configuration. After a transaction, the second byte of my rx buffer contains the value 0x00. When reading the WHO-AM-I register, however, it should contain 0x11 (this value is also output via the MISO line). I would greatly appreciate any suggestions.Here is the GPIO and SPI configuration (DMA below):LL_GPIO_InitTypeDef gpio_init_sck_miso_mosi = {0}; gpio_init_sck_miso_mosi.Pin = LL_GPIO_PIN_14 | LL_GPIO_PIN_13 | LL_GPIO_PIN_15

Split from Cmsis-DAP debugger in STM32CubeIDE as this is a new question about a different probe.Hi guys, sorry i haven't responded, i do not have the daplink anymore, i have it to a friend when i got a diy Blackmagic debug probe, and i have another problem:it works in gdb-multiarch but not in the ide, here is my configuration and gdb.txt fileinit:set lo

I'm experiencing an issue with the BLE_p2pServer example where CPU2 seems to fail to boot properly. Environment:Board: STM32WB5MM-DKIDE: STM32CubeIDE (latest version)STM32CubeProgrammer for flashing wireless stackExample: BLE_p2pServer from STM32CubeMX, imported to CubeIDE from .iocDetails: The application crashes during CPU2 boot sequence, specifically at LL_PWR_EnableBootC2(). UART debug prints show the execution stops during this operation:hw_ipcc.c:void HW_IPCC_Enable( void ){__SEV(); /* Set internal event flag and send event to CPU2 */__WFE(); /* Clear internal event flag */Debug_Print(">LL_PWR_EnableBootC2\r\n");LL_PWR_Enab

I am trying to use a G431 as an I2C device (slave). Unfortunately it can be made to latch up rather easily, getting stuck with an endlessly triggering I2C interrupt. It appears to be a flaw in the HAL code where it doesn't clear the interrupt flags, possibly due to its internal state machine being out of sync with reality. There are two situations that can cause this to happen. 1. The bus host (master) starts transactions back to back too quickly. Adding a 1ms delay between transactions fixes the problem.2. DMA is used for reception, but the host stops sending data early. I.e. HAL_I2C_Slave_Seq_Receive_DMA() is called with a certain buffer size, but the number of bytes sent by the host is less than that size. I thought that switching to interrupts instead of DMA might help, but it doesn't. It seems like the rate of interrupts triggering can cause the stuck-in-interrupt issue, but I have not deeply debugged

I am unable to get the USB bootloader to work on a custom board with an STM32F070C6. This board uses an 8 MHz crystal (chosen to avoid HSI issues when the HSE frequency is too high—due to space constraints, a lower-frequency crystal is not an option).For reference, I have another custom board (nearly identical in design) with an STM32F070F6, where the USB bootloader works correctly. On that board:With a 16 MHz crystal, the USB bootloader fails.With an 8 MHz crystal, the USB bootloader works as expected.The device is connected via a USB hub to account for the USB HUB issue.Tests Performed:Bootlo