• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 1575 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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 v6 : TMS320VC5501 support?

Haeseong Jo
Prodigy 180 points
Other Parts Discussed in Thread: TMS320VC5501

Hello,

I'm migrating my CCS v3.3 projects to v6.

Some of my projects using TMS320VC5501.

But I cannot found TMS320VC5501, but only TMS320C5501.

Is this the corrent device what I looking for?

I think it's not just a problem of device name,

 C5501.xml contains weired information. (i.e --sillicon-version=5501, instead of 5510:2)

Please check this issue. (FYI, VC5502 is same, I think)

Thanks in advance.

  • 0
    Guru 192875 points

    Hi,

    Haeseong Jo said:
    Is this the corrent device what I looking for?

    Yup, The TMS320VC5501 (5501) fixed-point digital signal processor (DSP) is based on the TMS320C55x™ DSP generation CPU processor core.

    Haeseong Jo said:

    I think it's not just a problem of device name,

     C5501.xml contains weired information. (i.e --sillicon-version=5501, instead of 5510:2)

    Silicon version should be indeed 5501.

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Prodigy 180 points

    Thank you for quick answer.

    If so, why VC5504 and VC5505 keep their 'VC' name?

    And, why CCS v6 keeps showing this message when I try to connect and debug my projects?

    C55xx: Trouble Writing Memory Block at 0x2c0 on Page 0 of Length 0x31d3: (Error -1146 @ 0x2C0) Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver. (Emulation package 5.1.507.0)

    In CCS v3.3, of course, the project has no issue like this.
    In v6, same issue with or without GEL file. (gel file that I've used with v3.3)

    Emulator : Blackhawk USB560 v2 STM
    CCS v6.0.1.00040
    Code Generation Tool : C55x v4.4.1

    FYI, my other projects using C5535 has no issue like this, both in v3.3 and v6.

    Thanks.

  • 0 in reply to Haeseong Jo
    Guru 192875 points

    Haeseong Jo said:
    C55xx: Trouble Writing Memory Block at 0x2c0 on Page 0 of Length 0x31d3: (Error -1146 @ 0x2C0) Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver. (Emulation package 5.1.507.0)

    Yes, then surely there's a mismatch. Did you try updating your CCSv6 to the latest sub-version? Sometimes this solves the issue.

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Prodigy 180 points

    Yes, my CCS v6 is up-to-date completely.

    This might be a bug of CCS v6.

    Please check and confirm, TI guy.

    I need a way to fix this quickly, Anyone? :)

  • 0 in reply to Haeseong Jo
    Guru 192875 points

    Haeseong Jo said:

    Yes, my CCS v6 is up-to-date completely.

    This might be a bug of CCS v6.

    Please check and confirm, TI guy.

    I need a way to fix this quickly, Anyone? :)

    Yup, I'm forwarding your query to a CCS expert.

    Goodluck & Regards,

    Gautam

  • 0 in reply to Haeseong Jo
    TI__Guru**** 168337 points

    Hi,

    Unfortunately I don't have a C5501 board with me, but I found a C5502 EVM and I was not able to reproduce the same issue as you. My BH 560v2 emulator connected and loaded the program just fine.

    If you have a C5502 board around, can you try to connect to it? This could indicate an issue specific to the C5501.

    One detail I noticed is that I sometimes had to issue a CPU Reset before loading the code (menu Run --> Reset --> CPU Reset) - otherwise the device would not allow this operation.

    Another detail (although I don't see it as very critical in this case) is the JTAG TCLK speed. Since you are finding problems, you may want to start at the legacy (10.368MHz) or reduce to a fixed slower speed and see if you get a more successful connection.

    Apart from this I am not 100% sure what else may be going on. I will see if I can get any additional ideas and reply here, ok?

    Regards,

    Rafael

  • 0 in reply to desouza
    Prodigy 180 points

    Actually I've just found a compromising way, just before your reply,
    and dear Rafael, you just got the point !!!

    I have to set my ccxml like the below :

    - Automatic with user specified limit = 10.0MHz (it seems the maximum in my case)
    - Rising edge allow faster TCLK (the standard falling edge is not suitable for faster TCLK)

    Anyway, I suggest that the C550x -> VC550x fix would be welcome,
    because it's surely confusing.

    Thanks again Rafael, and Gautam you too.

  • 0 in reply to Haeseong Jo
    TI__Guru**** 168337 points

    Hi,

    Thanks for reporting back your findings. This may be useful for others in the future.

    Haeseong Jo said:
    Anyway, I suggest that the C550x -> VC550x fix would be welcome,
    because it's surely confusing.

    Thanks for pointing that out; I understand it may be confusing. If I recall correctly, it was a decision made years ago to aggregate all C5500 devices in the drop down list of devices, so people would not get confused thinking that only the newer devices (the ones that start with "C" only) would be supported.

    In the target configuration editor the description itself mentions the "VC" in the part number in an attempt to reduce the confusion (or not... ).

    In any case, I can check to see if it is worth changing these part numbers to "VC" - the main issue is that this will break compatibility with all the target configurations already done by customers using these for years. Something that is simple to fix but tends to cause a lot of grief across the board.

    I'll reply back if something changes in this regard.

    Regards,

    Rafael