• 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 » Interface » Industrial Interface » Industrial Interface Forum » Problem with SN65HVD230 with BeagleBone
Share
Industrial Interface
  • Forum
  • Files
Options
  • Subscribe via RSS
Check out
Analog Wire blog
  • $core_v2_blog.Current.Name

    Cable equalization 101 – Automating your design

    Posted 1 day ago
    by Hooman Hashemi
    Judging by the number of views on a post related to numerical...
  • $core_v2_blog.Current.Name

    RS-485 - Who says you can't teach an old dog new tricks?

    Posted 5 days ago
    by Neel Seshan
    Would you agree that RS-485 has turned out to be one of the most...
  • $core_v2_blog.Current.Name

    Filter for thought

    Posted 7 days ago
    by Soufiane Bendaoud
    Have you ever wondered how engineers designed active filters...

Problem with SN65HVD230 with BeagleBone

Problem with SN65HVD230 with BeagleBone

This question is answered
Ajish Sasidharannair
Posted by Ajish Sasidharannair
on Dec 19 2012 04:02 AM
Prodigy20 points

 We  have interfaced SN65HVD230  with Beagle Bone's CAN Port and  the CAN Tx line is staying at High  when we are sendingd data.We are connecting in loopback mode with  one CAN transceiver CANH tied to other transceiver's  CANH and similiarly  for CANL also.  Is there any limitation for SN65HVD230 to work with other TI's microprocessors with CAN support. The datasheeet shows operation with TMS320LF243  and is it limited to this proceesor or this is a generic transceiver ?

 

Please share your comments.if anybody interfaced this IC with Beagle bone and  got working .

