File System manager constructor.
-At the moment it needs a MicroPython hex string without files included. -Multiple MicroPython images can be provided to generate a Universal Hex.
-MicroPython Intel Hex string or an array of Intel Hex -strings with their respective board IDs.
-Generate a new copy of the MicroPython Intel Hex with the files in the -filesystem included.
-Optional
boardId: numberWhen multiple MicroPython hex files are provided select -one via this argument.
-A new string with MicroPython and the filesystem included.
-Generate a byte array of the MicroPython and filesystem data.
-Optional
boardId: numberWhen multiple MicroPython hex files are provided select -one via this argument.
-A Uint8Array with MicroPython and the filesystem included.
-Read the files included in a MicroPython Universal or Intel Hex string and -add them to this instance.
-MicroPython Intel or Universal Hex string with files.
-A filename list of added files.
-Read the files included in a MicroPython hex string and add them to this -instance.
-MicroPython hex string with files.
-A filename list of added files.
-Read the files included in a MicroPython Universal Hex string and add them -to this instance.
-MicroPython Universal Hex string with files.
-A filename list of added files.
-The Board ID is used to identify the different targets from a Universal Hex.
-In this case the target represents a micro:bit version.
-For micro:bit V1 (v1.3, v1.3B and v1.5) the boardId
is 0x9900
, and for
-V2 0x9903
.
Converts the Python code into the Intel Hex format expected by -MicroPython and injects it into a Intel Hex string containing a marker.
-TODO: Throw error if filesystem is using the penultimate page already.
-Single string of Intel Hex records to inject the code.
-Intel Hex string with the Python code injected.
-Attempts to retrieve the device memory data from an MicroPython Intel Hex -memory map.
-MicroPython Intel Hex memory map to scan.
-Device data.
-Attempts to retrieve the device memory data from an MicroPython Intel Hex.
-MicroPython Intel Hex string.
-Device data.
-A TypeScript library to manipulate the micro:bit MicroPython filesystem.
-The docs can be found in -https://microbit-foundation.github.io/microbit-fs/.
-To add this package to your project:
-npm install @microbit/microbit-fs
-
-
-This software is under the MIT open source license.
- -Trust, partnership, simplicity and passion are our core values we live and -breathe in our daily work life and within our projects. Our open-source -projects are no exception. We have an active community which spans the globe -and we welcome and encourage participation and contributions to our projects -by everyone. We work to foster a positive, open, inclusive and supportive -environment and trust that our community respects the micro:bit code of -conduct. Please see our code of conduct -which outlines our expectations for all those that participate in our -community and details on how to report any concerns and what would happen -should breaches occur.
-This interface represents the data about the device target contained within a -MicroPython hex file.
-This data is stored in different formats depending on the MicroPython port, -V1 uses the UICR location, and V2 uses a table stored in flash.
-Device targeted by this hex file.
-End address for the flash memory.
-Size of a single flash page, in bytes.
-Full flash size in bytes.
-Start address for the flash memory.
-End address in flash where the MicroPython filesystem starts.
-Start address in flash where the MicroPython filesystem starts.
-End address in flash where the MicroPython runtime starts.
-Start address in flash where the MicroPython runtime starts.
-MicroPython version string.
-Options for importing Hex files into a MicropythonFsHex instance.
-Simple interface to pair an Intel Hex string with the board ID it represents.
-Represents the micro:bit Version the hex file targets.
-
Manage filesystem files in one or multiple MicroPython hex files.
-