| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
Everyone should now be using the new ooFatFs library. The old one is no
longer supported and will be removed.
|
| |
|
| |
|
|
|
|
| |
For polymorphic interfacing on C level.
|
| |
|
|
|
|
|
|
| |
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".
|
|
|
|
| |
And move declaration of mp_fat_vfs_type to this file.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Otherwise, they serve reoccurring source of copy-paste mistakes and
breaking nanbox build.
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Should allow to diagnose/try to recover FS easier.
|
| |
|
| |
|
|
|
|
|
| |
It's pretty rough way to detect yaota8266 being used, but otherwise allows
to have a filesystem in such config.
|
|
|
|
|
| |
Native code can hold pointers to objects on the heap, eg constant objects
like big integers.
|
| |
|
| |
|
|
|
|
|
| |
https://github.com/pfalcon/yaota8266 is a (WIP) OTA-enabled bootloader
which doesn't require reserving space 2x size of a firmware.
|
|
|
|
|
| |
There's no need to force ports to copy-and-paste this initialisation
code. If FSUSERMOUNT is enabled then this zeroing out must be done.
|
|
|
|
| |
With this patch, @micropython.asm_xtensa can be used on the esp8266 port.
|
|
|
|
|
|
|
| |
This patch allows esp8266 to use @micropython.native and
@micropython.viper function decorators. By default the executable machine
code is written to the space at the end of the iram1 region. The user can
call esp.set_native_code_location() to make the code go to flash instead.
|
|
|
|
|
|
| |
The 512k build recently overflowed because of the newly-enabled uselect
module. uselect is arguable more important than framebuf for small
devices so we disable framebuf to keep the 512k build within its limit.
|
| |
|
|
|
|
|
|
| |
So long as a port defines relevant mp_hal_pin_xxx functions (and delay) it
can make use of this software SPI class without the need for additional
code.
|
|
|
|
|
|
| |
websocket_helper.py is used by webrepl. If webrepl is enabled and
websocket_helper.py is not frozen bytecode it leads to heap
fragmentation.
|
|
|
|
| |
Select and poll will now work on socket objects.
|
| |
|
|
|
|
|
|
| |
If a port defines MICROPY_READER_POSIX or MICROPY_READER_FATFS then
lexer.c now provides an implementation of mp_lexer_new_from_file using
the mp_reader_new_file function.
|
|
|
|
|
|
|
| |
Implementations of persistent-code reader are provided for POSIX systems
and systems using FatFS. Macros to use these are MICROPY_READER_POSIX and
MICROPY_READER_FATFS respectively. If an alternative implementation is
needed then a port can define the function mp_reader_new_file.
|
| |
|
|
|
|
|
|
| |
Its addition was due to an early exploration on how to add CPython-like
stream interface. It's clear that it's not needed and just takes up
bytes in all ports.
|
| |
|
|
|
|
|
|
|
| |
The ESP SDK supports configuring the hostname that is
reported when doing a DHCP request in station mode. This commit
exposes that under network.WLAN(network.STA_IF).config('dhcp_hostname')
as a read/write value similar to other parameters.
|
|
|
|
|
|
| |
Now, to use frozen bytecode all a port needs to do is define
FROZEN_MPY_DIR to the directory containing the .py files to freeze, and
define MICROPY_MODULE_FROZEN_MPY and MICROPY_QSTR_EXTRA_POOL.
|
| |
|
|
|
|
|
|
| |
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).
|
|
|
|
|
|
|
|
| |
At the WS2812 driver level, a 400ns value was used for T0H (time high to
send a 0 bit) but LED specification says it should be 350ns +- 150ns.
Due to loop overhead the 400ns value could lead to T0H close to 500ns
which is too close from the limit value and gave glitches (bad data to
pixels) in some cases. This patch makes the calculated T0H value 350ns.
|
| |
|
|
|
|
|
|
|
| |
Previously they used historical "pyb" affix causing confusion and
inconsistency (there's no "pyb" module in modern ports; but people
took esp8266 port as an example, and "pyb" naming kept proliferating,
while other people complained that source structure is not clear).
|
|
|
|
|
| |
Following best-practice use of the const feature, to make it compatible
with Python.
|
| |
|