-
Notifications
You must be signed in to change notification settings - Fork 20
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
FNIRSI GC-01: Can’t install #106
Comments
observation 1: observation 2: |
note: the time/date and all settings were preserved all through this. I'm a bit worried now to remove both batteries and do a long-press on the reset button - this used to work on some other devices like motherboards to fully drain any flash but could also brick other devices for good. As I don't have a programmer maybe I should just give up until someone else experiences this behaviour......or not. thanks anyway. |
if I copy the 2.0rc5 file (112kb), then unmount and remount the text file changes to be "UNKNOWN.TXT" 2.0 often said "APPERR.TXT" when remounted after reboot it will say "READY.TXT" it always needs the reset pressed after any connection to turn off the LED and it then boots. |
observations: I give up. |
ok just before i fully give up: official FNIRSI firmware update video looks like WIndows 8 or 10, can anyone confirm they have managed to actually see the drive in Windows 11 23H2 Home or Pro? |
not sure why you just closed this....anyway.... Here is how you install on Ubuntu 22.04 if you have the same issues I had above ie not seen in any Windows versions and copying the .bin does nothing, device shows black screen with constant LED....etc.
viola the GC01 restarts with RadPro 2.0. it's literally that simple, so here's a wee trick that might be worth sharing with others "copy it twice" before going down the programmer/flashing route. observation: for some strange reason it stopped my USB keyboard from working properly even after the GC01 was disconnected, was like a 40-50second lag, mouse, ethernet, hdmi etc were all fine, just the keyboard, reboot sorts it. btw 2.0 seems to work perfectly, I'll try the 2.01 in a few days. |
just to add - changed the tube to J321 from the default J613 great work btw it all really improves the device (will try PC logging next week) thanks @Gissio |
for completion:
live CPM data is displayed as it updates in the graph window data displayed in NotePad: ==== Connect Rad Pro Device ========================================================== ==== Device Mappings =================================================================
|
Hi,
I have the APM version with J321 GM tube and standard screen
When it booted from new it said "ver 1.6" and read a background between 12-18uSv/hr
Windows 11 would not show the drive, USB 2 or 3 Pro or Home version no matter what buttons I tried. Tried on different PCs too, different hubs, ports etc. Device just boots with no drive created no matter what buttons pressed. eg Hold the power button and it boots then powers off.
In Ubuntu 22.04 it shows the BOOTLOADER drive when powered on - on any USB port.
Steps I took:
copied the RadPro 2 (later repeated with 2.01b3) - text file said READY.txt but no reboot, just showed 2 files on the drive.
red LED stays lit and wouldn't boot
removed the cable - also tried unmounting but made no difference
red LED stays lit and wouldn't boot
pressed reset button.
LED goes off but still wouldn't boot but did give BOOTLOADER drive with ERRAPP.txt file each time.
tried 100 different things eg every GC01 firmware, bootloader you shared to try and un-brick it.
sometimes the text in the drive says ERRAPP.txt sometimes it said READY.txt
always stayed constant red LED and required the reset button and a black screen.
LED was constant, longest I left it was 10mins.
copied the 1.6 version from the docs/device/GC01/firmware
2nd time i did this and pulled the cable, then pressed reset it finally booted
it now shows ver 1.6-2 when it boots
and my background readings vary from 16-58uSv/hr now.
I'm stumped!
any help would be appreciated as your firmware looks great but i'm scared I brick it again.
The text was updated successfully, but these errors were encountered: