Other Parts Discussed in Thread: TPS65982
In the System Config register (0x28) there are two checkboxs for USBEPenable and USBRPenable.
Most users it seems from the discussions have these bits both enabled. However, version 2.3 of this tool shows and controls these bits incorrectly.
The EP allows the TPS65982 to respond as an endpoint for Billboard requests, and the RP allows an external device to be attached to provide the billboard information. The EP takes precedence (I think).
If I select only EP in the AppCustomization tool then in the RAW view of Register 28, byte 13 = xxxx-x10x,
with RP selected byte 13 = xxxx-x01x,
both selected byte 13 = xxxx-x11x.
Now if you download the image to the TPS65982 with only one selected and then look in the system config register you will find that the Opposite one is checked.
I can read this register over I2C and see that even though it says RP, it really is the EP bit as the AppCustomization tool says.
If you don't look at or use the Host Interface tool it doesn't matter that the wrong bit is checked. But if you use the tool and check USBEPenable, you will enable RP and vice versa.
I found out the hard way when I was trying to get the billboarding working and only figured this out after making a few images and tracking the HostInterface reporting with what I had setup in the AppCustomization tool. I found out that it was flipped and confirmed it by reading the register over I2C with my own interface.
Bottom line I found that I could leave both bits checked and it looks like the EP overrides the RP selection.
But I don't know if this is completely safe.
Warren