• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 86 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.

DRV8334EVM: DRV8334EVM set up issue

Masato Matsuda
Prodigy 140 points

Part Number: DRV8334EVM
Other Parts Discussed in Thread: LAUNCHXL-F280049C, DRV8334, LAUNCHXL-F2800157,

Hi, my customer, Nidec mobility, is trying to set up DRV8334EVM with LAUNCHXL-F2800157 using MATLAB environment. Although LAUNCHXL-F280049C is recommended to use in the user's guide of DRV8334EVM, but can LAUNCHXL-F2800157 also work with DRV8334EVM using DRV8334_Sensored_Trapezoidal_GUI?

After powering up, issue SPI command using MATLAB with LAUNCHXL-F2800157 to initialize control regestor of DRV8334 according to following 22 data (24bits without CRC).

0x360007
0x340000
0x36BA06
0x388009
0x3C0301
0x3E0000
0x420000
0x440000
0x460300
0x480007
0x4A0000
0x4C0000
0x528888
0x5635F9
0x585141
0x5A00FB
0x5C0000
0x5E0800
0x6030BB
0x660000
0x6C0000
0x900000

After sending them out, nFAULT LED is lit, and then send them again then nFAULT turns off.

Why does nFAULT LED turn on every first time powering up, and it turns off after sending command second time? Is there any proper order to initinalize regester?

 

 

 

  • 0
    TI__Genius 11115 points

    Hello,

    The GUI will only operate correctly with the F280049C MCU launchpad. I would recommend evaluating DRV hardware with the original F280049C set up.

    This way, customer can validate the operation of the DRV, and eventually can write their own MCU code to test F2800157 later on.

    This is because DRV performance will be independent of the MCU used.

    Thanks,

    Joseph