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.

  • Resolved

DRV2605: DRV2605 Problem

Genius 4875 points

Replies: 10

Views: 1226

Part Number: DRV2605

Hi Team,

 

I experience a weird problem with the DRV2605.

I initialize the DRV2605 according to the datasheet, and I use ERM.

 

Once I set the GO bit in the GO register it will never reset, no effect on the ERM as well (no vibration).

 

During initialization the GO bit is set first in the calibration process, which should end after 1 second, the GO bit never resets.

 

I tried skipping the calibration, so the the GO bit is set in the diagnostics, the same result, the GO bit will not reset.

 

I tried to skip the diagnostics as well, and set the GO bit only for vibration, there was no vibration, and the GO bit will not reset.

 

I attach me code.

Best Regards,

Shlomi

drv2605.h

drv2605.c

  • Hi Shlomi,

    It will take me some time to review the code. It sounds like the device may be in software standby mode if there is no waveform being played. Can you readback register 0x01 to check this?

    Regards,
    Kelly Griffin
    System Engineer

  • In reply to Kelly Griffin:

    Hi Kelly,


    I set the mode register according to desired state (calibration, or normal operation [go triggered by software]). It is very clear reading the code. 

    In any case I will read the register to verify the settings received correctly and will report back.

    Thanks,

    Shlomi

     

  • In reply to Shlomi Yehezkia:

    Hi Kelly,

    I attached the registers values.

    I see the OC_DETECT, but there is no short on the OUT pins.

    I attached as well the ERM datasheet.

    Best Regards,

    Shlomi

    Z4KH2B0470652.pdf

    DRV2605.docx

  • In reply to Shlomi Yehezkia:

    Shlomi,

    According to register 0x1D or 0d29 = 0xA0, the device is set in ERM open-loop mode. We have a setup guide and also an excel table on the DRV2605 product page that can help with the register settings.
    That ERM should be compatible with our device.

    Regards,
    Kelly Griffin
    System Engineer

  • In reply to Kelly Griffin:

    Hi Kelly,

    Yes, register 0x1D is set (to ERM closed loop) only after the calibration procedure, as per paragraph 8.3.1 in the datasheet (initialization procedure)

     

    And by the way, it says the default is closed loop, but it is open loop, I don't change the register before the calibration and it is read as open loop after power up.

     

    In any case it didn't work, same problem persists.

     

    I tried using the excel, also got to the same results.

     

    I tried using the same initialization as in the firmware code of Haptic Feedback with Bluetooth® Low Energy and iOS App Reference Design - same results.

     

    I tried the initialization according to DRV2605 Setup Guide [SLOA189] paragraph 1.6.1, without performing the calibration, I tried executing waveform #1, the GO register stayed 1, status register was 0x61 (same results as before).

    I tried adding to the above the calibration routine (twice, once using open loop and once using closed loop), as per paragraph 2.2.1 of  DRV2605 Setup Guide and I get the same results.

     

    Best Regards,
    Shlomi

  • In reply to Shlomi Yehezkia:

    I found the problem, I swapped between the VDD and OUT- pins by mistake.
  • In reply to Shlomi Yehezkia:

    Hi Kelly,

    I fixed the pinout issue.

    Now occasionally all is well, but almost every time the calibration (or diagnostics) fail. what can be the reason?

    My code and ERM datasheet attached.

    Best Regards,

    Shlomi

    4135.drv2605.h

    0741.drv2605.c

    Z4TH5B1241992.pdf

  • In reply to Shlomi Yehezkia:

    Hi Shlomi,

    The calibration can be tricky. There are a number of recent posts on why the calibration can fail. Can you reveiw these and let me know if any suggestions fix your problem?

    Regards,
    Kelly Griffin
    System Engineer

  • In reply to Shlomi Yehezkia:

    Hi Shlomi,

    We haven't heard back from you. I am assuming that you were able to resolve your issue. If no, just reply with additional information or create a new post if this was locked due to time-out.

    Best Regards
    José Luis Figueroa
    Audio Applications Engineer
  • In reply to José Luis:

    Hi Jose Luis,

    Sorry, I didn't update you, it is solved.

    Thanks,

    Shlomi

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.