Barracuda Networks F80 Repair (Atom c2000 bug)

[nevusZ]

hy,
I have heard about repairing a synology NAS with the same cpu as my networking appliance(intel atom c2358)
https://www.eevblog.com/2020/03/10/eevblog-1288-synology-nas-dumpster-find-repair/
The cpu has the same errors, I fixed some appliances by completly change the cpu (BGA soldering by a company)
But this was to expensive.
I wonder if it would be possible to do the same as on the synology nas?!
My appliance is a Barracuda Networks NG Firewall F80.
It is manufactured by Lanner as far as I know.  The mainboard is from Microstar Internation - MSI.
I made some pictuers of the board.
I dont have any description of the appliance.
Is anyone able to help me get this done?
This is my first post in EEVblog, repairing stuff is a good thing instead of trash the usefull stuff.
https://ibb.co/jVY14Z0
https://ibb.co/RCR4f7W
https://ibb.co/fDyz6MR
https://ibb.co/1XVM7d1
https://ibb.co/D1vn8J6
https://ibb.co/JkrpsBF

[danikd]

Hello,

I have same firewall, only beep and blue and blue LED on start, no sign of life. Its same as on yours? How do you resolve it? Thx for info. Daniel

[perieanuo]

Hello,

I have same firewall, only beep and blue and blue LED on start, no sign of life. Its same as on yours? How do you resolve it? Thx for info. Daniel

he just explained, changing or reballing the cpu

[perieanuo]

hy,
I have heard about repairing a synology NAS with the same cpu as my networking appliance(intel atom c2358)
https://www.eevblog.com/2020/03/10/eevblog-1288-synology-nas-dumpster-find-repair/
The cpu has the same errors, I fixed some appliances by completly change the cpu (BGA soldering by a company)
But this was to expensive.
I wonder if it would be possible to do the same as on the synology nas?!
My appliance is a Barracuda Networks NG Firewall F80.
It is manufactured by Lanner as far as I know.  The mainboard is from Microstar Internation - MSI.
I made some pictuers of the board.
I dont have any description of the appliance.
Is anyone able to help me get this done?

you skipped the diagnose part, verifying if the processor is not soldered correctly, you didn't mentioned what's not working, does it boot etc...
try starting it pressing the cpu if it doesn't boot, see if it displays at least first page, or give us details about the failure

[wraper]

Hello,

I have same firewall, only beep and blue and blue LED on start, no sign of life. Its same as on yours? How do you resolve it? Thx for info. Daniel

he just explained, changing or reballing the cpu

It can be repaired by simply connecting a pull-up resistor between LPC_CLKOUT0 and/or LPC_CLKOUT1 and +3.3V power rail. The same as an official fix for Synology NAS, no CPU replacement needed. The issue is if LPC is exposed on particular PCB and if you can find it.

[wraper]

Potentially this could be it. Or some other pin header.

[perieanuo]

Hello,

I have same firewall, only beep and blue and blue LED on start, no sign of life. Its same as on yours? How do you resolve it? Thx for info. Daniel

he just explained, changing or reballing the cpu

It can be repaired by simply connecting a pull-up resistor between LPC_CLKOUT0 and/or LPC_CLKOUT1 and +3.3V power rail. The same as an official fix for Synology NAS, no CPU replacement needed. The issue is if LPC is exposed on particular PCB and if you can find it.

that's good news for op, tks
but for me that mobo doesn't look like a syno pcb

[wraper]

but for me that mobo doesn't look like a syno pcb

It has nothing to do with Synology in particular. It's Intel CPU silicon issue and fix/workaround is the same for any device where it fails.

[danikd]

Potentially this could be it. Or some other pin header.

Hello, many thx for info. How to find the proper pins? 3.3V is easy ... BUr CLK pins ...

[wraper]

I would probably check if any pin on particular connector has 3.3V on it. If it has, make a wire with two 1 pin DuPont connectors and a 100 ohm  resistor in series. Then try connecting it between 3.3V pin and every other pin except GND and try booting with each connection variant. If it boots, you have found the right pin and can solder the resistor permanently. By this method, chance of causing any further damage is small and chance of fixing the thing quite high.
In any case, without having another working board and oscilloscope to find the CLK signal, you wouldn't know for sure without a hit and miss testing.

[danikd]

Thx for info, I will test it and post results. Nice day! Daniel

[danikd]

Hello, I measured pins on this connector and :

1) 3.3V
2) 3.3V
3) 3.3V
4) 3.3V
5) 3.3V
6) 3.3V
7) 3.3V
1.5V
9) Ground
10) Ground
11) PIN Not Present
12) 0V

Its the right connector?

Thx for info ...

Daniel

[wraper]

Hard to tell when interface is not actually running due to failure. Pinout is completely different among manufacturers. Quantity of what seems to be data lines is about right for LPC. Try attaching pull-up resistor from 3.3V to pin 12 and if does not help, to 8. Just be sure to attach it to actual 3.3V power rail and not just data line with 3.3V logic high.

[danikd]

But how to find proper 3.3V rail ... somewhere on the board, not on connector? Many thx. Daniel

[wraper]

Well, it's likely on the connector. I would look if there is a thicker trace to some pin with 3.3V. Or you could check if some nearby capacitor has 3.3V on it. Then solder to that or test continuity to connector pins.

[danikd]

Hello, sorry for late reply, I was very very busy  Hope this weekend I will test it. Thicker trace with 3.3V already found. Nice day! Daniel

[amyk]

Look up information on what ICs are on the board and whether they connect to the LPC bus. If you find one, you can use it to find the clock pin.

[danikd]

Hello,

sorry for my late reply, I was very busy. Ty both pins and nothing work. Maybe there is another damage, because original power suplly was shorted. I know nothing about history of this device, so maybe time to move to another device Many thx for help on this best forum.
PF2022

Dan