• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 853 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TPS65982: TPS65982-EVM and Aardvark

Zach Moore38
Prodigy 60 points
Part Number: TPS65982
Other Parts Discussed in Thread: TPS65987D

Hello,

I have the TPS65982-EVM and the Aardvark i2c/spi host adapter. I am trying to understand the Application Customization Tool and am running into some problems.  It looks like I get a successful hardware connection to i2c address 0x38 (SDA1/SCL1). I have followed the slva786a and slvuar8a PDF's and am still confused as to how this is working. I have my aardvark hooked up to the TPS65982-EVM the same way it is shown in the slva786a PDF.  When I create a new project, and try to import the settings from the TPS65982-EVM, it says that it will go to the device 1, port 0 tab which is not viewable unless I'm in debug mode.. If i import the settings to the "Shared Device Settings", i see that registers in the "Common Settings" tab under "Raw View" are updated.  There is no "Global Device Settings Tab" in my software that I can see. Also, if I set the I2C Address to 0x38 and perform a test read, it returns APP.

Is there an updated applications note for the newest Application Customization Tool?

  • 0
    TI__Mastermind 36751 points

    Hi Zach,

    Here is a link to the latest application customization tool user's guide:

    I hope this helps.

    If this answers your question, PLEASE select This resolved my issue

    Thank you,

    Eric

  • 0 in reply to Eric Beljaars
    Prodigy 60 points
    Hi Eric,
    Thank you for the updated pdf. It seems that I am successful when I program the flash via SPI, but if I use the Host Interface Tools to try and program the low region, it verifies successfully but it doesnt seem that my registers reflect what should've been written. For instance i wrote 0xDEADBEEF to the customer use register, and after I write the low region this register does not show 0xDEADBEEF. If i flash the binary via SPI, the register does update to 0xDEADBEEF though, and any other configurations I had set are updated on the new device. My goal for this is to program an on board device via I2C and not SPI.

    Another note is that when i flash the binary via SPI it seems that when i do a test read it returns 'APP' but when i flash via i2c the test returns 'BOOT'. Sorry I am new to flashing roms.

    A final question is that we have boards with the TI83B, and we have a few flash devices that are configured for a TI82, is there an easy way to update these flash devices to work for the TI83B? I have the TPS65983 Application Customization tool.
  • 0 in reply to Zach Moore38
    TI__Mastermind 36751 points

    Hi Zach,

    It seems like you might be seeing an issue with the I2C communication on your setup. In both instances, the Mode register should be reading back APP. If you read back BOOT, the device has failed to load the configuration.

    The 83B should only be used for TBT devices that are following an Intel reference design. If that is not the case, I do not suggest using the 83B and instead looking at the TPS65987D if PD3.0 is required. The same I2C patch mechanism should work for the 87D and 82.

    If this answers your question, PLEASE select This resolved my issue

    Thank you,
    Eric

  • 0 in reply to Eric Beljaars
    Prodigy 60 points
    Hi Eric,
    Thank you for the answers.

    Our design will have the Titan Ridge on the board, but in the interim we would like to update the TI82 to the TI83B (these have been put onto boards already). Is there a way to update these easily? They currently only work with the TI82 since the flash has not been updated so the TI83B can boot properly.
  • 0 in reply to Zach Moore38
    TI__Mastermind 36751 points
    Hi Zach,

    I'm not 100% sure I understand your question. However, it is not recommended to run 82 firmware on an 83B device. If you have the latest TPS65983 Application Customization Tool, you will see which intel designs are supported by the 83B. It is not recommended to use the 83B for any application outside of those intel reference designs.

    Thank you,
    Eric