Experimenting with Jalapeno firmware...

[kano]

Additional information.

...
2) use the cgminer "java API stat" and look at the last miner (that should be last one due to hotplug)
...

"java API stats"

And it lists all the pools after the devices, so yes the last device (i.e. where [ID] != POOL* which come after the devices)

[ElitePork]

Thanks Ashitank.

Additional information.

...
2) use the cgminer "java API stat" and look at the last miner (that should be last one due to hotplug)
...

"java API stats"

And it lists all the pools after the devices, so yes the last device (i.e. where [ID] != POOL* which come after the devices)

Thanks for pointing that out.

Another tip, if you want to hardcode all engines to be running (regardless it's functional or not) change __TOTAL_DIAGNOSTICS_RUN from 10 to 0. It will skip all tests on the engines. Beware of the high HW error rate.

Next thing I wanna try is to change DO_NOT_USE_ENGINE_ZERO and overclocking it to 350mhz on the frequency and see what will happen. Hopefully it won't brick 

Last but not least to max out the fan speed (FAN_CONTROL_BYTE_REMAIN_FULL_SPEED) if the above is successful.

[K1773R]

Thanks Ashitank.

Additional information.

...
2) use the cgminer "java API stat" and look at the last miner (that should be last one due to hotplug)
...

"java API stats"

And it lists all the pools after the devices, so yes the last device (i.e. where [ID] != POOL* which come after the devices)

Thanks for pointing that out.

