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.

PGA970: PGA970 Firmware Example Code

Part Number: PGA970
Other Parts Discussed in Thread: USB2ANY, UNIFLASH

Hello,

I have a PGA970EVM development kit that I am interfacing with SPI. I noticed that in the SW user manual they mention example FW code but I haven't been able to find it. Could you please link the example code here if possible?

Thanks

  • Hi Eric,

    You should be able to locate the PGA970 software from this location:

    http://www.ti.com/lit/zip/sldc015

  • Hello Tom,

    Thank you very much for your response.

    I was looking for the the API files rather than the PGA970GUI program. I am referring to the API mentioned in this document.

     

    Thank you very much for your help.

    Sincerely,

    Eric

  • Hi Eric,

    Our PGA specialist will be back in the office tomorrow, I'll have him look into this for you.

  • Hi Tom,

    Thank you very much, I am looking forward to hearing back from your PGA specialist.

  • Hello Eric,

    The PGA970 example firmware is included in the mysecure software folder (along with the GUI and the datasheet) that you can request access for at the link that Tom shared. These functions are part of that example firmware. If you already have access to the mysecure software folder, please download the example firmware from that location.

    Regards,

  • Hey Scott,

    Thanks for your reply.

    Here are the contents of the zip file that Tom linked me. There is no firmware as far as I can tell can you let me know if there is a different link that contains the firmware?

  • Hi Eric,

    My apologies, please request access for the PGA970 mysecure folder here: https://www.ti.com/licreg/docs/swlicexportcontrol.tsp?form_id=301547&prod_no=PGA970-DESIGN&ref_url=asc_dc_padc

    Regards,

  • Hey Scott,

    Thanks for the link. I have sent out a request and will follow-up if this has solved my issue.

  • Hello Scott,

    Thank you very much for your help. I just wanted to get your thoughts on one last point. 

    The three items there are:

    • The full datasheet.
    • The .exe program to install the PGA970EVM GUI
    • The .exe program which seems to install the FW in C:\Program Files (x86)\Texas Instruments\PGA970GenericFirmware in a .zip file.

    May I suggest perhaps replacing that PGA970-Generic-Firmware-Installer.exe with just a zip of the folder contents shown below?

    After getting suspicious since a zip file with the FW was what I was expecting and I figured you were sending me the FW in some manner, I took a look at what the .exe did for the FW installer and realized the FW was in there and being copied to that directory which is a bit confusing but I could be mistaken. I just wanted to let you know that was the case.

    Some follow up question:

    1. Can you confirm that the .hex file inside the zip is the .hex file the PGA970EVMs come with loaded on the IC?
    2. From reading previous threads, I see that the PGA970 IC does not come with .hex file loaded. Is it safe to load this .hex file onto the PGA970 ICs on my custom boards and configure the PGA970 ICs over SPI similar to how the USB2ANY would configure the PGA970 registers over the GUI?
    3. What would be your recommended method for flashing the FW to the PGA970 ICs? Would you suggest using the USB2ANY/XDS200 with Code Composer for example?

    Thank you very much for your help.

    Sincerely,

    Eric

  • Hi Eric,

    The example firmware is packaged as an installer for the purposes of going through the clickwrap license before installing it.

    1. I'm not sure what firmware is included in the hex file to be honest. The PGA970 does not come with any firmware installed from the factory. The hex file is likely based on the example firmware, but since the example is mainly only shell functions, there is not much functionality already included.

    2. You can load the hex file, but as I mentioned above, there will most likely be no useful functionality as a part of it. Updating the firmware for the required application is up to the user.

    3. For flashing firmware in a production environment, using the XDS200 with CCS or Uniflash is the preferred method. If you are only evaluating for the moment, you can load a hex file using the USB2ANY through SPI/I2C/OWI. If you need debugging capability, you will have to use the XDS200 with CCS.

    Regards,