PGA460-Q1: Faill to store the setting into EEPROM

Hi Leo,

Note, the IO pin offers two different One Wire Interface (OWI) modes: Time Command Interface (TCI) and One-Wire UART (OWU). These are two very different OWI modes, which is why it's important to know which you are using in the GUI to ensure you are using the correct OWI mode in Energia (TCI or OWU). By default, the GUI may switch between these two modes (unless specified to operate in one exclusive mode), while the Energia sketch can only currently be used in one OWI mode.

The general procedure of updating, programming, and burning the EEPROM memory is:

1. Send bulk register write command (command 12) or several singe register write commands (command 10) to update the device settings. See Energia functions pga460::defaultPGA460 (bulk write) pga460::registerWrite (single write) in PGA460_USSC.cpp file for an example implementation.
2. Execute EEPROM burn routine as described in section "7.6.1 EEPROM Programming" of the datasheet. See Energia function pga460::burnEEPROM in PGA460_USSC.cpp file for an example implementation.

Hi Leo,

I double checked the PGA460 Energia library to make sure the TCI mode is working properly. I was able to successfully perform everything except the EEPROM program routine when using TCI. During debug, I found an mistake in the PGA460_USSC.cpp file in the burnEEPROM function that is preventing the TCI mode EEPROM burn routine from running. There is only one line of code you'll need to manually update as highlighted below in the PGA460_USSC.cpp file:

I will update this in the next Energia revision release since this mistake is preventing both TCI and SPI from entering their EEPROM burn routines.

Regarding your other TCI issues, try to following debug techniques:

1. The master controller is not generating the TCI commands from Energia.
   1. Use an oscilloscope to probe the BOOSTXL-PGA460's TCITX and TCIRX pins, and the PGA460PSM-EVMs IO pin. By monitoring these pins, and simply checking for toggle activity, we will confirm whether the master controller is actually generating the TCI commands from Energia in the first place.
2. The PGA460 is not responding to the TCI commands.
   1. Use an oscilloscope to probe the BOOSTXL-PGA460's TCITX and TCIRX pins, and the PGA460PSM-EVMs IO pin. On the IO pin during a response command, the master controller command will always pull the IO down to 0V for logic low, while the PGA460 will pull down the IO to a value slightly above 0V (in the mV range). You should be able to clearly see a difference between the master logic low and the PGA460 logic low on the IO pin due to the voltage difference of the logic low toggle.
   2. Alternatively, on the TCITX and TCIRX pins, the TCIRX pin should contain more toggle information in the event of a response command. If the PGA460 is not responding, then the TCITX and TCIRX pins will show identical information and toggle duration.
3. The PGA460's IO interface is disabled or in OWU mode in its register configuration.
   1. If the master controller is confirmed to be generating and sending the TCI commands from the master controller, but the PGA460 is not responding, there is likely an issue in the PGA460 setting specifically. Ensure the PGA460's IO_IF_SEL is set to '0' for TCI mode, and the the IO_DIS to '0' to enable the IO pin for TCI operation.
4. The master controller is not collecting the TCI data from the PGA460.
   1. If the hardware shows all communication to be good, such that the master is generating the commands, and the slave is generating a response, and the response is making its way back to the TCIRX pin at the BOOSTXL-PGA460 pin, then there is likely an issue with the MSP430. This would be unexpected considering the TCI mode works in the GUI. If this is the case, we will need to consider more advance debug.
5. The Energia sketch is not properly converting and reporting the master controller's captured TCI data.
   1. If the raw data is being captured successfully at the master controller, but is not being displayed properly, it is likely the MSP430 settings have been changed from their expected values. Energia should force the MSP430F5529 clock to 16MHz or 25MHz by default. If the MSP430 clock is something other than these values, this could lead to TCI timing conversion issues. Unless you've manually created an alternative clock case, this should not be an issue.

I suspect the issue is likely related to your device settings or your hardware. Let's see what your debug reveals.

Note, if you have configured and burned all of your EEPROM device settings using the GUI, you can enter 'x' (shows as '72' in terminal) on the Energia serial terminal when prompted for any device setting to skip this configuration since you have already confgured the user registers in advance. You'll only need to update the thresholds every time since the threshold values are in volatile SRAM memory. Here is an example working TCI configuration using pre-programmed EEPROM values:

This example uses a 40kHz transducer.