-
-
Notifications
You must be signed in to change notification settings - Fork 614
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After power cycle all settings are reset to default #777
Comments
On Portapack H2+ I cannot reproduce this issue on 1.6.0, the settings are saved. I had this problem, but it seems that the backup battery was dead (CR1220). I have a green HackRF clone with Portapack H2+ (the one with Li-Ion battery). I also followed the above steps listed by @Radiomix2000 . |
Hi @Radiomix2000 , And I could confirm that this problem started to appear after the merge of that PR #662 (May 28th) . Any local compiled binary prior to that PR#662 works well . You can try 1.5.3 and i presume that it should work well , but I guess that you will face that problem from 1.5.4 onwards. Pls try and let us know about it. My theory or guess , is that, this PR #662 is using some access to the SD card or internal persistent ram (to handle the persistent memory) with some access timing in the limit of the spec timings , and just adding some different compiled additional or fast CPU instructions or different HW tolerances (as your unit ) it will not work . Or maybe also related to some particular SD card or a tolerance combination ..., I have pending to bisect it and find out which is the critical code part , and try to solve it adding some additional delays or any other workaround . (But not done , because I always try to work with the latest official nightly (that works well to my units) Pls let us know that your set is ok with 1.5.3 or previous , and NG from 1.5.4 onwards . |
So I figured out the problem. The backup battery is really ok. BUT I had a hardware malfunction on PCB. The battery slot wasn't properly soldered. So after repair I checked firmwares 1.5.3 and the latest Night Build. Everything works good. |
Ok , @Radiomix2000 glad to see that you solved the problem . I was also thinking that other reason could be the cell battery discharge status , but as you indicated that it had a correct voltage I did not mentioned . |
Are not app configs stored to the sd card? a battery should not be needed right? |
Hi @pinarruiz , there are many data , like scanner frequency list , captured or Replay file.C16 data , captured AIS raw frames ,...that are stored in SD card . But in general the user Config App settings, are stored in "persistent ram memory " that needs to get also power supply from the RTC battery button cell . (It is also indicated in the wiki) |
I think there was some attempts to move everything (or make it an option) to the sd, but nobody has completed this task |
Thanks @Brumi-2021 and @eried did not read that parto on the wiki, i will include an rtc battery on it |
(Please try the latest nightly release before submitting this. You can find the latest nightly verison here: https://github.com/eried/portapack-mayhem/releases)
Describe the bug
After power cycle all settings are reset to default.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
All settings are saved after power cycle.
Affected versions
Portapack H1 hackRF
Please write any difference related with the Expected behavior, on the following versions:
Additional
The "save and load app settings" menu don't change the behavior of the bug.
The backup RTC battery on portpack PCB is checked - ok.
The text was updated successfully, but these errors were encountered: