Thetis Cannot Access 7000DLE MKII after Protocol 2 upgrade
Posted: Fri Apr 01, 2022 5:23 am
I recently received my 7000DLE MKII and got it running with Thetis 2.8.11 with the 21k9 patch. All was well.
Not being content to leave "good enough" alone, an upgrade to Protocol 2 was done using HPSDRBootloader v2.0.4.4. The program had no trouble contacting the radio to to do the programming, which appeared to complete normally. I powered off the radio, moved the bootloader switch to "OFF" and powered the radio back on.
Thetis complains that it cannot find the radio. I observed that Thetis was sending UDP packets (port 1024) to the broadcast address for the network. The right led is flashing (FPGA heartbeat). I can ping the radio IP from the Win7 computer.
Some strange things to note.
1) As shipped, the radio had the bootloader switch in the ON position. <----- Is this expected??
2) Thetis worked fine with the protocol 1 firmware in the radio with this switch ON.
3) After the upgrade, if the switch is OFF, I can ping the radio.
4) After the upgrade, if the switch is in the ON position, I cannot ping the radio. This is not unexpected, because presumably the bootloader does not need a IP address
5) The radio is getting its address via DHCP. It gets 10.48.96.48 with a netmask of 255.255.240.0
I am suspecting that the protocol 2 firmware may not be listening on the proper broadcast address for the UDP packets. When I bring up HPSDRBootloader and look at the IP setting dialog there appears to be no way to set a netmask. If I read the IP, then I see 255.255.255.255, which may mean DHCP is being used.
Note: if I change the computer's netmask to 255.255.255.0, then Thetis works, but the computer has problems with other IP based applications. This seems to confirm that Protocol 2 firmware is ignoring the netmask being issued by the DHCP server. Protocol 1 does not seem to have this problem.
As always, any help would be appreciated. I'm not sure how to get the Protocol 1 rbf file that was in the radio to restore operation.
Thanks,
Dale (W6EDT)
Not being content to leave "good enough" alone, an upgrade to Protocol 2 was done using HPSDRBootloader v2.0.4.4. The program had no trouble contacting the radio to to do the programming, which appeared to complete normally. I powered off the radio, moved the bootloader switch to "OFF" and powered the radio back on.
Thetis complains that it cannot find the radio. I observed that Thetis was sending UDP packets (port 1024) to the broadcast address for the network. The right led is flashing (FPGA heartbeat). I can ping the radio IP from the Win7 computer.
Some strange things to note.
1) As shipped, the radio had the bootloader switch in the ON position. <----- Is this expected??
2) Thetis worked fine with the protocol 1 firmware in the radio with this switch ON.
3) After the upgrade, if the switch is OFF, I can ping the radio.
4) After the upgrade, if the switch is in the ON position, I cannot ping the radio. This is not unexpected, because presumably the bootloader does not need a IP address
5) The radio is getting its address via DHCP. It gets 10.48.96.48 with a netmask of 255.255.240.0
I am suspecting that the protocol 2 firmware may not be listening on the proper broadcast address for the UDP packets. When I bring up HPSDRBootloader and look at the IP setting dialog there appears to be no way to set a netmask. If I read the IP, then I see 255.255.255.255, which may mean DHCP is being used.
Note: if I change the computer's netmask to 255.255.255.0, then Thetis works, but the computer has problems with other IP based applications. This seems to confirm that Protocol 2 firmware is ignoring the netmask being issued by the DHCP server. Protocol 1 does not seem to have this problem.
As always, any help would be appreciated. I'm not sure how to get the Protocol 1 rbf file that was in the radio to restore operation.
Thanks,
Dale (W6EDT)