MicroPython Forum (Archive)

The problem isnt's just the REPL.

There are many things that output stuff when strictly then shouldn't (for example ntptime) and given the lack of a concept of stdout and things an operating system would provide where should these go ?

Jon

Be a bit careful. with their figures. They're using a 300ms beacon interval. It's also worth remembering that infrastructure mode powers down the radio between its slots as a matter of course whereas Ad-Hoc doesn't. This is perfectly standard. If it wasn't like this your phone would be warm permanen...

The REPL only happens if you don't arrange for something else to happen at startup using a main.py/boot.by so this isn't a real problem. Dealing with the garbage is a combination of esp.osdebug(False) and the hardware tweaks I covered in another post http://forum.micropython.org/viewtopic.php?f=16&t...

I've found exactly the same.

The only low power mode that works, defined as reducing consumption, is deep sleep.

Jon

Or use the NodeMCU flashing tool which just works and knows what you have.

Stick it in a file and do say

import boot_test

For a lighter but really easy check run it on your host platform.

Jon

Done.

Jon

NEW: My first ever pull request has just been accepted

Why do we have to suffer this problem time and time again ? As I have said repeatedly esptool should stop there and then if the file is larger than the size of the flash it (guesses or knows) it is dealing with. Could somebody with the authority to do so please fix esptool ! (I'll have a go at the g...

These things are all very complicated and as such rather incompatible with normal definitions of "basic".

Email is incredibly intricate at the mercy of multiple external servers any of which can drop it. Do not be fooled into thinking you can just do this or that and it'll work properly.

Jon