Information on building required KSDK libraries.

cancel
Showing results for 
Search instead for 
Did you mean: 

Information on building required KSDK libraries.

Jump to solution
427 Views
davepfaltzgraff
Senior Contributor I

I am working on a KSDK project using PE. When I add fsl_i2c and try to compile, the linker is unable to find:

 

C:/Freescale/KS_2.0.0/eclipse//../toolchain/arm-none-eabi/lib/m4/fp/v4-sp-d16/libc.a

 

It would be nice if there was a single placed that listed which libraries could be found where, but I haven't stumbled on it yet.

 

Thanks

Labels (1)
0 Kudos
1 Solution
104 Views
davepfaltzgraff
Senior Contributor I

The basic problem is the maximum line limitation found in Windows. For the correct solution see Re: Re: KSDK Linker Error - Command line too long

View solution in original post

0 Kudos
7 Replies
104 Views
davepfaltzgraff
Senior Contributor I

There's something else going on here that doesn't make sense to me. I repeated the process and got the same error but this time for libm.a. I have checked and both are in the Project=>Properties=>C/C++ Build=>Settings=>Cross ARM C++ Linker=>Miscellaneous panel.

So, any suggestions welcome!

0 Kudos
104 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hi David ,

Could you upload your project ?

And what's the version of your KSDK ?

BR

Alice

0 Kudos
104 Views
davepfaltzgraff
Senior Contributor I

Hi Alice,

First, to answer your question, I'm using KDS 2.0.0with KSDK 1.1.0 on a

Windows 7 system. The KDS and KSDK are both installed to C:\Freescale.

My project is located at C:\Projects\Rebuild.

What I did this morning is build up a new project from scratch. I used

PE to load all the components needed. Once I had the same structure as

my original project, I generated the code and compiled. Since that was

clean, I copied over the source files from the other project and

recompiled. That was also clean

At that point, I did not have the I2C component added. So, I added it

in, regenerated the code and compiled. Thankfully, I got the same error,

but this time the project settings were as I expected them to be. So

that eliminated that possible problem.

Separately, I generated a short project that just had MQX and the I2C.

Since that compiled cleanly, I think it can eliminate the I2C as being

the source of the problem.

The attached file is the new project (Rebuild) that shows this problem.

After you unzip it and import it into a project, if you just use PE to

generate the code and compile, you should see the problem.

I'm sort of second guessing it, but it looks as though the string being

passed as the command line to the compiler might exceed the maximum

length allowed by Windows.

Let me know if you find anything (particularly a solution!) or need more

information.

Thanks,

Dave

0 Kudos
104 Views
Alice_Yang
NXP TechSupport
NXP TechSupport

Hi David,

I have test and check your project ,while it still have error when build.

So i refer to your component create a new project , and i have not cofigure the PE component detail,

while it have no error when build, so i send to your , and please test on it .

If it have not error,  i think you can configure on it .

Hope it helps

Alice

0 Kudos
105 Views
davepfaltzgraff
Senior Contributor I

The basic problem is the maximum line limitation found in Windows. For the correct solution see Re: Re: KSDK Linker Error - Command line too long

View solution in original post

0 Kudos
104 Views
davepfaltzgraff
Senior Contributor I

If you want me to test your solution, you need to forward it to me.

Also, it is important to me to have the PE involved in the design process.

Thanks

0 Kudos
104 Views
davepfaltzgraff
Senior Contributor I

Hi Alice,

I am working through some changes that were (inadvertently) made in the Project=>Properties. If I can make sense of them, I'll let you know. If not, I'll be glad to upload the project to see what you can find. I should know tomorrow.

Thanks

0 Kudos