Hi all,
I just received my jalapenos and they came with 1.2.9. I tried reflashing the firmware but it appears that it is not working. Any idea what I have missed? I merely change the source from singles setting to jalapeno by commenting line 26 and uncommenting line 24...
Topic: BFL BitForce SC Firmware source code (Read 28021 times)
I just received my Jalapeno. Its hashing at 5.1 mhash and stays around 43 degrees with 25 degrees environment.
Is there any way to know which firmware mine has without purchasing a JTAG adapter?
in cgminer:Is there any way to know which firmware mine has without purchasing a JTAG adapter?
java API stats | egrep '\[GetIn| BA'
[GetInfo] is the full dump of the GetInfo reply from the BFL ASIC
Being a Jalapeno it will most likely be 1.0.0
Please pardon my lack of knowledge, but where would we put these commands? I didn't realize CGMiner was capable of taking inputs like this?
API-README
I just received my Jalapeno. Its hashing at 5.1 mhash and stays around 43 degrees with 25 degrees environment.
Is there any way to know which firmware mine has without purchasing a JTAG adapter?
in cgminer:Is there any way to know which firmware mine has without purchasing a JTAG adapter?
java API stats | egrep '\[GetIn| BA'
[GetInfo] is the full dump of the GetInfo reply from the BFL ASIC
Being a Jalapeno it will most likely be 1.0.0
Please pardon my lack of knowledge, but where would we put these commands? I didn't realize CGMiner was capable of taking inputs like this?
hi guys,
Just got my 30gh bfl sc. Its hashing happily at 32 gh but was wondering if I could squeeze some more out of it. Its running 1.2. firmware so looks like is bit out of date. Which firmware should I flash? Do I do it the same way as Jalla?
Cheers,
GetInfo.....................
DEVICE: BitFORCE SC
FIRMWARE: 1.2.1
IAR Executed: NO
CHIP PARALLELIZATION: YES @ 8
QUEUE DEPTH:40
PROCESSOR 0: 15 engines @ 362 MHz -- MAP: FFFE
PROCESSOR 1: 15 engines @ 348 MHz -- MAP: FFFE
PROCESSOR 2: 15 engines @ 389 MHz -- MAP: FFFE
PROCESSOR 3: 15 engines @ 350 MHz -- MAP: FFFE
PROCESSOR 4: 15 engines @ 404 MHz -- MAP: FFFE
PROCESSOR 5: 14 engines @ 408 MHz -- MAP: BFFE
PROCESSOR 6: 15 engines @ 420 MHz -- MAP: FFFE
PROCESSOR 7: 15 engines @ 359 MHz -- MAP: FFFE
THEORETICAL MAX: 45192 MH/s
ENGINES: 119
FREQUENCY: 274 MHz
XLINK MODE: MASTER
CRITICAL TEMPERATURE: 0
XLINK PRESENT: NO
OK
0x00
Just got my 30gh bfl sc. Its hashing happily at 32 gh but was wondering if I could squeeze some more out of it. Its running 1.2. firmware so looks like is bit out of date. Which firmware should I flash? Do I do it the same way as Jalla?
Cheers,
GetInfo.....................
DEVICE: BitFORCE SC
FIRMWARE: 1.2.1
IAR Executed: NO
CHIP PARALLELIZATION: YES @ 8
QUEUE DEPTH:40
PROCESSOR 0: 15 engines @ 362 MHz -- MAP: FFFE
PROCESSOR 1: 15 engines @ 348 MHz -- MAP: FFFE
PROCESSOR 2: 15 engines @ 389 MHz -- MAP: FFFE
PROCESSOR 3: 15 engines @ 350 MHz -- MAP: FFFE
PROCESSOR 4: 15 engines @ 404 MHz -- MAP: FFFE
PROCESSOR 5: 14 engines @ 408 MHz -- MAP: BFFE
PROCESSOR 6: 15 engines @ 420 MHz -- MAP: FFFE
PROCESSOR 7: 15 engines @ 359 MHz -- MAP: FFFE
THEORETICAL MAX: 45192 MH/s
ENGINES: 119
FREQUENCY: 274 MHz
XLINK MODE: MASTER
CRITICAL TEMPERATURE: 0
XLINK PRESENT: NO
OK
0x00
thanks all you guys for the pointers.
I made some off-the-head calculations and determined I'm better off using my time elsewhere than to try squeeze the last coins out of that little single.
I made some off-the-head calculations and determined I'm better off using my time elsewhere than to try squeeze the last coins out of that little single.
In addition to setting the correct #define, you'll also want to choose the correct microcontroller (AT32UC3A1128 or AT32UC3A1256) in the project settings. Just to be safe you could start with the same version of the firmware that your device came with and go from there.
hmm, I don't even know how to read the firmware version from the device.
java API stats ... it's in there
hmm, I don't even know how to read the firmware version from the device.
See post #34 in this thread. This thread is a good read, I'd recommend it. In addition to setting the correct #define, you'll also want to choose the correct microcontroller (AT32UC3A1128 or AT32UC3A1256) in the project settings. Just to be safe you could start with the same version of the firmware that your device came with and go from there.
hmm, I don't even know how to read the firmware version from the device.
Anyone care to point me to another one that might exist?
Try the thread over at BFL forums.https://forums.butterflylabs.com/announcements/3282-bitforce-sc-firmware-version-1-2-5-a.html
These other two threads deal mainly with jalapenos, but most of the information should also be relevant to singles, little singles, and perhaps even minirigs.
https://bitcointalksearch.org/topic/howto-flash-your-jalapeno-to-8-ghs-244235
https://bitcointalksearch.org/topic/experimenting-with-jalapeno-firmware-236875
In addition to setting the correct #define, you'll also want to choose the correct microcontroller (AT32UC3A1128 or AT32UC3A1256) in the project settings. Just to be safe you could start with the same version of the firmware that your device came with and go from there.
first: thanks luke-jr for your work.
I'm looking to squeeze the last coins out of my little single by ways of overclocking and took a look at this thread and the stuff in firmware sources std_defs.h.
Can someone wrap this up for me? What exactly can I change in the sourcecode to try to get more speed?
Is it reasonably safe to flash a firmware from https://github.com/luke-jr/BitForce_SC.git as long as I set the Product Model correctly ("#define __PRODUCT_MODEL_LITTLE_SINGLE__" in my case)? Should that already automatically try to get the fastest speed for each chip?
I also googled around, but this is the most meaningful thread I found so far. Anyone care to point me to another one that might exist?
thanks for your help.
I'm looking to squeeze the last coins out of my little single by ways of overclocking and took a look at this thread and the stuff in firmware sources std_defs.h.
Can someone wrap this up for me? What exactly can I change in the sourcecode to try to get more speed?
Is it reasonably safe to flash a firmware from https://github.com/luke-jr/BitForce_SC.git as long as I set the Product Model correctly ("#define __PRODUCT_MODEL_LITTLE_SINGLE__" in my case)? Should that already automatically try to get the fastest speed for each chip?
I also googled around, but this is the most meaningful thread I found so far. Anyone care to point me to another one that might exist?
thanks for your help.
I am also interested in this. I have a bunch of early batch little singles and would like to get them running with 0 because I can keep them in stable +4 C ambient temperature after few days.
first: thanks luke-jr for your work.
I'm looking to squeeze the last coins out of my little single by ways of overclocking and took a look at this thread and the stuff in firmware sources std_defs.h.
Can someone wrap this up for me? What exactly can I change in the sourcecode to try to get more speed?
Is it reasonably safe to flash a firmware from https://github.com/luke-jr/BitForce_SC.git as long as I set the Product Model correctly ("#define __PRODUCT_MODEL_LITTLE_SINGLE__" in my case)? Should that already automatically try to get the fastest speed for each chip?
I also googled around, but this is the most meaningful thread I found so far. Anyone care to point me to another one that might exist?
thanks for your help.
I'm looking to squeeze the last coins out of my little single by ways of overclocking and took a look at this thread and the stuff in firmware sources std_defs.h.
Can someone wrap this up for me? What exactly can I change in the sourcecode to try to get more speed?
Is it reasonably safe to flash a firmware from https://github.com/luke-jr/BitForce_SC.git as long as I set the Product Model correctly ("#define __PRODUCT_MODEL_LITTLE_SINGLE__" in my case)? Should that already automatically try to get the fastest speed for each chip?
I also googled around, but this is the most meaningful thread I found so far. Anyone care to point me to another one that might exist?
thanks for your help.
Why is engine 0 always disabled?
It doesn't work on RevA chips.On RevB chips, they run 300 MHz faster, so with engine 0 they can get up to 71 Gh/s.
But due to the higher heat producted, this was damaging chips, so engine 0 is disabled.
I've received a new batch of singles. Now with firmware version 1.2.9. They have Rev. B chips.
I can not confirm that engine 0 is always disabled by default. Some, but not all, processors have 16 engines enabled.
I will spend now more time with playing with this new singles.
Why is engine 0 always disabled?
It doesn't work on RevA chips.On RevB chips, they run 300 MHz faster, so with engine 0 they can get up to 71 Gh/s.
But due to the higher heat producted, this was damaging chips, so engine 0 is disabled.
I've received a further order of singles (60GHs). The new singles have firmware version 1.2.9 and it looks like they have Rev. B chips on board.
The latest released firmware source code seems to be 1.2.8. ( see https://github.com/luke-jr/BitForce_SC )
Does anyone know were to find the 1.2.9 source-code, or when it will be released?
It looks like you, Luke-Jr, have a pretty good contact to BFL. Is it possible to ask BFL to use your git-hub repository or at least send you a package of every new released (version on delivered machines) firmware version?
The latest released firmware source code seems to be 1.2.8. ( see https://github.com/luke-jr/BitForce_SC )
Does anyone know were to find the 1.2.9 source-code, or when it will be released?
It looks like you, Luke-Jr, have a pretty good contact to BFL. Is it possible to ask BFL to use your git-hub repository or at least send you a package of every new released (version on delivered machines) firmware version?
Why is engine 0 always disabled?
Looking through the source code luke-jr posted I found this in std_defs.h:
Code:
// **** Change log Vs 1.2.6
// - Engine 0 operation supported
// - Auto detect if chip is Revision B or A (Revision B has engine 0 functional)
// - Engine 0 operation supported
// - Auto detect if chip is Revision B or A (Revision B has engine 0 functional)
So my guess is that there are two revisions of the hashing chips and in revision A engine 0 is broken, but this is just speculation. There are quite a few special cases in the code dealing specifically with engine 0.
By the way, the .atsuo file does not belong in the repository. It stores per-user settings like the set of open windows.
(See suo file source control.)
(See suo file source control.)
Is it safe to flash 1.2.6 to my Jaly? Im running 1.2.5 at the moment so do I flash it as per Kano guide?
I cannot support this.Luke, could you post compiled binary for Jaly?
I don't have a verified working compile procedure yet.Note that the 1.2.5 binary was for Little Singles only.
Hi,
Is it safe to flash 1.2.6 to my Jaly? Im running 1.2.5 at the moment so do I flash it as per Kano guide?
Luke, could you post compiled binary for Jaly?
Is it safe to flash 1.2.6 to my Jaly? Im running 1.2.5 at the moment so do I flash it as per Kano guide?
Luke, could you post compiled binary for Jaly?
Why is engine 0 always disabled?
Updated OP with 1.2.6.
Jump to: