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.

PGA300: PGA300 behavior of PWR pin

Part Number: PGA300
Other Parts Discussed in Thread: USB2ANY,

Hello,

I would like you to confirm whether following behavior is expected result or not.

Could you please confirm ?

--

Customer perform following sequence.

1. EVM of PGA300 connect to PC via USB2ANY.

2. Perform "Activate OWI" on GUI. (They do not perform any operation except this on GUI)

3. Check activation pulse on "PWR" pin.

Then, they observed waveform which is NOT described in datasheet before/after Activation-Pulse as shown below.

--

Best Regards,

  • Hi Machida-san,

    This is expected, and is a part of the GUI. It sends some additional OWI commands when the activation pulses are sent to confirm that the OWI communication is successful. This is how it knows to change the status indicator at the top of the GUI window.

    Regards,

  • Hello Scott-san,

    Thank you for your reply.

    Let me confirm about below.

    * You described  "It sends some additional OWI commands when the activation pulses are sent to confirm that the OWI communication is successful." in previous post.

    I understood that this means that we can see OWI communication pulse will be observed after activation pulse was sent.

    However, according to customer's waveform, OWI commuication pulse was observed before activation pulse was sent as well.

    Is that also expected result ?

    i understood that OWI communication pulse which we can confirm after activation pulse may be expected result. However, it seems that OWI communication pulse which we can confirm before activation pulse is NOT expected result..

    Best Regards, 

  • Hi Machida-san,

    I will have to check again, but I believe that the first pulses are to check if the OWI is already active before sending the activation pulse again.

    Regards,

  • Hello Scott-san,

    Thank you for your response.

    Do you have any update ?

    Best Regards,

  • Hello Scott-san,

    Sorry for asking several times. However, I would like to know about your status.

    According to detailed waveform of three, it seems that host controller send OWI write command in all three case.

    Again, what we would like you to confirm is

    1. This is expected waveform or not.

    2. In addtion, this is necessary in customer's system or not.

    Could you please send me your status ?

    Thanks in advance,

  • Hello Machida-san,

    It is normal for the EVM, but it is not necessary for OWI activation. Detailed instructions for activating OWI in normal use are included in the datasheet in the section titled: "Activating OWI Communication".

    Regards,
  • Hello Scott-san,

    Thank you for your reply.

    I understood that these three waveforms are NOT necessary at OWI activation.

    Let me confirm about below.

    * When using PGA300 GUI, could you please confirm why these three waveforms are sent to PGA300 ?

    I understood that these waveforms are NOT required from view point of "Device(PGA300)". however, we would like to confirm purpose of these waveforms.

    Best Regards,

  • Hello Scott-san,

    If you have any update, could you please share it ?

    On the other hand, I am trying to find/check source code of this GUI as another approach.
    I understand that this GUI is composed by python code and try to find source code.

    However, it seems that there is no entity of file.
    Do you know the location of these source file ?

    Best Regards,
  • Hi Machida-san,

    The OWI frame structure is shown here and described in the datasheet in the section number shown:

    The customer can determine what is being communicated by reading the bits being sent in those transactions if they are curious.

    The source code for the GUI is not included with the download since it contains proprietary TI information. We cannot share the GUI source code outside of TI.


    Regards,

  • Hello Scott-san,


    >The customer can determine what is being communicated by reading the bits being sent in those transactions if they are curious.

    We confirmed waveform "before two" and "after one".

    --
    1. waveform of "before two"


    The waveform structure was below.


    START bit -> Sync(8 bit (Value is "10101010xb")) -> STOP bit -> Wait(1bit)

    -> START bit -> Command(8bit (Value is "10000000xb", this means "OWI write")  -> STOP bit -> Wait(1bit)

    -> START bit -> Data 1 (8bit (Value is "00110000b", this means "Address is 0x30")  -> STOP bit -> Wait(1bit)


    -> START bit -> Data 2 (8bit (Value is "00000000b", this means "Written data is 0x00")  -> STOP bit

    2. waveform of "after one"


    The waveform structure was below.


    START bit -> Sync(8 bit (Value is "10101010xb")) -> STOP bit -> Wait(1bit)

    -> START bit -> Command(8bit (Value is "10000000xb", this means "OWI write")  -> STOP bit -> Wait(1bit)

    -> START bit -> Data 1 (8bit (Value is "00010000b", this means "Address is 0x10")  -> STOP bit -> Wait(1bit)


    -> START bit -> Data 2 (8bit (Value is "10101010b", this means "Written data is 0xAA")  -> STOP bit

    --

    All three waveforms mean that OWI write and access to "Reserved " region of OWI memory page(I referred to Table 4 of datasheet).

    So, we can NOT understand what these waveform are setting. could you please explain what these waveforms are setting ?

    Best Regards,

  • Hello Scott-san,

    Could you please send me your feedback ?

    Best Regards,