/* need to set opmode before you set config */
wifi_set_opmode(STATIONAP_MODE);
{
struct station_config *config = (struct station_config *) zalloc(
sizeof(struct station_config));
sprintf(config->ssid, "coolssid");
sprintf(config->password, "coolpass");
/* need to sure that you are in station mode first,
* otherwise it will be failed. */
wifi_station_set_config(config);
free(config);
}
When running a RTOS program, at startup and at regular intervals messages are send on the uart.
I am planning to use the uart for communicating with arduino, sending commands and receiving replies.
The "system messages" appearing on the uart will then interfere with this communication
- startup
pp_task_hdl : 3fff1f98, prio:20, stack:512
ApiMsgMutex created
idle_task_hdl : 3fff39f8
tim_task_hdl : 3fff3c58
xPortStartScheduler
OS SDK ver: 0.0.5 compiled @ Dec 25 2014 17:57:07
phy ver: 273, pp ver: 6
I found the "printf" of idle_task_hdl, tim_task_hdl, xportschedular in the freertos implementation, so can eventually update there.
Others not yet detected.
Is not a big issue as I can just ignore all on arduino at when restarted and submit my own "Ready" command.
But nice to have to understand where they come from and how to prevent.
-every 5 minutes this is send :
scandone
add 0
aid 2
aid end
cnt
connected with devolo-T, channel 6
dhcp client start...
ip:10.0.0.211
mask:255.255.255.0
gw:10.0.0.138
These are more troublesome as they directly interfere with arduino communication and need specific handling if I cannot prevent them.
Question is also on why the esp reconnects every 5 minutes. Is that "normal behaviour" for every wifi client ?
Kind regards,
Herman
hreintke wrote:LS,
When running a RTOS program, at startup and at regular intervals messages are send on the uart.
I am planning to use the uart for communicating with arduino, sending commands and receiving replies.
The "system messages" appearing on the uart will then interfere with this communication
- startupCode: Select allpp_task_hdl : 3fff1f98, prio:20, stack:512
ApiMsgMutex created
idle_task_hdl : 3fff39f8
tim_task_hdl : 3fff3c58
xPortStartScheduler
OS SDK ver: 0.0.5 compiled @ Dec 25 2014 17:57:07
phy ver: 273, pp ver: 6
I found the "printf" of idle_task_hdl, tim_task_hdl, xportschedular in the freertos implementation, so can eventually update there.
Others not yet detected.
Is not a big issue as I can just ignore all on arduino at when restarted and submit my own "Ready" command.
But nice to have to understand where they come from and how to prevent.
-every 5 minutes this is send :Code: Select allscandone
add 0
aid 2
aid end
cnt
connected with devolo-T, channel 6
dhcp client start...
ip:10.0.0.211
mask:255.255.255.0
gw:10.0.0.138
These are more troublesome as they directly interfere with arduino communication and need specific handling if I cannot prevent them.
Question is also on why the esp reconnects every 5 minutes. Is that "normal behaviour" for every wifi client ?
Kind regards,
Herman
You can use os_install_putc1 (esp_misc.h for details) to set custom (empty if you don't need printf) putc function. However the startup garbage will still show.