• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 535 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MCF8316A: MCF8316A0V vs. MCF8316A1V

Ben Gelinas
Prodigy 100 points
Part Number: MCF8316A
Other Parts Discussed in Thread: , MCT8316A, MCF8315A, MCT8315A

Hi,

I'm curious what the difference is with the MCF8316A0V and the MCF8316A1V.  My main confusion lies within the two different pinouts.  I have attached a couple of screenshots at the end of this post for reference: 

The MCF8316AEVM (eval board) is based on the MCF8316A0V and the pinout states that pins 37 and 38 are DACOUT1/XI and DACOUT2/X2, respectively.  I can see that the External oscillator circuit, although not populated, does exist on the eval board.  Furthermore, pin 36 is labeled as DACOUT/SOx, and pin 39 is labeled as ALARM.  When looking at the datasheet for the "MCF8316A" I can see that the pins 36-39 are: NC, NC, SOX, and NC, respectively.  I cannot find any documentation regarding the variation within the datasheet for the "MCF8316A" . 

This leads me to ask a couple of questions to hopefully clarify:

1.  On the eval board, my understanding is that the DACOUT pins are used for an optional external oscillator.  Is this correct? And, has this been removed on more recent iterations of the MCF8316 IC?

2.  Is it safe to assume that the pinout on the MCF8316 data sheet is correct?

3. Does the "MCF8316A0VRGFR" actually exist, or is this just an arbitrary placeholder for the eval board to host either the MCF or the MCT versions of the IC?  I can see that the pinout of the MCT is almost identical to the schematic model in the eval board datasheet, with the only obvious difference being pin 39 (ALARM on the eval board, NC on the MCT pinout).

4. Perhaps the most important question of all:  I would like to move forward with designing a motor controller based on the MCF8316A technology.  I am of the opinion that the best way to move forward is to assume the datasheet pinout for the MCF8316A is correct, and that I need not worry about DACOUT1, DACOUT2, or ALARM (none of these options would be used anyway).  Is this correct?

Thank you for all your help in clearing up some of my confusions.  I look forward to better understanding the variations of the motor driver IC family.

Datasheet Pinout for MCF8316A:

Datasheet Pinout for MCT8316A:

MCF8316A0VRGFR from eval board datasheet:

v

  • 0
    TI__Expert 5578 points

    Hi Ben,

    Thanks for your question on the Motor Drives E2E Forum. 

    I will aim to provide an answer on this by the end of the week!

    Best,

    Robert

  • +1 in reply to Robert Wedan
    TI__Expert 5578 points

    Hi Ben,

    It seems like the main source of the confusion is the EVM schematic and not the datasheet itself. The EVM schematic is reused and slightly adapted for the MCT8316A, MCF8316A, MCT8315A, and the MCF8315A to help with our design efforts. The only difference between them are those DACOUT, NC, and Alarm pins that you recognized.

    For all questions about device specifics your best source will always be the datasheet. There may be some nomenclature errors in the EVM schematic just because this gets reused and adapted for new devices.

    Looking at your questions, question 3 probably makes the most sense to start with.

    3 - You are correct, MCF8316A0VRGFR was a place holder OPN when building this schematic and is not released. We develop our EVMs in parallel with our devices so really small device name changes may occur. The Alarm pin you mentioned was a pin that can be found in the MCx8315A pinout.

    1 - I think this is answered in the previous questions but MCF8316A was never released with DACOUT pins.

    2 - Yes, the datasheet is the number 1 source for each part that we released and holds the best information about device specs, pinouts, and application details.

    4 - This is answered in the previous questions. You also might want to take a look at MCF8315A if you are interested in the Alarm pin functionality. MCF8315A is meant for lower power motors so this may also depend on your motor power requirements.

     

    I hope this provides some clarity to our portfolio. If you ever want to learn more about our offerings, please check out our BLDC integrated control portfolio landing page: https://www.ti.com/motor-drivers/brushless-dc-bldc-drivers/integrated-control-bldc-drivers/overview.html

     

    If this answers your question please help by marking this thread as resolved!

    Best,

    Robert

  • 0 in reply to Robert Wedan
    Prodigy 100 points

    Thanks so much for your reply, Robert!  This really helped clear things up and install some confidence in my understanding. 

    Cheers!