• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 315 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.

Original question:

OPT3101-SDK: Calibration Failed using SDK on OPT3101EVM

OPT3101-SDK: OPT3101EVM Communication Error While Calibrating

wcoe
Prodigy 80 points
Part Number: OPT3101-SDK

What debugging steps are recommended if the following error occurs in step 8 of the calibration routine (according to OPT3101 SDK Users Guide)?

The connections have been verified as follows: 3V3->J17.1, GND->J17.2, P4.1->J17.3, P4.2->J17.4, P2.0->J17.7. I've also included an image of the setup. Note: the USB to the EVM is not connected to anything.

  • 0
    TI__Mastermind 25845 points

    Hi,

    First thing to check is i2c connection. Was this setup working previously and then stopped working?

    Best,

    Alex

  • 0 in reply to Alex Bhandari-Young
    Prodigy 80 points

    Alex,

    This setup is new, and this is my first time calibrating. I have put a logic analyzer on the I2C output from the launchpad with the EVM disconnected and get this in TeraTerm:

    and this is the I2C transmission:

    I'm not sure if this is what the launchpad is supposed to be sending, but it is at least trying to communicate. If I try to read the I2C with the EVM connected, I can't pick up an communication attempts. I've also tried switching the Data/Clock lines on the EVM with no success. 

  • 0 in reply to wcoe
    TI__Mastermind 25845 points

    Hi,

    Can you confirm launchpad is enumerating correctly with the PC? You should see 4 com ports appearing when the launchpad is plugged in - 2 from the launchpad itself and then 2 more from the SDK which we will be looking for. If you share a screenshot I can check this. The next step if we see 4 is to issue a serial command from a terminal program like tera term to the control com port. This port will have hardware ID MI_00. You can try issuing "REGRx01" to read register 1.

    Best,

    Alex