Show Posts
I am using an Arduino compatible FTDI breakout board ( http://osepp.com/learning-centre/start-here/ftdi-breakout-board/ftdi-breakout-board-2/ ) instead of the FTDI cable but the result is the exact same. Similar to what Adam experienced, regardless of speed and the other serial settings, the wifi shield never responds.
BTW looking around in Github I think I found some code that appears to be relevant:
File : board_init.c ( https://github.com/arduino/wifishield/blob/master/firmware/wifiHD/src/board_init.c )
Code:
static void init_printk(void)
{
#ifndef NO_SERIAL
#if defined(CONFIG_CONSOLE_PORT)
const usart_options_t usart_options = {
.baudrate = 57600,
.charlength = 8,
.paritytype = USART_NO_PARITY,
.stopbits = USART_1_STOPBIT,
.channelmode = USART_NORMAL_CHMODE
};
usart_init_rs232(&CONFIG_CONSOLE_PORT, &usart_options, FPBA_HZ);
#endif
#endif /* NO_SERIAL */
}
{
#ifndef NO_SERIAL
#if defined(CONFIG_CONSOLE_PORT)
const usart_options_t usart_options = {
.baudrate = 57600,
.charlength = 8,
.paritytype = USART_NO_PARITY,
.stopbits = USART_1_STOPBIT,
.channelmode = USART_NORMAL_CHMODE
};
usart_init_rs232(&CONFIG_CONSOLE_PORT, &usart_options, FPBA_HZ);
#endif
#endif /* NO_SERIAL */
}
I think this proves that your settings are correct. But it brings up the question if CONFIG_CONSOLE_PORT was defined when our firmware was built. I suspect that it was not... hence the no response behavior.
I don't know enough about the firmware build environment. Maybe someone more familiar could help us out.
John