• State TI Thinks Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 3180 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.

CCS/TMS320C6748: Issue running a project after upgrading to CCSv7.1

Matt McCulley
Prodigy 140 points

Part Number: TMS320C6748
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

I recently updated to CCS v7.1.0.00016.  I initially tried to update to the latest version of all tools/support programs that we use but that did not work as I could not get my project to build.  It took a while but I eventually found that I had to revert back to the versions of tools/support programs that we had been using with the exceptions of CCS, SYSBIOS, and the XDC Tools.  That finally allowed me to get a project to build.  Now that I have a project that builds I am having an issue actually running the project.  It seems that with the updates something in the toolchain is not working properly anymore.  I get a failure with a Semaphore create call within the BIOS PSP when trying to initialize an SD card. 

The failure happens in the BIOS PSP code through this call sequence:

mmcsdStorageInit();  ->  PSP_blkmediaDrvInit();  ->  Semaphore_Params_init(&semAttr);

As a result of the call to Semaphore_Params_init() I get the following failure information:

Exception at 0xc0c37130
EFR=0x40000000 NRP=0xc0c37130
DMC Exception MPFAR=0x0 MPFSR=0x120
Security violation, Local L1/L2 cache memory Fault
Supervisor Read violation, Fault ID=0x0
ti.sysbios.family.c64p.Exception: line 256: E_exceptionMax: pc = 0xc0c37130, sp = 0xc08182a0.
xdc.runtime.Error.raise: terminating execution

My current setup includes:

CCSv7.1.0.00016

Compiler tools: 7.4.21

SYSBIOS 6.50.1.12

XDC Tools 3.50.1.12

BIOSPSP 3.0.1.00

NDK 2.25.0.09

EDMA3 2.12.0

With the following setup the project works just fine:

CCSv6.2.0.00050

Compiler tools: 7.4.21

SYSBIOS 6.46.2.47

XDC Tools 3.32.1.22

BIOSPSP 3.0.1.00

NDK 2.25.0.09

EDMA3 2.12.0

AS you can see the only differences in the 2 scenarios appear to be the CCS version, the SYSBIOS version, and the XDC tools version.

  • 0
    TI__Guru* 96960 points
    Can you try compiler version 8.1.2 or higher? This is required for SYS/BIOs 6.50.01.12 (per release notes).

    Todd
  • 0 in reply to ToddMullanix
    Prodigy 140 points
    Actually we can't make the move to the version 8.x code gen tools since we are C6000 based.

    This paragraph is included with the release notes for both the 8.0 and 8.1 code gen tools:
    "The C6000 CGT v8.x.0 release is intended for MCSDK, OpenMP, and/or OpenCL project development. For new and existing general purpose C6000-based application development projects, we recommend the use of the latest available C6000 CGT v7.4.x release ( v7.4.xx as of... )."

    I did originally try to use the version 8 tools but realized after a while that our 3rd party libraries had not been compiled on the 8.x code gen tools and are not compatible. This would require another purchase of the libraries to move up to the 8.x version.

    What I had found in the CCS v7.0.0 release notes was the following, but I did not interpret this as V8 was required.
    "C6000 v7 Compiler no longer included; v8 still included, and older releases downloadable"

    I now see in the SYSBIOS release notes what you have pointed out that version 6.5.01.12 indicates Minimum Required Software Versions:
    "C6x version 8.1.2 or later"

    If the code gen tools are the problem then it looks like I would have to step back to SYSBIOS version 6.46.04.53. I had other issues with CCS behavior when I previously stepped back to another SYSBIOS version, but I don't recall the exact problem right now.

    Can anyone confirm that I absolutely can not use the v7.4.21 code gen tools with SYSBIOS v6.50.01.12?
  • 0 in reply to Matt McCulley
    Prodigy 140 points

    Todd,

    Can you please check the above post and answer that last question.

    Thanks,

    Matt

  • 0 in reply to Matt McCulley
    TI__Guru* 96960 points
    The consensus I'm getting is that it is fine to move to 8.1.2. This is what was used to validate the kernel. You should not mix and match 8.1.2 with 7.4.21. For example, make sure everything is built with 8.1.2.

    Todd
  • 0 in reply to ToddMullanix
    Prodigy 140 points

    Just so I am clear, could you please answer the following 3 questions:

    1)  Are you saying that even though the release notes for the v8.x code gen tools recommend that "for C6000 projects you stay on the 7.4.x code gen tools" we could move to the v8.x code gen tools?          

    (Assuming that we compile everything included in our project, i.e. 3rd party libraries with v8 code gen tools)

    2)  You are also confirming that 7.4.21 code gen tools should NOT be used with SYSBIOS 6.50.X.X?

    In order to keep moving forward and due to the fact that we do not currently have 3rd party libraries built with v8 code gen tools:

    3)  Is it valid for me to use what we previously used in CCSv6 within CCv7?

    (Code gen tools: 7.4.21,  SYSBIOS 6.46.2.47,  XDC Tools 3.32.1.22,  BIOSPSP 3.0.1.00,  NDK 2.25.0.09,  EDMA3 2.12.0)

    Matt

  • 0 in reply to Matt McCulley
    Prodigy 140 points
    Todd,

    Can you please answer the last 3 questions.

    Thanks,
    Matt
  • 0 in reply to Matt McCulley
    TI__Guru* 96960 points
    Matt,

    1) Yes.
    2) Yes. We have not tested with that compiler version. Based on that, we don't recommend using it.
    3) Yes. You should be able to use all of those in CCSv7.

    Todd
  • 0 in reply to ToddMullanix
    Prodigy 140 points

    Todd,

    I installed the versions from item 3 above and built a project.  It does seem to run correctly, however, I get the following error when I select XDCtools version: 3.32.1.22 from the RTSC tab of the Project properties.

    "Platform name 'XXXXX' could not be verified. Your project may not build as expected."

    The only way I can get the error to go away is to select XDCtools version: 3.50.1.12.

    When XDCtools version: 3.32.1.22 is selected and I click on the Platform drop down list there is nothing shown in the list at all, not even my current platform file.

    There is a brief pop up window, almost as though it is searching for the repository directory, but nothing is found.

    Do you have any suggestions to get rid of this error?  

    Should I be concerned about the integrity of the build that occurs with this error?

  • 0 in reply to Matt McCulley
    Prodigy 140 points

    Todd,

    Any answers or additional information to the above situation?

    Matt

  • 0 in reply to Matt McCulley
    TI__Guru* 96960 points

    The warning can be ignored (since it is building). It is being fixed in the next CCS release.