node.dsleep() reliability - zombie mode

Left here for archival purposes.
 Topic locked

User avatar

Re: node.dsleep() reliability - zombie mode

By cal
- Fri May 01, 2015 4:29 am #16166
delinend wrote:
Eyal wrote:
delinend wrote:Around 17.9K


Since you are building your own fw: I remove (#define->#undef) all unused modules in app/include/user_modules.h and gain many Ks of heap. YMMV

HTH


Hi Eyal.

Soory.. I can't build self. But I want to.. Do you know where to start? Can I use a Raspberry with GCC or do I have to use a Ubuntu? I think the best in the start, to get more Heap, is as you say to disable modules, that I'm not going to use.
The FW I have tested, was linked nicely from @Cal https://github.com/chadouming/nodemcu-firmware, and the dsleep work on that FW for me. But I have many cripts, that is to large for that FW.

Thanks and best regards


Moin,

I would avoid raspberry in this case. Too special and to slow for crosscompiling.

I assume you use windows. I don't use it so take my advice with care.
You have multiple options to build.
- compile natively under windows - there is a big thread that explains how to do that. I didn't looked into the details.
- install linux, e.g ubuntu natively - Too heavy weight for simple first playing if you don't have spare hardware and need to add it to you existing setup.
- install linux in vm: http://www.psychocats.net/ubuntu/virtualbox
- without desktop, using putty to work on the vm: https://machinelearning1.wordpress.com/ ... rough-ssh/
- or with desktop

The links I added were just from a short search on the web. They look reasonable. The putty link has some
more tips about remote working and setting up a shared folder. You may find it easier to stay away from
text editor vi in the beginning. "nano" seems to be popular.
I would go for the linux in vm using putty to start with.
You can always change later.
If there is interest in that route I can open a new thread for that and offer help for the linux part.

Cal
User avatar

Re: node.dsleep() reliability - zombie mode

By MKoehler
- Fri May 08, 2015 8:05 am #16890
cal wrote:Moin,

I read that one should flash blank bin when changing sdk versions and only
flashing parts because otherwise code maybe confused because structure changed.

Hope that helps,
Cal


Hi Cal,

I can confirm that with different ESP modules and LUA-apps zombie mode has totally gone with this firmware: https://github.com/chadouming/nodemcu-firmware. ESP is now much more reliable. Memory is a real problem but I see people are working on that and there is always room for optimisation ;)

I have discovered a nasty disadvantage over earlier firmwares though: The WLAN performance has considerably decreased with the build I am using! If I put the old firmware and a given LUA code on a module and later on use the 1.0 firmware (see above) with the same LUA code and module, WLAN does not work in a very distant room in my house whereas with the old version it worked fine there. I have done different tests to confirm this behaviour but the WLAN transmission weakness persists. Could that be a memory issue too or is there a flag in the DEV-KIT for reducing transmission power that might have been set building the 1.0 firmware. Any ideas how to solve this unpleasant side effect?

Heinz-Georg
 Topic locked
Return to Bug Reports