Another tip, if you want to hardcode all engines to be running (regardless it's functional or not) change __TOTAL_DIAGNOSTICS_RUN from 10 to 0. It will skip all tests on the engines. Beware of the high HW error rate.

Next thing I wanna try is to change DO_NOT_USE_ENGINE_ZERO and overclocking it to 350mhz on the frequency and see what will happen. Hopefully it won't brick  

Last but not least to max out the fan speed (FAN_CONTROL_BYTE_REMAIN_FULL_SPEED) if the above is successful.

fans are always @ max at the jalapeno model. engine 0 wont work
using nonworking engines is also bad, you cant overclock as high due to the voltage drop.

[BTC-engineer]

Does anyone know why it looks from all user-reports that engine 0 doesn't work?
In my 16-Asic Singles all engines 0 are disabled. But why?
Regarding the ASIC Datasheet from Butterflylabs all ASIC's should have 16 engines.
Also a look on to the ASIC Mask picture is clearly showing 16 (nearly) identical engines on the chip.

It's hard to believe that on all NON-Grad A chips engine 0 is not working. It would make much more sense if a more or less random engine doesn't work.

Does anyone know more about?

[KNK]

engine 0 not working is a design limitation. If you have a single chip in the device you can use engine 0, but if you enable engine 0 on the first chip from a chain - you loose the rest of the chips

[BTC-engineer]

engine 0 not working is a design limitation. If you have a single chip in the device you can use engine 0, but if you enable engine 0 on the first chip from a chain - you loose the rest of the chips

Interesting. I'm reading the first time about this. Where do you have this information from (link) ?

So this would mean that about ~6% hashing power of every ASIC is wasted, if multiple of them are on one PCB in a chain.
However, if a multiple ASICs per PCB design is handling the single ASIC's separately (not changed), it would have an advantage of about +6% hashing power over the other design, right?

I know that on the BFL PCB is also a FPGA or CPLD. I guess the chip-routing is going through this device and can be changed. Maybe with a another logic and an firmware update, the Engines 0 could be used. I have to take a look into the schematics.

[bitpop]

Nothing is wasted. They already deliver over spec.

[kano]

...
Last but not least to max out the fan speed (FAN_CONTROL_BYTE_REMAIN_FULL_SPEED) if the above is successful.

cgminer already does fan control as needed

[KNK]

Interesting. I'm reading the first time about this. Where do you have this information from (link) ?

I have read that on BFL forum, but can't provide a link, also i don't remember exactly if the problem was with the 'rest of the chips' or the 'rest of the engines'.
You should look in the source of the firmware, not in the schematics

[chanberg]

Anyone have a dragon to sell me on the cheap? 40-45 bucks shipped

let me know

Danny

[goxed]

Can we program the long boards (Little single / Single) with the Avalon DRAGON successfully?

[tom99]

Anyone have a dragon to sell me on the cheap? 40-45 bucks shipped

let me know

Danny

   You buy this open h/w and more use than Avr Dragon jtag http://www.seeedstudio.com/depot/bus-blaster-v3-p-1415.html?cPath=63_69


ps: Just restocks few days ago

[K1773R]

Can we program the long boards (Little single / Single) with the Avalon DRAGON successfully?

yes, but take the 1.2.6+ firmware due to XLINK

[K1773R]

btw, if anyone needs to have their jala flashed in switzerland and dosnt want to buy a dragon, just send me a PM

[BTC-engineer]

Can we program the long boards (Little single / Single) with the Avalon DRAGON successfully?

yes, but take the 1.2.6+ firmware due to XLINK

Theoretically this is clear to me. My singles report firmware version 1.2.6 and I saw the firmware version 1.2.6 release from Juke-Jr. From my experience with other companies, I know that sometimes companies do not cleanly declare version numbers. So it could be that the version in my singles is not exactly the same than the released one.
Beside of this, it could be that BFL is doing anything during there production/test process, which is writing additional information into the device, which could be lost by a flash update. Unfortunately I didn't yet find the time to look deep enough into the sourcecode to exclude something like this. I know all of what I'm writing about is not very likely but possible and the investment was high enough to think twice about risking to overwrite the flash, beside of loosing warranty. 

So, do you, or anybody else,  already has flashed your own compiled firmware based on the released version 1.2.6?

From what I've seen it should be enough to setup the product define correct for the target unit, right?

[K1773R]

Can we program the long boards (Little single / Single) with the Avalon DRAGON successfully?

yes, but take the 1.2.6+ firmware due to XLINK

Theoretically this is clear to me. My singles report firmware version 1.2.6 and I saw the firmware version 1.2.6 release from Juke-Jr. From my experience with other companies, I know that sometimes companies do not cleanly declare version numbers. So it could be that the version in my singles is not exactly the same than the released one.
Beside of this, it could be that BFL is doing anything during there production/test process, which is writing additional information into the device, which could be lost by a flash update. Unfortunately I didn't yet find the time to look deep enough into the sourcecode to exclude something like this. I know all of what I'm writing about is not very likely but possible and the investment was high enough to think twice about risking to overwrite the flash, beside of loosing warranty. 

So, do you, or anybody else,  already has flashed your own compiled firmware based on the released version 1.2.6?

From what I've seen it should be enough to setup the product define correct for the target unit, right?

yes, but there are 2 defines, 1 saying single and a little bit deeper jala (if single), youd have to change this. i cant remember correctly but i guess you should be able to figure it out
you cant really kill it, if you create a nonworking firmware, just create another one for it.
if the security bit is not set, i suggest dumping the actual firmware as a form of backup (the 1.0.0 had the security bit set, so you couldnt do this).
if BFL didnt want us to play with the firmware and reflash the units, why should they make it so easy for us to do it? (releasing firmware + nice jtag)

[BTC-engineer]

Can we program the long boards (Little single / Single) with the Avalon DRAGON successfully?

yes, but take the 1.2.6+ firmware due to XLINK

Theoretically this is clear to me. My singles report firmware version 1.2.6 and I saw the firmware version 1.2.6 release from Juke-Jr. From my experience with other companies, I know that sometimes companies do not cleanly declare version numbers. So it could be that the version in my singles is not exactly the same than the released one.
Beside of this, it could be that BFL is doing anything during there production/test process, which is writing additional information into the device, which could be lost by a flash update. Unfortunately I didn't yet find the time to look deep enough into the sourcecode to exclude something like this. I know all of what I'm writing about is not very likely but possible and the investment was high enough to think twice about risking to overwrite the flash, beside of loosing warranty. 

So, do you, or anybody else,  already has flashed your own compiled firmware based on the released version 1.2.6?

From what I've seen it should be enough to setup the product define correct for the target unit, right?

yes, but there are 2 defines, 1 saying single and a little bit deeper jala (if single), youd have to change this. i cant remember correctly but i guess you should be able to figure it out
you cant really kill it, if you create a nonworking firmware, just create another one for it.
if the security bit is not set, i suggest dumping the actual firmware as a form of backup (the 1.0.0 had the security bit set, so you couldnt do this).
if BFL didnt want us to play with the firmware and reflash the units, why should they make it so easy for us to do it? (releasing firmware + nice jtag)

So you have already flashed your single(s). Was it the 30 or 60 GH version?

[K1773R]

Can we program the long boards (Little single / Single) with the Avalon DRAGON successfully?

yes, but take the 1.2.6+ firmware due to XLINK

Theoretically this is clear to me. My singles report firmware version 1.2.6 and I saw the firmware version 1.2.6 release from Juke-Jr. From my experience with other companies, I know that sometimes companies do not cleanly declare version numbers. So it could be that the version in my singles is not exactly the same than the released one.
Beside of this, it could be that BFL is doing anything during there production/test process, which is writing additional information into the device, which could be lost by a flash update. Unfortunately I didn't yet find the time to look deep enough into the sourcecode to exclude something like this. I know all of what I'm writing about is not very likely but possible and the investment was high enough to think twice about risking to overwrite the flash, beside of loosing warranty.  

So, do you, or anybody else,  already has flashed your own compiled firmware based on the released version 1.2.6?

From what I've seen it should be enough to setup the product define correct for the target unit, right?

yes, but there are 2 defines, 1 saying single and a little bit deeper jala (if single), youd have to change this. i cant remember correctly but i guess you should be able to figure it out
you cant really kill it, if you create a nonworking firmware, just create another one for it.
if the security bit is not set, i suggest dumping the actual firmware as a form of backup (the 1.0.0 had the security bit set, so you couldnt do this).
if BFL didnt want us to play with the firmware and reflash the units, why should they make it so easy for us to do it? (releasing firmware + nice jtag)

So you have already flashed your single(s). Was it the 30 or 60 GH version?

no i dont have the single, i just read trough all the threads + source to get my information, im playing with 2 jalas atm (maybe i can get a hold of a single and some more jalas soon )
btw, another thing. if you flash your singles, carefully watch the temps as cooling will be crucial!

[chanberg]

Anyone have a dragon to sell me on the cheap? 40-45 bucks shipped

let me know

Danny

   You buy this open h/w and more use than Avr Dragon jtag http://www.seeedstudio.com/depot/bus-blaster-v3-p-1415.html?cPath=63_69


ps: Just restocks few days ago

have you used it to confirm it works??

[tom99]

Anyone have a dragon to sell me on the cheap? 40-45 bucks shipped

let me know

Danny

   You buy this open h/w and more use than Avr Dragon jtag http://www.seeedstudio.com/depot/bus-blaster-v3-p-1415.html?cPath=63_69


ps: Just restocks few days ago

have you used it to confirm it works??

  check out this link https://bitcointalk.org/index.php?topic=262558.0