BQ76PL455EVM: Serial Communication, GUI - Unable to open COM port!

Hi Stepan,

Have you looked through the EVM and GUI user guide (found here:http://www.ti.com/lit/ug/sluuba7a/sluuba7a.pdf)?

Just to confirm, you have the EVM attached to either  cells or a cell simulator, so that the 455 can draw power? I would also ask to confirm that both actuators of the communication mode switch are set to "single"?

Hi,

I have faced the similar issue. The EVM is powered with cells and the led on board is lighted up.

I'm sniffing the communication with sw and computer tries to send messages to the port but nothing happens. The gui SW says that unable to open com port. I have installed the serial to usb drivers. I have also tried with 2 different windows 10 computers (one with fresh installation) and windows 7 but no luck.

How I can proceed with this to figure out if this is a SW or HW issue?

BR, Matias

Hi, 

unfortunatelly I wasn't able to make it work. I have tried the same as you and also to communicate with the board with the simple commands but nothing worked, the board did not even woke up. 

Sorry I couldnt help. If you succeed, let me know :)

SR

All,

if you are using less than 16 cells, have you shorted all unused cell inputs to the highest used cell?

Can you confirm that the switch actuators (both of them) for SW2 are set to single?

For the part that wakes up, have you measured the voltages on VIO, VP, VDIG, and VM?

For the part that doesn't wake up, have you measured V5VAO?

Was the USB-FTDI cable inserted with the exposed metal pads facing "up"?

Hi,

> if you are using less than 16 cells, have you shorted all unused cell inputs to the highest used cell?

14-16 are sort circuited to highest, so yes.

> Can you confirm that the switch actuators (both of them) for SW2 are set to single?

Both are set to single. Confirmed.

> For the part that wakes up, have you measured the voltages on VIO, VP, VDI>G, and VM?

All voltages were about 5V and VM was close to -5V

> For the part that doesn't wake up, have you measured V5VAO?

If usb cable wasn't connected V5VAO was still ~5V

> Was the USB-FTDI cable inserted with the exposed metal pads facing "up"?

Yes it was and D22 is lighted on after the cable connection.

Could you please provide me an example command that I could send over serial e.g. with TeraTerm to the board that will cause the device response something? In this way I could rule out if this is an issue with the GUI SW.

BR, Matias

Hi,

Some additional details:

After all it seems that I never get to the state where GUI tries to send anything to the port. It seems that the GUI just won't get the port open. Here is the log that I collected with com port monitor after port was selected from the GUI pop up until it says that unable to open the com port:

