• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 32 subscribers
  • Views 440 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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 PGA900

Udo Merz
Prodigy 10 points
Part Number: PGA900
Other Parts Discussed in Thread: UNIFLASH

Dear SR

Datasheet contains explanation of the individual API functions. But not the specification, such as timing. According to the documents, the development system is always necessary. we wont to programm the PGA900 without EVM/development system. Could you please send me programming specification or Library (API Function) to progam device?

  • 0
    TI__Mastermind 31655 points

    Hello Udo,

    The EVM is not necessary to complete PGA900 programming. There are several options to program the OTP through any of the available digital interfaces (SPI, I2C, or UART).

    If you are using SPI or I2C there are no special APIs needed, and there are not any public examples available. The full procedure for programming through either interface is included in the datasheet under the "OTP Programming using SPI" or the "OTP Programming using I2C" sections in the datasheet. The only timing restrictions are the timing specifications of the I2C and SPI interfaces themselves.

    The most efficient method for production is to use UART with a tool like Uniflash which includes PGA900 support. To complete programming through this method you will need a USB JTAG emulator (XDS200). An additional thing to note when using this method is that the PGA900.gel file included with Uniflash is set to remap the memory space to the DEVRAM instead of the OTP. You can easily modify the file to load the program to the correct memory space by modifying the config remap function:

    Config_Remap()
    {
    WR_MEM_08(REMAP_ADDR,0x01);
    }

    Above is the original. Simply change it to what is shown below:

    Config_Remap()
    {
    WR_MEM_08(REMAP_ADDR,0x00);
    }

    Regards,