Skip to content

Commit b1be839

Browse files
committed
add micropython link
1 parent 4285ec5 commit b1be839

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

docs/vscode/migrating.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,12 @@ The web-based Wokwi simulator is a powerful and well-integrated way to try out y
1111

1212
This checklist of steps should help you overcome the most common issues. It is assumed that you have already installed the VS Code extension for Wokwi (see the [Getting started guide](./getting-started)).
1313

14+
:::tip
15+
16+
Using **MicroPython**? The setup for MicroPython projects is quite different - please see the [Vs Code for MicroPython page](vscode-micropython.md).
17+
:::
18+
19+
1420
## Download the project source
1521

1622
To start, the first step is to save your online project. From the same menu, under the save button, you can then select to download a `.zip` archive of the project. This will contain useful files such as any source code and the `diagram.json` file used by Wokwi.
@@ -24,7 +30,7 @@ This step will create a boilerplate project in a working state, ready to add you
2430

2531
## Add the source
2632

27-
Depending on the complexity of your project, adding the source should be quite straightforward.
33+
Depending on the complexity of your project, adding the source should be quite straightforward.
2834

2935
<Tabs>
3036
<TabItem value="pio" label="PlatformIO" default>
@@ -97,6 +103,9 @@ Depending on the complexity of your project, adding the source should be quite s
97103

98104
All of the source files should go in `main.c`. If you have multiple source files, you should also update the `CMakelists.txt` file in the same directory to include any other files which need to be built.
99105

106+
</TabItem>
107+
<TabItem value="Zephyr" label="Zephyr">
108+
100109
</TabItem>
101110
</Tabs>
102111

0 commit comments

Comments
 (0)