An archive of community.esquilo.io as of Saturday January 26, 2019.

Reset does not appear to start Network

rbg

On powering up the board appears to connect to my access point as seen via the log

1970-01-01T00:00:00Z INFO Esquilo Operating System (EOS)
1970-01-01T00:00:00Z INFO for Esquilo Air
1970-01-01T00:00:00Z INFO Version 0.2
1970-01-01T00:00:00Z INFO Copyright (c) 2014-2015 Esquilo Corp.
1970-01-01T00:00:00Z INFO Starting USB CDC
1970-01-01T00:00:00Z INFO Initializing WICED
1970-01-01T00:00:00Z INFO Starting Wiced
1970-01-01T00:00:01Z INFO WLAN MAC Address: 00:0B:6C:42:12:81
1970-01-01T00:00:01Z INFO WLAN Firmware: wl0: Nov  7 2014 16:03:45 version 5.90.230.12 FWID 01-324f6561
1970-01-01T00:00:01Z INFO Initializing RTCS
1970-01-01T00:00:01Z INFO Initializing station interface
1970-01-01T00:00:01Z INFO Initializing access point interface
1970-01-01T00:00:01Z INFO Starting web server
1970-01-01T00:00:01Z INFO Starting TELNET server
1970-01-01T00:00:01Z INFO Starting SNTP client
1970-01-01T00:00:01Z INFO Starting ESTP process
1970-01-01T00:00:01Z INFO Starting network monitor task
1970-01-01T00:00:01Z INFO Starting SD manager
1970-01-01T00:00:01Z INFO Starting Squirrel VM
1970-01-01T00:00:02Z INFO Installing MFS over partition...
1970-01-01T00:00:02Z INFO SD card installed to sd:
2015-07-01T02:41:21Z INFO ESTP session open client 172.16.2.68 server 172.16.0.1
2015-07-01T02:47:32Z INFO Starting USB EOS shell

however if i press the reset button it does not, I however would have expected it to do so .. are my expectations incorrect ? smile

log for reset:

eos> log
1970-01-01T00:00:00Z INFO Esquilo Operating System (EOS)
1970-01-01T00:00:00Z INFO for Esquilo Air
1970-01-01T00:00:00Z INFO Version 0.2
1970-01-01T00:00:00Z INFO Copyright (c) 2014-2015 Esquilo Corp.
1970-01-01T00:00:00Z INFO Starting USB CDC
1970-01-01T00:00:00Z INFO Initializing WICED
1970-01-01T00:00:00Z INFO Starting Wiced
1970-01-01T00:00:05Z INFO Starting USB EOS shell
patrick

Your expectations are correct. You should be re-connecting on a reset. I assume the network LED also stays off when you reset and that you cannot reach the board over the network?

Does this always happen when you press reset?

rbg

The LED does not come on. It appears to fail bring up the network device. If there is additional debug information i should collect let me know -- i'd be happy to help root-cause. (i can load a debug build if you'd like)

patrick

It does look like something is going wrong during WiFi init. Thanks for offering to try a debug image. The one below enables a lot of logging in the WiFi code. It uses RAM very liberally, so please don't leave it on your device.

eos_esquilo_wifi_DEBUG_ONLY.img (860.8 KB)

rbg

here is what i see in the log:

eos> log
1970-01-01T00:00:00Z INFO Esquilo Operating System (EOS)
1970-01-01T00:00:00Z INFO for Esquilo Air
1970-01-01T00:00:00Z INFO Version 0.2-1-g68f25ab
1970-01-01T00:00:00Z INFO Copyright (c) 2014-2015 Esquilo Corp.
1970-01-01T00:00:00Z INFO Starting USB CDC
1970-01-01T00:00:00Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:00Z INFO Initializing WICED
1970-01-01T00:00:00Z INFO Starting Wiced
1970-01-01T00:00:00Z DEBUG wiced_rtos_init
1970-01-01T00:00:00Z DEBUG wiced_rtos_create_worker_thread thread: 1fff3158     priority: 2 stack: 4000 queue:1970-01-01T00:00:00Z DEBUG wiced_rtos_init_queue queue: 1fff315c name: WICED Queue size: 8 num: 15
1970-01-01T00:00:00Z DEBUG wiced_rtos_pop_from_queue queue: 1fff315c message: 1fff95b0 timeout: -1
1970-01-01T00:00:00Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:09Z INFO Starting USB EOS shell
rbg

