Your server rejected my original post, and I can’t figure out what is triggering this, so here is a cut down version:
I have an STM32F103B eval kit with IAR Workbench, which expires in 30 days. I set up Codesourcery, YAGARTO, and OpenOCD. However, I have the stupid IAR J-link which isn’t supported by OpenOCD. It appears I have to use Segger’s J-Link GDB server–is this really the case?
When I build my code with Codesourcery’s arm-none-whathaveyou GCC compiler, I get two files, a .elf that is too big to fit on my board (128KB on the board vs 140 KB .elf file) and 12KB .bin. When I try to load either through Eclipse using the Codesourcery arm-none-whathaveyou-gdb, I can connect to Segger’s J-link GDB server, but it appears that Segger’s GDB cannot download the code to the STM32 board. However, IAR workbench was able to do this. Does anyone have any suggestions?
I did some more research.
Is there any simple way to use the IAR J-link without the Segger J-Link GDB server?
Is Idealist a good option?
I am running into the same issues. I am working on an NXP but the experience is the same. Here is what I have found so far:
-
Segger J-Link without a license limits you to 32K when using GDB. No flash programming allowed without a license.
-
OpenOCD in its normal distribution does not include a JLink driver. There is, however, a patch is available here: http://www.shumatech.com/files/jlink.patch
(I found his how to on another site but I can’t find that link right now)
Now, the tricky part. I can not make the patch work. This is partially because I have no idea what I am doing. I am an embedded guy. 
It looks like you need the full cygwin tools with gnu to recompile the code. And the patch itself may patch only against an older OpenOCD release. 
I’d like to crack this nut as well…