• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 703 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

problem with pseudo error from error parser in builds

Alexander Stohr
Expert 1200 points

Excerpt from the build log of my current CCS 5.4.0.91 install:


making D:/*****/CortexA8/src/sysbios.aea8fnv ...
gmake[2]: Nothing to be done for `all'.
Build of libraries done.
C:/ti/ccs5.4.0.91/xdctools_3_25_00_48/bin/sed 's"^\"\(package/cfg/client_pea8fnvcfg.cmd\)\""\"D:/****/CortexA8/Debug/configPkg/\1\""' package/cfg/client_pea8fnv.xdl > linker.cmd
C:/ti/ccs5.4.0.91/xdctools_3_25_00_48/bin/rm -f package/cfg/client_pea8fnv.oea8fnv
#
# clea8fnv package/cfg/client_pea8fnv.c ...

Screen shot from the problems box:

Something seems to be dangling in the error parsing.

  • 0
    TI__Guru**** 173310 points

    Can you provide more information on the project you are building? Is this a TI example project or your own? If your own custom project, would you mind zipping it up and attaching it (or sending via private conversation) so we can duplicate the problem? Also does the build actually complete successfully in spite of the error in the Problems view?

  • 0 in reply to AartiG
    Expert 1200 points

    its the XDC part of a larger project - so its code that comes from TI that raises the problem.

    as visible in the log its targetting for the ARM Cortex A8 core.

    i am sorry i can not send you the whole project for IP right reasons and it has a noticeable size already. (shall i trip it? not yet... but see far below)

    once the XDC part is done and the build tells me about the error i can build again and the XDC part is skipped - but the error on the panel stays.

    just to make clear, XDC shall really create and use that command but CCS should be able to understand that those character sequence is not an error.

    proposal for reproducing that on your own:

    - create a simple makefile project

    - put the command "echo <critical_char_seqeunce>" into that makefile using an adequate form _or_ use "type <text_file_that_contains_critical_sequence>" instead for the makefile

    - run that project so that the critical lines of output will be exposed to CCS

  • 0 in reply to Alexander Stohr
    TI__Guru**** 173310 points

    Is your project a CCS managed make project or a makefile project? I'm trying to understand if this error would also be generated for CCS managed make projects. It would be very helpful and much appreciated if you could provide us with a test project that generates this error (if not your complete application then possibly a cutdown or simple project that demonstrates the issue). Thanks.

  • 0 in reply to AartiG
    Expert 1200 points

    as of now the project is a CCS managed make project.

  • 0 in reply to Alexander Stohr
    Expert 1200 points

    i will try to send you in private a zip file with a heavily stripped down project that shows the error on CCS5.5 for me.

    please confirm to me that reception was successful. (i am unable to find an "outbox" or "inbox" here in my forum profile area... - aaaah found it under keyword "conversations" on the very top bar)

  • 0 in reply to Alexander Stohr
    Expert 1200 points

    PING - anything new with that?