DRV8301 Suddenly Becomes Unresponsive

Edward Averill

Other Parts Discussed in Thread: DRV8301

I'm seeing some very odd behavior from the DRV8301 we're using in our motor control system.

Periodically, the chip either stops responding to SPI commands or replies to register reads with zeros. Getting a continual zero for device ID should never happen.

Are there any known issues that would cause this behavior? I'm only resetting the chip on system -power-up, otherwise it's continually enabled.

Also, are there any conditions other than over-temp that would cause the chip to reset? I have all the over-current operations tuned off, so that shouldn't be causing us any problems.

All assistance greatly appreciated. I'm hopeful we didn't somehow bake the chip, but I would expect the DRV to not work at all.

Ed Averill

over 9 years ago

0 Rick Duncan over 9 years ago

TI__Guru** 114905 points

Hi Ed,

Our expert on the device has been notified and should respond soon.

0 Edward Averill over 9 years ago in reply to Rick Duncan

Genius 3100 points

Thanks, I appreciate it!

Ed Averill

0 Nicholas Oborny over 9 years ago

TI__Mastermind 21320 points

Hi Ed,

Can you confirm a few things?

Is this behavior erratic or permanent?

How is the PCB manufactured? Is the PowerPAD well connected?

How is the layout and noise around the DVDD regulator? Noise on this pin could potentially cause a device reset (supplies the internal logic).

0 Edward Averill over 9 years ago in reply to Nicholas Oborny

Genius 3100 points

Good morning!

I had to pass this to the hardware guy - he's a bit busy but should get back to you soon.

It seems to be erratic - sometimes it'll run for hours, others POOF in just a few minutes.

Ed Averill

0 Jeff Salisbury over 9 years ago in reply to Nicholas Oborny

Intellectual 345 points

Thanks for asking.

Not quite sure how to answer how the pcb was manufactured. The powerPAD is there and should be well connected.

The layout has a 1uF cap between that pin and ground as per instructed by the datasheet. There is maybe 1/2 an inch of a trace before the DRV chip.

Sounds like Ed just found some timeout code problems. I will let him comment so I don't muddy the issue. Appreciate the help

0 Edward Averill over 9 years ago in reply to Jeff Salisbury

Genius 3100 points

The code issues are in the I2C Driverlib code - I'm off to the TI-RTOS forum to post.

0 Edward Averill over 9 years ago in reply to Edward Averill

Genius 3100 points

We got a new spin of our board on Monday, we can revisit this topic if it comes up in testing.

Going to close this as "answered" for now.

Ed Averill

Motor drivers

Motor drivers forum

DRV8301 Suddenly Becomes Unresponsive