Home arrow Support arrow Forums

Luminary Micro Forums
home | post reply | threaded view | PDF | help | rules
Boardwalk :: Forum List Luminary Micro Forums Design Stellaris 2006
<< Start < Prev 1 2 Next > End >>

mthomas

Senior Boarder

2006/10/11 14:57

Some examples for the GNU toolchain

Maybe interesting for users of the GNU-Toolchain
http://www.siwawi.arubi.uni-kl.de/avr_projects/arm_projects/index_cortex.html

Martin Thomas

login or register to reply

LMI Eric

Moderator

2006/10/13 11:23

Re:Some examples for the GNU toolchain

I noticed the following text on the linked site:

This hardware can also be used to program and debug external targets (from Luminary and others i.e. by using OpenOCD)

That statement is not true. The DLL that interfaces to the Keil tools only works with Luminary devices since it is based on our DebugLib functions. Also, to my knowledge, OpenOCD does not support our devices (nobody has requested the DebugLib functions). Unless they implemented their own interface DLL, it is not supported.

As a side note, the DebugLib functions that the Keil DLL uses are available upon request from Luminary Micro. They are in static library format, compiled with Visual Studio 2005.

Thanks for making the GNU code available for others! I'm sure many people will find this useful.

login or register to reply

mthomas

Senior Boarder

2006/10/13 16:53

Re:Some examples for the GNU toolchain

LMI Eric wrote:
I noticed the following text on the linked site:

This hardware can also be used to program and debug external targets (from Luminary and others i.e. by using OpenOCD)

That statement is not true. The DLL that interfaces to the Keil tools only works with Luminary devices since it is based on our DebugLib functions. Also, to my knowledge, OpenOCD does not support our devices (nobody has requested the DebugLib functions). Unless they implemented their own interface DLL, it is not supported.

Ok, the statement has been misleading. I wanted to mention that the FTDI2232-circut on the board could also be used as a JTAG-interface for targets with another ARM-core. OpenOCD supports this type of JTAG-interface. OOCD can not "handle" ARMv7/Cortex-M3 yet but targets based on other ARM-cores. I changed the text. If hope it's now clearer. Anyway: it's just an additional idea and I think it's off topic in this forum.

As a side note, the DebugLib functions that the Keil DLL uses are available upon request from Luminary Micro. They are in static library format, compiled with Visual Studio 2005.

For commercial tool-vendors a static library for MS-Windows might be interesting. But those who do not use a Microsoft OS can not use it. Maybe your company can extend OpenOCD by Cortex-M3-support and provide patches to the OpenOCD-developer(s). This will mean that you have to open your source-code but should also increase the number of your customers (users who run Linux, BSD, Mac-OS etc.).

Thanks for making the GNU code available for others! I'm sure many people will find this useful.

Thanks for providing the driver-libary and the examples.

Martin Thomas

login or register to reply

c_oflynn

Junior Boarder

2006/10/16 21:38

Re:Some examples for the GNU toolchain

Hey,

Thanks for the link. I'm on Linux so was looking for GCC.. although from what I can tell, the contest itself HAS to be done in the provided Windows kit? Or at least made to compile in it for the final version...

Regards,

-Colin

login or register to reply

englere

Gold Boarder

2006/10/22 10:18

Re:Some examples for the GNU toolchain

Maybe your company can extend OpenOCD by Cortex-M3-support and provide patches to the OpenOCD-developer(s). This will mean that you have to open your source-code but should also increase the number of your customers (users who run Linux, BSD, Mac-OS etc.).

It's possible to use a closed-source binary proxy as an intermediary between the USB Stack and an open source JTAG driver and/or debugger. This is being done with the msp430 USB BDM devices, which similarly use a proprietary protocol. The closed-source msp430-gdbproxy enables the use of the TI USB JTAG tool on both Windows and linux with the gdb debugger, and this is 100% free and redistributable.

Also, although the CodeSourcery gdb drivers only work on Windows, the same rules that permit the use of these closed source drivers on Windows would also allow them to be used on linux, assuming they wanted to do that. The biggest problem with the CodeSourcery solution is that it's not free, and even their personal-use license seems a bit expensive to me.

My experience is mostly on the Windows side, and I'd like to help make an appropriate closed-source driver for Windows that can inter-operate with open source debuggers, but be freely re-distributable (unlike the CodeSourcery drivers). Once done, I could work with linux experts to make it work on that platform.

I may also port my own visual debugger to support arm targets to give users a simpler debugging solution than gdb/Insight/Eclipse out-of-the-box. This would be not be up to the level of most commercial toolsets, but would be simple to use and free (and open source aside from that one one driver). My previous open source work has been for the Freescale hc12 devices.

Eric
http://www.ericengler.com/EmbeddedGNU.aspx
http://www.ericengler.com/Pluto.aspx

login or register to reply

mthomas

Senior Boarder

2006/10/26 14:07

Re:Some examples for the GNU toolchain

c_oflynn wrote:
Thanks for the link. I'm on Linux so was looking for GCC.. although from what I can tell, the contest itself HAS to be done in the provided Windows kit? Or at least made to compile in it for the final version...

Yes, the contest-rules demand that "the project software must be developed using Keil's RealView Microcontroller Development Kit". Like you I think that this should mean the it must be possible to build the binary from the submitted source-code with the Keil-tools since it does not matter which tools have been used during development (I often prototype code for Microcontrollers with a PC application and there is no RealView for x86 targets). Since Keil/ARM is also sponsor of the contest I can understand this rule but users who can not effort the full license will face the 16kB-limit. With the GNU-tools there is (of cause) no size-limitation and it is not too difficult to port the code to the RealView tools before submission. I have tried to write a small "GNU to Realview porting"-document, preliminary but maybe useful: http://www.siwawi.arubi.uni-kl.de/avr_projects/arm_projects/Howto_gnu_rv.html

Regards,
Martin

login or register to reply
<< Start < Prev 1 2 Next > End >>
Boardwalk :: Forum List Luminary Micro Forums Design Stellaris 2006

Luminary Micro Forums