openmano-mpy/esp8266/modules, branch master MicroPython source and hardware configuration for OpenMano ports: Make new ports/ sub-directory and move all ports there. 2017-09-06T03:40:51+00:00 Damien George 2017-09-06T03:40:51+00:00 01dd7804b87d60b2deab16712eccb3b97351a9b7 This is to keep the top-level directory clean, to make it clear what is core and what is a port, and to allow the repository to grow with new ports in a sustainable way. 
This is to keep the top-level directory clean, to make it clear what is
core and what is a port, and to allow the repository to grow with new ports
in a sustainable way.
esp8266: Reinstate 1-wire scripts by sym-linking to drivers/onewire/. 2017-06-22T06:33:20+00:00 Damien George 2017-06-22T06:33:20+00:00 85acf7645f14c4c5ef67238d6e03df1e3eaa8fb5 No changes have been made to the code, the files just moved. 
No changes have been made to the code, the files just moved.
drivers/onewire: Move onewire.py, ds18x20.py from esp8266 to drivers. 2017-06-22T06:28:07+00:00 Damien George 2017-06-22T06:28:07+00:00 a065d786753b83ab92873b90d8d61d9fe5639fdd 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). 
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).
esp8266/modules: Mount filesystem at root when creating for first time. 2017-05-26T07:05:58+00:00 Damien George 2017-05-26T07:05:58+00:00 eea584860dc65203dcae407819c2f139c1f71214 






esp8266/scripts: Move initsetup & port_diag tools to modules/.
2017-05-12T14:58:50+00:00

Paul Sokolovsky

2017-05-12T14:58:50+00:00

ddf0b7dbc3843f2025da5a4cc1b588340c4aad13












esp8266/scripts: Move drivers/modules to modules/ (frozen bytecode).
2017-05-12T14:57:23+00:00

Paul Sokolovsky

2017-05-12T14:57:23+00:00

e9308c189af388525becbcd42b81ea6d37738135












esp8266/modules/flashbdev: Reserve one sector for native code storage.
2017-05-12T13:08:54+00:00

Paul Sokolovsky

2017-05-12T13:08:54+00:00

5f7ce2a1ca65840ef95d0c044088bc38453b7471












esp8266: Change default settings to mount flash at root dir.
2017-05-05T10:15:10+00:00

Damien George

2017-03-10T06:14:21+00:00

e62235f8c755b270e478f403d8ac75c5192847ba












esp8266: Change to use new generic VFS sub-system.
2017-01-27T06:21:45+00:00

Damien George

2017-01-27T04:16:08+00:00

f9ecd484bbd698c0f85a3f40f391afeb01940052

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".





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".







esp8266/modules/flashbdev: Change RESERVED_SECS to 0.
2017-01-06T07:30:55+00:00

Damien George

2017-01-06T07:30:55+00:00

e343bea6e708d69258cd3d771b35d482ae22626b

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 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.