TUSB216-Q1: TUSB216-Q1 BC1.2 issue

Can you please provide more details regarding the following questions below: 

1. What is the normal business hours for the TI team and what is the time zone they are located in?
2. Who form TI will be supporting this effort. Can you please provide contact information. I am assuming the support will be live via Team meeting or Zoom, please confirm.
3. What equipment is needed to perform the debugging in the lab?
4. In regard to BC1.2 do you have a test plan of what signals needs to be captured and any additional activities you would like to see?  

Hi Fida,

fida almasri said:

What is the normal business hours for the TI team and what is the time zone they are located in?

We're located in Dallas, so Central time zone from 9AM to 5PM CST.

fida almasri said:

Who form TI will be supporting this effort. Can you please provide contact information. I am assuming the support will be live via Team meeting or Zoom, please confirm.

I'll be supporting this, we can discuss through this thread as needed. Teams or Zoom works for meetings as needed.

fida almasri said:

What equipment is needed to perform the debugging in the lab?

For the BC1.2 section, a USB-PET is typically used, per the USB BC 1.2 spec: USB_Battery_Charging_1.2_TestSpec.pdf

Sections 9.5 and 9.6 cover the failing tests indicated in the report.

If eye diagram testing is needed, a host PC with the XHSETT tool and an oscilloscope with a bandwidth of preferably greater than 500MHz that is able to capture the eye diagram or differential signal would be needed.

fida almasri said:

In regard to BC1.2 do you have a test plan of what signals needs to be captured and any additional activities you would like to see?  

Our main concern is just the failed tests that were indicated to us in the powerpoint sent previously, the CT_CDP_CMO_FS and CT_CDP_CMO_HS tests. There were the only tests that we have been told are failing, and have been asked to help debug.

Going by the report we were provided by DesaySV, these tests were the main ones noted as needing to be improved. They also noted that DCP testing did not need to be done. Looking at the report we were given previously, it looks like the errors in testing are less related BC1.2 and more related to data. As such, if possible, using a USB Protocol Analyzer to record USB communication during this testing would be good.

One question I had that I have not seen an answer to is how this testing was performed previously. It looks like someone on either the Paccar or DesaySV side has done this testing, or gone to a lab to have it done before, so I would like to ask what the setup used for that was, as the setup used then should also be applicable here. It would also be good for me to know on my end in case a setup can be replicated in our lab with an EVM. Please help to find out how this report was obtained, and if we can get more info about the setup.

If needed, we can setup a call to discuss.

Thanks,

Ryan

Hi Fida and team,

I should be available from 11/19-11/21 and 11/24-11/25, during business hours CST.

I've taken some time to do a little research, and it turns out that in September, the USB-IF actually changed what compliance testing is required for BC1.2: https://compliance.usb.org/index.asp?UpdateFile=Battery%20Charging&Format=Standard#168

Now, CDP compliance testing only requires this drop/droop test outlined in the mandate linked above, as the USB-PET used for BC1.2 compliance testing originally is now widely discontinued. These Ground Offset tests we have outlined are no longer required for CDP compliance.

It is up to you whether we continue with the testing previously outlined or prioritize these drop/droop tests instead. I believe it would be good to ask GRL if they have this board available, and if they can perform these tests if needed.

Thanks,

Ryan

Interesting update, I will check with the lab tomorrow. Thank you

Hi Ryan 

Update on agenda: BC1.2 testing will begin 11/20

Hi Yvonne,

Got it, sounds good.

Thanks,

Ryan