• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 620 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:

TPS65981: Firmware Questions

TPS65981: Firmware Questions

Robin Widmer
Prodigy 60 points
Part Number: TPS65981

Hi team,

I try to flash the firmware image into the memory chip via SPI. I took the Application customization tool to create my own application firmware. This firmware is running on TPS65981 EVM board but not on my own hardware.

After flashing it seems that every register on the TPS65981 is 0xFF... The Mode register 0x3 is undefined.

If I flash the recovery file to my hardware it is running --> Mode Register 0x3 is APP.

The size of the application Firmware is 136KB and the recovery firmware has 190KB.

Have you any idea what is going wrong?

Thank you

Robin

  • 0
    TI__Mastermind 36756 points

    Hi Robin,

    Since your application firmware is working on your EVM, I don't suspect it is an issue with the firmware. Are you booting your board from VBUS? If so, I suggest checking the pin strapping on BuspowerZ and the RP_D pins.  I would also suggest to make sure you are using the latest version of the configuration tool 3.18 from TI.com

    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,

    Thanks for the fast answer. I am not booting from VBUS, just 3v3 input. I also use the latest configuration tool 3.18. Still the same issue, board boots from recovery file on flash. So if I flash own Firmware File every Register seems to be 0xFF.. Here some Register Values of 0x3 and 0x2d:

    Register 0x3 recovery file flashed:

    Register 0x2D recovery flashed:

    Register 0x3 App Firmware (created on TI Application Customization Tool 3.18 and it works on EVM)

    Register 0x2D App Firmware (created on TI Application Customization Tool 3.18 and it works on EVM)

    Thanks for your help

    Robin

  • 0 in reply to Robin Widmer
    TI__Mastermind 36756 points
    Hi Robin,

    Those results are very strange. can you tell me what some of the registers you are changing are? Are you loading the full-flash image onto your board? Are you updating it over SPI or I2C? Please give me some steps as to how you are updating your board and what registers you are changing.

    Thank you,
    Eric
  • 0 in reply to Eric Beljaars
    Prodigy 60 points

    Hi Eric,

    thanks fo your reply. I made a few tests with different voltages on Vin. Under normal condtions the Vin Voltage is 3.3 Volts. The device is booting the recovery file on 3.3V but not my own firmware file. If I flash the Device (via SPI) while in recovery application and force a warm reboot command, the device is booting my firmwarefile and everything works as expected.

    My firmware is also working if I regulate the Vin Voltage under 3 Volts instead of 3.3Volts.

    I update the firmware via SPI.

    I changed the registers:

    Transmit Source Capabilities (0x32)

    Transmit Sink Capabilities (0x33)

    GPIO Event Map (0x5C)

    Best regards

    Robin

  • 0 in reply to Robin Widmer
    TI__Mastermind 36756 points

    Hi Robin,

    Is your SPI flash powered from the 3.3V LDO on the TPS65981? From your problem description it sounds like it may not be. I would suggest powering the SPI Flash and SPI pull-ups from the LDO_3V3 pin on the TPS65981. This would ensure the SPI flash is active when the TPS65981 tries to read the config back from it.

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

    Thank you,

    Eric