-
Thread
STM32 Changing PWM Duty Cycle in interrupt handler
aSma>> wrote in post #4970691: > The stm32f103 timer has only 16 bits. I assumed I needed to provide my data as uint32_t as the example from the SDK ( /STM32Cube_FW_F1_V1.4.0/Projects/STM3210E_EVAL/Examples/TIM/TIM_DMA/Src/main.c ) declares
stm32f103 has 20kb RAM. 8 ch * 64 pixel * 24bits/pixel * 1/8 byte/bits = 1.54kb With a 16bit timer you need about 3kb.
-
Thread
STM32 ADC & DMA corrupted Values
Are you using an STMF103C8xx or STM32F103CBxx? I am asking because the web is full of negative reports about fake products with wrong data transferred by DMA.
? Hi Lothar adcRawMemory is 288 Bytes and im sampling 6 channels. I2C Bus error could happen ... i have to check. whats the outcome if there is an error? >Are you using an STMF103C8xx or STM32F103CBxx? I am asking because the >web is full of negative reports about
-
Thread
STM32F103 math package
This is the overview of STM32F103 newly updated. It includes the clock tree of STM32F103 and more, hope it helps. https://www.embedic.com/technology/details/stm32f103
This is the overview of STM32F103 newly updated. https://get-9apps.com/web/ https://get-cartoonhd.com
-
Thread
GDB issue (cortex-M3)
, FTDI-drivers and STM32F103CB for the tests. Debugging from Eclipse works as expected (well, at least what I expected/needed). A little bit of additional information can be found in the readme.txt.
(): dcb_dhcsr 0x3000f, nvic_shcsr 0x20000, nvic_cfsr 0x0, nvic_bfar 0xe000edf8 Warning: 778 29500 cortex_swjdp.c:703 ahbap_read_buf_u32(): Block read error address 0x14, count 0x1 Error: 779 29500 gdb_server.c:1022 gdb_error
-
Thread
Eclipse & OpenOCD: AHBAP; Sticky und Mem Read Error
Hi everyone, I'm using the STM32-P103 board with Eclipse and oocd 0.2.0. my problem is that I can't use debugging. I use this for OpenOCD: gdb_port 3333 # Work-area size (RAM size) = 20kB for STM32F103RB device set
You can look here: http://www.mikrocontroller.net/articles/STM32#Demo-Projekte There is a link to "ChaN's FAT-Module with STM32 SPI" In this project is a complete Eclipse configurationwhere is working fine.
-
Thread
OOCD with the STM32F103
Good day every one! I'm using the STM32F103 series in an embedded application, together with OOCD. Now the 1st setup: STM32 Evalboard by KEIL with the STM32 in a 64 Pinout and 64 K Flash (STM32F103R8T6) Amontec-JTAG-Key OOCD r423 and r717 Worked just great :-) The 2nd setup: STM32 now in my embedded app. and with 48 pinout 64 k flash (STM32F103C8T6) Amontec-JTAG-Key OOCD r423 and r717 Didn't work! :-( Well it did work sort of, that is, OOCD finds the two JTAG-Devices inside
-
Thread
STM32 HAL Delay too slow
Hi, I recently started with an STM32F103C8T6 on a bluepill board. I am using SW4STM32 on Windows 10. When writing a program that blinks an LED on PC13 with the standard peripheral library and implementing my own SysTick_Handler
your own firmware. I give you a hint, how to do: https://www.mikrocontroller.net/attachment/316790/STM32F103C8T6.ZIP Just have a look into it - and use what you want if you are interested. btw: the binary in this archive should also work on a blue-pill board. W.S.
-
Thread
Helios GDB hardware debugging & JLink
gVectors, which has no line number information. HardFault_Handler () at src/vectors_stm32f10x_md.c:173 173 void HardFault_Handler (void) { while(1); } (gdb) #### and log of segger jlink gdb server: Select auto JTAG speed (2000 kHz) Writing 0x20000000 @ address 0xE000ED08 Downloading
STM32Test.zip may not be perfect for my STM32F103RBT6) I think my problem is with helios to gdb interface.
-
Thread
GCC 4.3
src\stm32f10x_can.o obj\Debug\lib\src\stm32f10x_dma.o obj\Debug\lib\src\stm32f10x_exti.o obj\Debug\lib\src\stm32f10x_flash.o obj\Debug\lib\src\stm32f10x_gpio.o obj\Debug\lib\src\stm32f10x_i2c.o obj\Debug
stm32f10x_can.o obj\Debug\lib\src\stm32f10x_dma.o obj\Debug\lib\src\stm32f10x_exti.o obj\Debug\lib\src\stm32f10x_flash.o obj\Debug\lib\src\stm32f10x_gpio.o obj\Debug\lib\src\stm32f10x_i2c.o obj\Debug
-
Thread
how can i debug code in ram ?
Sourcery G++ Lite Edition ,openocd and jlink on ubuntu 10.04.for the flash run,it work well.the MCU is STM32F103VE I download the start up code and link script from the web.I modify the link script to something like this: .isr_vector : { . = ALIGN(4); KEEP(*(.isr_vector))
I did test with STM32F103C8T6 ($3 chinese board, known as blue pill). The only thing I had to do is to write my linker script to put everything in RAM, then: 1. Put the jumpers at BOOT0 & BOOT1 pins to boot from RAM.
-
Thread
Which microcontroller to use and how?
, for example the STM32F103 series which is available in different sizes). Regarding your current monitor: If you measre the current between power supply and voltage regulator then you measure the current consumption
recommend to control the MAX5217 for the best results and more accurate? price is not important. the STM32F103 ?
-
Thread
STM32 GCC problem writing to flash bank 2
the code in the second sector. I was able to debug this code (using optimization level 0) on an STM32F103xD (which has 384K of flash) when unoptimized code was about 160K. However, the code has now grown to 220K unoptimized, 130K at optimization level 's'. Therefore I have been able to finish debugging
flash upgrade functionality on optimized code. To allow for future growth I have upgraded to an STM32F103xG, which has 1M of flash configured in two banks. I have been able to continue debugging, and I can run the flash upgrade into either bank when in debug mode. However, if I build the code at
-
Thread
Embeetle IDE free for all users, now supports Blue Pill and more.
and developed a visual debugger. Just recently, Embeetle IDE integrated the Blue Pill board. The STM32 Blue Pill is a 32-bit Arduino-compatible development board that features the STM32F103C8T6. A member of the STM32 family of ARM Cortex-M3 core microcontrollers. The STM32 Blue Pill board has nearly
Embeetle. https://www.kickstarter.com/projects/embeetle/embeetle-ide-integrating-wch-microcontroller-ch32v203 https://www.kickstarter.com/projects/embeetle/embeetle-ide-integrating-wch-microcontroller-ch32v003 As the Embeetle team grows, more and more MCU will be supported and we would love your precious
-
Thread
C++ STL and STM32
Hi, I have a problem with the C++ STL on the STM32. The following code works as expected on my hardware (chinese board with STM32F103..) [c] int main(void) { char Line[512]; std::list<std::string> *pHistory; pHistory
Hello Hase, I agree that I strain the stack a bit, but out of the 64k RAM in the STM32, I have less than 8k for .data and .bss sections. The remaining 56k are used for heap and stack. The initial stack pointer is set to the end of RAM and the heap grows upwards from the end of the .
-
Thread
Relative Jumps Only
impossible. If any questions are left, feel free to ask. Greetings, Lasse PS: Cortex-M3, STM32F103, Codesourcery GCC
Hi, it seemed so perfect, but it doesn't work. Code output is identical to compiling without -fPIC, my disassembly looks like: [code]0x0800185c <func+8>: bl 0x8001840 <func2>[/code] so no PIC at all. Has anyone got an(other) idea? Reading in the CodeSourcery List [1], i've found out
-
Thread
Using C++ Exceptions on Winarm 20080331 STM32 Target
HI All, I have recently installed WinARM 20080331 and created a test build for the STM32F103ZE target device. I am able to compile, link, and execute all 'C' code and some 'C++' code correctly. The problem appears when I attempt to use the C++ exception handling mechanism. I have
thinks terminate is called recursively? Here is the code for the library functions: #include <stm32f10x_lib.h> #include <sys/stat.h> //--------------------------------------------------------------------------// char * _sbrk_r (void * reent , unsigned incr) { static char heap_mem
-
Thread
embedding C source in the disassembler window
Anglia Electronics kindly sent me an Eclipse version of the STM32demo project. It includes a custom makefile, so it doesn't use any outside resource such as Solaris to create the makefile. I am trying to create my own project to emulate this with good success
shows that the commands used to build each module are typically: gcc -nostdinc -DLCD_ILI9320 -DSTM32F103x8B -IC:/Software/Mega_Link/Mega_Link/Include -Os -g3 -Wall -c -mthumb -march=armv7-m -ffunction-sections -fdata-sections -Wno-pointer-sign -o Source\usb_endp.o ..\Source\usb_endp.c and the linker
-
Thread
OpenHR20: Firmware for Honeywell Rondostat HR20E
2009-12-08 12:35:07 @07.49 ERR04dc 1a 06 9f 7b 8a e8 dc 5e b7 c3... 2009-12-08 12:34:07 @07.49 ERR04db 1a 06 51 80 12 51 cf e8 0a c6... 2009-12-08 12:33:07 @07.49 ERR04da 1a 06 7c d0 06 01 67 d6 97 c3... 2009-12-08 12:32:07 @
:29:07 @07.48 ERR04d6 10 06 80 aa d5 32 4d b3 48 ec... 2009-12-08 12:28:30 @30.11 ERR04d5 8c 70 ec 16 26 33 de ad 7c 2e... 2009-12-08 12:28:07 @07.48 ERR04d4 10 06 9e 84 0f 48 e1 6f 7b 6b... 2009-12-08 12:27:07 @07.45 ERR04d3
-
Thread
SimpleSerialTerminal
codes of the keyboard to the mapping table. The key scan codes were not straight from 112...123 for F1..F12, as can be seen in the attachment. I take the requirement for a more condensed representation in the monitor for decimal and Hex into account, thanks for your comment, Moby ;-) The requirements
during debugging of baud rate difficulties in a timer controlled bitbanging software serial of an STM32F103RBT ARM Cortex M3. If you wish a line feed carriage return in the monitor, your MIC has to send the #13 #10 chars. @Moby: which is the reason for better having a more condensed representation
-
Thread
Atmel announces ARM Cortex-M3 based Controllers
marked) but may enter in the segment with engines less pretensions replacing a good price the legendary C167 that is still present on the Renault and Ford cars and could be easily surpass by ARM speed and peripherals. A cortex M3 TI made with 20 channels Het, 16ch on 10bit ADC, DMA, 32KB RAM, 512MB flash
different manufacturers have differences, take the frequency for example, nxp lpc1700 is up to 100MHz, ST STM32F103ZE is 72MHz and Atmel AT91SAM3U is 96MHz. Meanwhile, they incorporate various peripherals, although most of them are the same. Before you choose these processors for your project, you shall evaluate