-
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
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
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.
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
-
Thread
Atmel announces ARM Cortex-M3 based Controllers
Star from Freescale) 16 bit and it is still used engine (max 2 cyl) and may leave room for more cheap 32bit. I admit I am not a very good connoisseur of ARM using for hobby now PIC24H (due to good price/performance) but for next year for sure I will happly go to 32bit core, ARM Cortex M3 or MIPS depending
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
-
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
: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 06 06 e7 f5 fd 16 2009-12-08 12:27:01 1)? 2009-12-08 12:26:01 @58.57 ERR04d2 3f b7 3d 45 91 08 04 55 ac 3c... 2009-12-08 12:25:07 <06> -D m32 s03 - V46 I1884 S1900 B2941 E00 2009-12-08 12:25:07 <06
-
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,
-
Thread
SD card lock and unlock
check out whether your SD card support lock/unlock. I have three SD cards tested, two from panasonic(32MB) and one from kingston(2GB),it seems the old panasonic card does not support this function, and the new kongston SD works well. You can use a mobile phone to check it. I don't know why Windows doesn't
SD 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
-
Thread
GCC 4.3
\src\stm32f10x_spi.o obj\Debug\lib\src\stm32f10x_systick.o obj\Debug\lib\src\stm32f10x_tim.o obj\Debug\lib\src\stm32f10x_tim1.o obj\Debug\lib\src\stm32f10x_usart.o obj\Debug\lib\src\stm32f10x_vector.o obj
\src\stm32f10x_systick.o obj\Debug\lib\src\stm32f10x_tim.o obj\Debug\lib\src\stm32f10x_tim1.o obj\Debug\lib\src\stm32f10x_usart.o obj\Debug\lib\src\stm32f10x_vector.o obj\Debug\lib\src\stm32f10x_wwdg.o obj