philips
|
|
June 29, 2013, 09:37:50 PM |
|
Cool! Have you tried tweaking the firmware?
|
|
|
|
kano
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
June 29, 2013, 09:45:55 PM |
|
Do they get lifetime warranty?
Maybe not after you mod the firmware and push it hard. They certainly would not be required to do so. I imagine when these break because of overclocking they will have a pretty similar characteristic. So if you are doing this, know what you are doing, don't go crazy, and you MUST upgrade the cooling. This includes all parts further stressed by more heat, not just the ASIC chips themselves. Yes this is really a Jalapeno only option coz they only have 2 chips. The later devices, 25-60GH/s I'd firstly be surprised if they could be clocked much faster, and secondly be worried that it would kill it very quickly without major work on the hardware cooling. Obviously they will already have the 1.2.5 or later firmware so this simple reflash wont make any difference, but messing with the firmware to clock it up higher ... I can see ASIC death and destruction on the horizon with the bigger devices
|
|
|
|
chanberg
|
|
June 29, 2013, 09:49:11 PM |
|
wish i had a jalapeno to reflash
|
|
|
|
danattacker (OP)
|
|
June 29, 2013, 09:55:20 PM |
|
Before Jalapeno 0: 6.2GH/s : After Jalapeno 0: 8.6GH/s Before Jalapeno 1: 5.5GH/s : After Jalapeno 1: 7.7GH/s
Very good. You must have 30 (or more) engines on Jalapeno 0.
|
|
|
|
macromode
Member
Offline
Activity: 104
Merit: 10
|
|
June 29, 2013, 10:11:12 PM |
|
@goxed What kind of temps are you getting with those aluminum heatsinks from the getinfo command? Is it a nice drop off from the original cooling solution?
|
|
|
|
jelin1984
Legendary
Offline
Activity: 2408
Merit: 1004
|
|
June 29, 2013, 10:25:01 PM |
|
cool
|
|
|
|
goxed
Legendary
Offline
Activity: 1946
Merit: 1006
Bitcoin / Crypto mining Hardware.
|
|
June 29, 2013, 11:07:42 PM |
|
Before Jalapeno 0: 6.2GH/s : After Jalapeno 0: 8.6GH/s Before Jalapeno 1: 5.5GH/s : After Jalapeno 1: 7.7GH/s
Setup for flashing Rev 2 Jalapeno with all aluminum heatsink.
Cool! Have you tried tweaking the firmware? Just tweaked the firmware. changes ln 101 in std_defs.h #define __ASIC_FREQUENCY_ACTUAL_INDEX 9 New Speeds Before Jalapeno 0: 8.6GH/s : After Jalapeno 0: 9.2GH/sBefore Jalapeno 1: 7.7GH/s : After Jalapeno 1: 7.9GH/s [P]ool management [S]ettings [D]isplay options [Q]uit BAJ 0: max 35C 3.76V | 9.213G/9.197Gh/s | A:171 R:0 HW: 7 U: 22.82/m BAJ 1: max 41C 3.50V | 6.986G/7.907Gh/s | A:150 R:0 HW:35 U: 20.01/m
|
Revewing Bitcoin / Crypto mining Hardware.
|
|
|
goxed
Legendary
Offline
Activity: 1946
Merit: 1006
Bitcoin / Crypto mining Hardware.
|
|
June 29, 2013, 11:08:19 PM Last edit: June 30, 2013, 01:31:12 AM by goxed |
|
@goxed What kind of temps are you getting with those aluminum heatsinks from the getinfo command? Is it a nice drop off from the original cooling solution?
those are just for use during flashing. It will kill the Jally for sure if used as a replacement after flashing.
|
Revewing Bitcoin / Crypto mining Hardware.
|
|
|
goxed
Legendary
Offline
Activity: 1946
Merit: 1006
Bitcoin / Crypto mining Hardware.
|
|
June 29, 2013, 11:09:29 PM |
|
Before Jalapeno 0: 6.2GH/s : After Jalapeno 0: 8.6GH/s Before Jalapeno 1: 5.5GH/s : After Jalapeno 1: 7.7GH/s
Very good. You must have 30 (or more) engines on Jalapeno 0. How can I get the stats of engines? I would want to know that. Thnks
|
Revewing Bitcoin / Crypto mining Hardware.
|
|
|
goxed
Legendary
Offline
Activity: 1946
Merit: 1006
Bitcoin / Crypto mining Hardware.
|
|
June 29, 2013, 11:12:56 PM |
|
a) a tiny hex screwdriver to remove the screws off the bottom of the Jalapeno
Btw the correct terminology for the required driver is Torx T9
|
Revewing Bitcoin / Crypto mining Hardware.
|
|
|
tom99
|
|
June 29, 2013, 11:13:47 PM |
|
look like your Jal 1 asic chips not good grade chip and Jal 0 look good.
ps: to get getinfo work u need to run cgminer config setting with api
|
|
|
|
goxed
Legendary
Offline
Activity: 1946
Merit: 1006
Bitcoin / Crypto mining Hardware.
|
|
June 29, 2013, 11:20:30 PM |
|
look like your Jal 1 asic chips not good grade chip and Jal 0 look good.
ps: to get getinfo work u need to run cgminer config setting with api
Then how can I get the API info? Can it be done with a browser URL? Thanks
|
Revewing Bitcoin / Crypto mining Hardware.
|
|
|
tom99
|
|
June 29, 2013, 11:45:53 PM |
|
read API readme file and sample file above api readme file.
|
|
|
|
goxed
Legendary
Offline
Activity: 1946
Merit: 1006
Bitcoin / Crypto mining Hardware.
|
|
June 30, 2013, 12:03:55 AM |
|
read API readme file and sample file above api readme file.
Okay so i guess i need to compile the sample api code. thanks
|
Revewing Bitcoin / Crypto mining Hardware.
|
|
|
tom99
|
|
June 30, 2013, 12:05:02 AM |
|
read post 159.
|
|
|
|
goxed
Legendary
Offline
Activity: 1946
Merit: 1006
Bitcoin / Crypto mining Hardware.
|
|
June 30, 2013, 12:52:08 AM |
|
great thanks! used the python api-example.py code.
python api-example.py stats
{u'STATUS': [{u'STATUS': u'S' u'Msg': u'CGMiner stats' u'Code': 70 u'When': 1372553376 u'Description': u'cgminer 3.3.1'}] u'STATS': [{u'Temp2 Max Time': 1372553345 u'Temp1 Max': 33.0 u'Min': 99999999.0 u'Que Watermark': 32 u'Driver': 2 u'Firmware': u'1.2.5' u'Flush ID': 0 u'Scan Sleep': 891 u'Results Sleep': 100 u'Que Full': 36 u'Overheat': False u'Work Queued': 37 u'Max': 0.0 u'Result ID': 251 u'Vmain': 12.398 u'USB Pipe': u'0' u'Elapsed': 204 u'Vcc1': 3.846 u'Vcc2': 0.993 u'Flushed': False u'Chips': u'(null)' u'Wait': 0.0 u'Que Low': 8 u'STATS': 0 u'Calls': 0 u'Que Size': 40 u'Work Complete': 420 u'Temp1 Max Time': 1372553224 u'ID': u'BAJ0' u'Work ms': 954 u'Temp2 Max': 45.0 u'Temp2': 42.81 u'Temp1': 32.41 u'GetInfo': u'DEVICE: BitFORCE SC0x0aFIRMWARE: 1.2.50x0aIAR Executed: NO0x0aCHIP PARALLELIZATION: YES @ 20x0aQUEUE DEPTH:400x0aPROCESSOR 3: 15 engines @ 319 MHz -- MAP: FFFE0x0aPROCESSOR 7: 13 engines @ 326 MHz -- MAP: F5FE0x0aTHEORETICAL MAX: 9023 MH/s0x0aENGINES: 280x0aFREQUENCY: 291 MHz0x0aXLINK MODE: MASTER0x0aCRITICAL TEMPERATURE: 00x0aXLINK PRESENT: NO0x0aOK0x0a0x00'} {u'Temp2 Max Time': 1372553347 u'Temp1 Max': 31.0 u'Min': 99999999.0 u'Que Watermark': 32 u'Driver': 2 u'Firmware': u'1.2.5' u'Flush ID': 0 u'Scan Sleep': 913 u'Results Sleep': 100 u'Que Full': 36 u'Overheat': False u'Work Queued': 37 u'Max': 0.0 u'Result ID': 249 u'Vmain': 12.097 u'USB Pipe': u'0' u'Elapsed': 204 u'Vcc1': 3.404 u'Vcc2': 0.987 u'Flushed': False u'Chips': u'(null)' u'Wait': 0.0 u'Que Low': 8 u'STATS': 1 u'Calls': 0 u'Que Size': 40 u'Work Complete': 372 u'Temp1 Max Time': 1372553328 u'ID': u'BAJ1' u'Work ms': 954 u'Temp2 Max': 43.0 u'Temp2': 40.98 u'Temp1': 30.11 u'GetInfo': u'DEVICE: BitFORCE SC0x0aFIRMWARE: 1.2.50x0aIAR Executed: NO0x0aCHIP PARALLELIZATION: YES @ 20x0aQUEUE DEPTH:400x0aPROCESSOR 3: 13 engines @ 286 MHz -- MAP: FFE60x0aPROCESSOR 7: 15 engines @ 284 MHz -- MAP: FFFE0x0aTHEORETICAL MAX: 7978 MH/s0x0aENGINES: 280x0aFREQUENCY: 291 MHz0x0aXLINK MODE: MASTER0x0aCRITICAL TEMPERATURE: 00x0aXLINK PRESENT: NO0x0aOK0x0a0x00'} {u'Min': 99999999.0 u'Work Roll Time': 0 u'Work Can Roll': False u'Work Diff': 10.0 u'Net Bytes Recv': 17219 u'Times Recv': 271 u'Times Sent': 263 u'Max': 0.0 u'Elapsed': 204 u'Pool Min': 99999999.0 u'Min Diff': 1.0 u'Work Had Expire': False u'Wait': 0.0 u'STATS': 2 u'Calls': 0 u'Bytes Sent': 30881 u'Pool Max': 0.0 u'Max Diff': 11.0 u'ID': u'POOL0' u'Work Had Roll Time': False u'Pool Calls': 0 u'Net Bytes Sent': 31610 u'Pool Av': 0.0 u'Bytes Recv': 17219 u'Max Diff Count': 443 u'Pool Attempts': 0 u'Pool Wait': 0.0 u'Min Diff Count': 219} {u'Min': 99999999.0 u'Work Roll Time': 0 u'Work Can Roll': False u'Work Diff': 1.0 u'Net Bytes Recv': 124376 u'Times Recv': 2 u'Times Sent': 2 u'Max': 0.0 u'Elapsed': 204 u'Pool Min': 99999999.0 u'Min Diff': 1.0 u'Work Had Expire': False u'Wait': 0.0 u'STATS': 3 u'Calls': 0 u'Bytes Sent': 232 u'Pool Max': 0.0 u'Max Diff': 1.0 u'ID': u'POOL1' u'Work Had Roll Time': False u'Pool Calls': 0 u'Net Bytes Sent': 1236 u'Pool Av': 0.0 u'Bytes Recv': 123936 u'Max Diff Count': 1 u'Pool Attempts': 0 u'Pool Wait': 0.0 u'Min Diff Count': 1} {u'Min': 99999999.0 u'Work Roll Time': 0 u'Work Can Roll': False u'Work Diff': 1.0 u'Net Bytes Recv': 1989 u'Times Recv': 3 u'Times Sent': 3 u'Max': 0.0 u'Elapsed': 204 u'Pool Min': 99999999.0 u'Min Diff': 1.0 u'Work Had Expire': False u'Wait': 0.0 u'STATS': 4 u'Calls': 0 u'Bytes Sent': 464 u'Pool Max': 0.0 u'Max Diff': 1.0 u'ID': u'POOL2' u'Work Had Roll Time': False u'Pool Calls': 0 u'Net Bytes Sent': 1348 u'Pool Av': 0.0 u'Bytes Recv': 692 u'Max Diff Count': 1 u'Pool Attempts': 0 u'Pool Wait': 0.0 u'Min Diff Count': 1}] u'id': 1}
|
Revewing Bitcoin / Crypto mining Hardware.
|
|
|
tom99
|
|
June 30, 2013, 01:41:37 AM |
|
anyone know if Jal comes with pci-e cable for power?
|
|
|
|
danattacker (OP)
|
|
June 30, 2013, 03:11:46 AM |
|
Wow! Both chips in that Jalapeno are running at insane speeds! I didn't even think the firmware would try to clock that high. That's pretty amazing that both chips are running at that speed given that BFL says the max frequency is ~294 MHz. I originally thought you had some perfect chips with 16 engines but wow.
|
|
|
|
tom99
|
|
June 30, 2013, 03:52:09 AM |
|
|
|
|
|
danattacker (OP)
|
|
June 30, 2013, 05:29:03 AM |
|
The JTAG pins on the jalapeno are surface mount not through-hole, although I suppose you can still make it work sort of. I have some surface mount right angle pin headers but I don't think they would fit because there are some components in front of the JTAG pins that I think would get in the way. I was thinking about just soldering the wires straight to the pads.
|
|
|
|
|