DRV8343S-Q1EVM: DRV8343 AND MSP430 mcu with EXTERNAL FT232RL USB CONVERTOR NOT DETECTED IN GUI

Hi Bhuvaneshwaran,

Can you show a picture of your setup? Make sure you power the EVM first before plugging in the USB cable into the EVM. 

Thanks,
Aaron

Hi Aaron 

I have attached my setup for connecting FTDI to target board and PC 

first is target board connected with FD232rl supply 3.3v ,GND,TX and RX pin

second image target board connected 12v from external power supply and corresponding of RX,TX, GND signal from FD232RL 

...

Please let me know your feed back !!!

still not able to connect FD232rl (USB to UART convertor ) in GUI, i have tried two more pc on same setup but not yet connected,

I have attached GUI log file for your reference

Hi Bhuvaneshwaran,

Can you share schematic of your DRV8343 PCB board? Does the FT232RL board connect to the correct pins of the MCU used on your board? Are you trying to replicate the DRV8343 EVM on your PCB so that it interacts with the GUI?

Thanks,
Aaron

Hi Aaron

                Yes , FT232RL board pin connected MCU through 6 pin connector (tx and rx for usb , swbdtio , swbtck for flashing , 3.3v and GND), its verified correctly connected.

sorry i am not able to share my schematic this is confidential issue ,

yes , i am trying to replicate the DRV8343 EVM on my  PCB but 

we can not use which is having DRV8343 EVB pcb internal LDO and FT232RL IC apart from this two most of schematic same , this is for (sensorless bldc motor) , development 

first we are trying to run the motor through GUI then move to further proceed, 

I have attached below image for your reference,

target board MCU will get power one is USB another one is external 12v power from drv8343 LDO output of 3.3v   .

.

Hi Bhuvaneshwaran,

I would not recommend trying to depend on running the GUI on a custom DRV8343-Q1 PCB board. 

The GUI application firmware depends on multiple protocols specifically designed for identifying EVM boards. I am not sure how this is implemented on DRV8343-Q1EVM, but I think it has something to do with DEVICE_ID and EVM_ID below. I am not sure in your schematic if you implemented this, but there are many things programmed in the firmware that is beyond my knowledge as this firmware/GUI was developed by a third party many years ago. Unless if you have exactly the same schematic, it is difficult to get the GUI firmware and GUI working on another hardware besides the EVM, and this is not a recommended approach for development. 

However, if you are able to program and flash to the MSP430 MCU on your board, I would recommend following the sensorless trapezoidal firmware example for MSP430 in TIDA-010031: https://www.ti.com/tool/TIDA-010031

This uses a much easier to follow sensorless trapezoidal algorithm compared to the DRV8343-Q1EVM application firmware, and you can use a tool such as GUI Composer to craft a usable GUI for your application. 

Thanks,

Aaron