Skip to content

Commit 38a16e5

Browse files
committed
Adding more docs.
1 parent ace905b commit 38a16e5

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

README.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ For MicroPython development we use a slightly modified version of the [`HDMI2USB
2020
(x) cd litex
2121
(x) Download prebuilt gateware + headers using `get-gateware.sh`
2222
(x) Compile micropython
23-
(x) Build flash image
23+
(x) Load micropython
2424

2525

2626
### Developing in HDMI2USB LiteX environment
@@ -31,14 +31,17 @@ For MicroPython development we use a slightly modified version of the [`HDMI2USB
3131

3232
(3) Set PLATFORM and TARGET correctly - IE "export PLATFORM=mimasv2" if using the MimasV2
3333

34-
(4) Run ./scripts/build-micropython.sh
34+
(4) Build the gateware with `make gateware`
35+
36+
(5) Run ./scripts/build-micropython.sh
3537

3638
This will give you an image for your target at `./build/$PLATFORM_$TARGET_lm32/micropython.bin` which you can then flash to your board.
3739

3840
#### Running MicroPython inside QEmu environment
3941

40-
The HDMI2USB LiteX environment provides some limited QEmu emulation of the FPGA gateware. This means you can test your code without needing hardware.
42+
The HDMI2USB LiteX environment provides some limited QEmu emulation of the FPGA gateware, this means you can test your code without needing hardware.
4143

44+
It can be used with the MicroPython image by running `./scripts/build-qemu.sh` and then replacing `-kernel qemu.bin` with `-kernel micropython.bin` in the last command.
4245

4346
## More Information
4447

0 commit comments

Comments
 (0)