Hi Poornima,
Yes. I understand ADV8005 can be used on I2C bus either at address 0x18 or 0x1A by setting ALSA pin to low or high. However Blimp does not grant this freedom.
In 1.81RC1 source code, just search the C codes under directory OSD_BMP that Blimp generated by grepping '0x1a'. You will see a bunch of statements
"HAL_read8 (0x1a, 0x1a23, &data, BUS_IIC2);"
"HAL_write8 (0x1a, 0x1a23, data, BUS_IIC2);"
, and so on.
These "hard-coded" codes vetoes address 0x18 for ADV8005.
We are using 8005 evaluation hardware and have ported 1.81RC1 software onto another MCU. Hardware engineers helped cutting apart i2c, spi, control wires from BF524, and let MCU do whatever BF524 does. The evaluation hardware leaves not much space for wires. Thus, we can only let ADV8005 stay at i2c address 0x18. And we discovered this limitation of Blimp.
A workaround can be whatever data read/written to address 0x1a, force it to address 0x18 in PLATFORM. But this workaround seems absolutely ridiculous. Right?
Warm Regards
Joel Ding