FNIRSI GC-01: Restore

[ChyrkaA]

Please help me restore my FNIRSI GC-01 device

Immediately after the purchase, I wanted to update my device to version 1.6. Downloaded the official firmware from the fnirsi website https://www.fnirsi.com/cdn/shop/files/GC01_V1.6.bin?v=15824974501055980857

I downloaded this file, connected it to a computer with Windows 11 via USB, the computer sees the connected device in the device manager as a USB Mass storage device, but the disk did not appear in Explorer. The same story happened with Windows 10. I inserted it into different ports and different cables - the result was the same.

Then I connected this device to the macBook and miraculously, the disk was mounted. The disk seemed to be 66 kilobytes in size, but the firmware was 64 kilobytes in size. But all the same, the firmware did not want to be copied to the mounted disk of the device and an error occurred that there was not enough space.

The third time, I managed to copy the firmware, ignoring messages about insufficient space. The firmware file has appeared on the device. I disconnected the device and that's it. It didn't turn on any further. I tried to download firmware version 1.6 again, but there was an error about insufficient space.

I tried to upload firmware versions 0.3, 1.5, and even RadPRO - the device still does not turn on. Then I connected the device to a computer with Ubuntu 22.04, the device is displayed, and there is now 85 kilobytes of free space in it. I tried downloading firmware version 1.6 again without any difficulty. But to no avail.

