Well Keil will supply you with a (rather outdated to the best of my knowledge) version of GCC for use with their IDE, so yes you can use it if you are also using the Keil IDE. Other than that I'm not aware of any other method.
-- Regards, Richard.
17 official architecture ports, more than 6000 downloads per month.
Certified by TÜV as meeting the requirements for safety related systems.
Although you can use ULINK2 and the GCC compiler, the answer to your questions remains NO, you can not use ULINK2 with gdb or a linux debugger.It has to be uVision! You might want to have a look at Segger J-Link, which runs with GDB.
Some information about the J-Link and links to Segger and Yagarto, which you might like, can be found here:
There are other alternatives. I needed a gnu toolchain development environment for arm to support work for the next 2 or 3 years. Recently bought in some Embest kit for evaluation and once you get over the bias that it's Chinese, the hardware quality is pretty good. I bought the STDV710C board + windows ide + UnitIce usb / network based jtag emululator / debugger. The IDE looks suspiciously uVision like, but uses the gnu compiler etc with their own debug interface. My guess is that the ide framework is licensed from Keil and they integrate the gnu toolchain. Like uVision, everything is pretty much locked down, with all the ide functionality in dll's, though all the gnu tools (but not insight) are also there to use. Have used uVision extensively and it's pretty good, but there is little tweakability and you are pretty much locked in to the solution. The advantage of course is that it works out of the box and there's good support from the vendor and there are examples for dozens of different hardware boards.
I wanted to use UnetIce with the gnu toolchain + Insight over the network, rather than usb, but the later versions of Insight have the Angel Debug Protocol, which UnetIce talks, removed. Digging a bit more, found out that this was removed quite recently, because, to quote, 'to remove cruft and because it wouldn't build under windows'. However, adp is still quoted on the arm website as an active debug protocol. You could include adp back into later versions of the insight source tree, but how easy that would be, I don't know. Someone at CodeSourcery removed it afaics, so perhaps ask them. Network based debug boxes from Abatron talk a more direct protocol, which the later versions of Gdb/Insight does support, but that is 2 to 3 times the cost of UnetIce, for similar functionality. (UnetIce = $400 on one Canadian website).
As well as windows machines, am a long time user of Sun kit and wanted multiple hosting for flexibility. Still quite attached to makefile build environments and it seemed like a good idea to use a Sparc / Solaris 10 host for development, though could have been Linux or other unix. Building a slightly less recent version of Insight, which still had the ADP support and now have a more or less complete arm toolchain that talks to UnetIce over the network. Still some work to do, but both Windows and Unix development environments are working. The network based interface is more flexible and more robust electrically than the more common usb interfaces, which can be quite fragile in the presence of untied grounds, power surge, static, etc.
In summary, a worthwhile investment in time...
---------------------- Greenfield Designs Ltd Oxford, England