Search found 123 matches

by tve
Mon Jun 08, 2015 4:56 pm
Forum: ESP8266 SDK
Topic: Device does not enter light sleep
Replies: 1
Views: 2161

Device does not enter light sleep

I am switching to opmode=1 (STA) and calling wifi_set_sleep_type to enter light sleep mode, however, the power consumption I see corresponds to modem sleep mode. I see the module running at ~15mA and waking up every beacon interval (DTIM1) during which the power jumps to ~60mA. I also see it continu...
by tve
Tue May 26, 2015 3:20 am
Forum: ESP8266 SDK
Topic: explain system_uart_swap
Replies: 0
Views: 2467

explain system_uart_swap

The SDK 1.0.1 documentation for system_uart_swap states: UART0 swap. Use MTCK as UART0 RX, MTDO as UART0 TX, so ROM log will not output from this new UART0. We also need to use MTDO (U0CTS) and MTCK (U0RTS) as UART0 in hardware. However, looking at 0D-ESP8266__Pin_List_v0.1.xlsx I see that function ...
by tve
Mon May 25, 2015 3:25 pm
Forum: ESP8266 SDK
Topic: error with sdk 1.1.0
Replies: 6
Views: 6009

Re: error with sdk 1.1.0

Yup... They got changed from PULLDWN to PULLUP2 without explanation. I suspect that there isn't an pull-down the chip... In the pin description XLS file the modes are described as reserved. Go figure...
by tve
Sat May 23, 2015 11:53 pm
Forum: ESP8266 SDK
Topic: SDK 1.1.0 problems
Replies: 16
Views: 10829

Re: SDK 1.1.0 problems

Can you please also explain the following changes? Is there a pull-down option on the gpio pins or is there not? What does "pullup2" do? diff -r esp_iot_sdk_v1.0.1/include/eagle_soc.h esp_iot_sdk_v1.1.0/include/eagle_soc.h 187c187 < #define PERIPHS_IO_MUX_PULLDWN BIT6 --- > #define PERIPHS...
by tve
Sat May 23, 2015 11:37 pm
Forum: ESP8266 SDK
Topic: SDK 1.1.0 problems
Replies: 16
Views: 10829

SDK 1.1.0 problems

Thank you for providing SDK 1.1.0 in the downloads forum. I have some problems with it: The SDK 1.1.0 removes os_timer_arm, os_timer_disarm, os_timer_setfn: what's your thinking? These were documented functions in the SDK 1.0.1 document so their silent disappearance is rather strange. E.g.: diff -r ...
by tve
Thu May 21, 2015 12:31 pm
Forum: ESP8266 SDK
Topic: OTA upgrade is not fail-safe
Replies: 10
Views: 5522

Re: OTA upgrade is not fail-safe

yes
by tve
Sat May 16, 2015 11:07 am
Forum: ESP8266 SDK
Topic: OTA upgrade is not fail-safe
Replies: 10
Views: 5522

Re: OTA upgrade is not fail-safe

Blank.bin is annoying because it resets all the wifi settings... What I'm concerned is that the problem I encountered highlights a deeper issue. It seems that the bootloader keeps track of "next partition for upgrade" in the settings in flash as opposed to basing it off which partition is ...
by tve
Fri May 15, 2015 2:54 pm
Forum: ESP8266 SDK
Topic: OTA upgrade is not fail-safe
Replies: 10
Views: 5522

Re: OTA upgrade is not fail-safe

There is a further bug, which is that after all of the above the system_upgrade_flag_set(UPGRADE_FLAG_FINISH) + system_upgrade_reboot() sequence reboots into user1.bin instead of user2.bin. In other words: - running in user1.bin - upload garbage user2.bin - call system_upgrade_flag_set(UPGRADE_FLAG_...
by tve
Fri May 15, 2015 12:42 pm
Forum: ESP8266 SDK
Topic: OTA upgrade is not fail-safe
Replies: 10
Views: 5522

Re: OTA upgrade is not fail-safe

I flashed the segment that is normally flashed to 0x00000 when using esp_open_sdk to produce a 0x0000.bin and a 0x40000.bin. I'm attaching it (ignore the .jpg extension, it's just there so I can attach it here). BTW, I noticed that the checksum in the user1.bin/user2.bin binaries does not include th...
by tve
Fri May 15, 2015 10:32 am
Forum: ESP8266 SDK
Topic: OTA upgrade is not fail-safe
Replies: 10
Views: 5522

Re: OTA upgrade is not fail-safe

Interestingly, after the above test I proceeded to serially flash user1.bin (only the 236KB user1.bin, not any of the other parts, such as the bootloader or the system params). At the end of the serial flash the following happened: load 0x40100000, len 1320, room 16 tail 8 chksum 0xb8 load 0x3ffe800...

Go to advanced search