• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 1172 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CAN using halcogen on TMS570

Aaron Thompson45
Prodigy 200 points
Other Parts Discussed in Thread: TMDX570LC43HDK, HALCOGEN

I have followed the tutorial () found on to try to set up a simple CAN network with the 2 TMS570LC43HDK boards () I have.

I have managed to generate the code in halcogen and inport the files into the CCS6 project, however every time I try to build the project to run on the board I get the following error. I have attached the very simple project along with a .txt containing the full console output from the build.

My apologies if this has been asnwered before, from my research I had found similar foroum posts but none contained this exact error.

<Linking>

warning #10366-D: automatic library build: using library "c:\ti\ccsv6\tools\compiler\arm_5.1.5\lib\rtsv7A8_A_be_v3_eabi.lib" for the first time, so it must be built.  This may take a few minutes.

cygwin warning:

 MS-DOS style path detected: C:\Users\s55296\Documents\Workspace\DCAN_TX\Debug

 Preferred POSIX equivalent is: /cygdrive/c/Users/s55296/Documents/Workspace/DCAN_TX/Debug

 CYGWIN environment variable option "nodosfilewarning" turns off this warning.

 Consult the user's guide for more details about POSIX paths:

   

cygwin warning:

 MS-DOS style path detected: C:\Users\s55296\Documents\Workspace\DCAN_TX\Debug

 Preferred POSIX equivalent is: /cygdrive/c/Users/s55296/Documents/Workspace/DCAN_TX/Debug

 CYGWIN environment variable option "nodosfilewarning" turns off this warning.

 Consult the user's guide for more details about POSIX paths:

   

cygwin warning:

 MS-DOS style path detected: C:\Users\s55296\Documents\Workspace\DCAN_TX\Debug

 Preferred POSIX equivalent is: /cygdrive/c/Users/s55296/Documents/Workspace/DCAN_TX/Debug

 CYGWIN environment variable option "nodosfilewarning" turns off this warning.

 Consult the user's guide for more details about POSIX paths:

   

 -->  error: '*.obj

' not found

gmake.exe[1]: *** [library] Error 1

>> ERROR: mklib: gmake error during rtsv7A8_A_be_v3_eabi.lib build

warning #10207-D: automatic RTS selection:  resolving index library "libc.a" to "c:\ti\ccsv6\tools\compiler\arm_5.1.5\lib\rtsv7A8_A_be_v3_eabi.lib", but "c:\ti\ccsv6\tools\compiler\arm_5.1.5\lib\rtsv7A8_A_be_v3_eabi.lib" was not found

undefined      first referenced          

 symbol            in file                

---------      ----------------          

__TI_auto_init ./source/HL_sys_startup.obj

exit           ./source/HL_sys_startup.obj

error #10234-D: unresolved symbols remain

error #10010: errors encountered during linking; "DCAN_TX.out" not built

>> Compilation failure

gmake: *** [DCAN_TX.out] Error 1

gmake: Target `all' not remade because of errors.

**** Build Finished ****

  • 0
    Guru 15740 points
    Have you tried to remove Cygwin from all the paths in CCS properties? It seems that it's make conflicts.
  • 0 in reply to Jan Cumps
    Prodigy 200 points

    Thank you Thfor the reply. How would I go about doing this?

  • 0 in reply to Aaron Thompson45
    TI__Guru 65480 points

    Hi Aaron,

    I think that someone the other day actually posted a link to this wiki page: 

    It talks about how to quickly find the 'sh' and 'gmake' that are pulled into your path with the 'where' command (windows equivalent to 'which' ;) )

    There are a lot of other posts on the CCS forum on this topic - most people temporarily remove C:\Cygwin from their windows path and restore it after the library is built.  But there was another post I saw recently (but can't find) where someone had a suggestion on changing the shortcut that launches CCS to change the path just for that process.

    This could be done by making a batch file that launches CCS after setting the path but I think there was something more elegant posted.  I'll do a little more looking to see if I can find the post.

    EDIT: Here's the post I was thinking of - see the suggestion on modifying the shortcut w %comspec% and the good explanation that follows.

  • 0 in reply to Anthony F. Seely
    Prodigy 200 points

    SOLVED - The problem was caused by the library not being auto generated when the "runtime support libraries" in Properties>General was set to "auto"

    By selecting the already created library in the arm_5.1.6 folder the problem was resolved