Home arrow Support arrow Forums

Luminary Micro Forums

<< Start < Prev 1 2 3 4 5 6 7 8 Next > End >>

ravaz

Platinum Boarder
Click here to see the profile of this user

2008/07/04 16:17

Re:CodeSourcery, DriverLib and first steps

If you want to compile by cmd line you should use:




arm-none-eabi-gcc -mthumb -mcpu=cortex-m3 -MD -Dgcc -o gcc/gdb.o -c ../../../utils/gdb.S


arm-none-eabi-gcc -mthumb -mcpu=cortex-m3 -O2 -MD -std=c99 -Wall -pedantic -DPART_LM3S6965 -c -Dgcc -o gcc/hello.o hello.c


arm-none-eabi-gcc -mthumb -mcpu=cortex-m3 -O2 -MD -std=c99 -Wall -pedantic -DPART_LM3S6965 -c -Dgcc -o gcc/rit128x96x4.o ../rit128x96x4.c


arm-none-eabi-gcc -mthumb -mcpu=cortex-m3 -O2 -MD -std=c99 -Wall -pedantic -DPART_LM3S6965 -c -Dgcc -o gcc/startup_gcc.o startup_gcc.c


arm-none-eabi-ld -T ../../../gcc/standalone.ld --entry ResetISR --gc-sections -o gcc/hello.axf gcc/gdb.o gcc/hello.o gcc/rit128x96x4.o gcc/startup_gcc.o ../../../src/gcc/libdriver.a c:/program files/codesourcery/sourcery g++ lite/bin/../lib/gcc/arm-none-eabi/4.2.3/../../../../arm-none-eabi/lib/thumb2/libc.a c:/program files/codesourcery/sourcery g++ lite/bin/../lib/gcc/arm-none-eabi/4.2.3/thumb2/libgcc.a


As you can see you are missing some file to be compiled (startup_gcc.c, gdb.S and rit128x96x4.c). You also didn't correcly add the libDriver.

You could try to start from the example workspace I posted and change the makefile in order to compile your project.


Regards

Post edited by: ravaz, at: 2008/07/04 16:19

login or register to reply

femtotech

Expert Boarder
Click here to see the profile of this user

2008/07/04 17:01

Re:CodeSourcery, DriverLib and first steps

Thank you for your answer.

I'll try that way for my own knowledge, but the boss wants I use the Eclipse IDE with arm-stellaris-eabi-gcc :(
He's going to order the Personal Edition.

I read thought the documentation but I didn't find a detailed start guide which shows how to include whatever should be included and how to properly setup the IDE.

Another thinh I don't understand is why if we use the Code Sourcery we need to include gcc stuff, like startup_gcc.c. I know CodeSourcery is gcc-based but I can't imagine what startup_sourcerygxx.c is used for.

I'm quite confused and frustrated... :(

Marco

login or register to reply

phomann

Senior Boarder
Click here to see the profile of this user

2008/07/07 01:37

Re:CodeSourcery, DriverLib and first steps

Hi Marco,

I purchased the personal edition and have had it for almost 12 months. I'm not sure I'm going to renew it. You understand that it is a $250.00 per year licence.

The reason I'm not that happy is that it doesn't really add much. They have a debug sprite that is mean to allow debugging, but I have found it very unreliable. Also it has it's own make cs-make.exe. This is not compatible with the standard make that comes with the LM driver lib. You need to edit the all the make files in the library, or use the version of the library that CS supplies. They have only release 2 versions, so it it not up to date.

I purchased the personal licence as I wanted an easy integrated environment to speed up my learning curve. This was mainly for the debugging features, that I can't get to work reliably. I believe that it has slowed my down.

I think I'm doing to go back to the command line compiler, called from the PSPad editor. As for debugging I'll try the open OCD route.

The other thing also is that Eclipse seems to be very restrictive on how to setup projects, but then it could be my lack of knowledge.

I reckon I've probably used about 6 weeks of the 12 month licence, I give it a go get so frustrated and drop it for a few months before going back again.

I'm desperate to convert some of my products from Microchip PIC products to an Arm. I love the LM chips and their features, but to get the development environment up and running seems a hurdle at the moment. The MPLAB IDE does make things a lot easier.


