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.
Part Number: DRV10983
Hi TI team,
I have successfully worked on the DRV10983-Q1 EVM. Able to perform some of the basic functionalities using the GUI (i.e. I2C Speed Control Override (On the Display tab), and Startup setting (On the Basic Settings tab)). I have similar prototype board that uses the DRV10983 mimicked off the Application schematic in the Datasheet. This prototype board when powered with the 3 phase motor wires connected to a sample BLDC motor, without any prior I2C programming or Analog adjustments, the motor runs in closed loop control as the motor was running with DRV10983-Q1 EVM PCB. I would like to program the prototype DRV10983 board using the I2C interface being used for EVM (Meaning with the use of the 10-pin ribbon cable connected to USB2ANY box which then connects to the DRV10983-Q1 EVM board). There are header holes available for test points next to the 10-pin ribbon connector which are available for this purpose.
When I power-up my prototype board, without powering the DRV10983-Q1 EVM board, to be able to program the board using the I2C interface in the GUI I get 3 error messages.
Please note: I have tried selecting both DRV10983, and DRV10983-Q1 EVM at the start-up prompts of the GUI to resolve the issue when using the prototype board. Note also that the SDL, SDA, FG, and SPEED wires from prototype board are the only wires being used to connect to the EVM board. I have not tried soldering the wires thru the holes in the "P2" area of the EVM. This will probably by next step if not successful. Also the EVM has not been powered up during the I2C programming phase only the prototype board that is being tested (Assuming that the I2C programming will still work regardless of whether the EVM powered or not when the prototype board using the DRV10983 is being used).
Please provide any input at your earliest on how to resolve this situation and if there are similar case examples your team maybe able to reference me in the E2E forum.
Thank you for your support.
In reply to Brian Schmidt:
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
I tried the above wiring, as suggested, with our board. So far this has not worked. I am not sure what is missing. Continue to receive the same register "write", and read" errors. I can share other details with you. Conversely, if its possible for you to reach out to Innocent Irakoze, at TI, he would be able to provide other details that I have shared with him.
In reply to Mohammad Atif:
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.