OpenGD77

BTW.

Try the "Patched official version"

https://github.com/rogerclarkmelbourne/ ... d_official

I think perhaps this does not check for the same thing which us causing the "Low bt version"

After you reload the OpenGD77, please try to find another PC and install the CPS etc, because its important for other users to know why you had this problem, so that we can perhaps fix the problem for other people.

The OpenGD77 CPS has a feature to read the MCU ROM, so that we can analyse the problem in your radio.

pipa wrote: ↑

Wed Apr 29, 2020 6:11 am

I have it installed on four PCs with different OS. Win10, 2xWinXP and Win7 and neither works. It always ends with a "Device not found" error.
The MCU ROM in my radio is already overwritten by GD77_patched_bootloader.bin as I wrote above.

OK.

Its strange that the COM port does not work on any PC you tried

Which driver are you using ? (post a link), or is it apart of the CPS install ?

pipa wrote: ↑

Wed Apr 29, 2020 6:11 am

I have it installed on four PCs with different OS. Win10, 2xWinXP and Win7 and neither works. It always ends with a "Device not found" error.
The MCU ROM in my radio is already overwritten by GD77_patched_bootloader.bin as I wrote above.

BTW.

I forgot you reflashed with the patched booloader.

If you have JLink etc there is a way to recreate the missing data.

https://github.com/talentraspel/GD-77/t ... pu-id_calc

But you have to use GDB to read addresses

0x40048054
0x40048058
0x4004805A
0x40048060

And put the data into a hex file first

Which is a bit complicated

Then output from the cpu-id-calc program needs to be flashed to the radio ROM via Jlink at address 0x7F800

pipa wrote: ↑

Wed Apr 29, 2020 7:08 am

Ufff. That's too complicated for me. I'll have to study as soon as I have time. At the moment I don't even know what GDB is ...

No worries

Yes. It us very complicated. We'll need to make a more simple way to do this, but it would need the COM port to be working

programmer error, wouldn't it be better to fix the windowshit localization problem, so that not every non-Englishphone ham has to solve it with some reinstallations and virtual installations and the like?

VK3KYY wrote: ↑

Sun Mar 22, 2020 7:39 am

Connect VTRef to VRef, otherwise there is a message about voltage
Connect the pin SWIO/TMS to the DIO pin
Connect the pin next to it labelled SWCK to the CLK pin
Connect RESET to the RST pin
Connect GND to GND

Sorry I can't remember the exact name of the pads on the PCB, and my board is covered with hot glue over the swd wires to avoid the pads being pulled from the PCB by the weight of the wires

Have you had time to make a video or, to identify the pads on the PCB?

Thank you,
AD7MR

I added an article on my site that details what I did to fix this issue on my Radio and hope it helps someone.
www.w1abq.com

I'll be adding more articles as I go. I literally have 1 day into fixing my radio

Thanks for the help here to get me where I did. I hope my info can help the next guy.

Excellent article.

Just one correction. The Com driver exe is just a general purpose serial driver installer, you need to run it via the .bat file as the bat file runs the exe and species the USB VID / PID numbers in the radio. It also specifies the name of the com port which the CPS searches for so that people don't need to manually select the com port of the radio.

The CPS installer tries to install the driver, but I know in some cases this does not work, And people have to manually re-run the driver installer.

I have three radios with the same defect described here, which I would like try to recover, I have read the posts but the related links do not work, if it is possible I would need the correct file and if it is possible some more info. I have a ST-Link V3, can I use it or do I have to buy a Jlink? Thanks