HL2 no longer visible on network

[neiljw...@gmail.com]

My latest HL2, from this year's batch (shipped in March 23), was originally working

well as expected.

Now it fails to be discovered on the network (1Gb wired)..

I've been through the Wiki Troubleshoot Network section.

It powers up and I get D2 flashing, D3 flashing and D4+5 on.

This suggests IP address assignment has succeeded via fixed IP or APIPA.

Nevertheless it is not discovered in Quisk or SparkSDR.

I set up a PC with the hermeslite.py connected directly to the HL2.

This also does not discover this HL2. It does successfully discover another

HL2 if I connect that instead.

After a few minutes the HL2 seems to attempt a reboot - a sequence of LEDs

runs through, not always ending up with the same combination. The current

one has of D2+3+4 flashing and D5 on.

I tried a factory image boot with CW and PTT pins shorted but the results were similar.

I'm not sure where to go from here. Any suggestions?

Thanks/73,

Neil  G4BRK

[Steve Haynal]

Hi Neil,

When both D2 and D3 are flashing (suggests IP assignment via fixed IP), Is D2 (nearest the ethernet port) flashing at twice the speed of D3 or the same speed?

Did you attempt reflashing the gateware with a Raspberry Pi? I ask as that can put the HL2 into the state you see if the Pi image wasn't updated to the latest gateware via the update button.

Do you have more than one HL2 connected to your network without changing the MAC address?

73,

Steve

kf7o

[neiljw...@gmail.com]

Hi Steve,

Thanks for getting back to me.

D2 seems to be flashing at twice the speed. At first I thought they were in antiphase at the same speed

but looking more carefully the speeds are different.

I haven't tried to reflash the gateware using a Raspberry pi. I have changed it to the cic (10 RX) version using

SparkSDR and it has been working using that.

I did first suspect a clash of MAC address as I have seen that before with another HL2, but as far as I remember

it was set to a different address soon after I did the initial set up. Presumably that wouldn't be an issue when

connected direct to a PC running hermeslite.py

73,  Neil  G4BRK

[Steve Haynal]

Hi Neil,

If D2 is flashing at twice the rate, then your gateware is new enough to recognize the KSZ9021 or KSZ9031 and it is unlikely some older gateware was installed.

Are the two LEDs on the ethernet jack solid amber and blinking green?

If you do have multiple HL2s on your network, I think it would be a good test to disconnect all and try to connect just the problematic one to the network with DHCP.

As you report, there is no difference with factory boot?

You can make a five minute inspection of the components around the ethernet jack. Perhaps there is a pin of the ethernet jack which has worked loose and needs to be resoldered. You can also try finger pressure on various components in the area.

Have you tried different ethernet cables?

If you do have a Raspberry Pi and feel comfortable doing it, it is worth trying to reprogram the original gateware. Make sure to double-click the update button on the desktop to retrieve the latest gateware.

Do you have a friend which can try connecting the HL2 to their network?

Any recent lightning strikes in your area?

You can arrange to send just the HL2 board to me if you like.

[neiljw...@gmail.com]

Hi Steve,

Thanks again for your time. I've been working my way through your list.

Ethernet jack LEDs solid amber, green blinks on hitting discover in SparkSDR.

No easy friend network to use but I set up my own using an old router with just a PC and

the HL2. The router DHCP was enabled. This behaves the same way - ie the HL2 is not discovered.

I have tried visual inspection, other ethernet cables and factory boot. No lightning here.

Next I tried to reprogram the gateware using an old Pi 3B+. Once I'd managed to get the Pi networking to work

I updated the image. I checked the files and they were indeed updated.

However after making the connections from the Pi to CN1 for programming and running program it did not

succeed (all 3 attempts failed to read the IDCODE).

I will recheck my jumper cables today in case one is open circuit or I have got the connections wrong.

I have checked several times but that doesn't mean it is right :-)

73, Neil  G4BRK

[Steve Haynal]

Hi Neil,

It is interesting that the ethernet jack LEDs are solid amber and green blinks on hitting discover in SparkSDR. This makes me think the problem may lie in the FPGA or KSZ9021/FPGA connections.

We changed the Raspberry PI pins for programming recently at Makerfabs request. Are you using the pins described here:

https://github.com/softerhardware/jam-stapl

73,

Steve

kf7o

[neiljw...@gmail.com]

Hi Steve,

Thanks for the further info. I was using the pin connections listed on the Wiki test and program page.

I moved the HL2 CN1 connection from pin 7 to pin 9 as described on the jam-stapl page and things

started to look better on the programming. I had to run the program script 3 times but in the end it

programmed successfully.

That's the good news - however it doesn't seem to fix the issue of the HL2 not being discovered,

using both normal and factory boot.

I'm a bit busy with family visitors at present but I will try more experiments when I have some time.

I will also attempt to check connections between KSZ9021 and FPGA.

Thanks again,

Neil G4BRK