Hi team,
I would like to know why I2C2 address can't match the datasheet.
If the I2C1 address is 0x23, I think I2C2 address should be 0x48, but the GUI show 0x38. May I know why?


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.
Hi team,
I would like to know why I2C2 address can't match the datasheet.
If the I2C1 address is 0x23, I think I2C2 address should be 0x48, but the GUI show 0x38. May I know why?


Jason,
I2C2 address can be overridden in Global System Config (0x27)
Thanks,
Chris
Jason,
Sorry the new 6.3.3 GUI has a separate register for I2C Address Override mapping (0x2B)

Hi Chris,
I don't see that in Dell GUI DELLONLY Application Customization 6.6.27
Could you help to check?
btw, why the GUI always show 0x38?

Jason
I do see it in the 6.6.27 GUI

Please attach the PJT so I can open it in the 6.6.27 GUI.
Hi Chris,
They need to modify it like below, right?

Please see attached file, if they don't override the I2C2 address, is it ok with that?
20220412_U4924DW_987dk_6.6.27_F907_14_10.pjt
Jason
Hi Chris,
One question, they use I2C2 in their design, I don't use 0x2B to override the I2C2 address, but I don't see anything wrong in their design, may I know why?

Jason
The GUI could be inaccurate in the value displayed. Best way to test is to read from 0x4F on I2C2 and see if it responds.
Just confirmed this is just a GUI issue. The I2C2 address does not update based on I2C_ADDR set.
Hi Chris,
So we don't need to override the I2C2 address on 0x2B, right?
Jason