I made different combinations, uploaded the firmware, then pressed Reset, turned on the device with the side button pressed. Nothing helped. The device still doesn’t turn on(((I have a processor on the ch32f10 device. Out of despair, I even tried to upload the firmware from apm. But nothing. I tried to upload the bootloader. Also nothing. The only thing is, after updating the firmware, sometimes the following files appear on the device: errapp.txt, unknown.txt and readme.txt (precisely readme.txt, not ready.txt, like many people on the forums).

I read here that you can upload the firmware once, and then again and overwrite it on the device. But Ubuntu does not allow me to do this, it says that there is not enough space on the device. When I ignore this error, the firmware file, for example, writes only 32 of the required 48 kilobytes.

The charging or connection indicator at the bottom glows red and sometimes green.

Friends, help, I beg you. What should I do? It's a shame about the device(((

[gc01noob]

1. don't press any button when it starts up, just connect it to a Linux like Ubuntu - what's the drive called? mine is "BOOTLOADER". the .txt files are system notifications eg apperr.txt means it failed - keep resetting till is says something like ready.txt
2. you'll find in the repo document folder a 1.6.1 version of the original firmware - this sorted mine when i bricked it many times at first when using Windows - make sure you do a full reset before every attempt and disconnect/reconnect - do not unmount/powercycle, fully remove the cable every time
3. make sure you are using the correct MCU version of the firmware
4. don't be afraid to reset the crap out of it until it complies
5. cables are critical, try every one you own.

seems there might be some non-complaint/maybe-fake versions out there - this is the 2nd this week

I pulled my hair out for days trying different methods and resetting with about 3 different .txt errors before i found that the copy twice/overwrite under Ubuntu GUI worked.
takign notes of everything you try as you try it helps a lot as it's easy to get confused.

if all else fails the STM flasher should be your best option - they're on ebay for around 10$/£

to help Gissio can you post the full specs of your device ie remove the case and post the actual MCU, screen and tube codes

[ChyrkaA]

Thanks for the answer. Below is a photo of the insides of my device. In the second photo the tube is unfolded; the inscription is not visible, but the marking is J321

Now I have connected the device again. Here is the file on it:

In the list of files for my chip, I found only version 1.5 firmware.

I downloaded it and uploaded it to my device. Then I disconnected the device from the cable - the device still did not turn on, I did not touch the reset button. Then I connected the device again and there is this file:

[ChyrkaA]

1. don't press any button when it starts up, just connect it to a Linux like Ubuntu - what's the drive called? mine is "BOOTLOADER". the .txt files are system notifications eg apperr.txt means it failed - keep resetting till is says something like ready.txt
2. you'll find in the repo document folder a 1.6.1 version of the original firmware - this sorted mine when i bricked it many times at first when using Windows - make sure you do a full reset before every attempt and disconnect/reconnect - do not unmount/powercycle, fully remove the cable every time
3. make sure you are using the correct MCU version of the firmware
4. don't be afraid to reset the crap out of it until it complies
5. cables are critical, try every one you own.

seems there might be some non-complaint/maybe-fake versions out there - this is the 2nd this week

I pulled my hair out for days trying different methods and resetting with about 3 different .txt errors before i found that the copy twice/overwrite under Ubuntu GUI worked. takign notes of everything you try as you try it helps a lot as it's easy to get confused.

if all else fails the STM flasher should be your best option - they're on ebay for around 10$/£

to help Gissio can you post the full specs of your device ie remove the case and post the actual MCU, screen and tube codes

Hi. How can I contact Gissio?

[gc01noob]

btw might be worth checking any hidden files on the drive and checking/editing any filenames to ensure they all match/overwrite.
don't touch the .txt it's a system message file and changes to report system status

[gc01noob]

ps. might be readme.txt and not ready.txt to mean it's ok - it's been a while....the other 2 are definitely errors so do a reset if it shows them unti they clear

always disconnect, reset then reconnect before trying anything new and never power it on while pressing any buttons or it will always fail. disk size doesn't report anything meaningful.
also doesn't hurt to reflash the repo 1.6 version between attempts

sorry can't help more, at the end all i needed to do was:
after resetting:

1. connect to Ubuntu with the best cable i had
2. power on
3. drag the .bin file, leave the window open
4. drag the .bin again to the same window
5. ok to overwrite
6. radpro then boots up

[ChyrkaA]

After installing firmware 1.5, when I connect the device to the computer, I need to press the Power button for the device to appear in Ubuntu.

How do you manage to overwrite a file if the remaining free space does not allow you to do so?

[gc01noob]

it doesn't report a correct drive size.
power it on before connecting.

[ChyrkaA]

How can I turn on the device if it does not show any signs of life without connecting to a computer? Or did I understand something wrong?

[gc01noob]

i see you get the "GC01 BOOT" drive....hmmmm same as the chap the other day
mine was the apm MCU and it gives "BOOTLOADER" and dragging twice worked.....

sorry can't help any more than to say keep trying things, maybe Gissio can shed some light on the matter, can take a while till he checks the page but he's knows the devices well.

[ChyrkaA]

Thanks for your time

[gc01noob]

if it says unknown.txt you need to disconnect and reset till it says readme.txt

[ChyrkaA]

Unknown appeared after firmware version 1.5

[gc01noob]

reset and try another one eg 0.3 till it says readme.txt

[ChyrkaA]

0.3 Unknow too((
Just checked

[mressl-itba]

The firmware on FNIRSI's website is for GC-01's with an APM32 microprocessor.

You need to install the firmware for GC-01's with a CH32 microprocessor, which you can get here:

https://github.com/Gissio/radpro/tree/main/docs/devices/FNIRSI%20GC-01/firmware

Unfortunately there isn't anything else I can do to help you.

[ChyrkaA]

The firmware on FNIRSI's website is for GC-01's with an APM32 microprocessor.

You need to install the firmware for GC-01's with a CH32 microprocessor, which you can get here:

https://github.com/Gissio/radpro/tree/main/docs/devices/FNIRSI%20GC-01/firmware

Unfortunately there isn't anything else I can do to help you.

Thanks for the answer. But I wrote above that I uploaded the firmware specifically for my chip

[alfmck]

As I can see from your photo, CH32 from WCH company is used, so you have to use v1.5 file and NOT 1.6 file which is for APM type of processors.
Now, when you killed the soft in your device, try to connect it to win11 or win10 PC and it should be seen on explorer. Then load the 1.5 soft to device.

[alfmck]

Strange. You made a reset by pressing microswitch close to USB connector? Please test the battery or charge it.
As you can connect to explorer of Linux or Mac and upload some files, it seems that downloader in MCU works properly.

[ChyrkaA]

Strange. You made a reset by pressing microswitch close to USB connector? Please test the battery or charge it. As you can connect to explorer of Linux or Mac and upload some files, it seems that downloader in MCU works properly.

Now I checked it with a multimeter. CR1220 battery - 2.77 volts, bad battery - 3.4 volts. Is this enough?

[alfmck]

And charge the main battery too.

[ChyrkaA]

And charge the main battery too.

CR1220 is good? Only main baterry?

[ChyrkaA]

And charge the main battery too.

No, that doesn't work either. I installed a new battery, tried loading different firmware onto the device - all to no avail(

[gc01noob]

fyi the battery condition is critical, you have a bad battery, almost all of them arrive with low batteries that need to be replaced.
sorry I assumed you had checked.
no point continuing or attempting any firmware changes until you have a good battery in there.....

[ChyrkaA]

fyi the battery condition is critical, you have a bad battery, almost all of them arrive with low batteries that need to be replaced. sorry I assumed you had checked. no point continuing or attempting any firmware changes until you have a good battery in there.....

What is the battery itself? CR1220?

[gc01noob]

honest advice to make your life easier: forget Windows, use Linux.

[gc01noob]

battery type should be printed on it but from memory 1220 (that's the size you can measure with calipers) sounds about right, you can get decent ones on ebay for a just few $/£ - make sure the date is a decent date in the future

[ChyrkaA]

battery type should be printed on it but from memory 1220 (that's the size you can measure with calipers) sounds about right, you can get decent ones on ebay for a just few $/£ - make sure the date is a decent date in the future

So I have a CR1220 - am I normal? Or should it be replaced?

[ChyrkaA]

battery type should be printed on it but from memory 1220 (that's the size you can measure with calipers) sounds about right, you can get decent ones on ebay for a just few $/£ - make sure the date is a decent date in the future

No, that doesn't work either. I installed a new battery, tried loading different firmware onto the device - all to no avail(

[gc01noob]

2.7v is bad.

[gc01noob]

forgot to also add: between attempts make sure you fully disconnect the USB cable, then reset, then reconnect. unmounting etc doesn't reset it properly.

to recap: I eventually found that with Ubuntu 22.04 Gnome you just need to disconnect the cable, reset, power on normally, connect the best quality cable you have and the drive will mount....then copy twice to the same window and it boots.
I tried everything and bricked it many times till radpro 2.01 worked and now it's great.

https://github.com/Gissio/geigerlog-radpro is awesome too.

[ChyrkaA]

forgot to also add: between attempts make sure you fully disconnect the USB cable, then reset, then reconnect. unmounting etc doesn't reset it properly.

to recap: I eventually found that with Ubuntu 22.04 Gnome you just need to disconnect the cable, reset, power on normally, connect the best quality cable you have and the drive will mount....then copy twice to the same window and it boots. I tried everything and bricked it many times till radpro 2.01 worked and now it's great.

https://github.com/Gissio/geigerlog-radpro is awesome too.

I don't understand how you could copy the same thing twice if the Ubuntu operating system prevents you from doing so, showing a message that there is not enough space for another, repeated copy.

[gc01noob]

that's the kind of crazy crp that happens with a weak battery or incomplete reset......

[gc01noob]

worst case: https://www.ebay.co.uk/itm/266731227085
and ~40p for some header pins.

[ChyrkaA]

that's the kind of crazy crp that happens with a weak battery or incomplete reset......

No, that doesn't work either. I installed a new battery, tried loading different firmware onto the device - all to no avail(

[Gissio]

ChyrkaA:

It's not right to demand that I answer your question.

Unfortunately there is only one piece of advice I can give you. Get an ST-LINK V2 programmer (clones work quite well) and flash the firmware with it.

Also: there is should be no relationship whatsoever between flashing and battery voltage.

[ChyrkaA]

hwlxqyj2utp53x91

wow! 104 megabytes! now I understand how you manage to copy twice. thanks for the video.

[ricsim]

The square hole by the battery is VCC

I understand that all this needs to be soldered? "The square hole by the battery is VCC" - what did you mean? As for everything else - I understand

If you want to do it right, yes then you solder on a header.
I did it quick and dirty by sticking in breadboard pins, and holding them down while flashing. (do not short, and hold them steady while it is flashing!)
One of the holes is more square that marks VCC. forget it it should be completely obvious without that remark as well.

[ChyrkaA]

The square hole by the battery is VCC

I understand that all this needs to be soldered? "The square hole by the battery is VCC" - what did you mean? As for everything else - I understand

If you want to do it right, yes then you solder on a header. I did it quick and dirty by sticking in breadboard pins, and holding them down while flashing. (do not short, and hold them steady while it is flashing!) One of the holes is more square that marks VCC. forget it it should be completely obvious without that remark as well.

thanks for the answer. ok, then i'm waiting for the programmer itself to arrive. as soon as it's delivered, i'll write to you here, if you don't mind, tell me what to do and what to do

[ricsim]

thanks for the answer. ok, then i'm waiting for the programmer itself to arrive. as soon as it's delivered, i'll write to you here, if you don't mind, tell me what to do and what to do

Absolutely NO need to write here when the programmer is delivered!
Try to flash it, IF you encounter issues, that are not explained in the documentation, and that you cannot resolve elsewere, you could think of writing here.

I am definitely not the right guy to help you, as I also just ordered the programmer for my GC-01s and the Bosean.
I never used it before or after.

Just follow this (and remember that your pinout differs, we already discussed this above, as yours has the pins marked)
https://github.com/Gissio/radpro/blob/main/docs/devices/FNIRSI%20GC-01/install-stlink.md

[ChyrkaA]

thanks for the answer. ok, then i'm waiting for the programmer itself to arrive. as soon as it's delivered, i'll write to you here, if you don't mind, tell me what to do and what to do

Absolutely NO need to write here when the programmer is delivered! Try to flash it, IF you encounter issues, that are not explained in the documentation, and that you cannot resolve elsewere, you could think of writing here.

I am definitely not the right guy to help you, as I also just ordered the programmer for my GC-01s and the Bosean. I never used it before or after.

Just follow this (and remember that your pinout differs, we already discussed this above, as yours has the pins marked) https://github.com/Gissio/radpro/blob/main/docs/devices/FNIRSI%20GC-01/install-stlink.md

Tell me, is my device successfully flashed?

[ChyrkaA]

Tell me, is my device successfully flashed?

[ricsim]

If it rebooted by itself, and is now running Radpro, then yes.
I have no clue about STM programming, but it looks way to short. so i guess it did NOT work.
Try again, and make sure that you follow the guide exactly.

[Gissio]

ChyrkaA: It's looking great: your programmer is talking to the GC-01 microprocessor. This means your GC-01 is about to get revived!

Please hang on a while, as there seems to be an issue with the FNIRSI GC-01 flashtool. I'll let you know when I release an update.

[ChyrkaA]

ChyrkaA: It's looking great: your programmer is talking to the GC-01 microprocessor. This means your GC-01 is about to get revived!

Please hang on a while, as there seems to be an issue with the FNIRSI GC-01 flashtool. I'll let you know when I release an update.

Hello. Thank you for your answer. Okay, I'll wait. Yesterday I checked radpro 2.0.2 - it didn’t work, the device never turned on.

That's why I'm waiting for a new flashtool)) Thank you. You gave me hope!)

[Gissio]

Thanks for waiting. Here goes a test version of the fixed flashtool Use the 2.0.2 v2 flashtool:

https://github.com/Gissio/radpro/releases

Let us know how it worked.

[ChyrkaA]

Thanks for waiting. Here goes a test version of the fixed flashtool:

radpro-flashtool-2.0.2-v2.zip

Let us know how it worked.

Gissio, it works!!! After two weeks, my device finally worked! Thanks a lot! Should I desolder the programmer wires? Or can I leave it in the case? You never know, maybe in the future, it will be necessary to download more firmware. If they don't affect the background in any way, I'd leave it

[Gissio]

I’m glad your counter revived.

It would have been best if you used a 4-pin header instead of soldering the wires directly. But as long as you make sure there is no electrical contact whatsoever, this shouldn’t be a problem.

[ChyrkaA]

I’m glad your counter revived.

It would have been best if you used a 4-pin header instead of soldering the cables directly. But as long as you make sure there is no electrical contact whatsoever, this shouldn’t be a problem.

and there seems to be no electrical contact with the cable that I soldered to the motherboard of the device. so I leave it in the case so as not to solder it again, because I don't have a connector.

how do I subscribe to your GC-01 firmware updates?

do you need a detailed history from me, what I did with the device, from the first failed firmware to how you helped me? maybe this will help you in future developments. and, tell me, why did this happen to me at all? why was the device not flashed by default, like everyone else's)? I'm just wondering what went wrong.

Thank you very much, Gissio, once again. there is a nuance) since my device did not work for a long time, I ordered another one)))))))) now I will have two of them))) the second one will be with the m4011 tube

[Gissio]

Go here https://github.com/Gissio/radpro and click on "Watch".

[ChyrkaA]

People, has anyone tried replacing the battery with an 18630 ​​on the GC-01 device? Is it worth trying, what do you think?