jacob.eva/opencom_xl_firmware
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add more detail

Browse Source
This commit is contained in:
jacob.eva 2024-05-27 17:53:09 +01:00
parent 493efc50fc
commit 6fe93feb9e
No known key found for this signature in database
GPG Key ID: 0B92E083BBCCAA1E
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/FAQ.md
View File

@ -8,7 +8,7 @@ It is also likely worth you reading [this material from Mark Qvist](https://unsi
The size of the expected EEPROM file changed between these two releases. In my in(finite) wisdom, I forgot to mention that upgrading between these versions would require a format of the user data flash sector on the RAK4631 so that the file can be recreated. The size of the expected EEPROM file changed between these two releases. In my in(finite) wisdom, I forgot to mention that upgrading between these versions would require a format of the user data flash sector on the RAK4631 so that the file can be recreated.
### Fix ### Fix
It can be fixed easily by running [this sketch](https://github.com/RAKWireless/RAK-nRF52-Arduino/blob/master/libraries/InternalFileSytem/examples/Internal_Format/Internal_Format.ino). Then, reprovision your EEPROM. For example, this can be done by using `rnodeconf -a`. It can be fixed easily by running [this sketch](https://github.com/RAKWireless/RAK-nRF52-Arduino/blob/master/libraries/InternalFileSytem/examples/Internal_Format/Internal_Format.ino) (you must open the serial monitor and press enter for it to actually format the flash). Then, reprovision your EEPROM. For example, this can be done by using `rnodeconf -a`.
## Write a hecking code of conduct!! ## Write a hecking code of conduct!!
no no