G2 Updated files and simplified update procedure
Re: G2 Updated files and simplified update procedure
@w-u-2-o
@KC2QMA
It was recently discovered that the Open Collector outputs were not as previously
documented. This only affects the G2.
Old pin assignment: New pin assignment: Updated G2 Manual:
[url]https://apache-labs.com/download_file.php?downloads_id=1023[/url]
@KC2QMA
It was recently discovered that the Open Collector outputs were not as previously
documented. This only affects the G2.
Old pin assignment: New pin assignment: Updated G2 Manual:
[url]https://apache-labs.com/download_file.php?downloads_id=1023[/url]
Re: G2 Updated files and simplified update procedure
So I need to figure out and re-map the pin assignments in Thetis Or make a new cable?
I see even the darn Ground pin is different!
Just want to make sure i understand.
I see even the darn Ground pin is different!
Just want to make sure i understand.
Re: G2 Updated files and simplified update procedure
I would probably re-make my cable.
As for your pihpsdr issue, can you try typing in, and post back the output
of those commands?
cd ~/github/pihpsdr
make clean
git remote -v
git pull
make
ls -l
As for your pihpsdr issue, can you try typing in, and post back the output
of those commands?
cd ~/github/pihpsdr
make clean
git remote -v
git pull
make
ls -l
Re: G2 Updated files and simplified update procedure
Wown1gp wrote:
It was recently discovered that the Open Collector outputs were not as previously
documented. This only affects the G2.

Rick--if you would please make a separate, dedicated post in the G2 forum that describes this then I will make sure it becomes a tacked/sticky post for everyone to easily reference.
Has this been reflected in the G2 documentation?
Re: G2 Updated files and simplified update procedure
w-u-2-o wrote:Wow. Can't believe Apache made that mistaken1gp wrote:
It was recently discovered that the Open Collector outputs were not as previously
documented. This only affects the G2.![]()
Rick--if you would please make a separate, dedicated post in the G2 forum that describes this then I will make sure it becomes a tacked/sticky post for everyone to easily reference.
Has this been reflected in the G2 documentation?
Re: G2 Updated files and simplified update procedure
@w-u-2-o
Scott, I posted an update in the G2 forum.
Scott, I posted an update in the G2 forum.
Ya, there's also a link in it to the updated G2 manual.Has this been reflected in the G2 documentation?
Re: G2 Updated files and simplified update procedure
Good thing I didn't blow up my amp! 

Re: G2 Updated files and simplified update procedure
New Title for Post:
"G2 Updated files and NOT simple update procedures"
"G2 Updated files and NOT simple update procedures"

