| 279 | | * When an unpowered JTAG adapter in a development environment is attached to the JTAG connector on a powered board (plugged into the 10-pin header but the adapter's USB is unpowered/attached to a PC) the GSC is held in a 'debug' state where code execution does not function properly. This coupled with newer uboot software that performs I2C bus recovery on failed transactions, allows the GSC to get out of sync with the IMX I2C master thus writing 0xff's to the GSC registers at 0x20 causing the GSC to put the board to sleep |
| 280 | | without the possibility of a wakeup event. Removing the GSC battery temporarily to reset the GSC is the only way to get out of this state. |
| 281 | | |
| 282 | | Note this errata will only occur when using a JTAG adapter that is not USB powered and connected to an already powered SBC through the 10-pin connector. To avoid this errata, connect the USB of the JTAG adapter to a powered host before applying power to the SBC. |
| | 279 | * When an unpowered JTAG adapter in a development environment is attached to the JTAG connector on a powered board (plugged into the 10-pin header but the adapter's USB is unpowered/attached to a PC) the GSC is held in a 'debug' state where code execution does not function properly. This coupled with newer uboot software that performs I2C bus recovery on failed transactions, allows the GSC to get out of sync with the IMX I2C master thus writing 0xff's to the GSC registers at 0x20 causing the GSC to put the board to sleep without the possibility of a wakeup event. Removing the GSC battery temporarily to reset the GSC is the only way to get out of this state. |
| | 280 | * Note this errata will only occur when using a JTAG adapter that is not USB powered and connected to an already powered SBC through the 10-pin connector. To avoid this errata, connect the USB of the JTAG adapter to a powered host before applying power to the SBC. |
