• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 401 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.

ULC1001: ULC1001-DRV290XEVM

fedi makni
Prodigy 100 points
Part Number: ULC1001
Other Parts Discussed in Thread: DRV2901, , USB2ANY

Hello,

We ordered the  ULC1001-DRV290XEVM and we got all the necessary documents (full datasheet and firmware...).

We tested the EVM and it works fine.

We tried to build our own PCB containing the module and the driver (drv2901) with all the necessary additional component based on the reference design, and we would like to use our own uC to control the chip.

We simply would like to test if the chip operate fine or not, the problem is that the source code is a little bit complicated compared to other I2C devices from TI that simply we can control one register or 2 registers and the job is done.

The register map is a little bit complicated and there's no easy explanation of how to start.

Our goal is to simply test the water cleaning mode and verify if the output matches the EVM output.

Does it require a lot of configuration to achieve this or maybe we didn't get the datasheet well?

Thank you.

  • 0
    TI__Genius 10502 points

    Hi Fedi,

    Let me clarify our understanding. You replaced the MSP430 with your own uC to control ULC1001, correct? And you are having trouble programming the new uC based on TI's MSP430 FW code?

  • 0 in reply to Kelly Griffin
    Prodigy 100 points

    Hello,

    No, we build a new PCB and we are programming it with ESP32.

  • 0 in reply to fedi makni
    TI__Genius 17610 points

    Hi Fedi, 

    On your new PCB you are controlling ULC1001 with ESP32, correct? If so, our EVM user guide section '5.5 GUI Functions' has I2C commands for various sequences including calibration, cleaning, diagnostics, etc. Additionally, our GUI can export a header file that is used in our EVMs firmware, which makes for simpler configuration of the device upon power up. Also in the GUI, you can record a script when operating that can also help in writing the firmware. Hope this helps. 

    Regards,
    Sydney Northcutt 

  • 0 in reply to Sydney Northcutt
    Prodigy 100 points

    Hello,

    Thank you for your response.

    I have several questions if you don't mind:

    1. We don't need to use the GUI in our test of course because we don't use the MSP uC correct? The GUI is just for our reference.
    2. I checked the EVM user guide section 5.5, For a quick test to check if the chip operate and behave normally, can we directly start manipulating the register mentioned in "5.5.6 run cleaning modes" and start directly as the table sequence provided or we are required to do some calibrations and initialisations before reaching the cleaning modes?

    Thank you again for your time and consideration.

    Best regards.

  • 0 in reply to fedi makni
    TI__Genius 17610 points

    Hi Fedi, 

    1. When using the GUI with our EVM, the MSP430 is not used. The GUI acts as the controller and communicates with ULC1001 via I2C. If your test is to make sure the board operates correctly, it may be easiest to connect the I2C line to a USB2ANY and connect to the GUI. This would be the quickest way to test the functionality of the board. 

    2. If you have an LCS (lens cover system) connected, you should run a calibration after powering up the device / before running any other modes. 

    Regards,
    Sydney Northcutt 

  • 0 in reply to Sydney Northcutt
    Prodigy 100 points

    Hello,

    Thank you.

    I think for the early test your recommendation of using the GUI will be very helpful.

    So in our case we don't need to use the ESP32 for that.

    My question is, is there any other recommended wire that need to be added other than SDA and SCL? I think GND is mandatory to be connected too right?

    Best regards.

  • 0 in reply to fedi makni
    TI__Genius 17610 points

    Hello,

    Right, if you use the GUI you do not need the uC for testing. I recommend you still include it on your PCB though and just have jumpers to connect / disconnect the I2C line. 

    You are correct. To connect to the GUI you need to connect SCL SDA and GND from your PCB to a USB2ANY, which then connects to your computer via USB.

    Regards,
    Sydney Northcutt