| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
No changes have been made to the code, the files just moved.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These drivers can now be used by any port (so long as that port has the
_onewire driver from extmod/modonewire.c).
These drivers replace the existing 1-wire and DS18X20 drivers in the
drivers/onewire directory. The existing ones were pyboard-specific and
not very efficient nor minimal (although the 1-wire driver was written in
pure Python it only worked at large enough CPU frequency).
This commit brings backwards incompatible API changes to the existing
1-wire drivers. User code should be converted to use the new drivers, or
check out the old version of the code and keep a local copy (it should
continue to work unchanged).
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The VFS sub-system supports mounting of an arbitrary number of devices
(limited only by available RAM). The internal flash is now mounted at
"/flash".
|
| |
|
|
|
|
|
|
|
| |
This effectively reverts the change that introduced this new constant.
The reason is so that users do not need to rebuild the filesystem on
their modules when upgrading the firmware.
Users can change RESERVED_SECS by hand if they need the feature, and in
future firmware it may default to a non-zero value.
|
| | |
|
| |
|
|
|
|
|
| |
This code is no longer pertinent for some time - since switchover to
SDK2.0, there must be correct flash size set for bootloader, or there's
a risk of flash data corruption. And indeed, the correct flash size is
by default auto-detected by esptool.py 1.2.
|
| |
|
|
|
|
| |
Starting at esp.flash_user_start(), the reserved sectors are for general
purpose use, for example for native code generation. There is currently
one sector reserved as such.
|
| |
|
|
|
|
| |
websocket_helper.py is used by webrepl. If webrepl is enabled and
websocket_helper.py is not frozen bytecode it leads to heap
fragmentation.
|
| |
|
|
|
|
| |
Previously, it was included only in release builds, but it's important
tool which should be always at the fingertips to be useful (and to
pump up its usage).
|
| | |
|
| |
|
|
|
| |
Following best-practice use of the const feature, to make it compatible
with Python.
|
| | |
|
| |
|
|
|
|
|
|
| |
As we're looking towards adding OTA support, calculation of a FlashROM
area which can be used for filesystem (etc.) may become complex, so
introduce C function for that. So far it just hardcodes current value,
0x90000. In the future the function may be extended (and renamed) to
return the size of area too.
|
| |
|
|
|
| |
Concurrent WebREPL connections were never supported, now actually check
for this.
|
| | |
|
| |
|
|
|
| |
This allows 1-wire drivers (eg DS18X20) to perform in-place operations and
hence do less memory allocations.
|
| |
|
|
|
|
|
|
|
|
| |
The OneWire class is now in its own onewire.py module, and the temperature
sensor class is in its own ds18x20.py module. The latter is renamed to
DS18X20 to reflect the fact that it will support both the "S" and "B"
variants of the device.
These files are moved to the modules/ subdirectory to take advantage of
frozen bytecode.
|
| |
|
|
| |
To accommodate growing firmware.
|
| | |
|
| |
|
|
|
|
|
|
| |
The idea behind decrease is: bytecode and other static data is also kept on
heap, and can easily become half of heap, then setting threshold to half of
heap will have null effect - GC will happen on complete heap exhaustion like
before. But exactly in such config maintaining heap defragmented is very
important, so lower threshold to accommodate that.
|
| |
|
|
|
| |
Should keep good chunk of heap unfragmented, if a user application allows
that at all.
|
| | |
|
| | |
|
| |
|
|
| |
Leads to less fragmentation at teh time user code starts.
|
|
|
To start with, the critical scripts _boot.py and flashbdev.py are frozen
to improve performance and reduce RAM consumption.
Saves about 1000 bytes of heap RAM for a bare boot with filesystem.
|
