Other NXP ProductsのトピックRe: KITSGTL5000EVBE Dev kit not responding, i2c fail

KITSGTL5000EVBE Dev kit not responding, i2c fail

stevem42 — Thu, 18 Sep 2025 19:39:39 GMT

Just received my KITSGTL5000EVBE Dev kit, went through the getting started documentation.

I get an i2c initialization error. When I try to connect.

I hooked up a Saleae 16 to all 16 pins on J1 and J2. When I check the schematic against the test points on the PCB, they are not matching up. That might be an error.

When I plug in the USB I get something on CTRL_DATA and CTRL_CLK (which the board has listed as TP8 and 9)

The website says this devkit comes with the board, and a cable and getting started guide. But in the documentation https://www.nxp.com/docs/en/user-guide/KTSGTL5000UG.pdf section 4.2 it says it comes with a 5v power supply. That's fine I hooked that up and was monitoring the current. When I first started the board drew 600ma with some initial spikes. After an hour or so trying to get this to respond, it's down to about 32ma.

At the moment U10 is outputting 1.5v, but I had seen it output 1.8v.

Any thoughts? Did I get a bad eval kit? Is there something else I should try?

Re: KITSGTL5000EVBE Dev kit not responding, i2c fail

TomasVaverka — Mon, 22 Sep 2025 06:30:08 GMT

Hi Xinlei (@Xinlei_Tang),

Could you please help with this customer's question regarding the KITSGTL5000EVBE?

Thanks & BRs, Tomas

Re: KITSGTL5000EVBE Dev kit not responding, i2c fail

Xinlei_Tang — Tue, 23 Sep 2025 02:13:34 GMT

I would first make sure double check the FTDI driver is install. paste the init script.txt to C drive. the software is a bit old. just double check if the driver is installed properly.

I setup the board with JP3, JP4, JP5 connected to Vreg for all the power. and JP2 connect to the OSC. (in the attached image there is no I2C clock)

regards

xinlei tang

Re: KITSGTL5000EVBE Dev kit not responding, i2c fail

stevem42 — Wed, 24 Sep 2025 14:05:44 GMT

xinlei tang,

Thank you for your response. Is there instructions for getting that driver to work with "modern" operating systems? When I follow the directions (in the document that seems to be written for a much older version of windows) I get the following message:

I have been so far unable to get Windows 10 or Windows 11 to take the drivers that I downloaded from your site. The only thing that the FTDI chip gets recognized as is a comm port. I'm assuming that's wrong.

I downloaded the Ftdi D2xx and D3xx drivers (which are also installed) to recognize that board but so far no luck.

Also any thoughts about the current and the fact the documentation says it comes with a power supply and mine didn't?

Thanks

Steve

Re: KITSGTL5000EVBE Dev kit not responding, i2c fail

Xinlei_Tang — Thu, 25 Sep 2025 02:33:59 GMT

Hi Steve

600mA is really high, is it still that high? I just measured mine, it is about 27mA. maybe it is a bad board.

for power supply, apparently there isn't one in the kit. I will bring it up to the hardware team to see if it supposed to have one?

for FDTI software, I am able to install it on windows 10. I think you have it installed

Re: KITSGTL5000EVBE Dev kit not responding, i2c fail

stevem42 — Thu, 25 Sep 2025 19:09:17 GMT

600mA is really high. And it surprised me. It was like that for about 30 minutes. And then dropped to 24mA. It's 24mA now. It was odd to me that the board drew so much current when I first plugged it in. It worried me when the StereoCodecControlSoftware.exe software wasn't connecting.

I was following your instructions online

https://www.nxp.com/docs/en/user-guide/KTSGTL5000UG.pdf

Which appeared to require the driver to be a FT2232C Channel A and FT2232C Channel B, which it was not, it was coming up as a com port. So I thought I was doing something wrong.

I downloaded the latest FTDI D2xx drivers, and followed your instructions but when it got to what driver was installed, I let it show up as a com port, and continued and it did work. They show up as 2 com ports, not the channel a and b, but the StereoCodecControlSoftware.exe software is now working and connecting.

Thanks.