• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 652 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.

OPT3101-SDK: Port the OPT3101 SDK to other MCU

Pengsheng Qiu
Intellectual 330 points
Part Number: OPT3101-SDK
Other Parts Discussed in Thread: OPT3101, OPT3101EVM

Hi!  Team:

    Complete engineering unit calibration with OPT3101 EVM, step INPRODCTION and external EEPROM

    I communicated with Gordon in the forum that after factory unit calibration, some parameters still need to be loaded through SDK, and these parameters cannot be written into external EEPROM through SDK；

The argument to the dev.resetInitAndViewData function must be True，

In porting SDK, loadIllumCrosstalkSet function, loadPhaseOffsetSet function entry parameter is True；

Red The checked section on whether the FLASH read operation function needs to be migrated, the parameters in the factory unit calibration are stored in the external EEPROM；

Thanks！

  • 0
    TI__Expert 6800 points

    Hi,

    Yes, these functions will need to be migrated so that when you perform the calibration, the previous calibration values for that unit can be loaded to the device so that the subsequent calibrations will be done correctly.

    Thank you,

    Brent Elliott

  • 0 in reply to Brent Elliott
    Intellectual 330 points

    Brent：

    There are also the following questions：

    1、Through the factory unit calibration in the SDK, the calibrated parameters are saved in the external EEPROM. The above two functions load parameters internally to read FLASH, what is the external EEPROM used to do；

    2、The distance data read from the register is not a calculated value that has been calibrated

    3、There is also a problem, porting SDK to other MCU platforms, code compilation consumes huge RAM resources, and the variable definition of hostController.cpp file consumes too much

    RAM resource consumption problem how to optimize!

    4、If an external EEPROM is used, how can the parameters obtained from the illumination crosstalk calibration and phase offset calibration be stored in the EEPROM so that the OPT3101 can load these parameters after re-powering

  • +1 in reply to Pengsheng Qiu
    TI__Expert 6800 points

    HI Pengsheng,

    1. In the SDK, the calibration parameters are saved to and loaded from the flash on the controller. Some changes will need to be made if you want to write to and read from EEPROM instead. I will not be able to support those changes at this time so you would need to implement this if you want to use EEPROM to store calibration parameters instead of the MSP430 flash memory.

    2. Can you clarify the question? The result register should read out a number that will directly translate to the distance when multiplied by a factor.

    3. This would need to be debugged further and I cannot support since this is porting to a different platform than what the SDK was originally written for.

    4. The OPT3101 has an i2c master which can be used to write and read from EEPROM.

    Thank you,

    Brent Elliott

  • 0 in reply to Brent Elliott
    Intellectual 330 points

    Brent：

    Is it documented that calibration parameters such as illumination crosstalk calibration and phase offset calibration are stored in the EEPROM? Or who can provide such technical support？

    Thanks！

  • 0 in reply to Pengsheng Qiu
    TI__Expert 6800 points

    Hi Pengsheng,

    The OPT3101EVM does not have an external EEPROM. It is expected that the EEPROM would be implemented in the board design for the application. The datasheet contains information on how to use the 3101's i2c master to communicate with an external EEPROM.

    Thank you,

    Brent Elliott