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.

CCS/BOOSTXL-DRV8305EVM: BOOSTXL-DRV8305EVM Vs BOOSTXL-DRV8320RS

Part Number: BOOSTXL-DRV8305EVM
Other Parts Discussed in Thread: DRV8305, BOOSTXL-DRV8320RS, TMS320F280049C, LAUNCHXL-F280049C, DRV8323, DRV8320

Tool/software: Code Composer Studio

Dear team,

This is regarding the usage of DRV8305 EVM with 280049C. Ideally demo board for using with TMS320F280049C  launchpad is BOOSTXL-DRV8320RS. But, if I want to use DRV8305 EVM with 280049C, would I need to change anything in the lab programs written for 280049C wrt to SPI settings. Like clock, speed etc.

And please let me know the possibility of using the Universal Instaspin GUI if I have to use it BOOSTXL-DRV8320RS & TMS320F280049C or BOOSTXL- DRV8305 EVM with TMS320F280049C.

Thanks,

Harish K.

  • Hello Harish,

    In general, we expect users to transition to their own launch pad of choice after playing with the pre-determined path to evaluate that the gate driver they've selected is good enough. In the case, the DRV8305's predetermined path is the LAUNCHXL-F28207F or LAUNCHXL-F28069M

    So if you want to stray from the predetermined path, you'll need to cross-reference the DRV8323 user guide, section 2.4 of the pin out of the LAUNCHXL-F280049C functions,  with the DRV8305 user guide, section 2.2 of DRV8305 EVM pin out, and make sure the inputs from the DRV8305 match the expected inputs on LAUNCHXL-F280049C.

    Once you've done that, the hardware is all set and I believe you do need to modify the labs a bit. I'll kick this post over to the C2k folks to give some guidance on what exactly needs to be changed.

    Best,

    -Cole

  • Hi Cole,

    Thanks for the reply. The reason that we wanted to use DRV8305 EVM since it is compatible for both 280049C & 28379D. I believe DRV8305 can be used as a plug n play for 28379D. 

    Awaiting your team response on the software side.

    Thanks,

    Harish K.

  • You can find the instaspin-foc labs based on lauchxl-f280049c and drv8320rs that supports a GUI. You just need to change the hal.c, hal.h and user.h and use the drv8305 driver instead of drv8320 driver in the example labs for supporting the drv8305 evm board, and you can still use the GUI in motor control SDK.

    MotorControl software development kit (SDK)

    http://www.ti.com/tool/c2000ware-motorcontrol-sdk

  • Hi Yanming,

    Thanks for the reply.  Are these the below functions that I need to modify in case if I want to use 8305 in the existing projects with 280049C?

    HAL_setupDRVSPI, HAL_readDRVData, HAL_writeDRVData & change the configuration of drv8320.h as per the registers in DRV8305.

    Or will it better if I just replace the files of drv8320 with drv8305.c, drv8305.h, DRV830x_SPI.c,DRV830x_SPI.h?

    Please suggest.

    Thanks,

    Harish K.

  • Replace all the functions with prefixal "DRV8320_", and use the drv8305.c/.h instead of the drv8320.c/.h in the project.

    Or you can change the drv8320 register definition in drv8320.h/.c based on the drv8305 datasheet.