-
Article
Datei:WordClock24h-an-STM32F103-C8T6.png
Anschluss-Skizze WordClock an STM32F103 Mini Development Board
-
Article
STM32 jump to bootloader
app.c. app.c ohne fwlib/HAL. Beispiel. Der folgende Code-Ausschnitt zeigt die ISR des USART1 eines STM32F103. Der Code sammelt alle empfangenen Bytes und zählt mit. Sobald 32bytes oder ein '\r' empfangen wurden, wird der String verglichen. Ist dieser "GBL\r", springt er in den Bootloader. Auf dem Programmier-Computer
-
Article
Datei:STM32F103C8T6 MiniDevBoard Schematic.png
STM32F103C8T6 MiniDevBoard
-
Article
Datei:STM32F103C8T6.png
STM32F103C8T6 Mini Development Board
-
Article
STM32 Eclipse Installation
Olimex ARM-USB-OCD FW-Lib 3.4.0 von ST Start-Up Code als C-Datei, keine einzige Assembler-Datei Für STM32F103RB (128K Flash) wegen Initialisierung Stack-Pointer Nutzt make Tool, muss aber zu gmake umbenannt werden, ist weiter unten beschrieben Installation. Installation von Eclipse. Damit Eclipse gestartet
und LD Linker-Datei src: die eigenen Quellcodes makefile Das Projekt wurde geschrieben für den STM32F103RC (256K Flash/48K RAM), läuft aber auch mit einem STM32F103xB da der Stack-Pointer auf 20K initialisiert wird. Details stehen in der Datei "src/stm32f10x_vector.c", Zeile 29,30: Damit wird der Stack-Pointer
-
Article
STM32F10x Standard Peripherals Library
programming manual Cortex-M3 eigene Peripherie (wichtig zb. NVIC) Datasheet des verwendeten µC Types (zb. STM32F103xC/D/E) Pinout des µC und alternative Verwendbarkeit der PINs Download from Documents and files for STM32F family Die ST Standard Peripheral Lib in CrossWorks. Aufgrund mehrfacher Anfragen, hier ein
-
Article
Datei:3pcs.jpg
Auf dem STM32F103C8T6 Entwickler Board sind BOOT0 und BOOT1 vertauscht beschriftet. Auf dem roten ST-Link Emulator ist das Plastik etwas aufgeschnitten. Auf dem blauen ST-Link Emulator sind CLK und TCK sowie DIO und
-
Article
STM32F103C8T6 Boards
Hauptsächlich aus China gibt es preiswerte STM32F103C8T6 Boards in 600 mil und 1300 mil Breite. Pinbelegung. Nachfolgend die Pinbelegung beider Versionen: Pin Name 600 mil 1300 mil Type POR-Fct Default Remap 1 VBAT 1 5 S VBAT 2 PC13-TAMPER- RTC(5)
-
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
[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>
-
Article
MP32F103-Stick: Ein Mini-Mikrocontroller-Board mit USB und bis zu 4MB Datenspeicher
Einarbeitung in diese Materie veröffentliche ich hier ein kleines Board mit dem Mikrocontroller STM32F103CBT6 von STMicroelectronics (www.st.com). Dieser Chip hat 128KB Flash, 20KB RAM, SPI, I2C, USART, USB, CAN, ADC und läuft bis 72 MHz. Das Board wird genauso aufgebaut sein wie mein MP2103-Stick: LINK
Betriebssysteme vom Hersteller FTDI-Chip angeboten werden. Funktionsmodell. LINK: Datasheet vom STM32F103CBT6 LINK: st.com-Page vom STM32F103CBT6 LINK: Datasheet und Anwendung vom AT45DBxxx LINK: Datasheet vom TPS62203 Schaltplan. Herzstück des Boards ist der Mikrocontroller STM32F103CBT6 (IC1) mit 128kB
-
Article
SportTracker
GPX-Datei Entprellen von Tasten Hardware. Im Moment läuft alles noch auf einem Keil Starterkit mit STM32F103ZE Controller. D.h. ein Schaltplan mit Layout ist noch nicht erstellt. Controller Pinning. Der Controller des SportTrackers ist aktuell wie folgt beschaltet: Pin Nr. Pin Port Config Funktion 70 PB11
-
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
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
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 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
-
Article
Benutzer:Avr-frickler
Discovery. stm32flash - Flash-Tool für STM32-Boards mit Bootloader (serielle Schnittstelle z.B. ET-STM32F103. Eclipse Plugin - Eclipse Plugin für diverse Toolchains. Artikel auf µC.net STM32_Eclipse_Installation - STM32 Toolchain in Eclipse integrieren. (Windows) STM32F10x_Standard_Peripherals_Library -
-
Article
BusAnalyzer
better. Maybe Qt should be considered as alternative. Hardware (Prototype). Interfacing FT2232H and STM32F103. Both devices are connected using their USART interfaces. A partly handshake is required because otherwise the FT2232H sporadically seems to loose some bytes. The STM32F103 provides 3 USARTs. The
for the bus powered configuration can be found in the FT2232H Mini Module datasheet. Interfacing STM32F103 and a CAN Transceiver. The CAN interface of the STM32F103 consists of CANRX and CANTX. Default pin configuration: PA11/EXT1-1, PA12/EXT1-3 Remapped pin configuration: PB8/EXT1-16, PB9/EXT1-17 A PCA82C250
-
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
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.
-
Article
Datei:Stm32F103xc.png
STM32F103xC-E
-
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
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
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
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.
-
Article
Datei:Stm32 aufbau.jpg
STM32F103xC STM32F103xD STM32F103xE High-density performance line ARM-based 32-bit MCU
-
Thread
Macro for Interrupt Routine
this is also wrong.. Any ideas? Thx Kenan p.s. I'm working with codesourcery and the stm32f103
-
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
Relative Jumps Only
impossible. If any questions are left, feel free to ask. Greetings, Lasse PS: Cortex-M3, STM32F103, Codesourcery GCC
-
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
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
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
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
-
Article
Datei:ARM USB Test.zip
Beispiel für die Nutzung des USB-Ports an einem STM32F103 als Virtual COM Port
-
Article
Datei:Timer2 STM32F103 1.0.rar
(Beispiel Projekt für die verwendung von Timer 2 mit Interrupt)
-
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
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
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
-
Article
Diskussion:Reichelt-Wishlist
Conrad bekommt man die) Alles spricht von ARM-CortexM3 nur Reichelt nicht. ARM-Cortex-M3 z.B. die STM32F103-Serie von ST.com -> Reichelt nö; es wird nur die super neue ST6-FAMILIE, 8-BIT angeboten. Generell fehlt mir so ein bischen Innovation im Bauelemente-Segment bei Reichelt. Es kann nicht sein, dass
-
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
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
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