Experimenting with Jalapeno firmware...

[kano]

cgminer doesn't care that the firmware thinks it is, I use the chip count to decide that.

[1714992817]

1714992817

[1714992817]

1714992817

[1714992817]

1714992817

[ElitePork]

Thanks Ashitank.

...

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.

Tested comment out DO_NOT_USE_ENGINE_ZERO and the jally won't start up.
Attempted to change the frequency from 291 to 350 but it still falls back to 280+. So I went to look into the codes and found that there is a method that detects the frequency and write it back. So I hardcoded the frequency to 350MHz. Starts up and runs @ 9GH/s but has near to 50% HW errors. So it's a fail.

I guess that's all for me know until my new jallies are shipped.
Regards
EP

[bitpop]

hope ck releases a single firmware and maybe updates jalapeno to 1.2.6

[fforforest]

Anyone flashed a single?

JTAG1 I get to low voltage using AT32UC3A1128/AT32UC3A1156
JTAG2 I cant read deviceid using AT32UC3A1128/AT32UC3A1156

Any ideas?

[K1773R]

i got a AT32UC3A1256. after you put the newer firmare on the dragon it showed up as AT32UC3A1256, before it showed as AT32UC3A1128 too.

[fforforest]

This is how it looks on my BFL Single, always worked on the jalapenos.

https://i.imgur.com/tgJKehg.jpg

[bitpop]

Is your cable backwards?

[fforforest]

Is your cable backwards?

Odd, it was backwards.
Thank you!

[BTC-engineer]

I've just connected my JTAG-ICE mkII to one of my singles.

The security-bit was also set on the singles, so after an erase there is no easy way back to the original firmware :-(

The interesting question is now, who is willing to take the risk first?

I've studied the sourcecode a little bit and found a lot of interesting places to play around.

[BTC-engineer]

I couldn't wait any longer and had to take the risk :-)

Just reflashed one of my singles with my first modified firmware.
Now I'm busy...

[tom99]

I couldn't wait any longer and had to take the risk :-)

Just reflashed one of my singles with my first modified firmware.
Now I'm busy...

  are you getting good hashrate for flashing new firmware?

[shackleford]

I've just connected my JTAG-ICE mkII to one of my singles.

The security-bit was also set on the singles, so after an erase there is no easy way back to the original firmware :-(

The interesting question is now, who is willing to take the risk first?

I've studied the sourcecode a little bit and found a lot of interesting places to play around.

I have been staring at the dragon I ordered a while back and contemplating. I am not really a trail blazer.. not in this circumstance anyway.

I am a bit confused and from what Luke was saying on that other thread it seems like the dragon would not work for singles but since they use it for Jalas I am thinking that can't be right.  Mine runs at 60 on the dot so I am thinking there is headroom.

I read it again, maybe the dragon will not work comment is just for the "TUMPA" JTAG interface

[soy]

Worked flawlessly, did it on 2 units. Do be careful, they are smt

How did bending the pins go?  I'm really good at snapping them off.

Just a thought, using wirewrap to bring the pins out to another set of pins, once, and leaving it in place.  Wirewrap is nice because the original pins are unchanged, adjacent pins can be wrapped without fear of shorting if done properly.  The connector one brings the wires out to can be prepared in advance while your waiting for a programmer to arrive.  Once in place buzz out your work to make sure the pins correspond.  Maybe get a spare female connector to put in place when you're done so as not to leave the pins of the added connector exposed.  Someday you may want to remove the connector, just reverse the wirewrap tool and unwrap the wires.

[K1773R]

Worked flawlessly, did it on 2 units. Do be careful, they are smt

How did bending the pins go?  I'm really good at snapping them off.

Just a thought, using wirewrap to bring the pins out to another set of pins, once, and leaving it in place.  Wirewrap is nice because the original pins are unchanged, adjacent pins can be wrapped without fear of shorting if done properly.  The connector one brings the wires out to can be prepared in advance while your waiting for a programmer to arrive.  Once in place buzz out your work to make sure the pins correspond.  Maybe get a spare female connector to put in place when you're done so as not to leave the pins of the added connector exposed.  Someday you may want to remove the connector, just reverse the wirewrap tool and unwrap the wires.

how about this?

[soy]

Worked flawlessly, did it on 2 units. Do be careful, they are smt

How did bending the pins go?  I'm really good at snapping them off.

Just a thought, using wirewrap to bring the pins out to another set of pins, once, and leaving it in place.  Wirewrap is nice because the original pins are unchanged, adjacent pins can be wrapped without fear of shorting if done properly.  The connector one brings the wires out to can be prepared in advance while your waiting for a programmer to arrive.  Once in place buzz out your work to make sure the pins correspond.  Maybe get a spare female connector to put in place when you're done so as not to leave the pins of the added connector exposed.  Someday you may want to remove the connector, just reverse the wirewrap tool and unwrap the wires.

how about this?

Nice.  The problem I've found with the grasp clips is that the clip bends and can be reshaped back only so many times before it snaps.

[bitpop]

My clips didn't work, they weren't u shaped but open.

[bitminterlt]

Thanks Ashitank.

...

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.

Tested comment out DO_NOT_USE_ENGINE_ZERO and the jally won't start up.
Attempted to change the frequency from 291 to 350 but it still falls back to 280+. So I went to look into the codes and found that there is a method that detects the frequency and write it back. So I hardcoded the frequency to 350MHz. Starts up and runs @ 9GH/s but has near to 50% HW errors. So it's a fail.

I guess that's all for me know until my new jallies are shipped.
Regards
EP

I can't seem to find the area where you can hardcode the frequency to set number, IE my jallys get up to 266 and 274 on each one. I would like to get them up to like 280 and see what happens from there and tune as needed.

Thanks for all the rest of the info!

[ElitePork]

I can't seem to find the area where you can hardcode the frequency to set number, IE my jallys get up to 266 and 274 on each one. I would like to get them up to like 280 and see what happens from there and tune as needed.

Thanks for all the rest of the info!

With reference to the firmware 1.2.6, ASIC_Engine.c line 1580, where you can see it is trying to set the frenquency. I tried changing the iFreqFactor to 350000000 but it gives me alot of HW error...
Note that it will not change the GetInfo details of the chips... because the details are calculated in another method...
Regards

[goxed]

I couldn't wait any longer and had to take the risk :-)

Just reflashed one of my singles with my first modified firmware.
Now I'm busy...

Kudos!! Please start a new thread with your results.

[BTC-engineer]

I couldn't wait any longer and had to take the risk :-)

Just reflashed one of my singles with my first modified firmware.
Now I'm busy...

  are you getting good hashrate for flashing new firmware?

My singles already reported to have the newest, official firmware version 1.2.6.
So by flashing it with this (unmodified) version, you should not expect any over-all hashrate increase. 
There is a little surprise about the delivered firmware version.

I could get better over-all hashrate after modifying the firmware.

I will open a new threat about my experience.