mirror of
https://github.com/sascha-hemi/pycom-documentation.git
synced 2026-03-21 06:06:03 +01:00
updated firmware update page
This commit is contained in:
@@ -18,8 +18,7 @@ aliases:
|
||||
|
||||
## Datasheet
|
||||
|
||||
The datasheet of the LoPy is available as a [PDF File]
|
||||
(/gitbook/assets/specsheets/Pycom_002_Specsheets_LoPy_v2.pdf)
|
||||
The datasheet of the LoPy is available as a [PDF File](/gitbook/assets/specsheets/Pycom_002_Specsheets_LoPy_v2.pdf)
|
||||
|
||||
|
||||
The Lopy is certified for [CE RED](/gitbook/assets/16-213298_expertise_pycom_lopy-1.0r.pdf) and [FCC ACC](/gitbook/assets/2090acc16_grant.pdf") [FCC BCC](/gitbook/assets/2090bcc16_grant.pdf) [FCC CCC](/gitbook/assets/2090ccc16_grant.pdf)
|
||||
|
||||
@@ -23,14 +23,24 @@ The basic firmware upgrade procedure can be found below, please follow these ste
|
||||
|
||||
After you're done with upgrading, you can use the Pymakr Plugins to upload and run programs in your device.
|
||||
|
||||
1. Before connecting your module to a Pysense / Pytrack board, you should update the firmware on the Pysense/Pytrack board. Instructions on how to do this can be found [here](/updatefirmware/expansionboard/).
|
||||
1. Before connecting your module to a Pysense / Pytrack board, you should check for updates of the firmware on the Pysense/Pytrack board. Instructions on how to do this can be found [here](/updatefirmware/expansionboard/).
|
||||
2. Disconnect your device from your computer
|
||||
3. Insert module into Expansion Board
|
||||
3. Insert the module into Expansion Board
|
||||
* On Expansionboard 2.0, connect a jumper cable or wire between `G23` and `GND`
|
||||
4. Reconnect the board via USB to your computer
|
||||
5. Run the Firmware Upgrade tool and click through the menus
|
||||
|
||||

|
||||

|
||||
> Checking 'Include Development Releases' will check for the development releases of the Firmware Updater Tool
|
||||
|
||||
|
||||

|
||||
> Checking 'Show Advanced Settings' will give you the option screen in the next figure.
|
||||
|
||||

|
||||
|
||||
> In some cases, erasing the NVS and CONFIG partitions can solve issues relating to WiFi, Timers or other variables stored in the NVS / CONFIG. Erase during update will remove all Python code on the device.
|
||||
|
||||
|
||||
6. The firmware version of your device is now upgraded to the latest version.
|
||||
* On Expansionboard 2.0, remove the jumper cable.
|
||||
@@ -39,7 +49,7 @@ After you're done with upgrading, you can use the Pymakr Plugins to upload and r
|
||||
|
||||
## Common issues:
|
||||
|
||||
* If you are having any issues, make sure the **TX and RX jumpers** are present on your Expansion Board, as the jumpers sometimes come loose in the box during transport. Without these jumpers, the updater will fail.
|
||||
* If you are having any issues uploading firmware to your device, make sure the **TX and RX jumpers** are present on your Expansion Board, as the jumpers sometimes come loose in the box during transport. Without these jumpers, the updater will fail.
|
||||
* On MacOS, the firmware upgrade tool needs access to the `/tmp` folder
|
||||
* On MacOS, there is an issue with signing of the firmware tool. Go to system preferences --> Security & Privacy --> General, and click "Allow" for the Pycom Firmware Updater tool.
|
||||
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 72 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 28 KiB |
BIN
static/gitbook/assets/firmware_update-0.png
Normal file
BIN
static/gitbook/assets/firmware_update-0.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 92 KiB |
BIN
static/gitbook/assets/firmware_update-1.png
Normal file
BIN
static/gitbook/assets/firmware_update-1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 97 KiB |
BIN
static/gitbook/assets/firmware_update-2.png
Normal file
BIN
static/gitbook/assets/firmware_update-2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 97 KiB |
Reference in New Issue
Block a user