Gissio / radpro

Custom firmware for Geiger counters/radiation meters (FS2011, Bosean FS-600, FS-1000, FS-5000, FNIRSI GC-01)
MIT License
154 stars 20 forks source link

FNIRSI GC-01: Clock resets, long boot time #73

Closed PsychoBitchy closed 4 months ago

PsychoBitchy commented 4 months ago

Hello. No matter what I try on my FINRSI CH32F

The device boots up just after the flash and is running fine, but if I switch the device off then on again multiple time, at some point ( there is no pattern that I could determine ) the device stays stucked on "Radpro version" screen then blacks out. In that state, not even the power button works. It's in hanged state.

Edit: The device eventually goes back to life, but after a solid 30 seconds or so. I had the impression it was stucked because at some point the boot process is much longer.

I have to reset then reflash to bring it back to life.

Never had a glitch with the stock firmware.

Any ideas?

output_9

PsychoBitchy commented 4 months ago

Edit: The device eventually goes back to life, but after a solid 30 seconds or so. I had the impression it was stucked because at some point the boot process is much longer. Not a bug, closing

Gissio commented 3 months ago

Most likely your CR1220 battery needs replacement!

I've added your issues to the Q&A section of the user's manual.

PsychoBitchy commented 3 months ago

Right, the button battery is indeed flat dead. That will solve the Date/hour resetting issue. But the device with 2.0Rc4 firmware still hangs at some point, I'm not able to replicate consistently. Will report here if changing the Button battery replacement fixes this issue as well.

Gissio commented 3 months ago

It's not actually hung, it's Rad Pro waiting for the microprocessor to start the real-time clock. The CH32 takes quite a while to do that.

Once you replace the battery, it should start right away.

PsychoBitchy commented 3 months ago

Hello, just a small update on this case: Replacing the board backup CR1220 battery indeed fixed every issues I had. Thanks for pointing out and eagle-eye spotting the issue here.