0 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_PROPERTIES) DOWN COM5
1 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_PROPERTIES) UP STATUS_SUCCESS 40 00 02 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10 01 00 00 00 ff 00 00 00 7f 00 00 00 70 6b 06 10 0c 00 05 1f 00 00 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 @...........................ÿ......pk.......................... 64 COM5
2 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_MODEMSTATUS) DOWN COM5
3 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_MODEMSTATUS) UP STATUS_SUCCESS 10 00 00 00 .... 4 COM5
4 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_BAUD_RATE) DOWN COM5
5 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_BAUD_RATE) UP STATUS_SUCCESS 90 d0 03 00 Ð.. 4 COM5
6 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_LINE_CONTROL) DOWN COM5
7 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_LINE_CONTROL) UP STATUS_SUCCESS 00 00 08 ... 3 COM5
8 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_CHARS) DOWN COM5
9 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_CHARS) UP STATUS_SUCCESS 1a 00 00 1a 11 13 ...... 6 COM5
10 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_HANDFLOW) DOWN COM5
11 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_HANDFLOW) UP STATUS_SUCCESS 00 00 00 00 00 00 00 00 00 08 00 00 00 02 00 00 ................ 16 COM5
12 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_BAUD_RATE) DOWN COM5
13 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_BAUD_RATE) UP STATUS_SUCCESS 90 d0 03 00 Ð.. 4 COM5
14 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_LINE_CONTROL) DOWN COM5
15 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_LINE_CONTROL) UP STATUS_SUCCESS 00 00 08 ... 3 COM5
16 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_CHARS) DOWN COM5
17 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_CHARS) UP STATUS_SUCCESS 1a 00 00 1a 11 13 ...... 6 COM5
18 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_HANDFLOW) DOWN COM5
19 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_HANDFLOW) UP STATUS_SUCCESS 00 00 00 00 00 00 00 00 00 08 00 00 00 02 00 00 ................ 16 COM5
20 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_BAUD_RATE) DOWN 90 d0 03 00 Ð.. 4 COM5
21 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_BAUD_RATE) UP STATUS_SUCCESS COM5
22 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_CLR_RTS) DOWN COM5
23 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_CLR_RTS) UP STATUS_SUCCESS COM5
24 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_CLR_DTR) DOWN COM5
25 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_CLR_DTR) UP STATUS_SUCCESS COM5
26 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_LINE_CONTROL) DOWN 00 00 08 ... 3 COM5
27 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_LINE_CONTROL) UP STATUS_SUCCESS COM5
28 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_CHARS) DOWN 1a 00 00 1a 11 13 ...... 6 COM5
29 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_CHARS) UP STATUS_SUCCESS COM5
30 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_HANDFLOW) DOWN 00 00 00 00 00 00 00 00 00 04 00 00 00 04 00 00 ................ 16 COM5
31 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_HANDFLOW) UP STATUS_SUCCESS COM5
32 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_BAUD_RATE) DOWN COM5
33 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_BAUD_RATE) UP STATUS_SUCCESS 90 d0 03 00 Ð.. 4 COM5
34 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_LINE_CONTROL) DOWN COM5
35 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_LINE_CONTROL) UP STATUS_SUCCESS 00 00 08 ... 3 COM5
36 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_CHARS) DOWN COM5
37 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_CHARS) UP STATUS_SUCCESS 1a 00 00 1a 11 13 ...... 6 COM5
38 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_HANDFLOW) DOWN COM5
39 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_GET_HANDFLOW) UP STATUS_SUCCESS 00 00 00 00 00 00 00 00 00 04 00 00 00 04 00 00 ................ 16 COM5
40 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_BAUD_RATE) DOWN 90 d0 03 00 Ð.. 4 COM5
41 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_BAUD_RATE) UP STATUS_SUCCESS COM5
42 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_CLR_RTS) DOWN COM5
43 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_CLR_RTS) UP STATUS_SUCCESS COM5
44 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_CLR_DTR) DOWN COM5
45 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_CLR_DTR) UP STATUS_SUCCESS COM5
46 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_LINE_CONTROL) DOWN 00 00 08 ... 3 COM5
47 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_LINE_CONTROL) UP STATUS_SUCCESS COM5
48 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_CHARS) DOWN 1a 00 00 1a 11 13 ...... 6 COM5
49 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_CHARS) UP STATUS_SUCCESS COM5
50 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_HANDFLOW) DOWN 00 00 00 00 00 00 00 00 00 04 00 00 00 04 00 00 ................ 16 COM5
51 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_HANDFLOW) UP STATUS_SUCCESS COM5
52 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_CLR_DTR) DOWN COM5
53 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_CLR_DTR) UP STATUS_SUCCESS COM5
54 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_TIMEOUTS) DOWN ff ff ff ff ff ff ff ff fe ff ff ff 00 00 00 00 00 00 00 00 ÿÿÿÿÿÿÿÿþÿÿÿ........ 20 COM5
55 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_TIMEOUTS) UP STATUS_SUCCESS COM5
56 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_WAIT_MASK) DOWN fb 01 00 00 û... 4 COM5
57 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_WAIT_MASK) UP STATUS_SUCCESS COM5
58 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_QUEUE_SIZE) DOWN 00 10 00 00 00 08 00 00 ........ 8 COM5
59 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_QUEUE_SIZE) UP STATUS_SUCCESS COM5
60 22/06/2017 08:26:06 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_WAIT_ON_MASK) DOWN COM5
61 22/06/2017 08:26:11 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_WAIT_MASK) DOWN 00 00 00 00 .... 4 COM5
62 22/06/2017 08:26:11 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_WAIT_ON_MASK) UP STATUS_SUCCESS 00 00 00 00 .... 4 COM5
63 22/06/2017 08:26:11 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_SET_WAIT_MASK) UP STATUS_SUCCESS COM5
64 22/06/2017 08:26:11 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_CLR_DTR) DOWN COM5
65 22/06/2017 08:26:11 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_CLR_DTR) UP STATUS_SUCCESS COM5
66 22/06/2017 08:26:11 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_PURGE) DOWN 0a 00 00 00 .... 4 COM5
67 22/06/2017 08:26:11 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_PURGE) UP STATUS_SUCCESS COM5
68 22/06/2017 08:26:11 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_PURGE) DOWN 05 00 00 00 .... 4 COM5
69 22/06/2017 08:26:11 IRP_MJ_DEVICE_CONTROL (IOCTL_SERIAL_PURGE) UP STATUS_SUCCESS COM5

