hi ,
i have been trying almost anything i could find over the internet to be able to do something.
I am using (trying to use actually) amontec key tiny, but i can set up any environment for it.
I tried openOCD/ eclipse / Gsourcery mostly, also tried IAR kickstart/GDB/openocd, under windows XP and ubuntu.
the debugger key is detected by windows XP, but it looks like i cant make openOCD work with the key.
I am not using the primer 2 ... i would have liked it, but it is too bulky for the application i wanted to do, so got a custom board off ebay. Might have been the first mistake but i dont think the board is at fault in my debugging problem. Here is the link for those who might be interested.
http://cgi.ebay.com/STM32F103RBT6-Devel … 2c52e0effc
You can find it here too with a proper Jlink debugger for a couple more $.
http://cgi.ebay.com/ARM-Cortex-M3-JLINK … 4018r28734
Anyway, i know i WILL have issues later with the board itself, as i will need the display to use SPI to free some pins, but i first need to get a program up and running on it. I wanted to use the debugger to install a simple adapted blinky prog, but i really cant.
here is the .cfg i have been using :
#daemon configuration
telnet_port 4444
gdb_port 3333
#interface
interface ft2232
ft2232_device_desc "my custom board"
#jtagkey taken from amontec
ft2232_layout jtagkey
#vid pid taken from amontec
ft2232_vid_pid 0x0403 0xbdc8
#slow but should work
jtag_speed 10
jtag_nsrst_delay 500
#jtag_ntrst_delay 200
#my evaluation board has only srst
reset_config srst_only separate
#jtag scan chain <= maybe this is at fault ?
#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
jtag_device 4 0x1 0xf 0xe
#target configuration
daemon_startup reset
#target <type> <startup mode>
#target arm7tdmi <reset mode> <chainpos> <endianness> <variant>
target cortex_m3 little run_and_halt 0
#target cortex_m3 little run_and_init 0
# 4k working area at base of ram
working_area 0 0x20000800 0x1200 nobackup
# all ram
#flash configuration
flash bank stellaris 0 0 0 0 0
openOCD just crashes telling me this first :
unable to open ftdi device: 2
ListDevices: 2
0: Amontec JTAGkey A
1: Amontec JTAGkey B
i have now been trying to work this out for 3 weeks and it really is driving me mad. If someone knows how to get a proper working something, please, tell me 
(
i am used to use these tools once installed (it is my job) but this is the first time i have to set this up, and i really cant 
