• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Development Tools » Code Composer Studio » Code Composer Forum » DM814x jtag debug of McASP
Share
Code Composer Studio
  • Forum
  • Announcements
Options
  • Subscribe via RSS
Common Questions
  • Code Composer Studio Forum Usage Guidelines

  • Resources
  • Code Composer Studio (CCStudio) Product Folder
  • Troubleshooting CCS
  • CCS Wiki
  • Download CCS
  • Order CCS
  • Tools Insider Blog
  • Bug Tracking
  • DM814x jtag debug of McASP

    DM814x jtag debug of McASP

    This question is not answered
    Andrew Elder
    Posted by Andrew Elder
    on May 10 2012 15:07 PM
    Intellectual710 points

    I am using CCS 5.1 under Linux on custom hardware.

    After I connect to the C764X core reading McASP0 registers at 0x48038000 return all zero.

    I then connected to the CortexA8 core and reading McASP0 registers returned 0x10C5387D.

    I have concluded that neither of these connection methods are showing me the McASP0 register settings. How do I read them?

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    All Replies
    • Viet Dinh
      Posted by Viet Dinh
      on May 10 2012 15:19 PM
      Genius15310 points

      Andrew,

      From the Data sheet, the L3 Memory map for McASP0 is:

      0x4600_0000 0x463F_FFFF 4MB McASP0 Data Peripheral Registers

      where as L4 Memory map for C674x is:

      0x4803_8000 0x4803_9FFF 0x0803_8000 0x0803_9FFF 8KB McASP0 CFG Peripheral Registers

      BR,

      Viet

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Andrew Elder
      Posted by Andrew Elder
      on May 11 2012 11:37 AM
      Intellectual710 points

      Viet,

      Thanks for pointing me in the right direction. In table 2-6, McASP0 is also listed as having an L4 base address of 0x0803_8000 (for the C64x). If I connect JTAG to DSP I should use the DSP's L4 address ?

      The implication from table 2-4 is that the DSP does not have access to McASP0 through the L3 interconnect ?

      Thanks,

      Andrew

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Viet Dinh
      Posted by Viet Dinh
      on May 11 2012 15:12 PM
      Genius15310 points

      Andrew,

      Yes, you should use the DSP's L4 address once you connected to DSP.

      It has limited memory to access from DSP.  Please check DS for the Mem avail.

      BR,

      Viet

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Andrew Elder
      Posted by Andrew Elder
      on May 11 2012 15:27 PM
      Intellectual710 points

      Viet,

      Thanks for the prompt reply. According to my reading, and inspecting Table 2-4

      0x0800_0000 0x08FF_FFFF 16MB L4 Slow Peripheral Domain

      maps to the "C674x DSP" column in table 2-6 which is where you got the

      0x4803_8000 0x4803_9FFF 0x0803_8000 0x0803_9FFF 8KB McASP0 CFG Peripheral Registers

      information you replied with several emails ago.

      The only thing is, if I connect via JTAG to the C674x core I still read back 0x0 for McASP when using address 0x0803_8000. Is that to be expected ? Is something blocking jtag accesses ?

      Regards,

      Andrew

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Viet Dinh
      Posted by Viet Dinh
      on May 16 2012 20:04 PM
      Genius15310 points

      Andrew,

      Sorry for late response.  Let me move this question to CCS to see if they can help you.

      BR,

      Viet

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Andrew Elder
      Posted by Andrew Elder
      on May 17 2012 07:49 AM
      Intellectual710 points

      We found that adding

      +  /* Enable McASP0 clock so it can be accessed by other CPUs */
      +  dev_clk = clk_get_sys("davinci-mcasp.0", NULL);
      +  BUG_ON(IS_ERR(dev_clk));
      +  clk_enable(dev_clk);
      +

      to the linux board support file enabled the DSP to configure the McASP.  We have not yet researched the exact side-effects (at a register level) of the above calls.

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    TI E2E™ Community
    • Support Forums
    • Blogs
    • Videos
    • Groups
    • Site Support & Feedback
    • Settings
    TI E2E™ Community Groups
    • TI University Program
    • Make the Switch
    • Microcontroller Projects
    • Motor Drive & Control
    Other Communities
    • Deyisupport
    • Designsomething.org
    • beagleboard.org
    • TI on Element 14
    • TI on TechXchangeSM
    Other Technical & Support Resources
    • WEBENCH® Design Center
    • Product Information Centers
    • Technical Documents
    • TI Design Network
    • TI Technical Articles
    • TI Training

    All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

    Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

    Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
    TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

    TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
    embedded processors, along with software, tools and the industry’s largest sales/support staff.

    © Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
    Trademarks | Privacy Policy | Terms of Use