CAN Bus transceiver SN65HVD232/230
Report Abuse
  • Reply
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
All Replies
  • Scott Monroe
    Posted by Scott Monroe
    on Dec 19 2012 08:06 AM
    Verified Answer
    Verified by Scott Monroe
    Expert4735 points

    Can you please clarify the following pionts of basic CAN debug so we can help you further.  The SN54HVD23x familly whould work fine with Beagle Bone (AM35xx). 

    The TXD pin is controlled by the MCU not the transceiver so I suspect you actually have s/w set up issues with the AM35xx CAN data and the transceiver isn't even getting any.  I'm not sure what you mean by loop back mode, is this a mode on AM35xx like on Stellaris where the data never actually comes out to the bus (transceiver) but is looped back internally on the CAN controller of the uP?

    CANH and CANL should be connected in linear bus fashion from the transcievers, with 120 ohm resistors at each end of the bus since it is a transmissions line and they are needed for CAN to work properly.  Please see app note SLOA101A  for CAN bus basics.  Up through page 8 should get you the basic info to help a lot. 

    If you can send a scope shot with the following it will let us know what is going on with the transceiver.  We need TXD (D), RXD (R), CANH and CANL.  Best is to put CANH and CANL at the same reference point as in recessive (logic 1 or high) they will be the same potential (~2.3V) and when you transmit a dominant (logic 0 or low) they will be seperated and CANH should rise to about 2.8V and CANL should drop to about 1.5V).   This will basically confirm if you are getting correct data out of the uP to the CAN transceiver.   Schematics of you set up would also be helpful.

    Other app notes that may help (hyperlinks hopefully work):

    •SLOA101A: Introduction to the Controller Area Network (CAN)
    •SLLA270: Controller Area Network Physical Layer Requirements
    •SLLA271:  Common Mode Chokes in CAN Networks: Source of Unexpected Transients
    •SLLA279A: Critical Spacing of CAN Bus Connections
    •SLLA109: A System Evaluation of CAN Transceivers
    •SLLA123: Using CAN Arbitration for Electrical Layer Testing
    •SLLA298B: Isolated CAN Reference Design
    •SLLA107: Live Insertion With Differential Interface Products
    •SLLA067B:  Comparing Bus Solutions
    •Article: “Signaling rate versus cable length: the CAN-bus timing trade-off” – CAN loop timing and arbitration

    -- Scott

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Dhiv Sekar
    Posted by Dhiv Sekar
    on Dec 20 2012 09:36 AM
    Prodigy65 points

    Hi Scott ,

            We belong to the software team of Ajish who posted question on this. You can see the schematic of what we have  done in the image below.

             Using CAN utilities , we tested CAN interfaces by sending and receiving data's in loopback mode , which is working fine . Also , we were able to see the signal change in DCAN0_TX pin .

            Then , on connecting the DCAN0_TX(P9- 20th pin) and DCAN0_RX(P9-19th pin) of the beaglebone to tx(D) and rx pin of the CAN transceiver and similarly DCAN1_TX(P9-26th pin) and DCAN0_RX(P9-24th pin) is connected to the tx(D) and rx pin of the other CAN transceiver , thus making loopback as Ajish said, we see only high signal on tx and rx.

    Hope you can help us further with this information.

    Thanks in advance,

    Dhiv.

            

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Scott Monroe
    Posted by Scott Monroe
    on Dec 20 2012 11:28 AM
    Verified Answer
    Verified by Scott Monroe
    Expert4735 points

    Schematically it seems to have 3 issues. 

    • Pin 8 which is the mode control, Rs should not be floating. Pin 8 floating may mean you are in low power standy mode which would not put data from D pin to the bus and thus no output to R. Please tie Pin 8, Rs to GND.
    • Pin 5 is Vref output pin.  This pin should not be tied to GND, that is a direct short to GND of this output.  Either leave it floating or use a capacitor to GND in the 100pF range.
    • Pin 3 is Vcc.  It should have 3.3V applied not just capacitors to GND (pin 2).
    •   Ideally a scope shot of D, R, CANH and CANL (with both at same reference) will be very helpful to see what is actually happening at the pins of the device in question.  Without basic scope debug there is a lot to guess about but little to offer solid advice.

    Please see look at figure 39, right end CAN node (SN65HVD230) in the datasheet for a basic schematic on how to use the device.

    Then please confirm the following: 

    • Pin 8: Rs is tied to gnd for High Speed Mode.
    • Pin 3: Vcc on pin 3 with respect to pin 2 is 3.3V.
    • Pin 5: is floating or capacitor to GND
    • The output levels of Sitara is set up to 3.3V thresholds of HVD230.  Make sure it isn't an open drain output or the timing input to the transceiver will not work.  There is only a weak pull up to hold the part in recessive (logic H) if TXD floats.  TXD timing will be way to slow in that case.
    • Output level on CANH and CANL.  Please see if they are DC at about 2.3V or actually have transitions.
    • As requested originally, a scope plot showing the signal path of the uP (TXD / D) to the transceiver, then the bus and back out of the receiver (R) to the uP (RXD) will help eliminate a lot of possible issues.

    -- Scott

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Scott Monroe
    Posted by Scott Monroe
    on Dec 20 2012 12:55 PM
    Expert4735 points

    See the correction above. -- Scott

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Dhiv Sekar
    Posted by Dhiv Sekar
    on Dec 20 2012 21:43 PM
    Prodigy65 points

    Thanks for the reply scott .

    We have connected gnd and vcc to the corresponding pins of transceiver as you said , but left out in the schematic by mistake. We will make all other corrections as you said , and get back to you.

    Regards,

    Dhiv .

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Dhiv Sekar
    Posted by Dhiv Sekar
    on Dec 21 2012 02:54 AM
    Prodigy65 points

    Thank you so much Scott. We couldn't have done it without your help. After making the changes , now both the interfaces are working fine . Transmission and reception are perfect between DCAN0 and DCAN1.

    Thanks and regards,

    Dhiv :)

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Ajish Sasidharannair
    Posted by Ajish Sasidharannair
    on Dec 21 2012 03:21 AM
    Prodigy20 points

    Thank you Scott  for the review and comments to our post.

     

    Regards,

    Ajish

    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