In the end I don't want to spend my time fighting a development tool tring to get it to do something that should be very basic, like build the LM libs.

Cheers,

Peter.

login or register to reply

femtotech

Expert Boarder
Click here to see the profile of this user

2008/07/07 05:23

Re:CodeSourcery, DriverLib and first steps

phomann wrote:
I purchased the personal edition and have had it for almost 12 months. I'm not sure I'm going to renew it. You understand that it is a $250.00 per year licence.

Argh! I didn't understand this! On the CodeSourcery page there is no mention of the limited-time license, as far as I see! Thank you for the info. :o)


What you said is very interesting, indeed.
I should reconsider once time again using the Lite edition.

Thank you again
Marco

login or register to reply

ravaz

Platinum Boarder
Click here to see the profile of this user

2008/07/07 07:29

Re:CodeSourcery, DriverLib and first steps

I also agree with phomann opinion. For me there are two choises for the IDE. The first is to use a real professional one like IAR ou KEIL (and paying the price for).
The second one is to use free solutions like the one I'm using.
Going to cheap commercial solution can make wasting your time.

Using a free solution can be painfull at the beginning, but after a while you will really understand all the process behind the IDE. Another positive point of this solution is that you can "easily" port to another architecture once needed.

If you are going to use the solution I proposed I will apppreciate if you could give me your feedback. I had also some headache before finnaly make everything working correctly. With your feedback we could improve the documentation and help other people on this task.

I also belive somebody here know the open source softwares better than me, please give your feedback as well...

The open source solution can really be an alternative to commercial IDE if we can come out with a clear and detailled documentation.


CB1 proposed a self installing preconfigured archive, I would like to help on this point but I'm not sure the license of those software permits the distribution. Does anbody know if if all the software I listed in the environment setup can be distributed by a third part?
In the case of a distribution does anyone have a domain we could use for that in order to put the documentation and the files somewhere else then in the forum?


Regards

Post edited by: ravaz, at: 2008/07/07 07:42

login or register to reply

cb1

Platinum Boarder
Click here to see the profile of this user

2008/07/07 12:45

Re:CodeSourcery, DriverLib and first steps

Gang-

As past college educator, small biz owner (took firm public) I've watched this Dev. Tool "saga" with growing concern. Running a new small biz my contacts/friends are mainly other small biz owner/operators - (IBM ain't calling)- following are our "combined" small-biz views...

1) At least ONE-THIRD- perhaps ONE-HALF(!) of the forum problems reported are caused by Dev Tool issues! Not "just" an LMI issue - ALL ARM forums have similar Dev Tool sagas. Yet strangely - the "unrecoverable" blood, sweat, tears investment continues...

2) Simpler - richer supported Dev Tools ARE available. (IAR, Keil are two we've used) Code-size limited versions are provided FREE - with no time restrictions.
256KB versions cost around $3K - but much can be done in 32KB.(free)

3) Cart BEFORE Horse! You "potentially" save $3K by "overcoming" the "mine-field" provided by "almost free" Dev Tools. What is your time worth? What do you do when a NEW problem arises? When a new micro is released? (new features/libs) When you have to "teach" a new employee "how" to successfully use your "cobbled" system? (of course you've fully documented ALL of your procedures/inclusions...)

4) Success of your new product. If your design succeeds - paying $3K for a simple, documented, straight-forward Dev Tool is a no-brainer. You have a paid, trained tech support group. Getting to market EARLY is crucial to product profitability. Overcoming Dev Tool issues STEALS productive time/effort/funds from your product. (and is immensely demoralizing!)

5) What biz are you in? We seek to deliver the best features, functions, performance using our LMI micros. We blend the micro with other, new "advantaged" parts so that we can "best" compete! We conceive then write the best code and exploit the micro's features/capabilities. We ARE NOT seeking nor interested in "how" you overcame the free Dev Tool battle. (and we ARE hiring)

Again this writing is the consolidation of several small biz owners w/in US/Eur. We are reacting to the "apparent" LOSS of much productive time by a large group of talented, motivated individuals. We have no tie to the commercial Dev Tools mentioned - my goal was to provide a manager's perspective to, "I've got this great new ARM micro - NOW What???"

login or register to reply
<< Start < Prev 1 2 3 4 5 6 7 8 Next > End >>