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.

DRV2605EVM-CT: Binary Counting->Analog Input mode, pressing any button seems to reboot the board

Part Number: DRV2605EVM-CT
Other Parts Discussed in Thread: DRV2605LEVM-CT, DRV2605L, DRV2605, USB2ANY

Im attempting to demo the analog input mode. However whenever I enter binary counting mode and go to mode 4 for analog input, when I press any button it appears to reboot the board and stick me back in Demo Mode.


Is this a known issue or a bad board? Is there an updated firmware? Anyone have analog input working with an eval kit?


Thanks

Jacob

  • Hi Jacob,

    Was this board recently purchased? Please try updating the firmware.
    I have not heard of this issue. We will test it and provide additional feedback.
  • Yes just this week from digikey. Do you have a way to tell current firmware version? What about a link to a newer firmware?
  • Actually I need to clarify, this is a DRV2605LEVM-CT. Seems like the newest firmware is sept 2014
    www.ti.com/.../DRV2605LEVM-CT
    So Im not thinking I could be much behind.

    Apparently I need an msp430 to update anyway which I dont have on me. Is there a way to blink firmware version or something?
  • Yes, it should be the current firmware. I tested this on the DRV2605 (it worked), but not the DRV2605L EVM. The devices are different. We will find a '05L EVM tomorrow an give it a shot.
  • Hi Kelly,

    Did you find anything? Thanks for checking on this.

    --Jacob
  • Hi Jacob,

    Sorry about the delay here. I had some trouble getting my CCS to flash the firmware. I wanted to make sure the firmware on my EVM was the released version on the web (should also be the version shipping in EVMs). Now that I have gotten it to work, it does seem like there is an issue with the analog input mode. When I go to mode 4 in binary mode and hit a button, the device just freezes. I am trying to figure out what is wrong with this function in the firmware.
    I have tried other modes and they seem to work well. Could you try testing with the PWM Input (Mode 2) in the meantime?
    I have also tried using the analog mode with Haptic Control Console (HCC). Do you have a USB2ANY board? This allows you to connect to HCC and you can test analog input mode this way.
  • No sadly analog input using the audio jack on EVM is specifically what I'm interested in evaluating.

    No I dont have a USB2ANY and research seems to indicate I cant purchase one?

    It sounds like Ill just need an msp430 and some headers in order to update my EVM when you release the new firmware? Is that still the preferred method?


  • Any very general estimation on what kind of priority this might get? Week, month, months?

    And just repeating my questions from above so they dont get lost:

    No I dont have a USB2ANY and research seems to indicate I cat purchase one? 

    When you have a firmware update It sounds like Ill just need an msp430 and some headers in order to update my EVM, Is that still the preferred method?

    Thanks,

    Jacob

  • Hi jacob,

    We will work on the firmware this week. Expect an update by Friday.
    In the meantime, I will reach out via email and we can get you a USB2ANY.
  • Hi Jacob,

    We were not able to get the firmware working correctly this week. We will continue to work on the solution next week.
  • Hi Kelly,

    Have you guys gotten any time to take a look at Analog Input mode? Ive located and soldered the headers on an msp430 so I should be good for a firmware update.

    Thanks,
    Jacob

  • Hey Jacob,

    The issue that we have found was that the size of the code was too large for the MSP430 microcontroller that can be found on that EVM. So whenever one had entered this mode, it would have come to memory overflow and the MSP430 would have reset itself or would have gotten stuck into an infinite loop.

    We have come up with a way to make this mode work by deleting some files. If you want this mode to work, you have to delete recorder and memory game, and also change the main.c code (because it contains #include and then those two files, you need to delete/comment that). Then debug the code again on the MCU and this mode will work.

    The only thing is, by doing so you will lose many other functionalities, so in order to regain them, you will have to put the old firmware back (the one that can be found on ti.com).

    Hope this helps, best regards,
    Marko