As per #810 & #796, only LUA_OPTIMIZE_MEMORY=2 & MIN_OPT_LEVEL=2 are
supported when building. This commit effects that limitation.
With this change modules/auxmods.h no longer needs to be updated for
every new module, nor do module writers need to cater for a hypothetical
LUA_OPTIMIZE_MEMORY < 2 scenario.
* Remove the "0.9.6; deprecated" comment regarding the master branch
* Add a paragraph on enabling debugging
* Clarify (I hope) the conditions under which you need to reformat your flash filesystem.
* Remove trailing blanks
Signed-off-by: Nick Andrew <nick@nick-andrew.net>
Based on @vowstar edits:
* Note that the SDK is the NONOS one
* Add links for NodeMCU devkit v1.0 and distinguish from v0.9
* Remove the ToDo list (as all are complete but for 1 item)
When lua assertions are enabled, normal operation results in many:
lobject.c:88: (((t1)->tt) == 4)
lobject.c:88: (((t2)->tt) == 4)
lobject.c:88: (((t1)->tt) == 4)
lobject.c:88: (((t2)->tt) == 4)
lobject.c:88: (((t1)->tt) == 4)
lobject.c:88: (((t2)->tt) == 4)
It comes from using the pvalue() macro for 3 pointer types, where
pvalue() also checks the type of pointer and complains through the
assertion where the type == 4 (TLIGHTUSERDATA).
Use the correct macro according to the type of data being compared
to eliminate this assertion error.
Signed-off-by: Nick Andrew <nick@nick-andrew.net>
Master contained two OW changes one of which was already reimplemented in dev using the
correct macros. The second was from hazarkarabay (f6d0c0c) that onewire_search()
returns a device address vector even when no device is found. I've reimplemented this
but using the correct index, rom_byte_number, rather than declaring a new temp index i.
List the latest set of modules in the example on disabling modules.
Show which file to edit to tag your firmware to identify it on boot.
Signed-off-by: Nick Andrew <nick@nick-andrew.net>
Put Marcel's online build server first, as this will be the go-to for
new users. Note that they should build 'dev' not 'master'.
Next, list the docker image which will build from your checked-out
repository and possibly including your own changes.
Finally, list the prerequisites if you want to build it all yourself,
including the sequence of commands (same as the docker image uses).
Signed-off-by: Nick Andrew <nick@nick-andrew.net>
The README is presently quite unreadable. The simpler examples of
programming an already-flashed ESP8266 are moved up, to give the
new user the flavor of what is possible with NodeMCU.
Instructions to build the firmware will follow.
Signed-off-by: Nick Andrew <nick@nick-andrew.net>
TerryE
Johny Mattsson
Marcel Stör
Nick Andrew
Vowstar
Johny Mattsson
Marcel Stör
btsimonh
Arnim Läuger
Ivan Lopez
Johny Mattsson