Skip to content

Commit d4f518f

Browse files
gijsiopeter-pycom
authored andcommitted
Minor patches
1 parent 67df76c commit d4f518f

File tree

3 files changed

+4
-18
lines changed

3 files changed

+4
-18
lines changed

content/gettingstarted/_index.md

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -120,13 +120,6 @@ Great work, the RGB-LED on your device should now blink in red, green and blue
120120

121121
In the previous section we got code running on on your Pycom module using the `run` feature of Pymakr. This is useful for quick testing but has a couple of drawbacks. Firstly the code does not remain on the device permanently. If you reboot the device, it will no longer be running your code. Secondly, it will only work if you are using libraries built into the firmware. If you need any extra libraries, these need to be copied to the device first. This is where the `upload` feature comes in. If instead of `run` you click `upload`, Pymakr will upload all the files in the project. These then persist on your device even between reboots, and allows you to use libraries from the `lib` folder in your project.
122122

123-
If you need to remove files from your device you can use the following commands:
124-
125-
```python
126-
>>> import os
127-
>>> os.fsformat('/flash')
128-
```
129-
130123
## Step 4: Using your shield
131124
From here on, you can continue to use the additional features of your expansionboard:
132125
>Note The Expansionboard requires no additional libraries and all functions work out of the box!
@@ -139,18 +132,19 @@ From here on, you can continue to use the additional features of your expansionb
139132

140133
|[WiFi](/tutorials/networks/wlan/) | [LoRa](/tutorials/networks/lora/) | [SigFox](/tutorials/networks/sigfox/) | [BLE](/tutorials/networks/ble/) | [LTE](/tutorials.networks/lte/) | Ethernet |
141134
|:---|:---|:---|:---|:---|:---|
135+
142136
## Further references
137+
143138
Now that we got the basic example running, you can continue with the links below.
144139

140+
* [Connect using Pybytes](/pybytes/gettingstarted/)
145141

146142
* [Tutorials and examples](/tutorials/)
147143

148144
* [Firmware API](/firmwareapi/)
149145

150146
* [FTP and Telnet](/gettingstarted/programming/ftp/)
151147

152-
* [Connect using Pybytes](/pybytes/getstarted/)
153-
154148
* [Registering with a network](/gettingstarted/registration/)
155149

156150
* [Updating the firmware of your device](/updatefirmware/)

content/pybytes/api/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ pybytes = Pybytes(conf)
1515

1616
pybytes.start()
1717
```
18-
Or on boot
18+
Or start the connection to Pybytes on boot, this way it's always available:
1919
```python
2020
import pycom
2121
import machine

content/pybytes/gettingstarted.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -63,11 +63,3 @@ After creation, you will land on the provisioning page. This is where we 'inform
6363

6464
You can continue to [display data from your device into the Pybytes dashboard](/pybytes/dashboard/)
6565

66-
## Final remarks
67-
If you wish to disable Pybytes, you can use `pycom.pybytes_on_boot(False)`. It is also possible to start Pybytes in a later stage (not on boot) by importing the module:
68-
```python
69-
from _pybytes import Pybytes
70-
pybytes = Pybytes
71-
```
72-
73-

0 commit comments

Comments
 (0)