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: 304
- 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 341 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