ESP8266 Community Forum

Posted: **Sun Jun 04, 2017 9:43 pm**

At least figured out this problem...On the esp12, the blue led light is the tx pin,
and so when you configure it as GPIO to flash the led as is done in the blinky example,
it bashes the os_print output. I disabled that function, and now I see the output at 115200 baud once my program sets the baud rate. Sheesh, I guess they put the led on there to see the tx happening when it isn't configured as gpio.

Well, now I get output, but I get the system debug output as well as my own os_print,
guess I will now try to turn of the system output or redirect them and see if that cleans up my output.

I like my msp430's, so much easier to get things done, but now I have wifi, kinda.

Posted: **Wed Sep 27, 2017 10:35 am**

I'm facing a similar problem did you ever figure this out? If not i'd be interested to see if you get the same results I do when connecting to a wifi network: I see logs from the config of the network at 9600 baud but I don't see any of the logs I printed myself. I do execute
This is in my user_init which is where the logs seem to be coming from:

Code: Select all

  uart_div_modify(0, UART_CLK_FREQ / 9600);
  wifi_set_opmode( STATION_MODE );
  os_memcpy(&stationConf.ssid, ssid, 32);
  os_memcpy(&stationConf.password, password, 32);
  wifi_station_set_config(&stationConf);
  wifi_station_connect();

ESP8266 Community Forum

os_printf, uart_init, iram1_0_seg overflow

Re: os_printf, uart_init, iram1_0_seg overflow SOLVED

Re: os_printf, uart_init, iram1_0_seg overflow