Topic: Experimenting with Jalapeno firmware... - page 16. (Read 62632 times)
Flash again
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 ?
What's a bam? Have you restarted the device?
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)
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)
Lol it tells you exactly what to do
I think you need to change the Device dropdown to match AT32UC3A1256. It currently shows AT32UC3A1128 as the selection.
make sure you got MCU 128 or 512.
maybe you u got AT32UC3A1xxx MCU.
maybe you u got AT32UC3A1xxx MCU.
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?
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?
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.
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.
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.
can other asics be overclocked, like the USB block erupters?
this section for BFL chip only.
can other asics be overclocked, like the USB block erupters?
Thanks for this. Upgraded my 5.5 Jalapeno to 8.1 GH/s .
Happy camper here.
I used a JTAGICE MKii with avrstudio 6 and the hex file released on the forums.
You can get an extra 0.2 GH/s out of it if you cool it below zero before plugging it in, so it will choose a higher frequency.
Happy camper here.
I used a JTAGICE MKii with avrstudio 6 and the hex file released on the forums.
You can get an extra 0.2 GH/s out of it if you cool it below zero before plugging it in, so it will choose a higher frequency.
Yes you must use zadig
thanks for the tip. Will try that when my 2 x jallies arrive next week
Yes you must use zadig
Got it. Cgminer working. Will take a little while for the hash rate to settle down and see how many errors I get with cgminer vs bfgminer. cgminer is reporting some HW nonce errors, with unit 1 having approx 3x more errors than unit 0.
Unit 0 (few errors) is running about 3.45 to 3.55v, Unit 1 (many more errors) always has a higher voltage by about 0.05v to 0.1v.
Just noticed in my Slush pool stats that my Jalapenos have found a block. Not bad after only a week. Pity I have to share it with the rest of the pool
On Windows OS (Win7 Ulti & WinXP, WinXP is a old noisy desktop but I used that to mine when i'm out for work. Win7 Ulti is my laptop and I used it to mine when i'm at home), I can't get bfgminer or cgminer working and both crashes on start up. I have had to use EasyMiner from BFL to get those jallies to start mining.
After reading that RaspPi can work on these jallies, I went to get one and spent 2 days to get it working. And the time spent is much worth it. I will suggest to get RaspPi for these 24/7 mining as it's much quieter and more configurable.
Back to the HW errors, my guess is the engines are giving the HW error. Based on the same configuration that the 2 jallies have, only possibility I can think of is the chip grading...
After reading that RaspPi can work on these jallies, I went to get one and spent 2 days to get it working. And the time spent is much worth it. I will suggest to get RaspPi for these 24/7 mining as it's much quieter and more configurable.
Back to the HW errors, my guess is the engines are giving the HW error. Based on the same configuration that the 2 jallies have, only possibility I can think of is the chip grading...
Yes you must use zadig
cgminer-nogpu still crashes at start up after reporting it cannot init the USB devices. I tried downloading the newer USB drivers from BFL's Driver page and installing them, but the installer reported I already have the updated drivers on my laptop.
Edit: I haven't switched to WinUSB so will try that and see how it goes.
Edit: I haven't switched to WinUSB so will try that and see how it goes.
Or you didn't switch usb drivers
Jump to: