nekromant/esp8266-frankenstein

Does "deepsleep" command work for you?

Closed this issue · 14 comments

For me, it prints some garbage and locks up module. I'm using gcc, libhal and newlib built from source.

You must connect gpio16 to rst pin. Its necessary . Other else it cant wake up.

Without GPIO16 connected to RST - that's what deepsleep does.

Without GPIO16 connected to RST - that's what deepsleep does.

And - maybe you could elaborate how you tested it then? Does your ESP-01 have it connected like that on the PCB? None of the module types available on Chinese market break out RST signal to the pin. I have ESP-03 here, and the behavior is above.

Ok, I see that on my ESP-03 has GPIO16 and RST routed to an SMD jumper, which is disconnected as shipped. Glad it will be possible to connect it, but it's still vendor cheating - they give you cheap stuff, but it's not suitable to do something really useful (like low-power stuff). Seen that before with CSR Bluetooth (HC-04 and friends) - any specs related to low-power are strictly hidden from public eyes, and otherwise the crap draws 2mA in "idle". That's why I stopped working on https://github.com/pfalcon/blutunode .

i saw 0,36ma in deepsleep. and i have esp-01. maaybe i remove power led and see lower than 0.36ma.
Without GPIO16 connected to RST deepsleep cant sleep and wake.

@alonewolfx2: Thanks for the info, appreciated.

i can compile and upload but its not working for my oled. i change adress
but still not working

2014-11-15 14:15 GMT+02:00 Paul Sokolovsky notifications@github.com:

@alonewolfx2 https://github.com/alonewolfx2: Thanks for the info,
appreciated.


Reply to this email directly or view it on GitHub
#1 (comment)
.


[ Dalından kopan yaprağın akıbetini rüzgar belirler... ]

i can compile and upload but its not working for my oled. i change adress
but still not working

Not sure what you mean. But good call, maybe you'll want to test my integrated sdk build script: https://github.com/pfalcon/esp-open-sdk . It produces firmware images byte-to-byte matching provided by @nekromant. Which would mean that either he doesn't use libc at all, or builds it from https://github.com/jcmvbkbc/newlib-xtensa too.

I have my toolchain built via crosstool-ng, newlib used as a blob. for now. However incurrent master there's a small bug in the linking so that some newlib functions like sscanf are undefined. I'll push a fix today.

newlib used as a blob

Ok, so maybe you'll be interested in https://github.com/pfalcon/esp-open-sdk too. It builds libhal and newlib from sources, pull out espressif SDK with "patches", etc.

Yeah, I've seen that - just haven't tested yet.

@pfalcon how can i use this open-sdk? can you explain a little?
i am getting when i try make after make command

inflating: esp_iot_sdk_v0.9.2/tools/xxd.exe
ln -s $(dirname esp_iot_sdk_v0.9.2/.dir) sdk
ln: failed to create symbolic link ‘sdk’: Read-only file system
make: *** [esp_iot_sdk_v0.9.2/.dir] Error 1
root@esp8266-VirtualBox:/mnt/Share/esp-open-sdk-master$

@alonewolfx2: could you please point me to how to put esp-1 to deep sleep... i.e. how to connect the GPIO16 and RST on the module? Did you just solder a jumper directly on the SOC pins, or is there a place for a jumper on the board?

Esp03 have on board place for soldering. Esp01 don't have. I use both. I am using 0 ohm resistor on esp03 and I soldered directly on esp01 soc.