TPS65987D: FW F707.10.06 clarification on "new feature"

Hi Ilya,

The GPxx 4CC commands are still available. However, if a GPIO is already mapped to a specific event, the event cannot be updated during run-time.

Thank you,
Eric

The FW document says that "GPIO Pin Configuration" will not be available, does that also apply only to run time settings for PU/PD, open drain etc? The flashed profile will still have the ability to at least set initial configuration, correct?

Hi Ilya,

That is correct. The GPIO config register is "Read Only" so the initial configuration loaded onto the SPI Flash cannot be changed during run time. However, these settings can be changed when adjusting the initial config in the SPI Flash.

Thanks,
Eric

Hi,

I guess, I'm still not quite clear what exactly is the "feature" that this new firmware brings. It says that "Host can only modify events in Event Configuration Register" - "Host Cannot Modify GPIO Pin configuration which was available in previous releases".
1) Event configuration register is the 0x5C, I don't see any other register in the spec that could fit the description?
2) GPIO Pin configuration is also 0x5C, correct?
3) The new feature blocks parts of the register for writes and unblocks others?

Regards,
Ilya

Hi Ilya,

1. Register 0x5C is in the Host Interface TRM: www.ti.com/.../slvubh2b.pdf
2. Yes, that's correct.
3. The new feature prevents GPIOs from being reconfigured during run-time.

Thank you,
Eric

Hi Eric,

This seems highly unusual for register based devices so

Specific questions:

1) Does the new feature block run-time writes to a PART of register 0x5C and allows writes to another PART of register 0x5C?

if yes,

2) Can you please identify specific BYTE/BITS are allowed to be written runtime and which specific BYTE/BITS are blocked from write?

I would like to get specific addresses, bytes and bits. Generic description such as "Events in Event Configuration Register" and "cannot modify GPIO Pin Configuration" is very nebulous and many assumptions can be incorrect. 

Thanks,

Ilya

Hi Ilya,

I think there is a misunderstanding here. Register 0x5C cannot be written to during run-time. None of the bits in 0x5C can be written to during run-time. This register can only be changed by updating the boot-up configuration.

Thank you,
Eric

Hi Eric,

There's certainly a misunderstanding. So back to original question which I still don't know the answer to.
As quoted from firmware update document for FW F707.10.06 :
"Host can only update the Events in Event Configuration Register" - What exact register address and bytes Host can update?
"Host cannot modify the GPIO Pin configuration which was available in previous releases" - What exact register and bytes host can no longer modify?

Thanks,
Ilya

Register 0x5C is Read Only and cannot be updated by the host during run-time.

This does not answer my questions.

Hello,

As quoted from firmware update document for FW F707.10.06 :
"Host can only update the Events in Event Configuration Register" - What exact register address and bytes Host can update?
"Host cannot modify the GPIO Pin configuration which was available in previous releases" - What exact register and bytes host can no longer modify?

Can I get a detailed answers to the questions above?

Thanks

Ilya,

Let me clarify, and do let me know if you've additional queries on the topic:

• By 'Event Configuration Register', we mean the 'GPIO Configuration' (0x5C) register as defined in Table 3-72 of http://www.ti.com/lit/ug/slvubh2b/slvubh2b.pdf.
• 'Mapped Event' for GPIO0 - GPIO22 correspond to Byte33 - Byte55 of 'GPIO Configuration' (0x5C) register.
• By "Host can only update the Events in Event Configuration Register", we mean that only 'Mapped Event' field of GPIO #X (where X is 0 - 21) configuration in 'GPIO Configuration' (0x5C) register is available for run-time configuration. Meaning (and for example), an event 'PlugEvent_Port1' assigned/mapped to GPIO0 can be changed to 'Cable_Orientation_Event_Port1' at run-time by updating Byte-33 of the 'GPIO Configuration' (0x5C) register. Note that the host shall explicitly reinitialize the GPIO status before mapping a new event to it.
• By "Host cannot modify the GPIO Pin configuration which was available in previous releases", we mean that no other fields of the 'GPIO Configuration' (0x5C) register except for 'Mapped Event' are available for run-time configuration. Meaning (and for example), the 'GPIO Polarity' cannot be modified by editing the GPIO_EVENT_POL field of Bytes 61-64 of the 'GPIO Configuration' (0x5C) register at run time.

-/Praneet

Thank you Praneet, this is exactly the level clarity I was seeking.

My main question has been answered but for sake of completeness:

In your note:
"Note that the host shall explicitly reinitialize the GPIO status before mapping a new event to it."

Not sure what is meant by "reinitialize the GPIO status". Something has to be done to register 0x72 before mapping new event?

Hi Eric;

I believe the open question are, as quoted from firmware update document for FW F707.10.06 :

"Host can only update the Events in Event Configuration Register" - What exact register address and bytes Host can update?
"Host cannot modify the GPIO Pin configuration which was available in previous releases" - What exact register and bytes host can no longer modify? 

Hi David,
Praneet answered the open questions with details that I requested. Just need another small clarification in the note he mentioned in case we have to utilize changing of events runtime.

So just to re-iterate the request for a small clarification from Praneet:

In your note:
"Note that the host shall explicitly reinitialize the GPIO status before mapping a new event to it."

Not sure what is meant by "reinitialize the GPIO status". Something has to be done to register 0x72 before mapping new event?

Thank you.