• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 52 subscribers
  • Views 1422 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.

Original question:

getting started with concerto controlcard and dock board...

CCS/F28M36P63C2: Device Drivers not found for the dual blinky project

Joshua Kurash
Intellectual 290 points

Part Number: F28M36P63C2
Other Parts Discussed in Thread: CONTROLSUITE

Tool/software: Code Composer Studio

Hi,

Im trying to build the dual core blinky example for the F28m36x Concerto device. I build the c28x side perfectly fine but the m3 side produced the following errors:

Could Not Find C:\ti\controlSUITE\device_support\f28m36x\v200\F28M36x_examples_Dual\blinky\m3\ccs\Flash\blinky_dc_m3.out
Could Not Find C:\ti\controlSUITE\device_support\f28m36x\v200\F28M36x_examples_Dual\blinky\m3\ccs\Flash\blinky_dc_m3.obj
Could Not Find C:\ti\controlSUITE\device_support\f28m36x\v200\F28M36x_examples_Dual\blinky\m3\ccs\Flash\blinky_dc_m3.d

I uninstalled and then reinstalled the control suite software to see if the download was bad, but that didn't fix the problem.

Thanks,

Josh

  • 0
    TI__Guru**** 173310 points

    Josh,

    Which version of CCS are you using? When importing the project into CCS did you enable the "Copy projects into workspace" checkbox?

    Could you save off the complete build log for the M3 project and attach it here for us to look at?

  • 0 in reply to AartiG
    Intellectual 290 points

    Hi AartiG,

    I believe my problem was that I was using the wrong version of the project. I was able to build both the m3 and the c2000 projects. Im new to code composer though and Im not sure how to load the executables to the c2000 side. I ran the m3 blinky and it works but the c2000 blinky doesn't.

    Josh

  • 0 in reply to Joshua Kurash
    Intellectual 290 points
    Sorry I forgot to mention, im using ccs 8.1
  • 0 in reply to Joshua Kurash
    TI__Guru**** 173310 points
    Josh,

    Have you had a look at the F28M36x Firmware Development Package User's Guide included with ControlSuite? Section 2.3 goes into how to debug dual core applications.

    I would suggest using the examples and looking at the doc for the latest version of the package v220 (found in C:\ti\controlSUITE\device_support\f28m36x\v220\doc).
  • 0 in reply to AartiG
    Intellectual 290 points

    Hi Aarti,

    So Im going through the F28M36x Firmware Development Package User's Guide and following the project creation section and im running into trouble when building the target.  Inside Code Composer, for the connection drop down, I cannot find the texas instruments xds100v2 usb emulator. Im not sure were I would be able to find it.

  • 0 in reply to Joshua Kurash
    Intellectual 290 points
    Im also running into trouble with the test code that was provided in the F28M36x Firmware Development Package User's Guide. The project wont build because the linker cannot find the "board_drivers/set_pinout_f28m3Xx.h" header for the include statement that was provided. I ran a search on the control suite folder and it doesn't appear to be within controlSuite
  • 0 in reply to Joshua Kurash
    TI__Guru**** 173310 points

    Joshua Kurash said:
    Inside Code Composer, for the connection drop down, I cannot find the texas instruments xds100v2 usb emulator. Im not sure were I would be able to find it.

    I see it in your screenshot - it is listed as Texas Instruments XDS100v2 USB Debug Probe.

  • 0 in reply to Joshua Kurash
    TI__Guru**** 173310 points

    Joshua Kurash said:
    The project wont build because the linker cannot find the "board_drivers/set_pinout_f28m3Xx.h" header for the include statement that was provided.

    I see the header file set_pinout_f28m36x.h in the folder C:\ti\controlSUITE\device_support\f28m36x\v220\MWare\board_drivers.  There is probably a typo in whichever file you are looking at.