after a bit :
1970-01-01T00:02:25Z DEBUG AP interface up
1970-01-01T00:02:25Z DEBUG wiced_rtos_pop_from_queue queue: 1fff315c message: 1fff95b0 timeout: -1
1970-01-01T00:02:26Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:26Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:26Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:26Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:26Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:26Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:26Z DEBUG wiced_rtos_send_asynchronous_event thread: 1fff3158 function: 1b54d arg: 1
1970-01-01T00:02:26Z DEBUG wiced_rtos_push_to_queue queue: 1fff315c message: 200036d0 timeout: 0
1970-01-01T00:02:26Z DEBUG result: 0
1970-01-01T00:02:26Z DEBUG worker_thread_main result: 0
1970-01-01T00:02:26Z DEBUG worker_thread_main function: 1b54d arg: 1
1970-01-01T00:02:26Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:26Z DEBUG AP interface up
1970-01-01T00:02:26Z DEBUG wiced_rtos_pop_from_queue queue: 1fff315c message: 1fff95b0 timeout: -1
1970-01-01T00:02:26Z DEBUG result: 0
1970-01-01T00:02:27Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:27Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:27Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:27Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:27Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:27Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:27Z DEBUG wiced_rtos_send_asynchronous_event thread: 1fff3158 function: 1b54d arg: 1
1970-01-01T00:02:27Z DEBUG wiced_rtos_push_to_queue queue: 1fff315c message: 200036d0 timeout: 0
1970-01-01T00:02:27Z DEBUG result: 0
1970-01-01T00:02:27Z DEBUG worker_thread_main result: 0
1970-01-01T00:02:27Z DEBUG worker_thread_main function: 1b54d arg: 1
1970-01-01T00:02:27Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:02:27Z DEBUG AP interface up
1970-01-01T00:02:27Z DEBUG wiced_rtos_pop_from_queue queue: 1fff315c message: 1fff95b0 timeout: -1
1970-01-01T00:02:27Z DEBUG result: 0

rbg

I did the eos command 'reset' and the log reads thus:

eos> log
1970-01-01T00:00:00Z INFO Esquilo Operating System (EOS)
1970-01-01T00:00:00Z INFO for Esquilo Air
1970-01-01T00:00:00Z INFO Version 0.2-1-g68f25ab
1970-01-01T00:00:00Z INFO Copyright (c) 2014-2015 Esquilo Corp.
1970-01-01T00:00:00Z INFO Starting USB CDC
1970-01-01T00:00:00Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:00Z INFO Initializing WICED
1970-01-01T00:00:00Z INFO Starting Wiced
1970-01-01T00:00:00Z DEBUG wiced_rtos_init
1970-01-01T00:00:00Z DEBUG wiced_rtos_create_worker_thread thread: 1fff3158 priority: 2 stack: 4000 queue:1970-01-01T00:00:00Z DEBUG wiced_rtos_init_queue queue: 1fff315c name: WICED Queue size: 8 num: 15
1970-01-01T00:00:00Z DEBUG wiced_rtos_pop_from_queue queue: 1fff315c message: 1fff95b0 timeout: -1
1970-01-01T00:00:00Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:09Z INFO Starting USB EOS shell
1970-01-01T00:00:50Z DEBUG Could not bring ARM core up
1970-01-01T00:00:50Z ERROR Could not download firmware
1970-01-01T00:00:50Z ERROR Could not initialize bus
1970-01-01T00:00:50Z ERROR Error -1 while starting WICED!
1970-01-01T00:00:50Z DEBUG wiced_rtos_init_timer timer: 1fff2190 time: 3000 handler: 18f51 arg: 0
1970-01-01T00:00:50Z INFO WLAN MAC Address: 6C:20:FF:1F:B0:00
1970-01-01T00:00:50Z INFO WLAN Firmware:
1970-01-01T00:00:50Z INFO Initializing RTCS
1970-01-01T00:00:50Z INFO Initializing station interface
1970-01-01T00:00:50Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:50Z DEBUG wiced_rtos_send_asynchronous_event thread: 1fff3158 function: 1b54d arg: 0
1970-01-01T00:00:50Z DEBUG wiced_rtos_push_to_queue queue: 1fff315c message: 1fff5a88 timeout: 0
1970-01-01T00:00:50Z DEBUG result: 0
1970-01-01T00:00:50Z DEBUG worker_thread_main result: 0
1970-01-01T00:00:50Z DEBUG worker_thread_main function: 1b54d arg: 0
1970-01-01T00:00:50Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:50Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:50Z DEBUG result: 0
1970-01-01T00:00:50Z INFO Initializing access point interface
1970-01-01T00:00:50Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:50Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:50Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:50Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:50Z DEBUG wiced_rtos_pop_from_queue queue: 1fff315c message: 1fff95b0 timeout: -1
1970-01-01T00:00:51Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:51Z INFO Starting web server
1970-01-01T00:00:51Z INFO Starting TELNET server
1970-01-01T00:00:51Z INFO Starting SNTP client
1970-01-01T00:00:51Z INFO Starting ESTP process
1970-01-01T00:00:51Z INFO Starting network monitor task
1970-01-01T00:00:51Z INFO Starting SD manager
1970-01-01T00:00:51Z INFO Starting Squirrel VM
1970-01-01T00:00:51Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:51Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:51Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:51Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:51Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:51Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:52Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:52Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:52Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:52Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:52Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:52Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:53Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:53Z DEBUG wiced_dct_get_wifi_config_section
1970-01-01T00:00:53Z DEBUG wiced_dct_get_wifi_config_section

patrick

Thanks for the logs. Looks to me like maybe the hardware reset line to the WiFi module is not working. Scott is the hardware guy, I'll check with him.

patrick

Scott agrees that it seems like a hardware issue with the reset line. If I send you a replacement and a postage label, would you mind sending it back for us to take a look at?

rbg

yes that would be swell (is that enough characters ??)