Quote from: frostedflakes on September 01, 2013, 01:26:10 AM

Don't know if this is typical for newer Jalapenos, but mine actually came from BFL with two chunks of the heatsink cut out over the fan and JTAG1 headers. Mine also didn't have a JTAG2 header soldered on. So didn't need to remove the heatsink to put the JTAG cable on and program the μC (of course didn't open it up and realize this until after I had already ordered a JTAG cable w/grabber kit that still hasn't arrived yet for like $10 off eBay).

http://img843.imageshack.us/img843/9178/c7dv.th.jpg http://img15.imageshack.us/img15/1646/m435.th.jpg http://img543.imageshack.us/img543/2346/mcf7.th.jpg http://img801.imageshack.us/img801/2996/0ghf.th.jpg

Was getting ~5.8GH/s with default firmware (not sure why but was running pretty high straight from the factory, but also had what seems to be fairly high HW error rate, about 2%, so effective hash rate would actually be a bit lower). Flashed an unmodified 1.2.5 to it and now getting 8.1GH/s-8.3GH/s, depending on how many engines initialize and at what speed they initialize. Even more hardware errors now, though, looks like roughly 4%. Might be some other issue with my setup.

Going to try letting it cool down for a bit here sometime and seeing if I can get it to reinitialize at a higher hash. Looks like currently it's only initialized with 13 engines on on chip 3 and 14 engines on chip 7, but they are clocked super high, 305MHz for chip 3 and 296MHz for chip 7. The #define __ASIC_FREQUENCY_ACTUAL_INDEX should be whatever the default is, 7 right? I didn't realize it would clock them that aggressively.

Before I was getting about the same number of engines initializing, 13-14, and they were clocking at 190-200MHz I think (again depending on whether you were cold booting and starting up the unit after it had been running for a bit).

And it looks like my Jalapeno bit the dust. RIP. Sad

Last night one of the ASICs seem to have stopped working, hash rate dropped down to ~4GH/s or so and only chip #7 was showing up when running java API stats. Then got home tonight and found the red status LED on the Jalapeno flashing quickly and cgminer unable to communicate with it.

Maybe I pushed the little guy too hard. Any ideas for reviving it or is it probably toast? Tried power cycling the unit but no luck. Going to leave it unplugged for a bit then try starting it up again and see if that does anything.

EDIT: Huh. Well that seemed to get it going again, at least for the time being. Still only recognizing processor 7, though, processor 3 no longer active and hashing.