• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 62 subscribers
  • Views 232 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

LP876242-Q1: Contact info for programming LP876242-Q1 devices

Sivakumar Subramanian
Prodigy 50 points
Part Number: LP876242-Q1


Tool/software:

Dear Sir/Madam,

We have 10 prototype boards(M.2 Cards) in which LP876242B0RQKRQ1  device is connected to FT4232H via I2C Interface.

Since the LP876242-Q1 devices can be communicated via SPI by default, we are unable to communicate it via FT4232H for configuring it through FTDI-I2C.

Can you please program the NVM of LP876242-Q1 devices in the 10 prototype boards to the following configuration?

  1. Control Interface to I2C (SPI is default in NVM)
  2. Vout1 = 2.5V
  3. Vout2 = 1.0V
  4. Vout3 = 1.2V
  5. Vout4 = 1.8V

Can please let us know the TI contact person details for the above service? 

Thanking you,

Regards,

Sivakumar S

  • +1
    TI__Genius 17610 points

    Hi Sivakumar,

    We do not have such service where we get board and do the custom updates as per the customer requirement. 

    However, we do support customer while implementing them successfully. 

    There seems to be two options. 

    1. Get EVM board and configure the NVM as I2C to the device and then soldered down to your card. 

    2. Implement the SPI protocol in the FT4232H in order to communicate with device on your board and then change it to I2C and then finally change the FT4232H communication to I2C. This is bit challenging as compared to the first option. 

    You can update the existing NVM using our Scalable GUI (Link) and we have documentation on how to update the NVM (Link). 

    Regards,

    Ishtiaque 

  • +1 in reply to Ishtiaque Panhwar
    Prodigy 50 points

    Hi Ishtiaque 

    Thanks for your reply.

    Our main requirement is to program the NVM to output the 4 voltages as mentioned, so on each powercycle, PMIC should output the same 4 voltages.

    We may adjust/fine tune the voltages using FTDI-SPI.

    1. Get EVM board and configure the NVM as I2C to the device and then soldered down to your card. - Ishtiaque 

    For configure the NVM as I2C, Do you mean the PMIC on the EVM board or external PMIC wired to the SPI Interface of the EVM?

    2. Implement the SPI protocol in the FT4232H in order to communicate with device on your board and then change it to I2C and then finally change the FT4232H communication to I2C. This is bit challenging as compared to the first option. - Ishtiaque 

    Using our FTDI-SPI application, can we change/configure the device communication mode from SPI to I2C? and also that can be stored into NVM?, so on next powercycle FTDI can talk to the device using I2C.?

    My understanding is that the device communication mode (SPI/I2C)  can be changed only by updating NVM that too using the EVM+GUI only right?

    Thanks

    Sivakumar S

  • 0 in reply to Sivakumar Subramanian
    TI__Genius 17610 points

    Hi, 

    Sivakumar Subramanian said:
    For configure the NVM as I2C, Do you mean the PMIC on the EVM board or external PMIC wired to the SPI Interface of the EVM?

    I mean PMIC on the EVM board, you need to solder the PMIC on the EVM board and change the configuration and then de solder it and then solder to your card. Which is not a optimal way to do that. It is just a work around for your few demo boards. In the end eventually you would need PMIC by default configured as I2C so that your board can communicate using debugger that you are mentioning.

    Sivakumar Subramanian said:
    Using our FTDI-SPI application, can we change/configure the device communication mode from SPI to I2C? and also that can be stored into NVM?, so on next powercycle FTDI can talk to the device using I2C.?

    I am not familiar with FTDI-SPI application, you may better have an idea whether it is configurable from SPI to I2C or not. With Current PMIC by default configured as SPI, you would need to configure FTDI to SPI protocol. 

    Sivakumar Subramanian said:
    My understanding is that the device communication mode (SPI/I2C)  can be changed only by updating NVM that too using the EVM+GUI only right?

    Yes you are understanding is correct. That's how it should be done. 

    Regards,

    Ishtiaque