• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 1256 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/TMS320F28335: CCS6 on MAC

Ali Topcu
Prodigy 30 points
Part Number: TMS320F28335
Other Parts Discussed in Thread: CCSTUDIO, C2000WARE

Tool/software: Code Composer Studio

Hi,

I am using MAC. I have CCS6 installed on my computer. I have training files which are under C2833x_CCS4 folder. I think they are created and run for windows computer. When I try to use it on my MAC, I am getting error.

Description Resource Path Location Type
make: *** target pattern contains no '%'. Stop. subdir_rules.mk /Lab7/Debug line 6 C/C++ Problem

Line 6: 

DSP2833x_ADC_cal.obj: /Applications/ti/ccsv6/eclipse/Ccstudio.app/Contents/MacOS/C:/tidcs/c28/DSP2833x/v131/DSP2833x_common/source/DSP2833x_ADC_cal.asm $(GEN_OPTS) | $(GEN_HDRS)

How can I fix it?

Thank you

  • 0
    Guru 192875 points
    Hi Ali,

    This looks like an include issue. Can you instead install CCSv7 on Mac? You can simply open Resource Explorer and import the latest example files for F28335 from C2000ware.

    Regards,
    Gautam
  • 0 in reply to Gautam Iyer
    Prodigy 30 points
    Thank you. I did what you said. It seems ok. However I have another problem. I am trying to download program to F28335. However, GEL extension pops up and it takes 5-10 mins. How i can fix it?
  • 0 in reply to Ali Topcu
    TI__Guru**** 173310 points

    Ali Topcu said:
    I am trying to download program to F28335. However, GEL extension pops up and it takes 5-10 mins. How i can fix it?

    There is a known issue with the performance of XDS100v1 probes specific to MacOS. If you are using a F28335 experimenter's kit with the onboard XDS100v1 emulation then you will be impacted. We hope to address this in a future release of CCS. In the meantime, you can use an external debug probe, such as XDS100v2 or XDS200 (if you have one), or you could try the workaround mentioned in this post. 

    Sorry about the inconvenience.

  • 0 in reply to AartiG
    Prodigy 30 points

    Thanks for your help. I followed the link you shared. It works fine for me.