@@ -46,14 +46,14 @@ How to use
46
46
47
47
This assumes that the board declares and defines the relevant SPI flash
48
48
configuration structs, eg in the board-specific bdev.c file. The
49
- ` MBOOT_SPIFLASH2_LAYOUT ` string will be seen by the USB DFU utility and
49
+ ` MBOOT_SPIFLASH_LAYOUT ` string will be seen by the USB DFU utility and
50
50
must describe the SPI flash layout. Note that the number of pages in
51
51
this layout description (the ` 64 ` above) cannot be larger than 99 (it
52
52
must fit in two digits) so the reported page size (the ` 32Kg ` above)
53
53
must be made large enough so the number of pages fits in two digits.
54
54
Alternatively the layout can specify multiple sections like
55
55
` 32*16Kg,32*16Kg ` , in which case ` MBOOT_SPIFLASH_ERASE_BLOCKS_PER_PAGE `
56
- must be changed to ` 16 / 4 ` to match tho ` 16Kg ` value.
56
+ must be changed to ` 16 / 4 ` to match the ` 16Kg ` value.
57
57
58
58
Mboot supports up to two external SPI flash devices. To configure the
59
59
second one use the same configuration names as above but with
@@ -115,6 +115,10 @@ The last element in the data sequence must be the end element:
115
115
116
116
* END: type=1, len=0
117
117
118
+ Note: MicroPython's ` machine.bootloader() ` function performs steps 1-4
119
+ above, and also accepts an optional bytes argument as additional data to
120
+ pass through to Mboot.
121
+
118
122
Loading firmware from a filesystem
119
123
----------------------------------
120
124
@@ -130,6 +134,9 @@ are located and what filename to program. The elements to use are:
130
134
131
135
The firmware to load must be a gzip'd DfuSe file (.dfu.gz).
132
136
137
+ The provided fwupdate.py script contains helper functions to call into Mboot
138
+ with the correct data, and also to update Mboot itself.
139
+
133
140
Example: Mboot on PYBv1.x
134
141
-------------------------
135
142
0 commit comments