On LogicPD's website, they provide a file -- 1014013A_OMAP-L138_GEL_BSL_Files -- containing lots of essential information useful for using their OMAP-L138 EVM board with CCS. Such as lots of header files, test files, GEL files, a linker command file, and a library. This information is essential for CCS to effectively use their EVM board.
I've followed their accompanying installation instructions, but nonetheless, CCSv4 doesn't seem to find those files. I presume CCS needs some kind of path or environment variable set, so it knows where to find these files. ???
I appreciate any help you may offer.
Walter,
I use PSPad as my editor. But many people use the v4 editor without issue. Can you attach your linker command fine again? I want to do a diff
ki
-----------------------------------
Don't forget to verify answers to your forum questions by using the green "Verify Answer" button.
Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.
Having CCSv5 problems? Check out the CCSv5 Troubleshooting Guide
Click here to track an issue. Enter your bug id in the "Find Record ID" box
Ki,
Here is my linker_dsp.cmd file. It is three bytes larger than your file, but the differences are invisible to the eye (in the CCSv4 editor and MS Notepad).
[P.S. The "Insert Media" command does not appear to be working. I've tried uploading my file five times now, and it doesn't seem to show up. What's up?]
Hit the Options link and use the File Attachment option to upload the file
Did the file upload yet?
Yup. Got it. I did a diff using a diff tool and the tool said that my cmd and your is different. But when the diff tool then opened up both files side-by-side, the files looked identical. I even enabled display of special characters and still the same. But dropping in your file in my folder, i got the same linker error. So I open your cmd file again in my editor and used the built it DOS format conversion tool and saved the file. The errors went away.
I don't know how that cmd file was some format besides DOS (Unix? Mac?). Do you use another machine besides PC? Maybe you have some setting for defualt file format and it is not DOS?
I'm using a PC Windows XP. Nothing unual. Not Linux, Unix, or Mac.
Very strange symptoms on this problem.
So I tried another experiment. I took Ki's linker_dsp.cmd file into my CCSv4 editor, made some insignificant change, saved it, and it re-built fine.
I did did the same using the MS Notepad editor, it re-built fine.
Whatever was weird in that file, it was both invisible and unaffected by these editors. That is, once the weirdness got into the file, these editors neither displayed it, detected it, nor fixed it. The editors simply pass along the weirdness to any daughter file, like some kind of genetic defect.
I don't know how the weirdness got into that file. So far, we can't even tell what the weirdness is -- except by the fact that it causes the linker failure. It's like a new kind of computer parasite that we don't know how to detect. We just know it is within some files, and not others -- and editors don't eliminate it.
Meantime, I just copied Ki's version of the file into all the many directories where it is needed. So at least I have a working system now.
Very strange. I'm curious what the explanation finally is. Let me know how it turns out.
Thanks for all your help!!!
Use a binary editor to spot the differences. I am sure that if you use notepad to save the file in Ascii encoding everything is fine as well. Maybe the copyright sign (which is not ascii) triggers the editors to save it in one of the unicode formats with a byte order mark. The linker cannot make sense of this. Maybe TI (am am new to the platform but assume the linker is TI's) could update the linker so it handles this AND DOS/Unix line-ending?
Peter
I can spot the difference with a binary editor. Thee characters in the beginning of Walter's cmd file that does not exist in mine.
Mine:
Walter's:
The original file from Logic PD does not have those extra characters either. Somehow, someway those characters got added when Walter modified the cmd file....
strange!
Ki-Soo Lee The original file from Logic PD does not have those extra characters either. Somehow, someway those characters got added when Walter modified the cmd file.... strange!
Actually not so strange:
http://en.wikipedia.org/wiki/Byte_order_mark#Unwanted_BOMs
http://www.howtofixcomputers.com/forums/windows-xp/extra-characters-beginning-file-ef-bb-bf-263070.html
Yes, I believe the problem characters were not in the original LogicPD linker_dsp.cmd file. However, the wrong library path was there, so I was forced to edit the file to correct the path. I used MS Notepad to do the edit.
Here are my suspicions about those problem characters. I needed to get the correct library path, so I used MS Windows Explorer to locate the file and obtain its path. I simply copied the path from the address line (near the top of the window) in MS Windows Explorer, and pasted it into MS Notepad. And saved the file. Quite simple, and ordinary. Nothing fancy. Perhaps something funny happens in that process?
Another suspicion centers on that 'copyright' character -- which is not a native ASCII character -- within the linker_dsp.cmd file. It is there in Ki's file, and in mine -- but Ki's file worked, and mine didn't. The copyright character obviously isn't the problem, but perhaps it causes the editors (Notepad and CCSv4) to handle the file in a fundamentally different way that enables the problem to materialize. Just my suspicions here.
------
Meanwhile, I am proceeding to use Ki's un-contaminated file, and all is working. I am grateful for that. I am a happy guy. Thank you again to everyone.
Here is my summary of the solution I learned here:
For grins, I opened my working cmd file in notepad and save the file (without doing anything). I noticed that those extra characters got added! And the of course the build failed. When I removed them, all was fine again.
But I then tried the same with some other project's cmd file I had laying around and saving in notepad did not do anything. I really don't have an explanation for this.
Walter Snafu Edit the .pjt file from LogicPD, change the ProjectDir line to: ProjectDir="$(Proj_dir)"
FYI - CCS 4.1.1 (which was released yesterday) has a fix where the above step is no longer necessary.
Ki-Soo Lee For grins, I opened my working cmd file in notepad and save the file (without doing anything). I noticed that those extra characters got added! And the of course the build failed. When I removed them, all was fine again. But I then tried the same with some other project's cmd file I had laying around and saving in notepad did not do anything. I really don't have an explanation for this.
Perhaps the "other project's cmd file" didn't have non-ASCII characters in it. ??? The files we've been dealing with (from LogicPD) had at least two non-ASCII characters (or extended-ASCII characters?) The copyright symbol, and the character before that (which is some type of foreign A symbol).
I suspect that when non-ASCII characters are in the file, then the editor needs some way of encoding those, and that requires more than 8 bits. And then the issue of endian-ness enters into the mix, and the three bytes at the beginning of the files tell the editor if it's an out-of-order endian-ness. I may not have the details of that right, but I think we're homing in on the cause: Non-ASCII characters, combined with endian issues.