-
- Posts: 305
- Joined: Mon Nov 11, 2019 7:39 pm
Re: G2 Updated files and simplified update procedure
I have modified the G2 update script, incorporating KD4YAL's improvements - thank you. It also checks for libraries that need to be installed.
cd ~/github/Saturn/scripts
./update-G2.sh
cd ~/github/Saturn/scripts
./update-G2.sh
Laurence Barker G8NJJ
Re: G2 Updated files and simplified update procedure
Here is a second revision of my G2 update script, The Bash script is designed to streamline the update and build processes for the "G2" project by providing a menu-driven interface. Key features include:
Menu-Driven Interface: Utilizes whiptail to present users with a text-based menu, allowing selection of various update and build tasks.
Modular Functions: Defines specific functions for tasks such as updating system libraries, pulling the latest code from the Git repository, building applications, installing device rules, copying desktop icons, verifying FPGA BIT files, and building the pihpsdr application.
Error Handling: Incorporates a check_status function to provide feedback on the success or failure of each operation, enhancing debugging and user awareness.
Git Integration: Includes functionality to update the Git repository and retrieve the current commit hash, ensuring the latest code is in use.
Build Automation: Automates the build processes for both p2app and desktop applications, reducing manual intervention.
System Configuration: Offers options to install udev rules and copy desktop icons, facilitating system setup and configuration.
Comprehensive Updates: Provides an option to perform all tasks sequentially, enabling a complete system update with minimal user input.
This script enhances efficiency by automating routine tasks and offering a user-friendly interface for managing the project's update and build processes. Could use a little more work but seems to be a good framework.
Enjoy 73 Jerry KD4YAL
Menu-Driven Interface: Utilizes whiptail to present users with a text-based menu, allowing selection of various update and build tasks.
Modular Functions: Defines specific functions for tasks such as updating system libraries, pulling the latest code from the Git repository, building applications, installing device rules, copying desktop icons, verifying FPGA BIT files, and building the pihpsdr application.
Error Handling: Incorporates a check_status function to provide feedback on the success or failure of each operation, enhancing debugging and user awareness.
Git Integration: Includes functionality to update the Git repository and retrieve the current commit hash, ensuring the latest code is in use.
Build Automation: Automates the build processes for both p2app and desktop applications, reducing manual intervention.
System Configuration: Offers options to install udev rules and copy desktop icons, facilitating system setup and configuration.
Comprehensive Updates: Provides an option to perform all tasks sequentially, enabling a complete system update with minimal user input.
This script enhances efficiency by automating routine tasks and offering a user-friendly interface for managing the project's update and build processes. Could use a little more work but seems to be a good framework.
Enjoy 73 Jerry KD4YAL
- Attachments
-
- update-G2-menu.sh.txt
- (6.97 KiB) Downloaded 346 times
Re: G2 Updated files and simplified update procedure
Now were finally getting to a "Simplified Update Procedure"
Thank You Jerry KD4YAL for your work on the install script !
When you buy a new car at the dealer, they don't also expect the customer to also be a auto mechanic
Thank You Jerry KD4YAL for your work on the install script !
When you buy a new car at the dealer, they don't also expect the customer to also be a auto mechanic

