Ask questions, find answers, and share insights on STM32 products and their technical features.
Hi, I am working with STM32F407VETx and it has total 192kb RAM, but its split into 3 regions:#define SRAM1_BASE 0x20000000UL // SRAM1(112 KB) #define SRAM2_BASE 0x2001C000UL // SRAM2(16 KB) #define CCMDATARAM_BASE 0x10000000UL // CCM(core c...
Hello,I am looking for a list of cycle counts for each instruction in the Cortex-M33 processor. For the Cortex-M4 processor, the ARM Technical Reference Manual includes a table of cycle counts for each instruction. The M7 ARM TRM doesn't seem to ha...
I'm trying to read the built-in temperature sensor on the MCU we're using (STM32L011F4P6)We only have the one calibration datapoint, so I can't use the temperature conversion function I'm familiar with.The code is as follows:int32_t analog_get_temper...
Hello, I have two custom boards based on the STM32G0B1CBU. When I try to program them via the SWD interface (using ST-LINK or SEGGER J-Link), I get the "No Device Found on Target" error. I checked the schematics and used an oscilloscope to make sure ...
STM32H743i-EVAL w/BSP V1.11.0SD Cards: 16GB SanDisk MicroSDHC I C4 (circle C with number inside) 16GB SanDisk MicroSDHC C2Both cards are supposed to be V2.0. Both work in all the SD devices (cameras, PC, thumb drive adaptors, USB readers). ...
Hi, I have a question about using a STM32l4+ Discovery Kit ( STM32l4S5 / b-l475e-iot01a ). I’m trying to use both microphones with the DFSDM function with DMA and send it to a PC COM-Port using UART (USART1). To program the Microcontroller I’m using ...
We have a new design using the STM32G474 and are having some weird issues with the SWV utility. Current setup:STM32Cube IDEST-Link V2-ISOL Debugger using SWCLK, SWDIO, and SWOSWD connection to micro with 33 ohm termination resistorsSWO was wired manu...
I use Modbus RTU 8N1 with 9600 bd. I always have sent the same 8 byte request. The first byte of the message is 0x01.In about 85% of all tests the STM32 evaluates the request correctly. In a 15% of all tests the first byte is evaluated as 0x80 or 0x...
