I just got my coolrunner in today and I was obviously excited to get it up and running...
I picked up a used 360(Zephyr). I'm using JTAG Tool 4.25. I'm trying to create the ecc file now but i'm getting this:
I've done some searching but every thread I find ends without an answer. What I have found leads me to believe that this Zephyr may just not be supported. Coolrunner(and the rgh in general) is supposed to work on Zephyrs, so if that's the case, why are there no warnings??
I'd appreciate any help.
I picked up a used 360(Zephyr). I'm using JTAG Tool 4.25. I'm trying to create the ecc file now but i'm getting this:
Code:
* found flash image, unpacking...
ECC'ed - will unecc.
Found 2BL (build 4558) at 00008000
Found 4BL (build 4558) at 0000fa70
Found 5BL (build 1888) at 00015170
* found decrypted CD
* found XeLL binary, must be linked to 1c000000
* we found the following parts:
SMC: 2.3
CB_A: 4558
CB_B: missing
CD (image): 4558
CD (decrypted): 8453
* checking for proper 1BL key... ok
* decrypting...
* checking if all files decrypted properly... ok
* checking required versions... ok
* patching SMC...
CRC32: 9f436632
! Warning: can't patch that SMC, here are the current supported versions:
- Trinity, version 3.1
- Jasper, version 2.3
- Zephyr, version 1.10
- Zephyr, version 1.13
- Falcon, version 1.6
* zero-pairing...
* constructing new image...
* base size: 6c000
* No separate recovery Xell available!
* Flash Layout:
0x00000000..0x000001ff (0x00000200 bytes) Header
0x00000200..0x00000fff (0x00000e00 bytes) Padding
0x00001000..0x00003fff (0x00003000 bytes) SMC
0x00004000..0x00007fff (0x00004000 bytes) Keyvault
0x00008000..0x0000fa6f (0x00007a70 bytes) CB_A 4558
0x0000fa70..0x00015a6f (0x00006000 bytes) CD 8453
0x00015a70..0x000bffff (0x000aa590 bytes) Padding
0x000c0000..0x000fffff (0x00040000 bytes) Xell (backup)
0x00100000..0x0013ffff (0x00040000 bytes) Xell (main)
* Encoding ECC, please wait ...
------------- Written to image_00000000.ecc
Press any key to continue . . .
I'd appreciate any help.