jacob.eva/RNode_Firmware_CE
1
0
Fork 0
mirror of https://github.com/liberatedsystems/RNode_Firmware_CE.git synced 2024-07-02 14:34:13 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add FAQ question for v1.72 upgrade upstream

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

6
Documentation/FAQ.md
View File

@ -4,5 +4,11 @@ Yes! Feel free to use the firmware in this repository for your produced RNodes.
It is also likely worth you reading [this material from Mark Qvist](https://unsigned.io/sell_rnodes.html). Do consider donating to him if your venture is successful, without him this project would simply be a schizo fever dream. It is also likely worth you reading [this material from Mark Qvist](https://unsigned.io/sell_rnodes.html). Do consider donating to him if your venture is successful, without him this project would simply be a schizo fever dream.
## Why does my RAK4631 not work after upgrading from v1.71 to v1.72 upstream?
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
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`.
## Write a hecking code of conduct!! ## Write a hecking code of conduct!!
no no