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.

LM3642: LM3642 Design inquiries

Part Number: LM3642

hi

I would like to ask about the LM3642 design as follows.

1. Development progress
- Control by I2C communication, HW pin such as STROBE, TX / TORCH etc. is not used.
- It is implemented in order of about 1.2A -> 350mA -> 350mA flashing -> Off in 4 steps.
- Designed to keep the LED always on at 1.2A, 350mA.
- The power source uses the battery to drop or turn off the LED brightness when falling below a certain voltage.
(Plan to use IVFM mode or read the IVFM bit in Flags Register (0x0B)

2. Inquiries
- I need to turn on the FLASH LED all the time.
   (I reset it to Enable Register (0x0A) before "Flash Time-Out Time". In this case, the blinking occurred.)

- When I "Read" the communication with the IC, I tried to communicate with "Chip Add + R / W (1) - Register Add (0x0B) - Rx Data" as shown in the figure.
  It seems that the second data (Register Add) can not be sent properly and the read can not be done properly.

  When "Chip Add + R / W (1) - Rx Data" communication is performed, communication is not done properly, but unidentified data is received.
  Is it correct to configure the communication protocol as "Chip Add + R / W (1) - Register Add (0x0B) - Rx Data" as shown in the datasheet?

  • Hello,
    There is no way for the LM3642 to sustain a 1.2A flash due to the digital control scheme and the thermal limitations of the package. The only way to leave the LED on all the time is to use torch mode but these are at reduced current levels.

    The I2C implementation on the LM3642 is based upon the I2C standard so there should not be any differences observed communicating with this device. Can you communicate with other I2C devices using your I2C master?

    Greg