Are the DRV8301 SPI messages necessary for Instaspin Motion on TMS320F28069M

Steven Hung

Other Parts Discussed in Thread: DRV8301, TMS320F28069M, MOTORWARE

Hello there,

I'm using Instaspin motion on the TMS320F28069M LanchXL with the DRV8301 booster pack.

I noticed in the Instaspin labs some configuration settings are sent to the DRV8301 booster pack during every cycle of forever loop and I want to use that SPI interface to integrate another sensor. I've commented those lines out with no perceived problems while running labs, but I wanted to know if I might have broken something in the long run. I left the initial HAL_writeDrvData and HAL_readDrvData before the forever loop.

Thank you,

Steven Hung

over 10 years ago

0 Nicholas Oborny over 10 years ago

TI__Mastermind 21320 points

Hi Steven,

There shouldn't be any issues in removing these from the "for loop". They are mainly to allow real time interfacing to the DRV8301 SPI for system debugging.

In a real system the SPI would be configured on startup and only polled if a fault occurred. Faults are signaled through dedicated GPIO pins (nFAULT and nOCTW) with details obtained from the SPI registers.

0 Steven Hung over 10 years ago in reply to Nicholas Oborny

Prodigy 80 points

Awesome, thank you Nick.

0 Jeff Stafford over 10 years ago in reply to Steven Hung

TI__Expert 4595 points

Keep in mind there are (2) SPI modules on the 069. I think MotorWare is using SPI-B so you do have the option to use SPI-A for devices.

C2000™︎ microcontrollers

C2000 microcontrollers forum

Are the DRV8301 SPI messages necessary for Instaspin Motion on TMS320F28069M