On the portable (and portableNative) examples, the UART_read in the console thread returns 0 on the first read after a power cycle. The example currently takes this as an error and closes the UART. A simple work-around is to either: 1. Delay the first UART_read until the UART is stabilized after the power cycle. We've found the following enough of a delay.    ** for (i = 0; i < 100000; i++) { } 2. Don't treat the zero return as an error. Instead simply call UART_read again.