• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 4 answers
  • Subscribers 31 subscribers
  • Views 565 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.

MCF8316AEVM: The development board goes down with no error reported

Cherry Zhou
Mastermind 22235 points
Part Number: MCF8316AEVM
Other Parts Discussed in Thread: MCF8316A, MCF8315A, MCF8316C-Q1

Hi Team,

TI EVM are being used, and it went down after a period of operation and no any errors were reported.

Could you help check this case? Thanks.

Best Regards,

Cherry

  • 0
    TI__Mastermind 24080 points

    Hi Cherry,

    I see that Auto Read Motor Status is enabled. The MCF8316A has a known I2C communication issue listed as Errata #8 in our Production device information FAQ. If I2C communication is made with the MCF8316A while the motor is spinning the device will not longer respond to I2C communication and will need to be power cycled to recover. To avoid this Errata we recommend not sending any I2C read or writes to the MCF8316A while it is operating the motor.

    Regards,

    Joshua

  • 0 in reply to Joshua Horlander Cruz
    TI__Mastermind 22235 points

    Hi Joshua,

    Thank you for the support and the customer would like to know if there is any other way to reset MCF8316A other than power cycled?

    Thanks and Regards,

    Cherry

  • 0 in reply to Cherry Zhou
    TI__Mastermind 18981 points

    Hi Cherry,

    Thanks for your post to the e2e motor drivers forum.

    Many of our team members are currently out of office for US holiday timeframe - but will be back in office by 1st week of January.

    Please anticipate a delayed response & feel free to provide additional information in the meantime.
    Best Regards,
    Andrew

  • 0 in reply to Cherry Zhou
    TI__Mastermind 24080 points

    Hi Cherry,

    The only way to reset the MCF8316A is to power cycle the device.

    If the customer needs to communicate with the device through I2C while the device is operating the motor I would recommend taking a look at the MCF8316C-Q1 which does not have this issue. The MCF8315A  has similar specifications to the MCF8316A although it is rated for lower current at 4A peak. 

    Regards,

    Joshua

  • 0 in reply to Joshua Horlander Cruz
    Intellectual 750 points

    Can you please double check that the I2C issue is still present in the *production* version of the MCF8316A?  I think I saw a different post from TI that claimed this issue was only in the preproduction samples and had been fixed in the production version.

    Can you please provide a link to the Errata document for the production version of the chip?  I do not see it under the "Technical documentation" tab on the product page.

    If indeed the bug is still there in the production chip, it's a show-stopper for me, as I need to use I2C to send speed commands to the motor controller; so with the bug, once the motor is spinning I can't turn it off....

  • 0 in reply to Marc Schuman
    TI__Mastermind 24080 points

    Hello Marc,

    The I2C issue for the MCF8316A is listed as Errata #8 in our Production device information FAQ: https://e2e.ti.com/support/motor-drivers-group/motor-drivers/f/motor-drivers-forum/1066777/faq-production-device-information. This issue is present in the production version of the MCF8316 device.

    If a similar device that can communicate over I2C while the motor is being driven is needed I would recommend taking a look at the MCF8316C which contains a small amount of register map differences from the MCF8316A. If your motors peak current requirement is less than 4A, I would recommend taking a look at the MCF8315A which also has some register map differences from the MCF8316A. Both the MCF8316C and MCF8315A are pin-to-pin compatible with the MCF8316A.

    Regards,

    Joshua 

  • 0 in reply to Joshua Horlander Cruz
    Intellectual 750 points

    Thanks for your response.  I've been wondering what the differences are between the MCF8316A and the MCF8316C-Q1.  I had thought that perhaps the difference was just the AEC-Q100 certification.  But it seems there are differences in functionality--e.g. the working I2C and the register map differences.  Can you detail precisely what all the differences are, or point me to a document that gives this information?  I have to say that it's really tiresome to have to try comparing two 177 page datasheets word for word to try to eek out what differences there might be.  I wish that TI (and other vendors) would make it a practice to clearly call out what the differences are when they have two very similar components.  Either in the preface of the datasheet or in a companion document.

    Also I really think that the errata should be provided as a document on the product page along with the datasheet and app notes, rather than buried in the forums.

  • 0 in reply to Marc Schuman
    TI__Mastermind 24080 points

    Hi Marc,

    We currently do not have a document that outlines the differences between the MCF8316A and MCF8316C-Q1 devices. I will outline some of the major differences for convenience:

    Hardware Additions:

    • MCF8316C-Q1 offers internal pull-up resistor for the FG and nFAULT pins
    • MCF8316C-Q1 offers DACOUT pins for internal variable output
    • the MCF8316C-Q1 is AEC-Q100 qualified

    Firmware Differences:

    • MCF8316C-Q1 has general corrections to the firmware bugs present in the MCF8316A
    • MCf8316C-Q1 has register bit fields for selecting the variable to output on the DACOUT pins and whether to use the internal pull-ups on the FG and nFAULT pins

    The MCF8316C-Q1 is drop in replaceable with the MCF8316A mostly offering more features and addressing errata present in the MCF8316A, like the I2C errata #8.

    Marc Schuman said:
    Also I really think that the errata should be provided as a document on the product page along with the datasheet and app notes, rather than buried in the forums.

    We will look into placing the errata for devices in the  Technical Documentation section of the devices product page, thank you for this suggestion.

    Regards,

    Joshua