• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 5 answers
  • Subscribers 64 subscribers
  • Views 851 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

TPS23880: TPS23880 EVM GUI is not controlling anything physical

TPS23880: GUI working with EVM, but not with own board

Hubertus Klein
Prodigy 60 points
Part Number: TPS23880
Other Parts Discussed in Thread: TPS2388

Hi,

when we access the TPS23880EVM with the GUI, then everything works fine.

When we access our own hardware, the GUI reads all registers (tested e.g. by changing the voltage), but it says: "Device not found. Check the device connection or the I2C address configured". So we can't use the Engineering View for debugging our application. In the application by the way we are not able to connect ieee802.3b-devices with Class 6 - on the EMV that's working.

On the TPS23880EVM we have this revision of the IC:

ID(0x1B): 0x55

SRAM-Revision(0x41): 0x01

Device-ID(0x43): 0xC4

On our own hardware we have the following one:

ID(0x1B): 0x53

SRAM-Revision(0x41): 0x40

Device-ID(0x43): 0xC4

Unfortunally we didn't get access to the new firmware yet - we logged some cases, but didn't get any information from mySecureSoftware@ti.com.


What can we do to connect the GUI to our own hardware? Are there version-issues maybe?

Does the IC not come with a valid firmware installed? - Like our ID is lower, but the SRAM-version higher than on the EVM.

What can we do if there is no answer from mySecureSoftware@ti.com (not in the spamfilter, neither), but we need to go into production very soonish and there is actually no time to evaluate another IC.


Many thanks.

  • 0
    TI__Expert 5615 points
    Hubertus,

    Just to be clear, have you requested access to the mysecure folder by clicking on the "Request Now" button located on the top of the Product folder - www.ti.com/.../description ? That will start the approval process so that you can get into the correct mySecure folder.

    I am sorry that response time has been slow from the distribution email you mention above and I will work with them to improve concurrently.

    Thank you for considering PoE products from Texas Instruments,
  • 0
    TI__Genius 15685 points

    Hi Hubertus,

    The TPS23880EVM GUI is embedded with the latest SRAM code. As long as it detects the TPS23880 device, it will load SRAM code automatically. Can you check if the I2C address you entered match the actual hardware I2C address(configured through A1 to A4 pins). 

    Our team is looking into my you didn't mysecure software. But before it is resolved, you can always copy the latest SRAM code and parity check code from MSP430 reference code.  The SRAM code is embedded in sram_code.c. The size of SRAM code is 0x4000h and size of parity check code is 0x800h. You can refer to the reference code and SRAM code load app note on how to load SRAM and parity code. Thanks.

    Best regards,

    Penny

  • 0 in reply to Penny Xu
    TI__Expert 5615 points
    Hubertus,

    Where have you learned of this email distribution list from (mySecureSoftware@ti.com)? I checked just now and that is not a working list.

    The correct way to request access is as I laid out above.

    Please let me know if having any troubles with it.

    Thanks,
  • 0 in reply to Thomas Lewis
    Prodigy 60 points

    Hi,

    we requested access to the software by clicking on the "Request Now" button. When there was no reply we created a case (REQ0023293) and one of your colleagues wrote that we should receive an Email from mySecureSoftware@ti.com.

    We can access the TPS23880-registers in the Register View, so the address is correct. But still the GUI says that the device was not found. How does the GUI detect a valid TPS23880?

    Many thanks.

    Regards,

    Hubertus

  • 0 in reply to Hubertus Klein
    Prodigy 60 points
    Hi,

    we exchanged one TPS23880 from our hardware and the TPS23880 from the EVM. Now the EVM shows the errors from before (SRAM-Version 0x40 etc.) and our own hardware works.

    There is one question left: How can we assure that we always purchase a working version of the IC? Is that assured when we order directly at TI-Store?

    Many thanks.

    Regards,

    Hubertus
  • 0 in reply to Hubertus Klein
    TI__Genius 15685 points
    Hi Hubertus,


    We test every parts on tester to make sure all parts pass ATE test before going out. Thanks.

    Best regards,
    Penny
  • 0 in reply to Hubertus Klein
    TI__Genius 15685 points
    Hi Hubertus,

    I found the reason why the part originally on your board didn't work. Actually the part with the below information is TPS2388 not TPS23880. Can you double check the top marking of the part? Thanks.

    ID(0x1B): 0x53

    SRAM-Revision(0x41): 0x40

    Device-ID(0x43): 0xC4

    Best regards,
    Penny
  • 0 in reply to Penny Xu
    Prodigy 60 points
    Hi Penny,

    you're right! On our boards there is a TPS2388.
    Many thanks for your help.

    Regards,

    Hubertus
  • 0 in reply to Hubertus Klein
    TI__Expert 5615 points
    Good trouble shooting Penny!

    Hubertus, we would appreciate you marking this thread as resolved now so that it will fall off our dashboard.

    Thanks,
  • 0 in reply to Thomas Lewis
    Prodigy 60 points

    Hi Thomas,

    I mark the thread as resolved. Can you on the other hand ask the software department again, if they can give us access to the updated information and firmware of the TPS23880? 

    Many thanks for your help.

    Regards,

    Hubertus

  • 0 in reply to Hubertus Klein
    TI__Expert 5615 points
    Hubertus,

    I have tracked down the root cause of the block in getting you added to the TPS23880 mySecure vault and corrected it.

    Please let me know if you do not receive an email, and ability to access the folder, within 24 hours.

    THANK YOU so much for being patient with us and escalating this via E2E to get resolution.