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/TMS320F28379D: workshop example error

Part Number: TMS320F28379D

Tool/software: Code Composer Studio

hi,

I am going through lab5 "System Initialization"  from TMS320F2837xD micro-controller Workshop and I got the Below ERROR after i clicked the "build" Bottom. Can you please tell me how to fix these errors:

1) Description Resource Path Location Type
#1965 cannot open source file "F2837xD_device.h" F2837xD_GlobalVariableDefs.c /Lab5 line 43 C/C++ Problem

2) Description Resource Path Location Type
#1965 cannot open source file "Lab.h" Gpio.c /Lab5 line 7 C/C++ Problem

3) C28xx_CPU1: GEL Output:
Memory Map Initialization Complete
C28xx_CPU1: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
C28xx_CPU1: GEL: Encountered a problem loading file: C:\C28x\Labs\Lab5\cpu01\Debug\Lab5.out Could not open file

thank you

  • Mahdi,

    These errors are caused by an incorrect or not specified path.  In the workshop manual, double check steps 3 and 4 on page 5-24 (page110).  Carefully check that the paths are correctly included.

    I hope this helps. If this answers your question, please click the green "Verified Answer" button. Thanks.

    - Ken

  • Mahdi,

    It's been a while since I have heard from you last. Therefore, I am assuming that my last reply resolved your issue and I will close this thread. If this isn’t the case, please reject this resolution or reply to this thread. If this thread locks, please make a new thread describing the current status of your issue. Thank you.

    - Ken