Experimenting with Jalapeno firmware...

[sdminer]

can other asics be overclocked, like the USB block erupters?

[tom99]

can other asics be overclocked, like the USB block erupters?

  this section for BFL chip only.

[Belkaar]

Has anyone found out why the variable

DO_NOT_USE_ENGINE_ZERO is set in the std_defs.h seems to me that this would allow almost 9 GHs/s if it would work. I'll do a little digging in the code before trying it...

Edit:

Does not change anything except it seems to have broken something. After flashing back the unmodified 1.2.5 cgminer shows all wrong statistics.

"BAJ 0:  max 61C 3.82V | 2.452G/575.5Gh/s | A: 152 R:0 HW: 1 WU: 8280.0/m"

But there is 8.1 GH/s hitting the pool.

[-ck]

Only 15 of the 16 engines in each chip can be used with the current design so you can't enable engine 0. If you try to enable it, you will be unable to run more than one chip so you'll be limited to ~4.5GH.

[Sztef89]

Please help I am doing everything according to the instructions...
Tested on Windows 8 and XP, the same error :/ Erase chips work perfect.
This error show up when I click on "Read" in "JTAG id" section
What can I do?

[tom99]

make sure you got MCU 128 or 512.

maybe you u got AT32UC3A1xxx MCU.

[macromode]

I think you need to change the Device dropdown to match AT32UC3A1256. It currently shows AT32UC3A1128 as the selection.

[bitpop]

Lol it tells you exactly what to do

[Sztef89]

I think you need to change the Device dropdown to match AT32UC3A1256. It currently shows AT32UC3A1128 as the selection.

Thank you ! That helps, but there is another problem :/

Cgminer log:

Code:

 BAM0: RequestQueJobStatus failed  x-1 (err=0 amt=15)
 BAM0: x-1 result too small (ERR:NO RESPONSE0x00) ignored
 BAM0: RequestQueJobStatus failed  x-1 (err=0 amt=15)
 BAM0: x-1 result too small (ERR:NO RESPONSE0x00) ignored
 BAM0: RequestQueJobStatus failed  x-1 (err=0 amt=15)
 BAM0: x-1 result too small (ERR:NO RESPONSE0x00) ignored
 BAM0: RequestQueJobStatus failed  x-1 (err=-7 amt=15)
 BAM0: GetResults failed  x-1 (err=-7 amt=15)
 BAM0: RequestQueJobStatus failed  x-1 (err=-7 amt=15)

[Sztef89]

Lol it tells you exactly what to do

indeed! I did not notice

again, but full cgminer log:

Code:

 cgminer version 3.3.0 - Started: [2013-07-15 23:42:01]
--------------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:0  HW:0  U:0.0/m  WU:0.0/m
 ST: 2  SS: 0  NB: 1  LW: 10888  GF: 0  RF: 0
 Connected to 192.168.1.55 diff 8 with stratum as user Sztef89_erupter
 Block: 00839637dd3d8d31...  Diff:26.2M  Started: [23:42:01]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 BAM 0:  max  0C 0.00V |  0.000/ 0.000h/s | A:0 R:0 HW:0 U:0.00/m

--------------------------------------------------------------------------------

 [2013-07-15 23:42:14] BAM0: x-1 result too small (ERR:NO RESPONSE0x00) ignored
 [2013-07-15 23:42:15] BAM0: RequestQueJobStatus failed  x-1 (err=-7 amt=15)
 [2013-07-15 23:42:16] BAM0: GetResults failed  x-1 (err=-7 amt=15)
 [2013-07-15 23:42:17] BAM0: x-1 result too small (ERR:NO RESPONSE0x00) ignored
 [2013-07-15 23:42:18] BAM0: RequestQueJobStatus failed  x-1 (err=0 amt=15)
 [2013-07-15 23:42:19] BAM0: GetResults failed  x-1 (err=-7 amt=15)
 [2013-07-15 23:42:20] BAM0: RequestQueJobStatus failed  x-1 (err=-7 amt=15)
 [2013-07-15 23:42:21] BAM0: GetResults failed  x-1 (err=-7 amt=15)
 [2013-07-15 23:42:22] BAM0: RequestQueJobStatus failed  x-1 (err=-7 amt=15)

[bitpop]

What's a bam? Have you restarted the device?

[Sztef89]

What's a bam? Have you restarted the device?

Ofcourse, I restarted device.

I asume BAM is my jalapeno... before flashing was BAJ, I think...

I check in my Windows 8 and Ubuntu... the same errors... before flashing everything worked properly.
What can I do ?

[bitpop]

Flash again

[tom99]

  most like bad flashed and you need to do it again and what firmware are you flashed to your Jal.

[cp1]

If flashing again doesn't help, make sure you have the latest cgminer.

[yonvanom]

What's a bam? Have you restarted the device?

Ofcourse, I restarted device.

I asume BAM is my jalapeno... before flashing was BAJ, I think...

I check in my Windows 8 and Ubuntu... the same errors... before flashing everything worked properly.
What can I do ?

BAM means BFL ASIC Minirig, so it looks like it's not being identified properly.
Did you compile the firmware yourself or did you use the precompiled .hex? If you compiled it yourself, I'd try flashing it again with the precompiled .hex.

[cp1]

BAM means BFL ASIC Minirig, so it looks like it's not being identified properly.
Did you compile the firmware yourself or did you use the precompiled .hex? If you compiled it yourself, I'd try flashing it again with the precompiled .hex.

Ah good catch, could be an incorrect define in the header.

[Sztef89]

I build myself code in Atmel Studio
https://forums.butterflylabs.com/announcements/3282-bitforce-sc-firmware-version-1-2-5-a.html

I tried three times but did not help... the same errors
I use newest cgminer 3.3.0

If you compiled it yourself, I'd try flashing it again with the precompiled .hex.

Where I get this precompiled hex ?

[cp1]

The hex is in this post:  https://bitcointalk.org/index.php?topic=244235.0

[Sztef89]

The hex is in this post:  https://bitcointalk.org/index.php?topic=244235.0

Flashed this hex, but still not working... :/ maybe this firmware isn't compatible with cgminer 3.3.0 ?