Home arrow Support arrow Forums

Luminary Micro Forums
home | post reply | threaded view | PDF | help | rules
Boardwalk :: Forum List Luminary Micro Forums General Discussion
<< Start < Prev 1 2 3 4 5 6 7 8 Next > End >>

cb1

Platinum Boarder

2008/07/07 12:45

Re:CodeSourcery, DriverLib and first steps



Post edited by: cb1, at: 2008/07/07 12:46

login or register to reply

ravaz

Platinum Boarder

2008/07/07 14:15

Re:CodeSourcery, DriverLib and first steps

I hope you didn't misunderstood me. There absolutely no "battle" against the commercial IDE, and I agree with you that professional tools is the best choice from a bussines point of view.

I think the sentance
The open source solution can really be an alternative to commercial IDE if we can come out with a clear and detailled documentation.
is the cause of the misunderstanding. I wrote it in a moment of "euphoria"...


You already clearly listes the weak points of open source tools, just for par codicio I would like to list some good points of free tools (purely personal):

1)For their nature free tools needs more reflection in order to work, for that reason Engineers that use them are normaly able to go deeper in the problems. The pain is payed pack by a intellectual improvement.

2)Some of the free tools I listed should be ranked as professional. I'm talking about eclipse and GCC. Eclipse is just amazing and still improving very fast. GCC is the base of many professional tools.

3)A lot of source code is outside ready to be used, most of this code is compiled using free tools. Offen I saw people unable to use it and reinventing the wheel because unable to understand "how it works". The free solution is nearer to all those projects and the "intellectual improvement" mentioned on the first point will help you reducing time and energy.

4)There's a lot to do with 32kb of codes, but what about the day you reach the limit? You will be forced to make a compromise on your project or to pay the bill. If none of them is possible the third option (I completely disagre with that one) is to use illegal copies, this sound to me very stupid when outside there is a free and legal option.

5)Sometimes engineers get frustrated by bad managers that don't have your correct approach and will not agree to spend the 3k$ for a professional tool.



Regards

login or register to reply

ravaz

Platinum Boarder

2008/07/07 14:15

Re:CodeSourcery, DriverLib and first steps



Post edited by: ravaz, at: 2008/07/07 14:15

login or register to reply

femtotech

Expert Boarder

2008/07/07 14:34

Re:CodeSourcery, DriverLib and first steps

Hi,

I'm on the way... I can successfully compile example application with the CodeSourcery G++ Lite and Eclipse Ganymede.

Following the guide posted in this thread I configured OpenOCD to debug the code, but I run into some errors. I hope this is the last step I have to fix before I can begin to write code!

When I start debugging (after OpenOCD) I get:

Code:

 source .gdbinit
target remote localhost:3333
0x00000000 in ?? ()
monitor flash cond_write_image erase "D:FemtotechDevelopmentSourcery G++DriverLiboardsek-lm3s6965_revc    estgcchello.bin" 0 bin

SWJ-DP OVERRUN - check clock or reduce jtag speed
dcb_dhcsr 0x30003, nvic_shcsr 0x20000, nvic_cfsr 0x10001, nvic_bfar 0xe000edf8
JTAG failure -107

/* this error is repeated many times */

JTAG failure
Ignoring packet error, continuing...
Reply contains invalid hex digit 116
b ResetISR
No symbol table is loaded.  Use the "file" command.
monitor soft_reset_halt



I tried to decrease the Jtag clock speed but with no effect.

What should I check?

Marco

login or register to reply

ravaz

Platinum Boarder

2008/07/07 14:40

Re:CodeSourcery, DriverLib and first steps

in the debugger run command try to use this:

target remote localhost:3333
monitor flash cond_write_image erase "pathToYourBin" 0 bin
target remote localhost:3333

login or register to reply

femtotech

Expert Boarder

2008/07/07 14:56

Re:CodeSourcery, DriverLib and first steps

ravaz wrote:
in the debugger run command try to use this:


I guess you're talking about the initialize command. As described in your guide the run command should be:

Code:

 
b ResetISR
monitor soft_reset_halt
monitor sleep 500
continue
clear ResetISR



Anyway, the error is the same also in that way.

Marco

login or register to reply
<< Start < Prev 1 2 3 4 5 6 7 8 Next > End >>
Boardwalk :: Forum List Luminary Micro Forums General Discussion

Luminary Micro Forums