Topic: Experimenting with Jalapeno firmware... - page 26. (Read 62593 times)
Interesting... Watching
danattacker, which jtag port is used? there seem to be two?
JTAG1
danattacker, which jtag port is used? there seem to be two?
JTAG1
I have high hopes for my 5 ghs jally.. but any increase is an increase.
my dragon programmer will be here in a few days, Ill be posting the results.
danattacker, which jtag port is used? there seem to be two?
my dragon programmer will be here in a few days, Ill be posting the results.
danattacker, which jtag port is used? there seem to be two?
Yeah I think most 5s can do 7. Actually one of mine has issues but the other I'm sure can do 7.
Josh stated that for 7GH version they will use binned chips.
From Shoutbox
From Shoutbox
Quote
The 7's will have chips that do 3.5 GH/s easy . The 5's may or may not, depends.
No I don't think bfl had time to bin them nor that many bad ones.
Cool. Cracking mine from 5 to 7 ghs would be awesome too. Hope we can do that at some point.
Do you realize that most likely the 5GH/s doesn't need to have all the engines in working order in the chips, but the 7GH/s probably does?
Cool. Cracking mine from 5 to 7 ghs would be awesome too. Hope we can do that at some point.
Hmm I thought the problem is they didn't support that?
Hope you greatnesses can answer these soon.
How to overclock/crack jalapenos?
How to fix p2pool?
For Jalapenos, you might be able to trivially hack them to work with p2pool in BFGMiner at least - without firmware changes.How to overclock/crack jalapenos?
How to fix p2pool?
Basically, you want to get it to use the noncerange interface instead of the bqueue interface.
Hope you greatnesses can answer these soon.
How to overclock/crack jalapenos?
How to fix p2pool?
How to overclock/crack jalapenos?
How to fix p2pool?
I don't suppose anyone has details about how to compile the firmware on linux? 
Atmel Studio exists on Linux as well.
Regards
Hmm after comments from Luke-Jr I've looked in the Fedora repositories and there are
RPMs of all of: gcc-avr32 4.7.1-0.1.20120606.fc18.1, binutils-avr32 2.23.51.0.3-1.fc18 and avrdude 5.11.1-2.fc18 ...
So it's a start at least ...
Damn, I'm gonna end up spending a lot of time with this
(better put it aside until I finish what I'm doing at the moment)
RPMs of all of: gcc-avr32 4.7.1-0.1.20120606.fc18.1, binutils-avr32 2.23.51.0.3-1.fc18 and avrdude 5.11.1-2.fc18 ...
So it's a start at least ...
Damn, I'm gonna end up spending a lot of time with this
(better put it aside until I finish what I'm doing at the moment)
I don't suppose anyone has details about how to compile the firmware on linux?
Atmel Studio exists on Linux as well.
Regards
I don't suppose anyone has details about how to compile the firmware on linux?
I have a "make" branch on GitHub with a Makefile.This is still very WIP-quality: I don't know if the output works at all.
But first, you need a toolchain...
Here's how to get one on Gentoo (not intended for novice users!):
Code:
crossdev -t avr32 -s1 # this will fail! but sets up stuff for us
# BEGIN binutils
mkdir -p /etc/portage/patches/cross-avr32/binutils/
cd /etc/portage/patches/cross-avr32/binutils/
PATCHES="
20-binutils.2.20.1-avr32-autoconf.patch
30-binutils-2.20.1-avr32-bfd.patch
31-binutils-2.20.1-avr32-binutils.patch
32-binutils-2.20.1-avr32-gas.patch
33-binutils-2.20.1-avr32-include.patch
34-binutils-2.20.1-avr32-ld.patch
35-binutils-2.20.1-avr32-opcodes.patch
40-binutils-2.20.1-avr32-fixes.patch
41-binutils-2.20.1-avr32-fpu.patch
42-binutils-2.20.1-avr32-bug-7435.patch
50-binutils-2.20.1-avr32-mxt768e.patch
51-binutils-2.20.1-avr32-uc3c.patch
52-binutils-2.20.1-avr32-uc3l0128.patch
53-binutils-2.20.1-avr32-uc3a4.patch
54-binutils-2.20.1-avr32-uc3d.patch
55-binutils-2.20.1-avr32-uc3l3l4.patch
"
for patch in $PATCHES; do
wget http://distribute.atmel.no/tools/opensource/avr32-gcc/binutils-2.20.1/$patch
done
# Possibly change make.conf to MAKEOPTS=-j1 - not sure if necessary
USE='-* multitarget' emerge =cross-avr32/binutils-2.20.1-r1
# interrupt build (Ctrl-Z) immediately after patches are applied
cd /var/tmp/portage/cross-avr32/binutils-2.20.1-r1/work/binutils-2.20.1
$EDITOR opcodes/Makefile.am # find avr-dis.c and add under it: avr32-asm.c avr32-dis.c avr32-opc.c
for d in . gold intl libiberty gprof ld binutils etc gas opcodes bfd; do ( cd "$d"; autoreconf; ); done
fg
aclocal -I config
autoconf
automake
autoheader
for d in bfd opcodes binutils gas ld; do
pushd $d
autoconf
automake
autoheader
popd
done
fg
# interrupt build (Ctrl-Z) after bfd has configured
cd /var/tmp/portage/cross-avr32/binutils-2.20.1-r1/work/build/bfd
make headers
fg
# DONE binutils
# BEGIN gcc
mkdir -p /etc/portage/patches/cross-avr32/gcc/
cd /etc/portage/patches/cross-avr32/gcc/
PATCHES="
30-gcc-4.4.3-avr32.patch
31-gcc-4.4.3-avr32-rmw.patch
32-gcc-4.4.3-avr32-sleep-builtin.patch
33-gcc-4.4.3-avr32-ucr3fp.patch
34-gcc-4.4.3-avr32-fpu.patch
35-gcc-4.4.3.avr32-delay-cycles.patch
36-gcc-4.4.3.avr32-list-devices.patch
40-gcc-4.4.3-avr32-fpemul-fixes.patch
41-gcc-4.4.3-avr32-fix-const_int_addr.patch
42-gcc-4.4.3-avr32-fix-reorg_opt_bug11763.patch
43-gcc-4.4.3-avr32-4_4_3-upgrade.patch
44-gcc-4.4.3-avr32-bug-12671.patch
45-gcc-4.4.3-avr32-bug-7435.patch
46-gcc-4.4.3-avr32-bug-9675.patch
50-gcc-4.4.3-avr32-mxt768e.patch
51-gcc-4.4.3-avr32-uc3c.patch
52-gcc-4.4.3-avr32-uc3l0128.patch
53-gcc-4.4.3-avr32-uc3a4.patch
54-gcc-4.4.3-avr32-uc3d.patch
55-gcc-4.4.3-avr32-uc3l3l4u.patch
"
for patch in $PATCHES; do
wget http://distribute.atmel.no/tools/opensource/avr32-gcc/gcc-4.4.3/$patch
done
USE='-*' ACCEPT_KEYWORDS=** emerge =cross-avr32/gcc-4.4.3-r3
# DONE gcc
# BEGIN atmel-headers
layman -a luke-jr
ACCEPT_KEYWORDS=** emerge cross-avr32/atmel-headers
# DONE atmel-headers
# BEGIN newlib
mkdir -p /etc/portage/patches/cross-avr32/newlib/
cd /etc/portage/patches/cross-avr32/newlib/
# skip 10-newlib-1.16.0-avr32-atmel-version.patch
PATCHES="
30-newlib-1.16.0-avr32.patch
31-newlib-1.16.0-flashvault.patch
"
for patch in $PATCHES; do
wget http://distribute.atmel.no/tools/opensource/avr32-gcc/newlib-1.16.0/$patch
done
ln -s /usr/portage/sys-libs/newlib /usr/portage/local/crossdev/cross-avr32/
USE=-* ACCEPT_KEYWORDS=** emerge =cross-avr32/newlib-2.0.0
# interrupt build (Ctrl-Z) immediately after source unpacks
cd /var/tmp/portage/cross-avr32/newlib-2.0.0/work/newlib-2.0.0/
for patch in $PATCHES; do
patch -p0 <"/etc/portage/patches/cross-avr32/newlib/$patch"
done
cd newlib
autoreconf
fg
# interrupt build (Ctrl-Z) immediately after you see:
# >>> Install newlib-2.0.0 into /var/tmp/portage/cross-avr32/newlib-2.0.0/image/ category cross-avr32
mkdir -p /var/tmp/portage/cross-avr32/newlib-2.0.0/image//usr/avr32/lib
# DONE newlib
ln -s /usr/lib/binutils/avr32/2.20.1/ldscripts/ /usr/avr32/lib/
I don't suppose anyone has details about how to compile the firmware on linux?
Virtualbox?
I don't suppose anyone has details about how to compile the firmware on linux?
The GetFrequency and SetFrequency never became operational. The reason is that we realized it's best to determine the frequency on startup. So I'm not sure if the command works at all or not.
Regards,
Regards,
Ah, ok that explains it. Thank you.
The GetFrequency and SetFrequency never became operational. The reason is that we realized it's best to determine the frequency on startup. So I'm not sure if the command works at all or not.
Regards,
Regards,
Jump to: