You're gonna need internet to mine with these controllers. Unless for some reason the PC you're using is not on the same network it doesn't make a difference.

I've had PI crashes because of unstable power. A good way to tell if you're having unstable power is if the red power LED is flickering. TP1 and TP2 on the RPi should measure above 4.75V with the Pi active and hashing away. Best to use a known good power adapter (like a good original phone charger that's at least 1A capable).

I have the same setup with you and am experiencing the same issue.

I build the BFGminer myself. 10 gridseeds on the PI. After awhile (seemingly random time) one of them will stop submitting shares and I have to restart BFGminer for it to work again.

That sounds like almost normal bootup sequence. Anything when you enter the IP address into your browser?

Anyways just to let you guys know. I have successfully used the serial TTL and terminal + TFTP method to restore a bricked controller. Upload the v1 image in 1st and then from there the actual V3 firmware itself. If you get stuck doing that, do post where you are at.

Try the V1 image. It might throw up some more error messages but give it some time before either it auto reboots or you gotta reboot it.

Yeah, which is the point of having a freq column. Previously all were either manually set or a global clock freq. Now they might end up running at different freqs.

Upgraded my V3c to V3d, seems to be mining good. Very stable hashrates at the pool. Would love to have the current clock speed display on a separate column on the miner page (1st page) just as a quick indication of what they are clocked at currently.

For some reason I seem to be getting more HW errors with this firmware version compared to cgminer on RPi.

V3c firmware seems to have fixed my issue with 2 and 3 reporting 0. 

Looks like the page is still down. Oh well...

To elaborate more about my issue. I see the upload progress go from 0-100%, next moment instead of doing it's thing, it comes up with this message.

I tried that. Including using Chrome's incognito mode to arrest any cache issues. Nope. Still the same error message.

I have yet another unit that throws this error when I try to upload the initial binary.

Error: Firmware with name 'LAG3355_upgrade_v2' is not found   

I have the same issue with my updated from V2 (with V1 image) controller. 2 and 3 always report 0.

Tryied to upgrade my V2 units. (HW V1.6). All I get is this error "Sysupgrade: cat: write error: Broken pipe cat: write error: Broken pipe cat: write error: Broken pipe cat: write error: Broken pipe Invalid image type. Image check 'platform_check_image' failed."

Andareed: did you measure the voltage output of the regulator to find out how much did this increase the voltage to? Just curious as to how much this mod changes the voltage.

Conductive pens might be a viable option. Someone needs to try that out.

R2 and R8 are 0805 sized resistors. They are not terribly hard to solder, compared to say 0402 sized parts, but replacing R8 might be more of a challenge because of it's location.

A small soldering iron, good light, some soldering (not plumbing) flux, desoldering braid/wick and a pair of tweezers (failing that, a toothpick) should make short work of this.

Hi Icoin, wow that looks fantastic. I suppose it'll come with spring loaded screws or something to mount onto the board. I just wished the Spartan-6 had a metal lid instead of it being encapsulated in epoxy like at the moment, that seriously hampers our cooling efforts. Ah well...