PGA460: Capture Analog echo data form PGA460

Part Number: PGA460 How many ways to Capture Analog echo data form PGA460? I want to extract eigenvalues of echo data,and process the echo data. 1) Test pin? What is the abbreviation of ASC 2)Echo data dump from UART? 3)Echo data dump from USART? How can I set and operate?

user6060721, There are three methods of extracting the echo envelope data from the PGA460 as you've noted: 1) Analog output: If you want to use your own ADC to capture the amplified analog output, then set the TEST_MUX value to 0x01, and capture from the TEST pin. 2) Echo data dump: The PGA460 stores 128 bytes of the echo envelope time of flight activity. This is a heavily down sampled version of the digital signal processed output to help users to locally set the threshold values. If you don't require a high resolution capture of the post-DSP output, then use this output. You will need to set DATADUMP_EN=1, send a Preset 1 or 2 burst//listen command (CMD 0-3), wait the equivalent record length time, then read back the Echo data dump by sending CMD 7. This can be done through UART, USART (SPI), or OWU. 3) Direct data burst capture (USART/SPI only): This mode can provide the ADC output at an 8-bit 1MHZ rate or 12-bit 500kHz rate. The PGA460 does not locally buffer any of the direct data burst, so you will need an MCU or external memory to store the clocked out data in real time. This mode is recommended for users that intend on applying their own DSP routine. This is similar to the analog output, but will be digitized for you by the PGA460, removing the need for an external ADC. This mode will require you to send a Preset 1 or 2 burst/listen command through SPI, then immediately afterwards continuously send an 8MHz clock signal the SPI-SCLK pin to get envelope data from the SPI-MISO pin.

Thanks. When we use debug tool PGA460-Q1 EVM，the tool used Echo data dump through UART to capture the Echo envelope. Is this right?

What is the signal path of Echo data dump，thanks

user6060721, Yes, the PGA460-Q1 EVM GUI defaults to displaying the Echo Data Dump plot through UART, which is the output stage of the nonlinear scaling block (last stage of DSP) from Figure 35. To change the GUI graph mode to the Direct Data Burst (USART/SPI) output, you can go to Data Monitor --> Graph --> Graph Mode, and select which Direct Data Burst output stage you want to display (ADC output or a DSP stage). Note, the GUI takes a couple of seconds to capture the Direct Data Burst data, so please wait and don't think the GUI has crashed. The longer the record length time, the longer the update time after clicking START.

When I debug my own PGA460 device. After I load memory Map,I can not connect PGA460 through OWU interface. memory map is the attachment. GRID_USER_MEMSPACE-2020-03-13_audiowell_58K_280cm.txt

And when I load memory map successfully，the threshold is wrong. So,I have two confuse： 1.What is the right procedure of connect PGA460 through OWU 2.When debug through OWU，can I load or save memory map，how is the right procedure？ The user guide is very brief about OWU debug， thanks

user6060721, When I checked your register map text file, I found that address 0x1E is set to a value of 0x0F. You need to change this value to 0x8F so that the IO_IF_SEL bit is set to '1' for One-Wire UART mode. Right now it is indicating to use IO-TCI mode, which is why you may be experiencing difficulties loading the file. You can save and load the register map text file by OWU through the Memory Map page just as you would in UART mode. Please see the PGA460-Q1 EVM GUI's OWI Evaluation for an External Module (Video Demonstration): PGA460-EVM-GUI-OWIEvaluation-VideoDemo.zip on the PGA460 E2E FAQ.page for additional details on running the GUI in OWU mode.

Akeem Whitehead: I can read EDD through OWU.My GUI is Rev.1.0.2.0 But when I reload my memory map(the memory map is saved by OWU mode in GUI),but GUI display incorrect. especially the Theshold，can not load from the memory map.When I click T-to-U，there is an error. GRID_USER_MEMSPACE-2020-04-24_194009.txt

user6060721, Note that the "T-to-U" button means "copy threshold register values to USER_DATAx register values". You don't want to use this button if you are attempting to load the threshold values to the Threshold tab of the GUI. When you load the memory map txt file, the Threshold tab values should update automatically, though you may have found a GUI bug. Try these steps: When you first start the OWI mode of the GUI, the first thing you should do is toggle any of the threshold values under the Threshold tab. For example, click up or down on P1 Time 1. Run burst/listen command using the RUN button. The echo data dump and thresholds should now be displayed. The threshold will be random since the threshold values have been properly loaded yet. After the first burst/listen command, then try loading the txt file in the Memory Map page. The correct threshold time and level values should now show under the Threshold tab. Let me know if this works. I will check my GUI code to see where a potential bug may exist.

Akeem Whitehead, 1.When I first start the OWI,I adjust threshlod P1 time1 from 600 to 1400, 2.After run burst and listen,threshold change to 1400 all. 3.After I Load memory map,there is a note,I clicked yes. 4.After restart,the threshold is wrong 5.Attachment is my memory mapGRID_USER_MEMSPACE-2020-04-24_194009_OWU.txt