On 04/13/2017 12:29 AM, Priyanka Jain wrote:

<snip>


 /* Debug Server firmware */
 #define CONFIG_SYS_DEBUG_SERVER_FW_IN_NOR @@ -256,6 +268,7 @@
unsigned long get_board_sys_clk(void);
 /*
  * I2C
  */
+#define CONFIG_SYS_I2C_FPGA_ADDR       0x66
LS2080ARDB current u-boot code is closely tied with qixis code at many places.
And if try to decouple QIXIS code with u-boot code, it will take a lot of code 
changes.
So, I just bypassed the final QIXIS call keeping other code changes for Qixis 
access via I2C.

For customized boards, which uses RDB code as reference, having proper way of 
CPLD access via I2C will be useful.
Also the board issue of CPLD access via I2C is getting fixed in next similar 
board LS2081ARDB.
Please suggest how to proceed on this.


You said the CPLD is not accessible via I2C bus. What do you get by pretending it is there? You know once you define this macro and CONFIG_QIXIS_I2C_ACCESS, all QIXIS access will go through I2C. If it doesn't do what you expect, how good is that as a reference design?

One way to get around this hardware bug, is to handle NO_QIXIS.

York

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to