Forums

Powder,

Can you capture SDA and SCL during the boot with a scope and provide the capture?

You've strapped the EEPROM to address 0xA0, correct?

Frank

Frank Minich Hello!
Prototype chip on tusb3200 customers in our board, can use the oscilloscope to capture the SDA and SCL, but we can not capture the tusb3200 chip SDA and SCL,
Sincerely Thank you!

Frank Minich Hello!
Captured with an oscilloscope to SDA, only to drop down our tusb3200 chip 0.5Vp-p, the reduction was not low enough. That tusb3200 do not have access 24c64, is not it?
Thank you!

Frank Minich Hello!

Are certainly able to determine already built tusb3200 eeprom boot process? If so, it certainly is a hardware problem.

 Thank you!

Powder,

I'm not understanding everything that you say, so please bear with my questions.

If the TUSB3200 can't pull SDA and SCL down, your EEPROM won't note the address byte, and so won't 'ACK' the address;  then the TUSB3200 thinks there's no EEPROM.  Is that what you see?

I'm kind of confused by your use of 'customer'.  Do you have two different boards, one of which works OK and one doesn't?

Can you share your board's schematic (or, at least the I2C and EEPROM section)?

Frank

Frank Minich Hello!
Are certainly able to determine tusb3200 have built the same eeprom boot process? If so, it certainly is a hardware problem.

Thank you!

Powder,

I just burned a 24LC64 with Rev929.bin as provided in the FDK (7070 bytes) and installed in a TUSB3200EVM.  The image comes up fine.

This image assumes an AC97 codec.

Regards,

Frank

Frank Minich Hello! Down by only 0.5v SDA has been resolved. But still access the 24c64 is very short, unsuccessful. Only replaced Prototype with customers on tusb3200ac exchange test access 24c64 success, about 5 seconds, with Rev929.bin FDK program, this program can also be used to modify the descriptors, burn to 24c64, and run successfully. But for the other five tusb3200ac can not be completed access 24c64. It seems that five tusb3200ac internal bootstrap not right? Do tusb3200ac no consistent internal bootloader? How to obtain the correct tusb3200ac internal bootloader? And how to load tusb3200ac internal? Thank you!

Frank Minich
Hello!
tusb3200ac only sent to the 24c64 0XA0 a byte, 24C64 back the "ACK" after, tusb3200ac over, then repeat about 100ms to send 0XA0 a byte, 24C64 back the "ACK" after, tusb3200ac over. No further then send the address, and read 24C64?

Prototype with customers now on tusb3200ac, everything is normal, and completed the sound development of the corresponding compiled, the audio output is normal, basically is about to complete project development work. However, not all the other successful visit tusb3200ac chip 24c64. Please advise.

Thank you!

Powder,

I apologize if I don't understand all that you wrote.  Perhaps you could send me a problem description in your native language and I could locate someone here who is fluent in that language.  My email is fminich@ti.com.

I am currently out of the office, to return on Monday 12 December.

No other TUSB3200A user has reported any problem like this with the TUSB3200A, so it has to be something either with your board or with the particular TUSB3200A device that you are using.

I will capture the I2C traffic on a working TUSB3200A EVM early next week.

In the mean time, could you capture SDA and SCL during the boot sequence and post?

Regards,

Frank

Powder,

Here's the initial capture of SDA (above) and SCL (below) at the start of boot:

This was captured on a TUSB3200AEVM1.  Here's the remainder of the address byte, showing the ACK from the EEPROM):

 Here's the address and the second byte:

And here's the initial sequence:

Regards,

Frank

Frank Minich
Hello!
     Oscilloscope to observe the normal I2c, and now from the client side to get two tusb3200ac chips, put on our development board everything is working! Explain our side of the tusb3200ac chip supply, depressed and even Arrow Electronics (Shenzhen) Co., Ltd. This agency did not tusb3200ac chip supply? Let's toss the pain for so long, please supply the relevant departments to reflect the ti's such a situation. Mr. Frank Minich or you have given us support and confidence, or we can design and other companies, have long given up ti's tusb3200 chip. Here once again express our deep thanks to you!