... | ... | @@ -41,11 +41,11 @@ After the flashing, your FreeDSM should boot for the first time. To perform the |
|
|
|
|
|
# Later ESP32C3-CORE web upgrades procedure
|
|
|
|
|
|
The up to date **firmware.bin** and **autoexec.bec** to perform the upgrade of your FreeDSM are [available here](../home#firmware-releases).
|
|
|
The up-to-date **firmware.bin** and **autoexec.bec** to perform the upgrade of your FreeDSM are [available here](../home#firmware-releases). The FreeDSM will reaint its current configuration after the upgrade.
|
|
|
|
|
|
To perform a complete upgrade of the FreeDSM, it is mandatory to update the Berry script and the firmware (the FreeDSM will maintain the current configuration) if the first two digits do not match (for example, Berry script 2.4.7 is correct for Firmware 2.4 but you must also upgrade the firmware if the current version is 2.3). You can check this version information in the main web page of your device.
|
|
|
To be successful with the complete upgrade of the FreeDSM, it is mandatory to update the Berry script and the firmware if the first two digits of their versions do not match (for example, Berry script 2.4.7 is compatible with Firmware 2.4 but you must also upgrade the firmware if the current version is 2.3). You can check this version information in the main web page of your device.
|
|
|
|
|
|
To perform the update, access to the web interface of your FreeDSM (you can check the IP address in your router or, physically, access to the configuration option of the device, "AP information" will tell you the IP on the LCD screen.
|
|
|
To perform the update, access to the web interface of your FreeDSM (you can check the IP address in your router or, physically, access to the configuration option of the device, "AP information" will tell you the IP on the LCD screen).
|
|
|
|
|
|
- **First, Berry script (file autoexec.bec)**: Main Screen, selecting "Consoles" -> "Manage File System" you will see this screen:
|
|
|
|
... | ... | @@ -53,17 +53,17 @@ To perform the update, access to the web interface of your FreeDSM (you can chec |
|
|
<img src="img/F_upgradeSc.jpg" width="450" align="center"/>
|
|
|
</div>
|
|
|
|
|
|
Select the new "autoexec.bec" using the uppter left button and select "start upload" (it will overwrite the current one).
|
|
|
Select the new "autoexec.bec" using the uppter left button and select "Start upload" (it will overwrite the current one).
|
|
|
|
|
|
- **Second, firmware (file firmware.bin)**: Main Screen, selecting "Firmware Upgrade" you will see this screen:
|
|
|
- **Second, firmware (file firmware.bin)**: Main Screen, select "Firmware Upgrade" and you will see this screen:
|
|
|
|
|
|
<div align="center">
|
|
|
<img src="img/F_upgradeFw.jpg" width="450" align="center"/>
|
|
|
</div>
|
|
|
|
|
|
It is possible to update online (check that the url is:
|
|
|
https://gitlab.citic.udc.es/lia2-publico/g4s/-/wikis/fw/firmware.bin) but it is recommended to download the "firmware.bin" and proceed with "Upgrade by file upload" and press "start upgrade"
|
|
|
https://gitlab.citic.udc.es/lia2-publico/g4s/-/wikis/fw/firmware.bin) but it is recommended to proceed with the previously downloaded "firmware.bin" from this page and proceed with "Upgrade by file upload" and later pressing "Start upgrade".
|
|
|
|
|
|
After that, the FreeDSM will reboot and you will see the version of both in the main screen (Firmware and Script must match the first two numbers in version).
|
|
|
After that, the FreeDSM will reboot and you will see the new version information in the main screen (remember, firmware and script must match in the first two numbers of the version).
|
|
|
|
|
|
If something fails and the FreeDSM boots in SAFEBOOT mode (shown in red on the web interface) simply repeat the process for the firmware flashing. Check that you are using the correct **firmware.bin**, downloaded from this page. |
|
|
If something fails and the FreeDSM boots in **SAFEBOOT** mode (shown in red on the web interface) simply repeat the process for the firmware flashing. Check that you are using the correct **firmware.bin**, downloaded from this page. |