Like I said, I have downloaded and installed the latest driver from the FTDI site. The file was CDM v2.12.26 WHQL Certified, is that correct?

BR, Matias

Hi Matias,

Alright, this  one  will  be tricky. This appears to be a software/pc problem, and not an  actual pl455 problem.  Unfortunately, the person who originally developed this GUI is  no longer with the team, so please  bear with me  as we try to figure this out.

To be sure, you downloaded it from this site: http://www.ftdichip.com/Drivers/VCP.htm ? This is a low hanging fruit, but can you verify that you downloaded the correct 32 bit or 64 bit version? That is the correct version, i believe. 

Another low hanging fruit, but did you try using different cables? To my knowledge, we have never had a problem with these cables being kitted in with our EVM, but crazier things have happened.

Can you confirm that nothing  else is using the COM port?

EDIT: The software  design reference also has many examples of what you can send over serial, and the responses you should receive back. http://www.ti.com/lit/an/slva617a/slva617a.pdf

Hi,

>To be sure, you downloaded it from this site: http://www.ftdichip.com/Drivers/VCP.htm ? This is a low hanging fruit, but can you verify that you downloaded the  correct 32 bit or 64 bit version? That is the correct version, i believe. 

I did try to replace all the drivers with x64 versions directly to window's system32 etc folders to make sure that correct version is used, but it didn't help.

>Another low hanging fruit, but did you try using different cables? To my knowledge, we have never had a problem with these cables being kitted in with our EVM, but crazier things have happened.

I have 2 cables and both give the same error.

>Can you confirm that nothing  else is using the COM port?

Other apps can open the port, so there can't be anything using the port.

>EDIT: The software  design reference also has many examples of what you can send over serial, and the responses you should receive back. http://www.ti.com/lit/an/slva617a/slva617a.pdf

I have tried to send those commands over putty / teraterm without response

Could you please try to test this with teraterm and copypaste the command and reponse if you are able to communicate so that I can do the same?

I received 2nd board this week and it behaves just in the same way, no able to open com port. I have tried with windows 10, clean windows 10 installation and clean windows 7 pro with the required .net framework installed from windows update and with offline installation package.

The led on the board lights up if I have the pack connected and I plug the USB to any of tested computers.

What is the FTDI driver's version / date that you are using? I have tried drivers from sep 2016 (windows10) and feb 2017 (windows7), most like some other versions as well, but those are currently installed.

So far I haven't try with 32bit version of windows, but I hope that you can get the board working with both versions.

-Matias

Dear David W,

Just willing to let you know that I was able to communicate with the board by using real term. I was able to request voltage readings from the board and after converting hex values to voltages with the formula found in your docs I also confirmed that readings were correct.

Still no luck with the GUI, nothing helps. I have been trying with multiple setups. Could you share an older version of the GUI? As far as I know the GUI is not even trying to send anything to the com port.

I truly hope that you can help me with this situation while it is blocking all the development on top of your product!

BR, Matias

Hi Matias,

Glad you got it to talk, at least... now we know the EVM is good.

I will be honest with you, this one will be a challenge for me... anyone that was involved with this GUI development has long since left the company and moved on to other roles.

Just to confirm, you have a 64 bit processor and a 64 bit OS? Or are you using a 32 bit windows OS? If either one is 32 bit, you will have to move to the 32 bit driver.

Have you tried to reinstall the GUI software? I am using the latest FTDI driver for the 64 bit windows OS.

Hi,

>Just to confirm, you have a 64 bit processor and a 64 bit OS? Or are you using a 32 bit windows OS? If either one is 32 bit, you will have to move to the 32 bit driver.

I have tried both 64 and 32 bit Windows 7 OS versions with HP Z800 and HP Z220 and 64 bit Windows 10 with fujitsu E746

>Have you tried to reinstall the GUI software? I am using the latest FTDI driver for the 64 bit windows OS.

I have reinstalled above HP setups (windows + .NET framework + FTDI + GUI) several times with no difference.

-Matias

Hi from Russia!

We have the same problem, described above.

Please share GUI-Software version 1.0.0.15 (9-15-2014) if there is no other solution.

All,

Sharing an older version of the GUI is not something i can do, unfortunately.

Would either of you be able to put a logic analyzer  on TX/RX and see what is coming  out of the PC, i f anything?

Have you re-installed the  GUI?  

If anything, i would suggest developing  with a MCU