Newbie catch22 problem with JTAG dongles

Hi,
At least I feel it's a catch 22 problem.
I have two working JTAG dongles, one from Olimex http://olimex.com/dev/arm-jtag-ew.html
and one j-link from Segger/IAR and noone seems to work with the free version of ARM tool.
I cannot afford a third.
I built one simple blinking example for the STM32F103ZE (?) under the .../boards/ST directory.
I got one error complaining that my installation is non-standard and could not figure out where the wrong path is stored, but after copying the needed libraries to the wanted path everything went well and I got a blinky.hex file in the obj directory. Fine, but how to download it to my target. No option for binary output what I could see.
Reading the help file I found
FromELF --bin --output=out.bin blinky.axf
Error: no license
OK, I know but I got the hex file !
Is there no way to download my file within Keil?
Well, hex2bin blinky.hex
OK, this gave me a binary file I can use with
stm32loader.py -p com15 -e -w blinky.bin

Building the project went very smooth and quick but the last part could maybe be easier.
Any hints from old gurus?
Thanks for reading,
Bo in Finland, not US

 try

options for target/utilituies/settings has an entry for Signum

Erik

 RE: Newbie catch22 problem with JTAG dongles

You can add post-build steps to call your scripts (Project|Options|User). I use that to launch the hex2bin for my project.

 RE: Newbie catch22 problem with JTAG dongles

Thanks guys!
It worked!
Well, my blinky worked after few weeks of struggle with all kind of obscure problems a typical newbie get stuck with. I know we should first read all about it, the C-bible, the tool and debugger with all it's documentation and then the MCU data sheet, programming manual, reference manual and all errata and when we are finished we have lost interest of the whole thing because we never even got to the blinking led. That's why you brave guys are so important not only to me but also to all other newbies in similar situation reading about it. I'm the hw guy who basically knows how the hw works but sw is another world and it takes some time to learn starting near zero. Some learn by doing and some by reading and I'm in between. A small example is very useful and blinky is a good start. Then all the reading make more sense. I also think the compiler and linker is very unforgiving and demands precise input. Hope that will change to more human like response later.

I tried the Signum debugger option but I'm now on Win7 so the Olimex driver don't install complaining about a missing usb dll. I need to install Keil on my xp where it works and try again.

I also tried the post processing feature but did some typo error I guess as it hanged there. Maybe I later make a bat file and try again. Now it also works outside Keil so I got blinky to work.

My next task is to get the LCD working, that would be great. I sure will search the forums for graphic LCD setup hints.

Thanks again,
Bo