Anan 7000 DLE MKI Firmware ugrade problems.

[electronics-tech]

Hello all. I, like others decided it was time to update the firmware in my 7000 DLE MKII. Protocol 2. Purchased in Spring 2022.

Downloaded the file. 1019_Metis_Orion_MkII_Protocol_2_v2.0b.zip. My serial number ends in 591A

Ran Bootloader. Detects my board, and the MAC ID. Programmed. Move Switch, turn on and no heartbeat. Tried several attempts through a layer 1 switch. Tried directly connected. Still nothing.... But it does indicate that it has erased and programmed 100%.

When I run the Bootloader is still see's the MAC ID and the IP I programmed, but it just isn't there on the lan or directly connected.

What am I doing wrong here?

Thanks.

Ron.

[electronics-tech]

OK. Update. First of all that should have read 7000 DLE MKII in the Subject.

AND my radio was purchased in JANUARY 2023. So that makes a lot of a difference here.

I just read a thread about the P2 protocol firmware that is concerning from W2UO.

"Because there was no prior warning from Apache of this change there is currently no available Protocol 2 firmware for units shipped after 1 July 2022 at this time. If you load existing P2 firmware the unit will not work."

The question is, what firmware can I downgrade to?? To get this working again?

Ron.

[w-u-2-o]

See this topic: viewtopic.php?f=32&t=4462

[electronics-tech]

Thanks Scott. I did...

____
Hardware using the EP4CE115F29C8N Cyclone IV series FPGA

- ANAN-7000DLE MKII serial number DX8300497A or higher ( mine is higher)
- Andromeda with serial number ending in -CIV

Latest firmware
Metis_Orion_MkIII_Protocol_2_v2.1.26c.rbf
(1.37 MiB) Downloaded 276 times


___

That is what I programmed. Is this not the correct firmware for an Orion 7000 DLE MKII Post 2023? My serial is higher that 497A.

It all worked fine before the flash.

Thanks.
Ron.

[w-u-2-o]

I'm confused. First you write:

Downloaded the file. 1019_Metis_Orion_MkII_Protocol_2_v2.0b.zip.

Then you write:

Metis_Orion_MkIII_Protocol_2_v2.1.26c.rbf...That is what I programmed.

Which is it? Or did you try both?

Four things to consider:

1. If Bootloader runs OK, then you did not brick the unit, i.e. the Bootloader part of the image remains OK.

2. You can try all three files in the aforementioned link. None will break/brick the unit even if it is the wrong file. Once you find one that works you'll know exactly what FPGA you have. Make a note (maybe on a piece of tape on the back or bottom of the unit) for future reference.

3. If you are updating from Protocol 1 to Protocol 2 it is possible you have a problem whereby the link to the PC is not GigE. P2 requires GigE, it will not run at any other speed. Even if all NICs, switches, etc. are GigE rated it is possible to have a bad cable that is screwing things up. 100Mbit only requires 2 pairs on the cable to be good, GigE requires all 4 pairs. Make certain you are GigE "clean" all the way through.

4. What sort of IP addressing are you using? DHCP, static or APIPA? Everything must be properly configured on both the ANAN and on the PC side.

[electronics-tech]

Thanks Scott. And yes I tried them both. And yes you are correct that it is not Bricked so far.

I think I will try them all.

As for the networking. Originally it was all DHCP . But I reserved both the ANAN and Lenovo PC's IP's in the router/modem.

Now I am attempting to just give it an UNUSED IP in the DHCP table. But when I use Angry IP on any machine here, the Anan's IP just refuses to be there. Main modem/router is a TP-Link ER7206 and I am using the DHCP server in it. I need to check if there is another switch that is in the way.

Everything is Gigabit, DHCP and not APIPA And the Anan was for sure Protocol 2. . It all did work before the flash, so I have something wrong.

I will try your suggestions. One way to find out is take the hood off the unit and read what the FPGA says I guess.

Thanks again.

[electronics-tech]

You were right about trying all 3 firmware's. Turns out it was : Metis_Orion_MkIII_P2_CV_21.7.rbf. so I know now what FPGA I have.

I have it statically assigned now. And all is looking good. I was just afraid of bricking the radio, so I had to reach out. The MK III turned me off from trying the firmware.

You learn a lot by trying things that is for sure and I am glad I did. I really wanted this on a static IP.

I thank you again Scott. You are most helpful to us all. As usual.

Best 73
de
VE3NLS

[w-u-2-o]

Glad you got it sorted

Now that you know unambiguously which FPGA you have, take a look at the following topic:

viewtopic.php?f=32&t=4588

There are some slightly newer versions available to you that fix a QSK bug.

[W4WMT]

There are some slightly newer versions available to you that fix a QSK bug.

And the latest Cyclone V versions also fix the 100Hz VFO offset bug.

[electronics-tech]

That's great guys. Thank you both for the heads up on that.

VE3NLS