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.

PGA460-Q1: Initialization PGA460 for values EEPROM.

Part Number: PGA460-Q1
Other Parts Discussed in Thread: BOOSTXL-PGA460, PGA460

Hi,

If I use the BOOSTXL-PGA460 demoboard to configure the parameters and write to memory, when the PGA460 is restarted is it necessary to write the registered ones referring to the thresholds settings that the rest would automatically be running?

  • Hi Jonatan,

    Yes, when you program the EEPROM, registers from address 0x00 to 0x2F will be retained and automatically loaded into the working register space after power cycle. The EEPROM includes all registers other than the threshold settings. The threshold registers are stored in volatile SRAM memory, will always reset after power-cycling, and must always be written to at least once after power-up to clear the THR_CRC_ERR to enable bursting.
  • Hi Akeem,

    One more question: I realized that by using the BOOSTXL-PGA460 demoboard, after configuring all the parameters and saving the Memory Map .txt file, by rebooting the demo and loading this Memory Map file, the command is sent to set individually all registers of PGA460. I will use the BOOSTXL-PGA460 demo to configure the devices in production, the data I write to EEPROM memory is the settings from address 0x00 to 0x2A. For all the rest of the parameters (threshold settings, band-pass filter settings, low pass filter settings, etc.) I have to configure via firmware Master sending the command to set the register, correct? How will I use the OWU communication mode, since I will have at least 2 sensors to manage in my application, can I set these parameters that are not in the EEPROM by the OWU interface command?

    Thank you.
  • Hi Jonatan,

    One-Wire UART mode offers the same register access as standard UART. You can use OWU to write to all devices address - both EEPROM and SRAM (i.e. threshold).

    By the way, the DSP's band-pass and low-pass filter coefficients are automatically updated based on the EEPROM values of the band-pass bandwidth and low-pass cutoff. You do not need to manually updated these values unless you are using the high-frequency range (180-480kHz) or are intentionally forcing an off-center frequency.
  • OK,

    So for my application using the BOOSTXL-PGA460 demoboard on the production line to configure and record the EEPROM with the parameters and address of each UART device connected to the OWU bus, it is enough the master, when initializing, to send a broadcast command for setting the values threshold for all devices on the bus and then the burst/listen commands for each address, receiving distance values and handling them?
  • Jonatan,
    Yes, when initially powering up, you can send a broadcast write bulk threshold command to globally update all threshold values to the same time and level preset mappings, and then issue individual UART_ADDR based burst/listen and ultrasonic measurement result commands to update and collect data per module in a running system?
  • Akeem,
    OK. Thank you for information.
    I will develop the master firmware and any doubt, we talked.
  • Akeem,
    I am using an external module with OWU communication connected to BOOSTXL-PGA460 demo (J6 connector). I'm finding it strange the distance value being informed, as you can see in the picture the excitation signal of the sensor and the echo received along with the Threshold levels should have a distance of approximately 30cm. In the field UMR is reported 11,239 meters.

  • Hi Jonathan,

    The PGA460 device installed on the BOOSTXL-PGA460's IO pin is completely decouple via software or hardware?
    If the echo data dump and threshold values read out to correctly reflect what you are displaying, there is no reason the UMR should not update.

    Be sure that you have checked the "UMR" checkbox in the Plot/Export tab. Also try unchecking the "EDD" checkbox to exclusively update the UMR table. Regardless of the interface mode, the UMR does not update when DATADUMP_EN=1. The GUI should automatically update the DATADUMP_EN bit between each EDD and UMR iteration, but you may have discovered an error case.
  • Hi Akeem,

    Yes it is decoupled via hardware (desoldering R15). I noticed that this problem happens both using the OWU interface and the UART. Here are 2 more examples of the situation where this occurred:

  • Hi Jonatan,

    A few more items to check/debug:

    1) Do you see the false positive when running a listen only command?
    2) Is the device set to Time Decouple mode at 65ms (max) to prevent the DECPL from activating internally?
    3) If you change the digital gain's LR starting threshold time to a different value, does the false positive peak also move?
    4) I see you are currently using Preset 2, which is set to digital gain SR=x1 and LR=x4. If you set both to x1 or both to x4, do you still see the false positive?