New ongoing "Development" version has been created

DL2MF
Posts: 3
Joined: Sat Nov 16, 2019 3:26 pm
Location: Germany
Contact:

Re: New ongoing "Development" version has been created

Post by DL2MF » Mon Apr 19, 2021 6:53 pm

Hi Roger & @all contributors,

although not been active for a very long time I'm still remembering the first days of this lovely community project.
When updating my firmware only a few days ago I noticed the latest bad news.

Just want to say a big "Thank you!" for this ambitous and amazing project!

73 Mike, DL2MF

VK3KYY
Posts: 3597
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia
Contact:

Re: New ongoing "Development" version has been created

Post by VK3KYY » Mon Apr 19, 2021 9:02 pm

The source code will be releases as soon as possible, however at the moment I'm having problems getting the last release commit to build.


Under the terms of the Open Source license, it is still not possible for me, or anyone else to publish public releases from the firmware, as the Open Source license requires that all sources to the firmware release be available, and this is not possible because the firmware binary file is 30% from the closed source official firmware.

Perhaps someone intends to write a patching loader, but this would require more work, which I'm not willing to do.

Overall, the mistake with the software license has finally killed the project for me.


I'll attempt to release the firmware in the next 24 hours, depending on how much free time I have to get it to compile.

footloosejava
Posts: 38
Joined: Sun Nov 24, 2019 12:10 pm

Re: New ongoing "Development" version has been created

Post by footloosejava » Tue Apr 20, 2021 6:05 am

DG3GSP wrote:
Sun Apr 18, 2021 7:57 am
Hello Roger,

so maybe a mailinglist would be temporary a assistance - if you decide to continue this incredible project.
If this project continues in an other form or with an other licence - I'd love to support this anymore with translations/testing..

Anyway, i wish to say thank you very much to you and all the other developers for spending so much of your spare time.
YES. ROGER.
THANK YOU
WE ARE GREATLY INDEBTED AND HUMBLED BY YOUR CONTRIBUTION.

VK3KYY
Posts: 3597
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia
Contact:

Re: New ongoing "Development" version has been created

Post by VK3KYY » Tue Apr 20, 2021 6:17 am

The sources from the last beta release have now been committed.

ok1pt
Posts: 99
Joined: Mon Jul 20, 2020 3:38 am

Re: New ongoing "Development" version has been created

Post by ok1pt » Tue Apr 20, 2021 7:21 am

VK3KYY wrote:
Tue Apr 20, 2021 6:17 am
The sources from the last beta release have now been committed.
Hello Roger,
Many thanks ! I just did git pull, started the compile, and... 0 Errors, 0 Warnings... So immediately flashed it, and ... it works!
Extreme thanks to you, I believe that the project can continue its life! Now it's neccessary to find a method, how to allow individual end users to link the binary blobs to pre-compiled image. I have the following idea:
- The image will be compiled as obvious, i.e. with binary blobs, so all the references, addresses etc. will be in place.
- A special "blanking" utility will then replace all the foreign binary code with zeroes. I believe that such utility can be developed easily (I can try it in my free time as well).
- An end user will have to extract the blobs from official FW by the tool, which is already available - I remember that I had to do it to be able to compile the project. It will be neccessary only once.
- Using another special program (again very easily writable), the blobs will be inserted back to the zeroed parts of the sgl file.
- It would be good to publish an MD5 hash of the complete sgl file to allow users to check, whether they patched the distributed blanked image properly.
... and I believe, that all the problems with licensing a file containg foreign code are then ironed out...
With regards & 73
Pavel

VK3KYY
Posts: 3597
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia
Contact:

Re: New ongoing "Development" version has been created

Post by VK3KYY » Tue Apr 20, 2021 7:35 am

