Spent some spare time lately to continue my efforts to run the Odyssey-2 in Linux, with a direct connection to the Ethernet port. This is an unmodified unit with the original firmware as was supplied when it went into production. I has the original boot loader and AOP-1.10 firmware.
I first tried to run Ody-2 with a direct Ethernet connection but it would not work. I then connected it to my ISP's router and was able to access it via the WiFi connection and I used HPSDRProgrammer-v2-nopcap to give Ody the default static IP of 192.168.2.160 and the computer's port the static IP of 192.168.2.100, as advised by David. However, every effort and every info I found on the Web failed to make it work. I could only get the ping tool to work successfully but not discovery by any software.
I then tried to connect with Ody using the direct Ethernet connection but with DHCP, so I used the programmer with a connection to the router to reset Ody-2 to work with DHCP. After much effort and experiment, I succeeded to have the Odyssey-2 respond to ping and be discovered by both the programmer and ghpsdr so that now I have a chance to actually run Ody-2.
There is however a catch - Odyssey-2 will only work with DHCP if the following sequence is followed:
1. Set up the O/S dhcpcd service to separately set up WiFi and Ethernet.
2. Use ethtool -s eth0 speed 100 duplex full autoneg off to set up the port.
3. Switch on Odyssey _after_ starting the computer (and the dhcp service) so that (apparently) Odyssey makes a DHCP request when the dhcpcd server is ready.
This is fair enough, better than having to work with a router or switch but I would prefer to make it all work without manual operations every time. I have added the ethtool command to the rc.local int script and that is done at boot time. Also set up Void Linux's "runit" init system to run dhcpcd separately at boot time so all that is left is the need to switch on Ody after boot is finished.
So, having got this far, I feel that I should try to upgrade Ody-2 to newer firmware but I rather not go as far as importing the needed hardware to reprogram with the new boot loader, since the necessary software will not run on Linux anyhow.
So I would like to ask, can I safely upgrade the AOP-1.10 firmware to the latest available, using only the HPSDRprogrammer and existing boot loader, and if so, will it work with a non-static IP address (under DHCP)? If not, will it be more likely to succeed with a static IP and with a direct Ethernet-to-Ethernet connection?
Apologies for the long post, but its been a much much longer effort to get this far! ;-)
Neoklis - Ham Radio Call:5B4AZ