• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 3 answers
  • Subscribers 32 subscribers
  • Views 818 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:

PGA460-Q1: Initialization PGA460 for values EEPROM.

PGA460 - UART Diagnostic Data Field.

Jonatan Cegoni
Prodigy 175 points
Part Number: PGA460-Q1
Other Parts Discussed in Thread: PGA460, BOOSTXL-PGA460, MSP-EXP430F5529LP

Hi Akeem,,

I am using OWI communication with the PGA460-Q1 sensor. I'm doing the EEPROM, TVG and Thresholds settings. As soon as I start the BURST / LISTEN commands, I noticed that at some point I am receiving the diagnostic byte with the value 0x60 and the rest of the data 0xff.

Note: Register UART_DIAG = 0.

What could it be?

Thank you.

  • 0
    TI__Expert 7599 points

    Hello Jonatan,

    Akeem is out of office and will respond to your request next week. 

    Meanwhile have you had a chance to look at the PGA460 FAQ ? If not please do so. 

  • 0 in reply to Arjun_Prakash
    Prodigy 175 points

    Ok Arjun,

    Adding more information: I noticed that this situation occurs more frequently when performing the burst / listen for preset2. In this case, a significant variation occurs between the distance values and after a time all bytes are received at 0xff. For preset1, the distance values remain more stable and it is practically does not occur to receive the 0xff bytes for the command 5 (Ultrasonic measurement result).

    Thank you.

    Jonatan Cegoni.

  • 0 in reply to Jonatan Cegoni
    Prodigy 175 points

    Hi Akeem,

    Do you have any feedback on this?

    I also noticed that testing with the demoboard (BOOSTXL-PGA460) for both UART and OWI communication, the bit that refers to "General UART Error" is always active.

  • 0 in reply to Jonatan Cegoni
    TI__Mastermind 27950 points

    Hi Jonatan,

    The fact that the EVM-GUI combination is reporting a general UART error is concerning, as I have not encountered this error on the TI hardware. As described in Table 4 "UART Diagnostic Data Description" of the datasheet, a General communication error can occur when:

    • SYNC filed stop bit too short
    • Command filed incorrect stop bit (dominant when should be recessive)
    • Command filed stop bit too short
    • Data field incorrect stop bit (dominant when should be recessive)
    • Data field stop bit too short
    • Data field PGA460-Q1 transmit value overdriven to dominant value during stop bit transmission
    • Data contention during PGA460-Q1 UART transmit

    A few questions I have:

    1. When the error occurs, does it eventually resolve itself if you send another Preset 2 burst-and-listen command, or does it remain until you power-cycle?
    2. Is there a difference between the configuration of your Preset 1 and Preset 2 settings?
    3. Are you exclusively evaluating the OWI-OWU mode on the GUI-EVM, or have you developed your own hardware and software to test this communication mode?
    4. Can you confirm that the device is bursting just prior to the error when the P2 B+L command is sent by probing the transducer positive terminal? I'd like to confirm that the device is always receiving and properly executing the command even when the diagnostic and UMR reporting error occurs.
    5. In the case when the diagnostic reports 0x60, how many 0xFF values are also returned in the same packet?

  • 0 in reply to Akeem Whitehead
    TI__Mastermind 27950 points

    Hi Jonatan,

    I've made a recent realization that when the IO_IF_SEL bit is '1' for One-Wire UART mode, the General UART Error bit of the Diagnostic Field is high. Do you have the bit IO_IF_SEL=1 in your case? This error reporting may be an unintended bug in the device; I'll need to verify, though it does not seem to impact performance/operation.

  • 0 in reply to Akeem Whitehead
    Prodigy 175 points

    Hi Akeem,

    Yes, the IO_IF_SEL bit is high in my application and also the tests I do with Demo (BOOSTXL-PGA460).

    Thanks.

  • 0 in reply to Jonatan Cegoni
    Prodigy 175 points

    Hi Akeem,

    I noticed that a new version of PGA460-Q1 EVM GUI software (1.0.2.0 Rev.T) is available, but this version has a problem, because testing OWI communication with my application or DemoBoard (BOOSTXL-PGA460) a error occurs witch communication, this does not allow the driver to be configured and it is not possible to run the commands. Installing the previous version PGA460-Q1 EVM GUI (1.0.1.9 Rev.S), everything works normally.

  • 0 in reply to Jonatan Cegoni
    TI__Mastermind 27950 points

    Hi Jonatan,

    I am unable to replicate this error. I am still able to successfully use the OWI-mode of the PGA460-Q1 EVM GUI of version 1.0.2.0. Are you still able to use the standard mode of the latest GUI? You can also force the reprogramming of the MSP-EXP430F5529LP to ensure you have the latest version of the firmware installed, although there was no firmware updated moving from version 1.0.1.9 to 1.0.2.0.

    You can also probe the IO pin to check if the master controller is transmitting data, and check if the PGA460 is responding. If there is communication at a device level, then it is likely GUI related, which I will need to further investigate.