Re: G2 Updated files and simplified update procedure
Hi John (KC2QMA),
Keep in mind other manufacturers aren't opening their software to the world.
I don't mind putting in a little time to help improve the product. This is the
idea behind open-source software.
The end result, you will have a hot rod instead of a factory car like everyone else.
Jerry, KD4YAL
Keep in mind other manufacturers aren't opening their software to the world.
I don't mind putting in a little time to help improve the product. This is the
idea behind open-source software.
The end result, you will have a hot rod instead of a factory car like everyone else.
Jerry, KD4YAL
Re: G2 P2APP Updated files and simplified update procedure
Hello,
Has anyone successfully updated P2APP a G2 Ultra with an 8 inch display?
My terminal comes up: pi@raspberrypi:~ $
Attempting to change to the root directory as a YouTube video suggests, cd ~ prior to the github update script does not work.
Thanks,
Greg
Has anyone successfully updated P2APP a G2 Ultra with an 8 inch display?
My terminal comes up: pi@raspberrypi:~ $
Attempting to change to the root directory as a YouTube video suggests, cd ~ prior to the github update script does not work.
Thanks,
Greg
Re: G2 Updated files and simplified update procedure
That is the correct directory to run the update scripts from. If you are like me, you probably have a typing error causing your problems.
James
WD5GWY
James
WD5GWY
Re: G2 Updated files and simplified update procedure
Jerry,kd4yal wrote:Here is a second revision of my G2 update script, The Bash script is designed to streamline the update and build processes for the "G2" project by providing a menu-driven interface. Key features include:
Menu-Driven Interface: Utilizes whiptail to present users with a text-based menu, allowing selection of various update and build tasks.
Modular Functions: Defines specific functions for tasks such as updating system libraries, pulling the latest code from the Git repository, building applications, installing device rules, copying desktop icons, verifying FPGA BIT files, and building the pihpsdr application.
Error Handling: Incorporates a check_status function to provide feedback on the success or failure of each operation, enhancing debugging and user awareness.
Git Integration: Includes functionality to update the Git repository and retrieve the current commit hash, ensuring the latest code is in use.
Build Automation: Automates the build processes for both p2app and desktop applications, reducing manual intervention.
System Configuration: Offers options to install udev rules and copy desktop icons, facilitating system setup and configuration.
Comprehensive Updates: Provides an option to perform all tasks sequentially, enabling a complete system update with minimal user input.
This script enhances efficiency by automating routine tasks and offering a user-friendly interface for managing the project's update and build processes. Could use a little more work but seems to be a good framework.
Enjoy 73 Jerry KD4YAL
Thank you for sharing this script. Being a Linux newbie I am not sure how to go about setting it up correctly. If you could offer a few hints on how to setup and use your Bash script I for one, would be grateful.
I am sure it isn't that difficult, but I hesitate trying just anything and messing up a working system. ( I have read some things on using a Bash script online, but I am not certain if the procedure is correct)
Any guidance you can offer would be appreciated.
James
WD5GWY
Re: G2 Updated files and simplified update procedure
I received my G2 Ultra this week, it was working fine. The issue was it didn’t have the latest pihpsdr already loaded which I find ridiculous. Then if you download the so called manual from the manufacturer web site it isn’t the latest one. I have no experience with Linux whatsoever, but I begin the update process for pihpsdr. If you follow the directions in the so called manual you are screwed. Luckily doing some research i found the correct manual on the correct GitHub page for the latest version 2.5, which again should have already been installed. If you own a G2 ultra please read the latest manual before you start anything. You will find out that you have 2 pihpsdr folders in different places, one is a version from 2022 that as far as I can tell has no business being on there to begin with but that’s the one all the sources tells you to upgrade from,unless you have the latest manual and read to the end to find out that the version your using is under the GitHub folder. That makes the update process very different and in the latest manual it wasn’t that clear either. Anyway I start the update process and get a error message about having to merge files or stash files before i can proceed, i have to stop google what that means and how to do it. I find what I believe is the correct way to merge them but it just made things worse. Instead of dealing with trying to fix it, I thought my best option was to just download the latest version directly as a new install. I have to rename or move the current pihpsdr folder to be able to do this, which again took more time to google to find out how to do it. Finally was able to download the file, but halfway thru it locked up and i had to start over. This time it loaded, was able to open and run pihpsdr, oh by the way you do not want to select start automatically if you have the G2 ultra, there is no way be able to access that menu again to change it which I found out. I had to find the file command and go in and edit it to stop it which again took time. The reason for this as I found out later is to be able to access the drop down menus to select the correct settings to run the G2 ultra. Back to my adventure, of course when i did start pihpsdr none of the front buttons or knobs on the radio would work. At least i could use the mouse to change things, now comes the interesting stuff. I switch to the p2app to run thetis on my PC, and it says it can run because it needs an update. Wow, so I begin the process of figuring out how to update that which again took more time, I’m probably over 4 hours into this so far. By this time I’m getting a little more understanding on how to use the command prompts and to make a long story a tad shorter, I was finally able to get the p2app update done only then to find out I now have to upgrade the FPGA firmware. I finally got that done and by this point Ive noticed that even on the forums the instructions are not always very clear or precise and a lot of times not correct unless you know that some of the commands that are given are showing on different lines when it should all be on one. To my knowledge after all the things Ive read, no where does it tell you the need to update all those programs after you update pihpsdr. I started at 6pm and finally had it all running again a little after 1am. It’s my honest opinion that all that is complete BS.
Ive owned a 100, 200d, 8000, 7000 and now the G2. I’m probably a little more persistent than most people and wasn’t stopping until I got it figured out but there is no reason for it to be this convoluted. Good luck if you buy one, cause you’re on your own basically.
Ive owned a 100, 200d, 8000, 7000 and now the G2. I’m probably a little more persistent than most people and wasn’t stopping until I got it figured out but there is no reason for it to be this convoluted. Good luck if you buy one, cause you’re on your own basically.
Re: G2 Updated files and simplified update procedure
I understand your pain. The best thing I can suggest is to look carefully at what the latest version of PiHPSDR have to offer before deciding to do an update. The old saying " if it's not broke, don't fix it" applies with the G2 radios. The first thing I tell anyone with a new G2 is to get it working with what is already installed in the radio. There may be a good reason that the factory doesn't install the latest version of the software in the radio when they ship them.
James
WD5GWY
James
WD5GWY
Re: G2 Updated files and simplified update procedure
While I agree with you 1000% that there is no reason for it to be that convoluted, you are certainly not on your own. It's possible that, had you posted some questions and requested some help on the forum here a bit earlier in your journey, it might have gone a somewhat easier. Nevertheless, well done on getting it all sorted on your own, particularly as you wrote that you are not familiar with Linux.Jdsbose wrote: Sun Jun 29, 2025 7:03 pm I received my G2 Ultra this week, it was working fine.
{Long rant deleted}
I’m probably a little more persistent than most people and wasn’t stopping until I got it figured out but there is no reason for it to be this convoluted. Good luck if you buy one, cause you’re on your own basically.
At any rate, I have to agree that it would be a lot better if:
1. The products left the factory with the latest and greatest on them. If they don't, this is on Apache.
2. The documentation was better. Alas, all documentation is produced by volunteers in the open source community, not Apache, so they are what they are.
3. Update procedures were supported by scripts or, even better, by the software itself. Alas and again, all software, firmware and middleware is produced by volunteers in the open source community, not Apache.
4. There was an image file that could simply wipe the entire SD card and put anyone at the latest and greatest configuration.
I continue to be surprised that nobody in the community has produced a slick and easy set of scripts to update a G2. I don't have one, so it's not something I could do, but if I did have a G2 I would have developed such scripts on my own as a matter of convenience and then shared them here on the forum.
If you are looking to brush up on your Linux skills, there is a handy guide to what topics you might study here: viewtopic.php?t=4724
Bottom line: when you bought from Apache all you paid for was hardware. They do you a little favor by putting some software on there, but all the software, firmware, middleware and documentation comes from open source developers, not Apache.
Re: G2 Updated files and simplified update procedure
The remark that your all alone could have been worded better. I really appreciate all the work done here on the forums to help guys like me. The reason I didn’t ask on the forums basically is I’m not that patient, that’s on me. Once I started the process I was bound and determined to get it done.
Re: G2 Updated files and simplified update procedure
No worries! Just keep those cards and letters coming! 

