-
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
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
said, I didn't look into DMA before as my initial analysis was it > would need too much RAM. 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
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 the µC and than 'hangs': The output of OOCD with debug = 3:
-
Thread
STM32F103VET6 und CH340R
I have a problem with my PCB. I recieved it a few days ago and it is already completly presoldered. If i connect it via USB-TYPE B to my pc it is showing me nothing in device menager.... The CH340G should be visible to be able to programm it via usb.... If i connect it via micro-usb unknown device is popping up. But that does not help me :). I have added the schematic. Hope someone can help me.
-
Thread
Which microcontroller to use and how?
you want something larger then I would recommend any ARM based microcontroller, 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 of
recommend to control the MAX5217 for the best results and more accurate? price is not important. the STM32F103 ?
-
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.
.. 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 fake products with wrong data >transferred by DMA. the mcus are from the STM32F0xx and STM32G4xx Family. they should be
-
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 and
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
Problem with gnu ld and STM32
Hello, I'm trying to make anSTM32F103 work with the Code Sourcery tool chain. Using the attached ld command file, I get these errors: Invoking: Cross GCC Linker gcc -L"/home/Tommi/workspace/FWLib/Release" -Wl,-T ../SRC/STM32_Lnk.cmd
Thomas H. wrote in post #2576758: > Hello, > I'm trying to make anSTM32F103 work with the Code Sourcery tool chain. > Using the attached ld command file, I get these errors: > > Invoking: Cross GCC Linker > gcc -L"/home/Tommi/workspace/FWLib/Release" -Wl,-T ../SRC/STM32
-
Thread
STM32 GCC problem writing to flash bank 2
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 optimize
-
Thread
how can i debug code in ram ?
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
GDB issue (cortex-M3)
ARM-eabi 2009Q1, OpenOCD (different but rather up-to-date versions), Amontec JTAGkey, 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.
2009Q1, OpenOCD (different but rather up-to-date versions), Amontec JTAGkey, 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." I am also using Eclipse
-
Thread
connected DIN MIDI Out cable disturbs encoder
Hey, i am currently working on a MIDI related project utilizing a STM32F103 and a Hex Buffer (74HC365). I have the following problem: reading the encoder works fine (handled via interrupts) until i connect a midi cable to the midi out port, then the readings of the encoder
-
Thread
Relative Jumps Only
impossible. If any questions are left, feel free to ask. Greetings, Lasse PS: Cortex-M3, STM32F103, Codesourcery GCC
-
Thread
STM32 and SMBus
Hello everyone, I am trying to communicate with a MAX11068 from a STM32F103 over SMBus, but it does not work as expected. Has anybody worked with the SMBus and would be so kind to provide sample code? Michael
-
Thread
Interrupt handler in C++ File?!
Hi guy's I have the following problem. I'm using the STM32F103RB and Sourcery G++ Lite 2008q1-126 and I try to implement the Interrupt Handlers in a C++ File. I'm using C and C++ Code in my project and if I implement the handlers in a C File everything is
-
Thread
STM32 & ADC AD7699: fading SPI MISO level
Hey guys, I'm facing a problem working with an STM32F103RET6 and an ADC AD7699 (datasheet: http://www.analog.com/static/imported-files/data_sheets/AD7699.pdf). I thought maybe some of you might have similar experiences and could give me a hint. As you
-
Thread
Matrix/vector operations on a Cortex™-M3
Hello everybody! I am using a Cortex™-M3 based MCU (STM32F103VET6) and the gcc arm compiler for some project. As there will a lot of matrix/vector operations come along the way I would like to know if anybody has experience with maybe existing libraries concerning
-
Thread
SD card lock and unlock
card support, you would see a "password protection". I use the MOTO E6 to lock my card, and use STM32F103VBT6 to unlock, then use STM32 to lock and E6 to unlock, both works well. I use the SPI mode. If I cound help you, please email chairang<at>126.com
-
Thread
yagarto example project for STM32F100C4 chip
Hello, I'm new user of the yagarto tool-chain. The example project for STM32F103 works well for me. I'm going to move to simpler target chip STM32F100C4. It should be the Low density Value Line device (STM32F10X_LD_VL). I'm not sure how to setup-up project or how to modify linker
-
Thread
Problems with Helix MP3 Decoder
UnpackFrameHeader" [referenced from C:\IAR Systems\Embedded Workbench 5.4\arm\examples\ST\STM32F10x\ IAR-STM32F103ZE-SK\ARMP3\Flash Debug\Obj\mp3dec.o] Can someone give me help and tell me where can be the problem? Thank's everybody. Excuse me for my english, it's very bad.
-
Thread
STM32 GDB / OpenOCD Commands and Initialization for Flash and Ram Debugging
incorporated in a make file for flash vs ram building for this mcu, if this matters of course. mcu: STM32F103VET6 I am using Eclipse Helios with Zylin Embedded CDT, Yagarto Tools and Bins, OpenOCD .4, and have an Olimex ARM-USB-OCD-H Jtag adapter. I have already configured the ARM-USB-OCD and added
-
Thread
Helios GDB hardware debugging & JLink
and segger jlink appears to work correctly. (the yagarto STM32Test.zip may not be perfect for my STM32F103RBT6) I think my problem is with helios to gdb interface.
-
Thread
Macro for Interrupt Routine
this is also wrong.. Any ideas? Thx Kenan p.s. I'm working with codesourcery and the stm32f103
-
Thread
ARM fixed point vs. floating point
Hi, I'm creating application on ARM STM32F103VE. I have to multiply several matrix in very short time. I'm thinking about using Fixed Point, to speed up my calculations. So that I wrote union: typedef union fxpntu{ int full; struct
-
Thread
[STM32] Crossreference ChipID - Device (EN / DE)
ein Artikel davon machen. Best Regards, Schöne Grüße, Albert F. [code] <device type="STM32F103 (High Density)" coretype="CM3"> <core_id>0x1ba01477</core_id> <chip_id>0x414</chip_id> <flash_size_reg>0x1FFFF7E0</flash_size_reg> <flash_int_reg>0x40022000</flash_int_reg>
-
Thread
Wordclock stopped working
board_led_init... button_init... timer2_init... wpsbutton_init... Version: 2.9.5 Hardware: STM32F103 Display: WC12h LEDs: WS2812 GRB rtc is online eeprom is online ws2812: external pullup detected eeprom is online current eeprom version: 0x00000000 updating EEPROM to version 0x00020900..
-
Thread
C++ STL and STM32
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 = new std::list<std::string>; [ ... all the necessary initialisation ...] while (1) {
-
Thread
SimpleSerialTerminal
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
Embeetle IDE free for all users, now supports Blue Pill and more.
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 all the capabilities of the Arduino module but at a lower price. Check out Embeetle
-
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 read
-
Thread
Eclipse & OpenOCD: AHBAP; Sticky und Mem Read Error
debugging. I use this for OpenOCD: gdb_port 3333 # Work-area size (RAM size) = 20kB for STM32F103RB device set _WORKAREASIZE 0x5000 interface ft2232 ft2232_device_desc "Olimex OpenOCD JTAG TINY A" ft2232_layout "olimex-jtag" ft2232_vid_pid 0x15BA 0x0003 # script for stm32 if { [info
-
Thread
Atmel announces ARM Cortex-M3 based Controllers
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
-
Thread
openocd target program issue
also watch/modify openOCD commands/responses by "telnet localhost 4444" command. For target chip STM32F103, for me works: target remote localhost:3333 monitor soft_reset_halt monitor soft_reset_halt monitor soft_reset_halt monitor reset halt load monitor soft_reset_halt break main continue
-
Thread
GCC 4.3
YaWinARMteprelpack 2008/03" and it worked perfectly in my project. If somebody is interested a STM32F103 demo is included: http://sourceforge.net/projects/chibios/ It can be compiled with both the Codesourcery GCC 4.2.1 and WinARM GCC 4.3.0, it looks like the 4.3.0 is able to produce faster code