ok after 30 rgh and many many jtags i have come across my first big block jasper . How do i know if its 256 or 512. nandpro states 128kb block size
First BB Jasper
- Thread starter AudioProUK
- Start date
hahahah ....yeah i dint think of that ...twat ,.hahaha
well theres 352 left so its got to be a 512 , thanks
well theres 352 left so its got to be a 512 , thanks
Last edited:
Martin C
VIP Member
Does it matter? Nope!
ALL non 16MB jaspers should be dumped and written using -r64 / -w64, with the exception of ecc which is +w64.
ALL non 16MB jaspers should be dumped and written using -r64 / -w64, with the exception of ecc which is +w64.
ahh ok... thanks martin . thought it was a bit of a wait for 512 mb .lol i did have a hunt but was reading -r512 and -w512 thought that seemed a bit weird
cheers bud
cheers bud
@martin c : im writting the image_00000000.ecc with +w64 and its stopping at 004f is that right , this damn thing is refusing point blank to glitch. its 6750 so thats not an issue . Ive got a 100nF cap on gnd and A now (all ive got) but nowt any advice ?? Seem to me that the green led is flashing faster than usual too .
Last edited:
eec only flashes to 004f I believe mate - did on my jaspers but they weren't big block
what did u use to create the ecc file?
I think Martin used a 680pf cap, and others like seanr28 used a 68nf cap
what did u use to create the ecc file?
I think Martin used a 680pf cap, and others like seanr28 used a 68nf cap
Last edited:
Yeah I think that was to just speed it up . This wont glitch at all . Damn thing . I read a post by uber and he said anywhere from 68 - 100nF is ok . bloody BB jaspers . When i run it through multibuilder would it tell me if it was using a donor CB or would it just come up with 6750 im asuming its a 6750 as thats what multibuild is telling me . tried degraded and it says bad file length but im assuming thats because its 64 not 16
created the ecc with MB 0.2
created the ecc with MB 0.2
Last edited:
Martin always uses mutlibuilder I believe and never has an issue, but I use bestpigs ecc generator - had a few issues with other ones, but I haven't used mutlibuilder I must admit lol
my Jasper would not glitch AT ALL untill I moved the CPU_RST wire away from the coils and used the bestpigs ecc......but as I say - it was only a 16MB mate
my Jasper would not glitch AT ALL untill I moved the CPU_RST wire away from the coils and used the bestpigs ecc......but as I say - it was only a 16MB mate
What are those "coils" that you guys always talk about?
I only got one that didn't glitched and the only way was to move the green wire around (as a matter of fact it was a tip from AudioProUK)
I only got one that didn't glitched and the only way was to move the green wire around (as a matter of fact it was a tip from AudioProUK)
ahh ive sussed it ....the green wire was a gnats cock into the resistor above . happily glitching now ...cheers guys !!!
the colils are the 2 round doughnut looking things on the top near the hana
BTW the 100nF is making a big diff to the boot times . 45secs without , 10 secs with !
the colils are the 2 round doughnut looking things on the top near the hana
BTW the 100nF is making a big diff to the boot times . 45secs without , 10 secs with !
Last edited:
- yes - coils are the copper donuts lolyeah it is .. its only got to be a hair width out and its game over , seems another symptom of that is a really fast flashing green light , not more regular but quicker flash.
I used Jtag Tool on my 256 jasper and i'm sure it read and wrote the full nand, took around 3/4 hour to read the nand.
So there is no need to backup the whole nand then?
can I get a pic of the green wire placement as my Jasper is really taking the piss now just will not glitch
Martin C
VIP Member
with 16MB Jaspers - you read the 16MB - with BB Jaspers you read 64MB - so reading 64MB when there is only 16MB would throw errors - do them as they should be done