ok1pt wrote:
Tue Apr 20, 2021 7:21 am
VK3KYY wrote:
Tue Apr 20, 2021 6:17 am
The sources from the last beta release have now been committed.
Hello Roger,
Many thanks ! I just did git pull, started the compile, and... 0 Errors, 0 Warnings... So immediately flashed it, and ... it works!
Extreme thanks to you, I believe that the project can continue its life! Now it's neccessary to find a method, how to allow individual end users to link the binary blobs to pre-compiled image. I have the following idea:
- The image will be compiled as obvious, i.e. with binary blobs, so all the references, addresses etc. will be in place.
- A special "blanking" utility will then replace all the foreign binary code with zeroes. I believe that such utility can be developed easily (I can try it in my free time as well).
- An end user will have to extract the blobs from official FW by the tool, which is already available - I remember that I had to do it to be able to compile the project. It will be neccessary only once.
- Using another special program (again very easily writable), the blobs will be inserted back to the zeroed parts of the sgl file.
- It would be good to publish an MD5 hash of the complete sgl file to allow users to check, whether they patched the distributed blanked image properly.
... and I believe, that all the problems with licensing a file containg foreign code are then ironed out...
With regards & 73
Pavel
Legally you can't use that official binary as its not available from the Radioddity site.

I'm probably not allowed to have the official firmware in a Github repo and may have to delete it.

You will need to reverse engineer the latest binary and find the location of the codec blocks and then modify the firmware function entry pointers and the linkers to suit that version.
There is no guarantee that the codec block locations in the latest available official firmware would be compatible, if they are overall larger , as you may exceed the MCU rom space

Also you will need to find the encyption key offset used by that firmware and use that to encrypt the firmware, otherwise it won't match the offficial firmware.

And you'll need to update the loader, as it only works for 1 specific encryption key.

Or your loader will need to decrypt 2 different files, and merged then re-encrypt to the key the loader supports.

oh1fss
Posts: 41
Joined: Mon May 04, 2020 11:53 am

Re: New ongoing "Development" version has been created

Post by oh1fss » Tue Apr 20, 2021 7:41 am

ok1pt wrote:
Tue Apr 20, 2021 7:21 am
Many thanks ! I just did git pull, started the compile, and... 0 Errors, 0 Warnings... So immediately flashed it, and ... it works!
Good to hear that!

Many thanks to Roger, it is because of you that I started using OpenGD77! You have done impressive work!

The difference between CB users and radio amateurs is that we want to tinker with the equipment that we use. Therefore I believe that open source is the future of ham radio: WSJT, fldigi, cqrlog, gqrx, quisk, Linux, DIY radios, ...
ok1pt wrote:
Tue Apr 20, 2021 7:21 am
Now it's neccessary to find a method, how to allow individual end users to link the binary blobs to pre-compiled image.
Is it really necessary?

When switching from the official Radioddity firmware to OpenGD77, the bytes of the BLOB should not change at all - providing that the official firmware is of the same version from which the BLOB was originally extracted. So installing the OpenGD77 firmware just copies the same bytes that already are in the radio!

And has anybody really complained about using the BLOB?

VK3KYY
Posts: 3597
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia
Contact:

Re: New ongoing "Development" version has been created

Post by VK3KYY » Tue Apr 20, 2021 8:01 am

oh1fss wrote:
Tue Apr 20, 2021 7:41 am
And has anybody really complained about using the BLOB?

Yes. That was one complaint.

The software license requries you to supply all sources for your release.

You can't pick and choose about the availability of the source code.

Its all or nothing.

oh1fss
Posts: 41
Joined: Mon May 04, 2020 11:53 am

Re: New ongoing "Development" version has been created

Post by oh1fss » Tue Apr 20, 2021 8:16 am

VK3KYY wrote:
Tue Apr 20, 2021 8:01 am
The software license requries you to supply all sources for your release.
But isn't the BLOB a system library? If not, why not? At least it is used like a library, via the wrappers?

And everybody who has the radio already has a copy of it in the flash memory?

http://www.gnu.org/licenses/gpl-faq.htm ... yException

User avatar
YT5HOK
Posts: 167
Joined: Sat Nov 16, 2019 11:36 am
Location: Belgrade, KN04FR

Re: New ongoing "Development" version has been created

Post by YT5HOK » Tue Apr 20, 2021 8:37 am

Leave it alone guys...

Malicious people killed the project.

Main developers are not coming back to OpenGD77.

Respect their decisions.

Say thanks and move on...
Marko

Post Reply