- 05 Apr, 2019 1 commit
-
-
Terry Ellison authored
* Rebaseline firmware to non-OS SDK version 3.0 * Note that SDK version 3.0 introduces the concept of a Flash Partition Table(PT). This is located at Flash offset 0x10000 in our firmware build. * The firmware is now PT aware with both LFS and SPIFFS taking their partition size and location from the PT * A new tool `tools/nodemcu-partition.py` is now used to initialise these data and can also download LFS and SPIFFS images to these partitions.
-
- 22 Jun, 2018 1 commit
-
-
TerryE authored
-
- 16 May, 2017 1 commit
-
-
Arnim Läuger authored
* align 8MB and 16MB auto flash support with sdk 2.1.0 * remove SAFE_API * fix flash size mismatch detection logic
-
- 26 Dec, 2016 1 commit
-
-
Arnim Läuger authored
-
- 26 Jun, 2016 1 commit
-
-
moononournation authored
* update esptool.py to v1.2-dev * add 64 Mbit and 128 Mbit support
-
- 18 May, 2016 1 commit
-
-
Johny Mattsson authored
- Stop fighting against the SDK in terms of owning/writing the init_data block. NodeMCU included a default init_data block because originally the SDK did not, but by now it's not needed. - Expose a way to reconfigure the ADC mode from Lua land. With most people using the cloud builder and not able to change the #define for byte 107 this has been a pain point. - Less confusion about which init_data has been used. Lua code can now simply state what mode it wants the ADC to be in, and not worry about the rest of the init_data complexities such as the init_data changing location due to flashing with wrong flash_size setting, or doing/not doing a chip-erase before loading new NodeMCU firmware.
-
- 23 Feb, 2016 1 commit
-
-
dnc40085 authored
esp_init_data_default.bin in SDK 1.51
-
- 22 Jan, 2016 1 commit
-
-
devsaurus authored
-
- 30 Dec, 2015 1 commit
-
-
Huang Rui authored
-
- 12 Dec, 2015 1 commit
-
-
Johny Mattsson authored
There was only one genuine use of this macro, all other places were using it only as a necessary compensation. While this was fine as long as it was the first meg of flash which was mapped, it became incorrect and quite dangerous whenever this assumption did not hold (such as when running from the second slot in an OTA scenario). The flash API now uses actual addresses, not translated/mapped addresses, and the users of this API have been adjusted accordingly. This makes the flash API work correctly regardless of what flash mapping is in use. The old macro is still available under the new name INTERNAL_FLASH_MAPPED_ADDRESS, and this is used to detect flash writes where the source is mapped flash (and thus has to be bounced), and to adjust the _flash_used_end linker symbol when used with flassh_find_sector() by the filesystem code. The latter usage is not OTA-proof, but in an OTA scenario the filesystem needs a fixed location anyway and thus would not use this code path.
-
- 12 Nov, 2015 1 commit
-
-
Johny Mattsson authored
Make ADC vs readvdd33 option user_config.h configurable for the init data, and made readvdd33 the default.
-
- 29 May, 2015 1 commit
-
-
dnc40085 authored
-
- 21 May, 2015 1 commit
-
-
HuangRui authored
-
- 05 May, 2015 1 commit
-
-
Vowstar authored
-
- 24 Mar, 2015 1 commit
-
-
funshine authored
-
- 22 Mar, 2015 1 commit
-
-
funshine authored
-
- 15 Mar, 2015 3 commits
- 14 Feb, 2015 2 commits
- 11 Feb, 2015 1 commit
-
-
HuangRui authored
-
- 06 Jan, 2015 2 commits
- 05 Jan, 2015 4 commits
- 02 Jan, 2015 1 commit
-
-
HuangRui authored
-
- 31 Dec, 2014 3 commits
- 30 Dec, 2014 2 commits