Jasper 16, 256, 512 - how to tell?

[axelll]

Hi,

I just got a Jasper to RGH. How can I know how much memory it has? The date of manufacturing on the case is: 20.09.2009. I read that, all the jaspers made in 2009 have 512 RAM. Is that true? How else can I check?

Thanx

 

[cfull1]

Dump your nand with NandPro, it will tell you want size nand is.

Flash Config: 01198010 = 16MB (small block controller)
Flash Config: 00023010 = 16MB (big block controller)
Flash Config: 008A3020 = 256MB
Flash Config: 00AA3020 = 512MB

 

[Martin C]

Read my roadmap for n00bies post.

 

[oO Elite Oo]

Perhaps using the search feature and reading very carefully before posting would help. Its like submitting essay with our even researching.

 

[axelll]

Got stuck...

1. dumped 2 nands - they match
2. Bad blocks in first 50, image attached
3 Tried to repair the bad blocks as in the Martin post(Bad Block remapping for ecc (first 50 blocks) ), log below:

C:\Users\alex\Desktop\Nandpro>fc /b jasper1.bin jasper2.bin
Comparing files jasper1.bin and JASPER2.BIN
FC: no differences encountered

C:\Users\alex\Desktop\Nandpro>nandpro usb: -r16 nandecc.bin
NandPro v3.0a by Tiros
Looking for usb interface device
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x000000..0x0003FF
File: nandecc.bin
Reading
Error: 250 reading block 21
Error: 250 reading block 37
03FF

made image.ecc with 360 Multibuilder

C:\Users\alex\Desktop\Nandpro>nandpro usb: +w16 image_00000000.ecc
NandPro v3.0a by Tiros
Looking for usb interface device
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x000000..0x0003FF
File: image_00000000.ecc
Opt: Spare data will be initialized
Opt: Block markers will be initialized
Opt: Ecc will be re-calculated
Writing
Error: 202 Programming block 21
Error: 202 Programming block 37
004F

C:\Users\alex\Desktop\Nandpro>Nandpro nandecc.bin: +w16 image_00000000.ecc
NandPro v3.0a by Tiros
Using Virtual Nand Device File: nandecc.bin
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x000000..0x0003FF
File: image_00000000.ecc
Opt: Spare data will be initialized
Opt: Block markers will be initialized
Opt: Ecc will be re-calculated
Writing
004F

C:\Users\alex\Desktop\Nandpro>Nandpro nandecc.bin: -r16 bb1.bin 21 1
NandPro v3.0a by Tiros
Using Virtual Nand Device File: nandecc.bin
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x000021..0x000021
File: bb1.bin
Reading
0021

C:\Users\alex\Desktop\Nandpro>Nandpro nandecc.bin: -r16 bb2.bin 37 1
NandPro v3.0a by Tiros
Using Virtual Nand Device File: nandecc.bin
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x000037..0x000037
File: bb2.bin
Reading
0037

C:\Users\alex\Desktop\Nandpro>Nandpro usb: -w16 bb1.bin 3FF
NandPro v3.0a by Tiros
Looking for usb interface device
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x0003FF..0x0003FF
File: bb1.bin
Writing
03FF

C:\Users\alex\Desktop\Nandpro>Nandpro usb: -w16 bb2.bin 3FE
NandPro v3.0a by Tiros
Looking for usb interface device
Flash Config: 0x00023010
Block Size: 16KB Block Limits: 0x0003FE..0x0003FF
File: bb2.bin
Writing
03FE

Programmed CR with Jasper.xsvf

Coolrunner is trying to glitch, I get the green light flashing every 5 sec. I tried both PHAT and SLIM, nu glitch. Any idea?

 

[axelll]

pics attached. I used this layout since I've RGH'ed some Falcons and they glitched from 1st time.

 

[axelll]

last one

 

[axelll]

Got it fixed, changed the green wire layout(under the clamps) and now I'm in xell :-D

 

[axelll]

...problems again, sometimes it glitches ok, sometimes it glitches but only 3-4 rows of xell are displayed, sometimes it glitches and the screen is completly grey / artefacts and sometimes doesn't glitch at all. Any ideas? I tried to desolder / resolder, same thing. It glitches right first time after resoldering then glitches partially or at all. Should I use a cap?

 

[WNYConsoles]

Skimming through the thread and reading your last reply it sounds like it's freezing up due to interference so try re-routing your RST wire.

 

[axelll]

Thanx, CPU was fine, POST was messing XELL, rerouted and now it boots almost instantly.
One more thing:

- I have those 2 BB at 21 and 37(first 50)
- I made a repaired NAND after Martin "receipt
- Last step is to put nandflash.bin anx xenon.elf to USB stick and install from xell
- Those 2 bad blocks will not be written, right? Should I write them manually exactly as I did with .ecc?

Thanx

 

[Martin C]

Just build and write - Multi_builder / XeBuild / etc will deal with these bad blocks for you.

 

[axelll]

So, when I'll write nandflash.bin, should I use original nand and not the healed one, correct?

 

[Martin C]

When you create your RGH NAND, select your original untouched NAND dump and CPU key.

You then flash the created nandflash.bin to your console.

The only reason you have to manually write to the NAND is due to having bad blocks which needed to be remapped and even then that should have been using a copy of the original dump.

 

[axelll]

still no luck with xell, I tried rerouting wires, I even changed them, desoldered, resoldered...sometimes the console boots to XELL, sometimes freezes in xell window, sometimes xel rows freeze for a second then XELL continues loading and most of the times XELL isn't loading. Could there be a faulty CR? Or just interferences? I read that I could insulate the wires but the insulation foil should be grounded. I don't know what else to do...

 

[Wretched]

I use a cap on my 16mb jasper and it boots like the Falcons

 

[Martin C]

your CPU_PLL_BYPASS wire has too much exposed. Cut to max 2mm and resolder.

 

[axelll]

The capacitor must be of 68 nf, right?
OK, I'll try to resolder the PPL_BYPASS with less wire exposed first, If this does not do the trick, then I'll use the capacitor.

 

[axelll]

Should I try from the start with J-Runner? I saw that it corrects the bad blocks automaticaly if they are in first 50

 

[axelll]

Just build and write - Multi_builder / XeBuild / etc will deal with these bad blocks for you.

First time, when I got to flashing nandflash.bin and xenon.elf I had 2 errors writing block 21 and block 37. The console didn't boot and I remember I forgot to set the LDV in options.ini. Anyway, If the final nandflash image was not written on 21 and 37, I guess I must extract those blocks from nandflash.bin as bb1 and bb2 then write them manually to NAND, is that correct? This is what I meant with the post I'm quoting.