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.

PGA900 programming

Other Parts Discussed in Thread: PGA900, PGA900EVM, USB2ANY, PGA970

How can I programme PGA900 to use in my actual pressure sensor. ? Is evaluation board necessary to programme PGA900?

  • Hi Sebin, to program the PGA900 for your specific application you will need:

    1. Firmware for the M0 in the PGA900 - this is where you implement your compensation algorithm for calibration and where the PGA900 registers are configured as well. There is a reference firmware in the product folder that can be downloaded and it's a very good starting point. This reference firmware is a project in Code Composer Studio (CCS) so you will need to download CCS at ti.com. The document SLDU015 is a quick start guide on how to import this firmware and compile it. After your firmware is ready, you will need to download it to the PGA900.

    2. Hardware - to download the firmware to the PGA900 you will need the PGA900EVM. The firmware can be downloaded 2 ways:

    a. Using the XDS200 (this is NOT part of the PGA900EVM kit). The XDS200 is the debugging probe used for the PGA900 (M0). It allows to add break points and such to debug your code. The PGA900EVM has a connector for the XDS200. You can download directly to the device using CCS.

    b. Using the PGA900GUI (available at the product folder) - this GUI will allow to download the .hex file (compiled firmware from CCS) to the device using the PGA900EVM. The PGA900EVM kit comes with the USB2ANY which is the hardware needed to connect the EVM to the GUI and PC.

    Let me know if you have any more questions. Thanks,

    JV

  • Hi All.

    Can I debugging pga900 project use usb2any from PGA900EVM, or usb2any only for downloading code, and for debugging need buy XDS200?

  • Hi, your statements are correct. The USB2ANY and PGA900GUI are used to download .hex files to the PGA900, either to the Development RAM or the OTP. The Development RAM will allow you to debug main functionalities of the code once the code is running and you can do this multiple times without burning the OTP of the device. However, to perform code debugging (breakpoints for example), you must use the XDS200.

    Let me know if you have any more questions, thanks,

    JV
  • Hi Javier.

    Can I use the jtag XDS510 for debugging PGA900, instead XDS200?

  • Hi, the XDS510 does not support Single Wire Debugging (SWD) which is how we communicate with the M0 in the PGA900. Therefore the XDS510 cannot be used as a debugging probe for the PGA900.

    Thanks,

    JV
  • Hi Javier.

    Is there a possibility in CCS v6.x.x make simulation for PGA900?

    Thanks.

  • Hi, TI no longer supports simulators so they have all been removed.

    Thanks,

    JV

  • I am trying to setup a development environment for the PGA900 under my currently installed CCS v6.1.2.00015. I have read SLDU015 and found it to be quite useless. I've gone to the TI website and downloaded two files from the 'software tools' section (sldc009a and sldc010a). I found these files to be completely useless also since some pinhead decided not to put a file exrension on them. I can't tell if they are zip files, exe files, or whatever. All I really want is a Compiler, a useful library and maybe a sample code base. A pretty simple request, but as usual all I can find is flashy literature. The first 5 steps in the SLDU15A PGA900 Software Quick Start Guide were garbage.

    Step 1 download CCS v6.1.1.00022   I already have v6.1.2.00015 latest from TI, can I not use this one?

    Step 2 while installing CCS, use option Setup Type: Complete Feature Set    There was no option named complete feature set

    Step 3 check whether rstv6M0_T_le_eabi.lib is present   Are you kidding me? Is this for real?

    Step 4  in case above is not present, then copy file to C:....   Where am I supposed to get the file? (local food lion?). I found rtsvtM3_T_le_eabi.lib, will this do?

    Step 5 copy PGA900 folder to any path    Again, where do I get that? Maybe I'll try the local car dealership for that one.

    Some help would be nice.

  • James, apologies for the late reply, I was on business travel. CCS v6.1.2 fixes 7 bugs present in version CCS v6.1.1. That being said, the Software Quick Start Guide (SLDU015A) is based on version 6.1.1 so there might be some minor changes other than the bugs. The goal of the Software Quick Start Guide are 3:

    1. Get customer able to import and build the PGA900 reference firmware (SLDU010) present at ti.com.

    2. Get customer to be able to generate a .hex file using CCS.

    3. Get customer to be able to run code in the PGA900 using either the GUI (.hex file) or the debugging probe XDS200.

    Based on your request of a compiler, library and sample code then everything should be on the web:

    a. Compiler is CCS, which you already have.

    b. Library and sample code are SLDU010.

    If you don't have the XDS200, then you will need to generate a .hex file and download that to the device using the PGA900GUI (SLDU009A) which is also on the web. Both, the SLDU009 and the SLDU010 can be extracted using 7-zip. After unzipping, SLDU010 actually will contain an installer (.exe file) because of click wrap licenses purposes. After running the installer, it will place in the location of your choice, the licenses and a .tar.gz file containing the firmware. These are Unix files. You will need to extract the .tar.gz file twice and you will finally see 2 folders inside, "code" and "docs". The docs folder contain the rtsv6MO_T_le_eabi library that you might need to copy to the location mention in SLDU015A. It also contains the .gel file, among others, needed in case you are using the XDS200. 


    The PGA900 folder that you refer to in step 5...is actually the "code" folder I mentioned previously. Step 5 states "Copy PGA900 folder (having PGA900 code) or ‘code’ folder into any path (for example, D:\temp)".


    Let me know if you have further questions, thanks,


    JV

  • Hi All.

    I am using CCS Version: 6.1.2.00015 

    I am try config XDS200, I do all as in sldu015a, but on step 15, I  have not properties "SWD Mode - User COM port is target UART port". So I am use this: "Enable SWD Mode with SWO Trace enable".

    But after "Saving", I am try "Test Connection" and they tell only [Start: Texas Instruments XDS2xx USB Debug Probe_0] and that all.

    When I  do this "Test Connection" swdclk have not clk signal from XDS200 (I look this via oscilloscope).

    Can XDS200 work with v6.1.2.00015 ? If yes, why it is does not work?

  • Hi JSI,

    The XDS200 should work with that version of CCS. I have seen this difference for the SWD/jTAG settings before and I will discuss with the CCS team to resolve the discrepancy. 

    What I do know is that with the options you are seeing you should set the mode to "Enable SWD mode with SWO Trace Disabled"

    Try that and let me know if that resolves your problems. 

    Thanks,

    Matt

  • Hi Matt.
    I set the mode to "Enable SWD mode with SWO Trace Disabled", but this is similar does not work. Still have not signal on jtag pins

  • JSI,

    I know you said you followed the steps in the quick start guide, but can you verify that the GEL, LIB and HEX files found in the Reference Firmware Docs folder are copied to the proper locations in your CCS directory?
  • Yes, I am copy: PGA900.xml M0_systick.xml, M0_nvic.xml, and pga900_csr.xml, pga900.gel as write on sldu015a. Also copy rtsv6M0_T_le_eabi.lib to the C:\ti\ccsv6\tools\compiler\ti-cgt-arm_5.2.5\lib\
    Hex not copy, there need not hex.
  • Yes, I am copy all as in sldu015a. also copy rtsv6M0_T_le_eabi.lib to the C:\ti\ccsv6\tools\compiler\ti-cgt-arm_5.2.5\lib.
    Hex file not copy, in docs files have not hex.
  • Sorry JSI, I meant the PGA970.XML document. It sounds like everything has been copied to the correct place.

    When you press the "Test Connection" button, what do you see as a result?
  • when I am press "Test Connection" then ccs show window "Test Connection" where write only "[Start: Texas Instruments XDS2xx USB Debug Probe_0]". And that all.
  • JSI,

    There should be more activity in that window than just that, in either a failing or passing situation. Can you not expand the window and see any additional information?
  • Hi Matthew

    I say that there is no more data in window,  also on JTAG signal CLK is not present at this moment. Nothing else happen after press test button.

    But if I press debug button, then clk signal is present on jtag pins, so jtag and windows drivers is worked. But can't connect with pga.

    So now for first need do correct test. But jtag have not reaction when press test button.

  • Can I write the OTP with the XDS200 ? Debugging the application in the devram nicely works with the XDS200 but I cannot find a reference on how to write the OTP without using USB2ANY and the associated TI application.

    rgds

    Hermann

  • Herman, Attached is a document that explains how to do this. Let me know if you have any issues. I will work to have this put together and publicly put on TI.com. 

    Programming OTP using XDS200 USB JTAG emulator.pdf

  • I tried to program PGA900 OTP using PGA900EVM via SPI . OTP verification hasn't successful. Please help me out.

    Thanks in advance