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.

DS110RT410: About a system of two DS110RT410s in series with unprogrammed EEPROM .

Part Number: DS110RT410
Other Parts Discussed in Thread: DPS-DONGLE-EVM, USB2ANY

Hi,Team

I build a system with one EEPROM and two DS110RT410s in series.

I intend to connect the READ_EN of the first DS110RT410 to ground and the ALL_DONE of the first device to the READ_EN of the next DS110RT410.

The eeprom is not initially programmed.

So first you have to write the eeprom with SigCon software.

According to the snlu126c documentation, the DS110RT410 SMBUS_EN should be able to connect to the ground.

So I'm trying to be able to connect the SMBUS_EN of two DS110RT410s to the ground. I will connect SMBUS_EN to ground when writing EEPROM.

Is there any mistake in this idea? 

Is there nothing I need to do with the two READ_ENs?

翻訳結果

  • Hi,

    One item I would like to clarify is that although SigCon will generate a hex file for the EEPROM, it will not facilitate writing that hex file to the EEPROM.

    With that said, you are correct that connecting SMBUS_EN to ground when writing EEPROM should ensure that the DS110RT410 do not communicate on the SMBus lines.  You don't need to do anything with the READ_EN pins.

    If for some reason this procedure does not work as expected, let me know and I can propose an alternative procedure.

    Thanks,
    Drew

  • Thank you for your answer!

    It seems that it is not specified in the data sheet, but can it be interpreted that SMBUS
    of DS110RT410 is disabled when SMBUS_EN is connected to ground?

  • Hi,

    Yes I suspect this is the case.  This is the behavior of some similar devices (and is documented in their datasheets).

    Thanks,
    Drew

  • OK. Please tell me another one. I will be able to disconnect the I2C bus of the EEPROM that is not programmed in the circuit. If so, can the two DS110RT410s be initialized, controlled and debugged with Sigicon-Softaware? Are there any notes about READ_EN and SUMBUS_EN? I'm thinking of USB2ANY or DPS-DONGLE-EVM for the connection to I2C. By the way, I am thinking of creating a separate software for writing to EEPROM and writing the HEX file output from Sigicon-Softaware by I2C.

  • Hi,

    Yes it is possible to control these devices with SigCon Architect.  I would recommend using a USB2ANY to interface between SigCon and I2C.

    In regards to READ_EN and SMBUS_EN, you will want to set these such that the device is in "slave mode".  For this mode, tie READ_EN LOW and SMBUS_EN HIGH.

    Thanks,

    Drew

  • Thank you for your answer.

    I have come up with it.

    This EPPROM has an I2C address of 0xA0 (0x50 in 7bit expression) when the A2 terminal is GND, and 0xA8 (0x54 in 7bit expression) when it is High. Therefore, isn't it the same as disconnecting from the two DS110RT410s just by setting the A2 terminal to High? If I think it's right, you only need one switch.

  • Hi,

    If you want to configure the DS110RT410 through SigCon architect, it will need to be in "slave mode".

    You are correct that the EEPROM will no longer be accessible if it has a different address than expected, but without changing READ_EN and SMBUS_EN, the DS110RT410 will still be in "master mode".

    Thanks,

    Drew

  • When the A2 pin of the EEPROM is set to High and cannot be accessed, I will set the SMBUS_EN pin to HIgh (slave mode) and the READ_EN pin to Low.

    According to the data sheet, when the power is turned on in this state, the DS110RT410 first enters the master mode and uses the EEPROM for reference, but since it cannot be referenced, it will eventually settle in the slave mode. As a result, Sigcon will be ready for use. Is this idea wrong?

  • According to the data sheet, when the power is turned on in this state, the DS110RT410 first enters the master mode and uses the EEPROM for reference, but since it cannot be referenced, it will eventually settle in the slave mode. As a result, Sigcon will be ready for use. Is this idea wrong?

    Yes this should work.

    Thanks,
    Drew