• State Resolved
  • Locked Locked
  • Replies 13 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 301 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DRV8316REVM: How to reset, 3.3VBK doesn't light up anymore

Maxime Lemonnier
Prodigy 10 points
Part Number: DRV8316REVM
Other Parts Discussed in Thread: DRV8316, LAUNCHXL-F280049C, DRV8305,

Hi, 

I've been sucessfully communicating with the drv8316 using SPI, I could read all the registers, unlock write, write to some registers. I'm powering the EVM using an 12V/15A power source source and I am communicating with it using a MCU.

MCU [GND, MOSI, MISO, SCK, SS] <-> EVM [AGND, SDI, SDO, SCK, nCS]

I've noticed something weird: When I power-cycled the EVM board from the 12V source, the D3 led as well as the 3.3VBK LED would stay lit, **I had to unpower the MCU to make the leds shut down**.

That means it powers itself from the nCS pin!!!

I was trying different settings, including changeing the SDO_MODE to push-pull mode, power-cycling the device to restore default values.

Then the 3.3VBK led stoppe lighting up, and I could never communicate through SPI again.

I've just ordered a LAUNCHXL-F280049C with the pale hope to revive it, but really, I can't see how I could do anything wrong by just power-cycling and SPI-ing with the board.

I'm quite sad, I have no backup board.

Thank you!

  • 0
    TI__Intellectual 1350 points

    Maxime,

    I'll get a response to you by the end of tomorrow.

    best,

    Johnny

  • 0 in reply to Johnny Vallespir
    Prodigy 10 points

    Just ordered a new REVM board, I still have to find out what I did wrong with the first one. Looking forward your answer. I also have a DRV8305 BOOSTXL board that did not behave like this at all.

  • 0 in reply to Johnny Vallespir
    TI__Intellectual 1350 points

    Hello Maxime,


    We have not yet investigated SDO_MODE through SPI, as this device is rather new. One of my teammates plans to replicate this issue in the lab. Please let us know if you'd like us to send you a new board. In the meantime, please check for apparent shorts or open circuits via a continuity test in between AGND and the 4 SPI pins, and between AVDD and the 4 SPI pins and let me know what you find.


    Best,
    Johnny

  • 0 in reply to Johnny Vallespir
    Prodigy 10 points

    Hi Johnny,

    I did the checks you asked for, not short found.

    AGND <-> (SDI, SDO, SCK, nCS)

    3.3VBK <-> (SDI, SDO, SCK, nCS)

    I would't mind a new board, since it also fried my MCU nCS pin :)

    I'm willing to assist you debugging this in any way, I of course have a decent scope and logict analyser.

    My  LAUNCHXL-F280049C is out for delivery.

    You might want to know that this  behavior (3.3VBK led staying lit event if I power cycled VBAT) was present before I fiddled with SDO_MODE (it was in fact the reason why I fiddled with it, kinda quick trial/error thing) 

  • 0 in reply to Johnny Vallespir
    Prodigy 10 points

    whops!

    sorry, whist time I really tested with AVDD (using one side of C1), same result, no short.

  • 0 in reply to Maxime Lemonnier
    Prodigy 10 points

    I just received my LAUNCHXL, hooked up instaspin, connected correctly ("Hardware Connected").

    (using https://dev.ti.com/gallery/view/InternalBLDC/DRV8316REVM_InstaSPIN_Universal_GUI/ver/1.0.0/)

    The UI could identify various stuff such input current and voltage as well as Bus Voltage, but that's just the MCU's ADC working. When I click run the motor don't move.

    Also, "MCU_LED" on the 8316REVM is shut down, and I tried to manually read all valid register addresses and got all 0's

    I gues that confirms clinical death.

    There is no sign of harm on the board whatsoever.

  • 0 in reply to Maxime Lemonnier
    TI__Mastermind 26046 points

    Hi Maxime,

    Can you perform the following steps when connecting to InstaSPIN just to confirm? (not documented correctly in User's Guide)

    1) After Hardware Connected, click "Enable System" on GUI

    2) Wait for "OffsetCalc" box to automatically uncheck

    3) Click on SPI register tab and click "Read" to read all registers. 

    A good way to show whether SPI is working is if "NPOR" bit = 1 after read. MCU_LED only lights up after motor is identified. 

    I am looking into the SDO_MODE issue in the lab now, will provide an update by EoD. 

    Thanks,
    Aaron

  • 0 in reply to Aaron Barrera
    TI__Mastermind 26046 points

    Hi Maxime,

    Can you perform the following steps when connecting to InstaSPIN just to confirm? (not documented correctly in User's Guide)

    1) After Hardware Connected, click "Enable System" on GUI

    2) Wait for "OffsetCalc" box to automatically uncheck

    3) Click on SPI register tab and click "Read" to read all registers. 

    A good way to show whether SPI is working is if "NPOR" bit = 1 after read. MCU_LED only lights up after motor is identified. 


    I just ran a test setting SDO_MODE to push pull mode, performed a functional SPI read, power cycled the device to restore defaults, and 3V3BK and VM LEDs turned off as expected. I did not see any issues where 3.3VBK LED stayed on after power cycling the board. Are you by chance connecting MCU power to 3V3BK on the DRV8316REVM, or supplying any external power besides VM to the EVM elsewhere?

    Thanks,
    Aaron

  • 0 in reply to Maxime Lemonnier
    Prodigy 10 points

    Weird, I can't reply to you directly.

    So I did all you suggested. SPI is dead, NPOR on IC STATUS is 0, in fact everything is 0. My LA tells me this.

    logic analyser, SPI mode 1, MSB First

    you can see some small spikes on MISO, but I think they're just noise.

    I swear I had this weird 3.3VBK LED not shutting down from the very beginning, when connecting, precisely:

    Atmel SAMD21 [GND, MOSI, MISO, SCK, SS] <-> DRV8316REVM [AGND, SDI, SDO, SCK, nCS]

    as well as +12V/VGND on VBAT/PGND

    **Note, I had not plugged a motor yet**

    The board worked for a few hours and 15-30 power-cycles (I never got to try it with a motor). I did not have a  LAUNCHXL-F280049C at that time.

     Are you by chance connecting MCU power to 3V3BK on the DRV8316REVM, or supplying any external power besides VM to the EVM elsewhere?

    No, 100% positive!

    I was hooked up exactly as shown (plus maybe L-A probles)

  • 0 in reply to Aaron Barrera
    Prodigy 10 points

    If you're kind enough to send a replacement board, If you included a couple DRV8316 chips, I would try to rework the board to confirm that the issue was with the chip and not some other component.

  • 0 in reply to Maxime Lemonnier
    TI__Mastermind 21805 points

    Hi Maxime,

    Aaron will get back to you tomorrow on this issue.

    Thanks,

    Matt

  • 0 in reply to Matt Hein
    Prodigy 10 points

    Hello Matt, Hello Aaron,

    Firstof all thanks a lot for what you've already tried. I'm very gratefull.

    Unfortunately, I think there is very little thing to do for now.

    I ordered a new EVM board from Ti.com which should arrive early next week.

    Johnny suggested that it might be possible to send me a replacement, which could prove usefull considering what happened with the first board.

    Again, I'd be curious to try to rework the bricked board with a new DRV8316 chip, but these kind of packages are a bit tricky.

  • +1 in reply to Maxime Lemonnier
    TI__Intellectual 1350 points

    Thanks for the update, we are in the process of shipping parts. Let us know when you receive your parts, and we can open up a new thread if needed.