• 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 » Digital Signal Processors (DSP) » C5000 Ultra Low Power DSP » C5000 Ultra Low Power DSP Forum » Why can't use second McBSP- McBSP1 as GPIO in C5510 DSK
Share
C5000 Ultra Low Power DSP
  • Forum
  • Announcements
Options
  • Subscribe via RSS
Top 6 Wiki Links
  • C5000 Main Wiki
  • C5000 Software
  • C5515 Boot-Image Programmer
  • CSL (including CSL 3.00)
  • C5000 Connected Audio Framework
  • Porting C5000 Teaching ROM to C5535 eZdsp
  • Forums

    Why can't use second McBSP- McBSP1 as GPIO in C5510 DSK

    This question is answered
    Shanjie Chen
    Posted by Shanjie Chen
    on Nov 28 2010 20:17 PM
    Prodigy110 points

               I can configure the McBSP0 as GPIO and read  status in C5510 DSK  using following codes: (I add the code in the example program: CCStudio_v3.1\examples\dsk5510\bsl\led, led project)            

                                 hMcbsp0 = MCBSP_open(MCBSP_PORT0,MCBSP_OPEN_RESET);
                                  MCBSP_RSETH(hMcbsp0,SPCR1,0x0000); 
                                  MCBSP_RSETH(hMcbsp0,SPCR2,0x0000); 
                                  MCBSP_RSETH(hMcbsp0,PCR,0x3800);  //0011 1000 0000 0000

                                  MCBSP_FGETH(hMcbsp0,PCR,CLKRP);  // read the CLKR0 status

                 But it is surprising that I can't not  read/write pins of another McBSP---- McBSP1  --- using the same way???   DSP always reads the "0" status of CLKR1 while changing its iuput to high voltage 3.3 V (I delete the code above, only deal with McBSP1) 

                                  hMcbsp1 = MCBSP_open(MCBSP_PORT1,MCBSP_OPEN_RESET);
                                  MCBSP_RSETH(hMcbsp1,SPCR1,0x0000); 
                                  MCBSP_RSETH(hMcbsp1,SPCR2,0x0000); 
                                  MCBSP_RSETH(hMcbsp1,PCR,0x3800);  //0011 1000 0000 0000

                                  MCBSP_FGETH(hMcbsp1,PCR,CLKRP);  //read the CLKR1 status

               Can all the McBSPs be configured as GPIO??? or only McBSP0???

     

     

    McBSP GPIO
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    All Replies
    • Steve Tsang
      Posted by Steve Tsang
      on Nov 29 2010 10:39 AM
      Verified Answer
      Verified by Shanjie Chen
      Genius12675 points

      Yes. Both should be allowed to configured as GPIO. On the DSK, they are connected to on-board AIC23. Are you changing the CLKR1 on the AIC23? Or the expansion connector pin 33 and rerouted via MISC register in CPLD of DSK?

      -------------------------------------------------------------------------------------------------------

      Please click the Verify Answer button on this post if it answers your question

      --------------------------------------------------------------------------------------------------------

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Shanjie Chen
      Posted by Shanjie Chen
      on Nov 29 2010 10:57 AM
      Prodigy110 points

      Does  DSP pin CLKR1 not connect P2--Peripheral Expansion Connector pin 39 CLKR1 directly????

       I only test "McBSP as GPIO" in P2--Peripheral Expansion Connector, not AIC23???

      And I also can't not use McBSP2 as GPIO  in P3 HPI Expansion Connector?? 

      I only want to add some input to McBSP pins in  P2--Peripheral Expansion Connector and test its input status, I need 12 pins configured as GPIO pins

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Shanjie Chen
      Posted by Shanjie Chen
      on Nov 29 2010 13:50 PM
      Prodigy110 points

                    I notice that in order to make McBSP1 buffer work and pass the signal from McBSP pins in  P2--Peripheral Expansion Connector, we should make the voltage of pin 1 OE1 and pin 13 OE2  low, i.e, CPLD_EXP_McBSP1n signal should be also low, how can I control the CPLD_EXP_McBSP1n signal???

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Naser Salameh
      Posted by Naser Salameh
      on Nov 29 2010 14:40 PM
      Verified Answer
      Verified by Shanjie Chen
      Expert8095 points

      HI Shanjie: My quick feedback.

      You may need to pull DC_DET signal low. This is explained in the documentation of the C5510 dsk.

      http://c5000.spectrumdigital.com/dsk5510/docs/dsk5510_techref.pdf
      The DSK also multiplexes the McBSP1 and McBSP2 of on-board or external use. This function is controlled through the CPLD MISC register as you mentioned. McBSP multiplexing need to be select in the external CPLD MISC register mapped in CE1 memory space (0x300000 data memory word address).

      Regards,

      Naser

       

       

       

      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