Forums

Hi,

I have got the same errors but I have MSP430G2553 and the latest CCS.

error #10016-D: --abi=eabi not supported when producing TI-COFF output files
fatal error #10011: cannot continue with specified options; aborting

I am also looking forward to receiving the solution.

Thx.

Same here... !

Hmmm... hard to start something with an Error (10016 & 10011)

Any solutions?

Thanks.

 Hi all, COFF has nothing to do with windows and administrative login, it seems to be a linker error: simply this extended code is not supported, to solve the trouble the code generated from grace is needed to, set the same port with two different part and inspect what is different in the bad and good one.

Yes! Yes!

Windows, administrative rights....Nice!

Sorry, but I don't get that...I try to "learn something here" but first I have to figure were it is the problem...  software or computer.

If I was soooo smart why to use This Smart Software.

I had play with some ARM7 with Eclipse but the problem, always, was to config Eclipse and Processor start-up file. The rest was just "Try and Learn" or "Slow and Go"...!

Inspect a configuration what suppose to BE CREATED AND INSPECTED BY THE SOFTWARE? Do I have to reverse engineering the software too?

What was the purpose of this "easy" software?

Thx.

Bogdan Toma

Windows, administrative rights....Nice!

 Hi Bogdan, this appear as worst to me, I am using Linux and still CCS for Linux has some problem, I got the winzz version and more problem arises from....

 Grace is a still new software so be patient till all issue were eliminated, a big remake is in progress and sometime remake of thing insert new threat not so simple to catch and fix.

 The purpose of this software I never used is to simplify peripheral register programming and help user to do that cumbersome task. If you wish to use some feedback to distributor sending errors and malfunctioning part can help refine to a better product.

Hi all,

It's not totally clear to me what is causing your issue because I'm not sure what version of CCS and Grace you are using.  If you are using CCS 5.2.0 Beta1, you *might* be seeing an issue with ELF vs COFF settings when building with Grace.  I am now looking at CCS 5.2.0.00044 (i.e., Beta2), that has a number of improvements in this area as well as an update to Grace.  This was only released last week, and if you are a CCS 5.2 user and have not yet updated to .00044, then I would suggest doing so.  If the issue you are seeing has been resolved in a later release then great, but if not then I would like to reproduce the issue on my end.

Thanks, Dave

OK, we looked into this further and I think I understand what you are encountering.

In CCS 5.2.0, the product was changed so that the Linker's build output format is now ELF (rather than COFF).  When you are building a Grace project, the project's RTSC Target (which contains information about the selected device, compiler and linker) must be correctly set.  However, the change to the ELF default exposed a bug in which the RTSC target does not automatically get set up correctly.

This is a known bug and I thought the fix was due to be included in the CCS 5.2.0 Beta 2 release, but unfortunately it was delayed to the Beta 3 release, which is scheduled for April 17.

In the mean time, here is the easiest work-around procedure that I could think of.  After you have created a Grace project:

1) Open the project properties window.

2) Under the Main tab Advanced Settings section, change the Output Format from "eabi (ELF)" to "legacy COFF".  Then change it *back* to "eabi (ELF)".

3) Select the project properties RTSC tab.

4) The target should now be (correctly) be set to ELF (i.e., "ti.targets.msp430.elf.MSP430).

5) You will need to select an appropriate platform.

6) Click OK.  The build should then work.

Thanks for your patience while CCS 5.2.0 goes through its beta cycle.

Dave

Bogdan Toma

Windows, administrative rights....Nice!

The problem is that the latest OS version often changes some default permissions (worst example: when moving from XP to Vista) and things that worked when the application was developed, suddenly stop working. For most cases, there is an automatic workaround applied (e.g. the 'roaming' folder structure and the virtual folde rmapping), but in some more complex cases, things simply stop working.

And software developers often don't use the latest OS versions, because the migration would break their development tools.

It's a hen-and-egg thing.

However, some errors shouldn't happen if the software has been thoroughly tested on all usual platforms before release. Or at least there should be an FAQ entry with a workaround.
But maybe there is, and you just didn't see it?

Jens-Michael Gross

And software developers often don't use the latest OS versions, because the migration would break their development tools.

It's a hen-and-egg thing.

 You are right, I still use XP SP2 (LOCKED!!!) due to I don't wish toss money to M$ (they got from me for a Vista licence I removed and wasted out) and I cannot pay a fortune to buy again programmer and tools I wish to use. Vista and 7 remove FDD and parallel support, I need both so I NEVER wish to DOWNGRADE to vista nor seven nor amenity of M$ too.

 I am tired of be constrained to pay for something I don't use and suffer of thirdy party (UIF and some EZ430) hardware burnt out due to an upgrade.