Re: G2 Updated files and simplified update procedure
Now for a positive note, I really like pihpsdr, I think it works great. I was a tad skeptical until I started using it but so far it’s been fine, I actually like the receive audio out of it better than thetis in its standard settings.
-
- Posts: 305
- Joined: Mon Nov 11, 2019 7:39 pm
Re: G2 Updated files and simplified update procedure
There are some scripts that do some of this, and the next version of the manual will describe them. Unfortunately the newest "bookworm" release of the pi operating system distro has changed a lot of things, and for example the mechanism to autostart programs at power on is totally different. so the documentation and the scripts need to be updated; and now need to be version sensitive.
Jerry KD4YAL wrote a script that updates much of the necessary software (./home/pi/github/Saturn/scripts/update-G2.sh) and very recently published a new version. However it doesn't update piHPSDR. It does take a backup, so if the process fails you can revert.
Richie MW0LDE wrote a couple of python "helper" apps in his repository at https://github.com/ramdor/G2Tools. I know Abhi wants a clone of that in future factory images.
The install procedure for piHPSDR was totally changed a year or so ago, and no the manual hasn't caught up with that. Why the factory image has two copies of piHPSDR I have no idea.
And yes, a set of image files that can be copied to an SD card would make this all a lot easier. I have suggested it before, but I can try again.
Jerry KD4YAL wrote a script that updates much of the necessary software (./home/pi/github/Saturn/scripts/update-G2.sh) and very recently published a new version. However it doesn't update piHPSDR. It does take a backup, so if the process fails you can revert.
Richie MW0LDE wrote a couple of python "helper" apps in his repository at https://github.com/ramdor/G2Tools. I know Abhi wants a clone of that in future factory images.
The install procedure for piHPSDR was totally changed a year or so ago, and no the manual hasn't caught up with that. Why the factory image has two copies of piHPSDR I have no idea.
And yes, a set of image files that can be copied to an SD card would make this all a lot easier. I have suggested it before, but I can try again.
Laurence Barker G8NJJ