openmano-mpy/docs/reference, branch master MicroPython source and hardware configuration for OpenMano tools: Add filesystem action examples to pyboard.py help. 2021-02-13T03:37:28+00:00 Brianna Laugher 2021-02-12T11:15:43+00:00 d128999938d6b44f52f4d0c6e1f5169ab3c1e7a5 Signed-off-by: Brianna Laugher <brianna.laugher@gmail.com> 
Signed-off-by: Brianna Laugher <brianna.laugher@gmail.com>
docs/reference/repl.rst: Add information about new raw-paste mode. 2020-12-01T11:35:13+00:00 Damien George 2020-11-30T00:34:23+00:00 a14ca31e8579a07f263bca0dd4b0dd03f43befa2 Signed-off-by: Damien George <damien@micropython.org> 
Signed-off-by: Damien George <damien@micropython.org>
docs/reference/glossary.rst: Fix minor grammar error, An -> A. 2020-10-22T04:40:11+00:00 Kevin Thomas 2020-10-03T12:35:41+00:00 6eebdbc495a52d1965d7e9255816db310041f96a 






docs/reference/packages.rst: Fix typo, remove duplicate "port".
2020-09-30T13:32:24+00:00

David Lechner

2020-09-25T15:47:59+00:00

ee7568ca8d4f1a5d09a123cf5f7a1e430b8f4c9d

Fixes #6485.





Fixes #6485.







docs: Fix Sphinx 3.x warnings, and enable warnings-as-errors on build.
2020-06-05T11:42:17+00:00

David Lechner

2020-06-04T01:38:45+00:00

1e6d18c915ccea0b6a19ffec9710d33dd7e5f866

This enables warnings as errors and fixes all current errors, namely:

- reference to terms in the glossary must now be explicit (:term:)
- method overloads must not be declared as a separate method or must
  use :noindex:
- 2 cases where `` should have been used instead of `





This enables warnings as errors and fixes all current errors, namely:

- reference to terms in the glossary must now be explicit (:term:)
- method overloads must not be declared as a separate method or must
  use :noindex:
- 2 cases where `` should have been used instead of `







docs/reference: Add note about multiple exceptions when heap is locked.
2020-06-02T05:56:34+00:00

Andrew Leech

2020-06-01T06:16:25+00:00

e54626f4c1b5cb4de0b5dc86d820bb36c1d6499f












esp8266: Change from FAT to littlefs v2 as default filesystem.
2020-04-04T05:30:36+00:00

Damien George

2020-03-26T11:35:32+00:00

e0905e85a7ad2961aa9192f6130565860e531ad3

This commit changes the esp8266 boards to use littlefs v2 as the
filesystem, rather than FAT.  Since the esp8266 doesn't expose the
filesystem to the PC over USB there's no strong reason to keep it as FAT.
Littlefs is smaller in code size, is more efficient in use of flash to
store data, is resilient over power failure, and using it saves about 4k of
heap RAM, which can now be used for other things.

This is a backwards incompatible change because all existing esp8266 boards
will need to update their filesystem after installing new firmware (eg
backup old files, install firmware, restore files to new filesystem).

As part of this commit the memory layout of the default board (GENERIC) has
changed.  It now allocates all 1M of memory-mapped flash to the firmware,
so the filesystem area starts at the 2M point.  This is done to allow more
frozen bytecode to be stored in the 1M of memory-mapped flash.  This
requires an esp8266 module with 2M or more of flash to work, so a new board
called GENERIC_1M is added which has the old memory-mapping (but still
changed to use littlefs for the filesystem).

In summary there are now 3 esp8266 board definitions:
- GENERIC_512K: for 512k modules, doesn't have a filesystem.
- GENERIC_1M: for 1M modules, 572k for firmware+frozen code, 396k for
  filesystem (littlefs).
- GENERIC: for 2M (or greater) modules, 968k for firmware+frozen code,
  1M+ for filesystem (littlefs), FAT driver also included in firmware for
  use on, eg, external SD cards.





This commit changes the esp8266 boards to use littlefs v2 as the
filesystem, rather than FAT.  Since the esp8266 doesn't expose the
filesystem to the PC over USB there's no strong reason to keep it as FAT.
Littlefs is smaller in code size, is more efficient in use of flash to
store data, is resilient over power failure, and using it saves about 4k of
heap RAM, which can now be used for other things.

This is a backwards incompatible change because all existing esp8266 boards
will need to update their filesystem after installing new firmware (eg
backup old files, install firmware, restore files to new filesystem).

As part of this commit the memory layout of the default board (GENERIC) has
changed.  It now allocates all 1M of memory-mapped flash to the firmware,
so the filesystem area starts at the 2M point.  This is done to allow more
frozen bytecode to be stored in the 1M of memory-mapped flash.  This
requires an esp8266 module with 2M or more of flash to work, so a new board
called GENERIC_1M is added which has the old memory-mapping (but still
changed to use littlefs for the filesystem).

In summary there are now 3 esp8266 board definitions:
- GENERIC_512K: for 512k modules, doesn't have a filesystem.
- GENERIC_1M: for 1M modules, 572k for firmware+frozen code, 396k for
  filesystem (littlefs).
- GENERIC: for 2M (or greater) modules, 968k for firmware+frozen code,
  1M+ for filesystem (littlefs), FAT driver also included in firmware for
  use on, eg, external SD cards.







tools/pyboard.py: Add -d as an alias for --device.
2020-03-30T00:37:32+00:00

Lars Kellogg-Stedman

2020-03-25T17:31:18+00:00

3a0f64fc7aafe9fa39f518aec389ef5f55b40007












tools/pyboard.py: Support setting device/baudrate from shell env vars.
2020-03-30T00:37:32+00:00

Lars Kellogg-Stedman

2020-03-25T17:23:01+00:00

1cf994c48b912254802f48e31eaf95e49ac55a82

Allow defaults for --device and --baudrate to be set in the environment
using PYBOARD_DEVICE and PYBOARD_BAUDRATE.





Allow defaults for --device and --baudrate to be set in the environment
using PYBOARD_DEVICE and PYBOARD_BAUDRATE.







docs: More consistent capitalization and use of articles in headings.
2020-01-06T11:17:29+00:00

Jason Neal

2020-01-01T11:51:42+00:00

aec88ddf0326187c567d4e4507149fb7c54ba91d

See issue #3188.





See issue #3188.