• 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 » Microcontrollers » Hercules™ Safety Microcontrollers » Hercules™ Safety Microcontrollers Forum » All Tags » DCAN
Share
Hercules™ Safety Microcontrollers
  • Forum
  • E2E Wiki

Browse by Tags

Hercules™ Safety Microcontrollers

Welcome to the Hercules™ Safety Microcontrollers Section of the TI E2E Support Community. Ask questions, share knowledge, explore ideas, and help solve problems with fellow engineers. To post a question, click on the forum tab then "New Post".

Sign In to Post
Tags
You have subscribed to this tag. To view or manage your tag subscriptions, click here.   Close
You have unsubscribed from this tag. To view or manage your tag subscriptions, click here.   Close
You are currently viewing:
DCAN
  • CAN
  • crystal
  • DCAN communication
  • DCAN IFx registers
  • DCAN interrupts
  • DMA
  • HALCoGen
  • loop-back
  • oscin
  • tms570
  • TMS570LS
  • tolerance
  • VIM
Related Posts
  • Forum Post: Are there any requirements on the device clock input related to the DCAN module? (CAN network timing related?)

    Anthony F. Seely Anthony F. Seely
    Are there any requirements on the device clock input, (or tolerances on the crystal used with the device) related to the DCAN module?
    on Apr 7, 2010
  • Forum Post: Does DCAN_INTPNDX bit is set unconditionally upon successful transmission of DCAN Message irrespective of TxIE bit of the respective Message Object?

    Pashan Pashan
    Hello, In the TMS470R1VF3382 devices with SCC CAN Controller, there was a TA bit for every Transmitted Message Object [spnu197e.pdf]. I am trying to implement similar behaviour of Transmit_Message_Acknowledge within DCAN. How do I perform the similar function of Transmit_Completed in Polling...
    on Oct 18, 2010
  • Forum Post: Re: DCAN Message Object, Receive Message Interrupt Processing, DCANINT apparently incorrect

    Pratip Kumar Pratip Kumar
    Hi Tony, I'm in discussion with a CAN expert reagrding the issue that you are facing. I will get back to you soon. Best Regards, Pratip
    on Nov 26, 2010
  • Forum Post: Re: DCAN Message Object, Receive Message Interrupt Processing, DCANINT apparently incorrect

    Pratip Kumar Pratip Kumar
    Hi Tony, We tried to replicate this scenario and we do not see any issue from our side with your settings as you have explained above: - 2 Nodes - 2 Mail boxes [0x5 (configured for ID 0x222)and 0x10(configured for ID 0x229)] I assume the configuration on the receive side is as on the transmit...
    on Dec 6, 2010
  • Forum Post: DCAN Message Object, Receive Message Interrupt Processing, DCANINT apparently incorrect

    Tony Morrell Tony Morrell
    Hi, I have two DCAN message objects configured with all parameters the same except for the 11-bit arbitration id (in DCANIF1ARB). Message object 5 is the first receive message object configured and is the lowest numbered (i.e. highest priority receive message). Message object 10 is configured following...
    on Nov 23, 2010
  • Forum Post: DCAN stuff error

    Jonas Axelsson Jonas Axelsson
    I get "stuff error" ( ErrStat = 0x00000063 ) when I send messages with the function "canTransmit". I use the USB stick and CCSv4. I run the demo project "Demo_Software_Ver1_1". I have only added two lines: canInit(); i = canTransmit((canBASE_t *)canREG1, canMESSAGE_BOX1...
    on Jul 15, 2011
  • Forum Post: TMS570 CAN bit rate calculation

    Luffy Li Luffy Li
    Hi, everyone, We’ve met a problem in TMS570 CAN bit rate calculation, could you help me to check it? Thanks! As we all know, the Prop_Seg, which is part of the bit time, depends on the delay of driver ,the delay of the receive circuit and the delay of driver line. In my opinion, the delay...
    on Oct 11, 2011
  • Forum Post: Re: CAN Bus TX-RX

    Jean-Marc Mifsud Jean-Marc Mifsud
    Gil, I did some test to reproduce your environment and I don't see your problem. In DCAN to enable the external Loop Back mode, you have to: 1] Set TEST (bit7) in DCANCTL at offsett 0x00. 2] Set EXL (bit8) in DCANTEST at offsett 0x14. While in this mode, the DCAN will be able to transmit...
    on Feb 17, 2012
  • Forum Post: HALCOGEN 3.0 issue related to CAN driver

    J Joson J Joson
    I don't know if this is already reported. I did not see one. There is a strange defect in CAN driver code : /** @file can.c * @brief CAN Driver Source File * @date 15.dec.2011 * @version 3.00.000 ..... */ The following busy wait loop is sprinkled throughout the code, /** - Wait until...
    on Mar 2, 2012
  • Forum Post: RE: IO / Functional Multiplexing during program execution

    Diwakar Bansal Diwakar Bansal
    Hello Lorenz, Sorry for the delayed response. - MII does not support GIO functionality. - DCAN does support GIO mode, which can be used prior to DCAN initialization and DCAN node participating on the bus. But it is not recommended to switch back from functional to GIO mode once the DCAN communication...
    on May 8, 2012
  • Forum Post: DCAN Initialisation Corrupted in DCANTIOC/DCANRIOC on write to DCANCTL

    Tony Morrell Tony Morrell
    Hi, I have a problem with DCAN module initialisation. In the following code snippet I set DCAN initialisation mode by write to DCANCTL with CCE = Init = 1. I then configure both Tx and Rx by write to DCANTIOC and DCANRIOC. I then exit initialisation mode by writing to DCANCTL again with CCE = Init...
    on Aug 20, 2012
  • Forum Post: TMS570 DMA and DCAN Hardware Request

    Joris Gansler Joris Gansler
    Hello, I'm trying to configure DCAN and DMA to move incoming messages from the IF3-Registers to an address in RAM. Therefore I connected DCAN1 (with MessageBox1 as TxD) and DCAN2 (with MessageBox1 as RxD) and set the Update Enable Bit for the DCAN2-MsgBox1. To enable DMA Request for DCAN2IF3 I set...
    on May 6, 2011
  • Forum Post: DCAN IF1CMD, DCAN IF2CMD Register Busy Bit setting condition

    Pashan Pashan
    Hello, Within DCAN there are registers called IF1CMD, IF2CMD Within those registers, there is a bit called BUSY. This above mentioned bit is set to 1 whenever CPU writes the MESSAGE NUMBER field of the above registers. Is that the one and only one condition due to which this BUSY bit will...
    on Dec 2, 2010
  • Forum Post: CAN-BUS problems

    Michael Enggaard Pedersen Michael Enggaard Pedersen
    Hello, What am I doing wrong? I'm trying to get the CAN-bus up running on a Hercules development board. Until now I have copied the example from HalCodGen on CAN-bus with interrupt. I am adding this to a small program where I am already have interrupt up running from RTI and ADC. But...
    on Mar 20, 2012
  • Forum Post: TMS570 CAN Data transfer is not

    Alex Dikusar Alex Dikusar
    Hello, someone has experience with the board TMS570-CAN ( https://www.olimex.com/Products/ARM/TI/TMS570-CAN/ ) as it is with its modules CAN. Created the project: /** @example example_canCommunication.c * This is an example which describes the steps to create an example application which * configures...
    on May 16, 2013
  • Forum Post: how received all dcan message identifier number from one message box or whitout message boxs.

    Halil Ibrahim Halil Ibrahim
    Hi, I want to receieved 43 can message with tms570LS31xhdk. I dont want to using all message box. how received all dcan message identifier number from one message box or whitout message boxs. Thanks.
    on May 17, 2013
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