Program Shuriken Video V3 Please Help!

[bytesaber]

Was the verifying successful without shorting?

Is JP1 the through hole pair of pads next to R4? Do I literally just short them, or should a capacitor or something be used?

It appears that it was not successful on verify, without shorting. I did not realize that I should have closed JP1. I will continue with the recompile, and more appropriate flashing program before trying again. Looks like I need to rebuild the cable based on your parallel port design. (4x 100ohms on different pins.)

I never recompiled anything. I just took the .bin as is.

For science, here is the output from happy_bunny's flasher + his parallel port schematic + open JP1 + his spi_flash.bin from gcdv_update_0_5.zip + having a xc3s200a instead of xc3S50a. (whew!)

Spoiler

Show

Z:\Console Stuff\Gamecube\shuriken\parallelport\fpga_flash>fpga_flash.exe spi_flash.bin
Opening parallel port LPT1
On windows system 2
setting ECP port to SPP bidirectional mode
serial flash in idle state 0x00

Bulk erasing flash checking status...
status = 00
done!
programming code..
214 pages ...
programming at 213
done, verifying...
!!! page 0 failed to verify
046: bf != aa
047: ff != 99
048: ff != 30
049: ff != a1
04a: ff != 00
04b: ff != 07
04c: ff != 20
04d: ff != 00
04e: ff != 31
04f: ff != 61
050: ff != 09
051: ff != ee
052: ff != 33
053: ff != 21
054: ff != 3c
055: ff != 0f
056: ff != 31
057: ff != a1
058: ff != 00
059: ff != 49
05a: ff != 31
05b: ff != 41
05c: ff != 2f
05d: ff != 08
05e: ff != 31
05f: ff != c2
060: ff != 02
061: ff != 21
062: ff != 00
063: ff != 93
064: ff != 30
065: ff != e1
067: ff != cf
068: ff != 30
069: ff != c1
06a: ff != 00
06b: ff != 81
06c: ff != 31
06d: ff != 81
06e: ff != 08
06f: ff != 81
070: ff != 32
071: ff != 01
072: ff != 00
073: ff != 1f
074: ff != 32
075: ff != c1
076: ff != 00
077: ff != 05
078: ff != 32
079: ff != e1
07a: ff != 00
07b: ff != 04
07c: ff != 32
07d: ff != a1
07e: ff != 00
07f: ff != 0e
080: ff != 32
081: ff != 61
082: ff != 00
083: ff != 00
084: ff != 32
085: ff != 81
086: ff != 00
087: ff != 00
088: ff != 33
089: ff != 41
08a: ff != 18
08b: ff != f2
08c: ff != 33
08d: ff != 62
08e: ff != 00
08f: ff != 00
090: ff != 00
091: ff != 00
092: ff != 30
093: ff != 22
094: ff != 00
095: ff != 00
096: ff != 00
097: ff != 00
098: ff != 30
099: ff != a1
09a: ff != 00
09b: ff != 01
09c: ff != 50
09d: ff != 60
09e: ff != 00
09f: ff != 00
0a0: ff != 6a
0a1: ff != 60
0a2: ff != 00
0a3: ff != 00
0a4: ff != 00
0a5: ff != 84
0a6: ff != 00
0a7: ff != 10
0a8: ff != 00
0a9: ff != 00
0aa: ff != 40
0ab: ff != 00
0ac: ff != 00
0ad: ff != 00
0ae: ff != 00
0af: ff != 00
0b0: ff != 00
0b1: ff != 00
0b2: ff != 00
0b3: ff != 00
0b4: ff != 00
0b5: ff != 00
0b6: ff != 00
0b7: ff != 00
0b8: ff != 00
0b9: ff != 00
0ba: ff != 00
0bb: ff != 00
0bc: ff != 00
0bd: ff != 00
0be: ff != 00
0bf: ff != 00
0c0: ff != 00
0c1: ff != 00
0c2: ff != 00
0c3: ff != 00
0c4: ff != 00
0c5: ff != 00
0c6: ff != 00
0c7: ff != 00
0c8: ff != 00
0c9: ff != 00
0ca: ff != 00
0cb: ff != 00
0cc: ff != 00
0cd: ff != 00
0ce: ff != 00
0cf: ff != 00
0d0: ff != 00
0d1: ff != 00
0d2: ff != 00
0d3: ff != 00
0d4: ff != 00
0d5: ff != 00
0d6: ff != 00
0d7: ff != 00
0d8: ff != 00
0d9: ff != 00
0da: ff != 00
0db: ff != 00
0dc: ff != 00
0dd: ff != 00
0de: ff != 00
0df: ff != 00
0e0: ff != 00
0e1: ff != 00
0e2: ff != 00
0e3: ff != 00
0e4: ff != 00
0e5: ff != 00
0e6: ff != 00
0e7: ff != 00
0e8: ff != 00
0e9: ff != 00
0ea: ff != 00
0eb: ff != 00
0ec: ff != 00
0ed: ff != 00
0ee: ff != 00
0ef: ff != 00
0f0: ff != 00
0f1: ff != 00
0f2: ff != 00
0f3: ff != 00
0f4: ff != 00
0f5: ff != 00
0f6: ff != 00
0f7: ff != 00
0f8: ff != 00
0f9: ff != 00
0fa: ff != 00
0fb: ff != 00
0fc: ff != 00
0fd: ff != 00
0fe: ff != 00
0ff: ff != 00

done!
Z:\Console Stuff\Gamecube\shuriken\parallelport\fpga_flash>

[bytesaber]

We've discussed the slow programming with happy_bunny but he never fixed the old app. If you can recompile it just make all "sleep" "Sleep" (read the last pages viewtopic.php?f=3&t=2810&start=175 ).

I did not realize happy_bunny's app was never fixed. How time is handled with sleep() vs Sleep(), and effects his flashing app makes sense to me now. Late last night in the AM hours, I had both happy_bunny's parallel port schematic up, and yours. As well as which program to use for either. I just went with happy_bunny's for curiosity. I'll use your approach next.

This is not meant as a negative response to happy_bunny. Just stating that I see clearer now. I'll have to make a new guide or something after this. Thanks!

[bytesaber]

You can probe the red one for voltage to see if it's working with the "wrong" fpga :

I measured 2.1v at that pin to chasis ground.

[bytesaber]

I switched to SPIPGM. My flash erases fine. However during programming I get mismatched size warnings. Verify is full of errors.

Where does a capacitor go in your diagram? I don't see one. Why is pin 1 and 14 blue?

I'm using a M25P40

[bytesaber]

Get the compiler from here 5.9.0 or newer. https://sourceforge.net/projects/orwell ... 0Releases/

What am I compiling? Can I not just download the ready to go .bin from github? https://github.com/ikorb/gcvideo/blob/m ... v3-2.3.bit

I downloaded that, and then ran:

Code: Select all

promgen -spi -p bin -o gcvideo-dvi-shuriken-v3-2.3.bin -s 512 -u 0 gcvideo-dvi-shuriken-v3-2.3.bit

I then flashed gcvideo-dvi-shuriken-v3-2.3.bin

Code: Select all

spipgmw /i
spipgmw /u
spipgmw /e
spipgmw /b
spipgmw /p gcvideo-dvi-shuriken-v3-2.3.bin
spipgmw /v gcvideo-dvi-shuriken-v3-2.3.bin

/i , /u , /e, and /b, all looked great.

/p claimed unexpected end of file. I think that's just simply because the flash is 4Mbit and the .bin is smaller.
/v however, produced many errors.

Sorry for all the posts. Am I on the right path? It does not work. I can confirm the cube is booting by watching it on the composite side during a test. No joy on hdmi. Just blank.

[TALANTO]

The diagram you've found in my posts was for using the board only (not attached to GC). In your case don't put battery or other power source!

Is JP1 the through hole pair of pads next to R4? Do I literally just short them, or should a capacitor or something be used?

Yes, it is. Just short.

Looks like I need to rebuild the cable based on your parallel port design. (4x 100ohms on different pins.)

You don't have to if you use happy_banny's app only. I've changed it because I wanted to use one programmer for both apps.

I never recompiled anything. I just took the .bin as is.

This file is for xc3S50a.

For science, here is the output from happy_bunny's flasher + his parallel port schematic + open JP1 + his spi_flash.bin from gcdv_update_0_5.zip + having a xc3s200a instead of xc3S50a. (whew!)

Totally wrong. One error and it won't work you have hundreds. Short the jumper.

How time is handled with sleep() vs Sleep()

tueidj explains.

I measured 2.1v at that pin to chasis ground.

I've expected 1.8v but never actually measure it without the PCB. I think this is the GC listening high and your board doesn't work. If works it should be 3.3v.

I switched to SPIPGM. My flash erases fine. However during programming I get mismatched size warnings.

It expects 512K but the bin file is less memory. It's OK if you first erase than program. You also use hex editor and fill the file wit FF up to 512K.

Verify is full of errors.

Short JP1.

Where does a capacitor go in your diagram? I don't see one.

I don't think you need a capacitor in your setup. My setup was with lithium battery (without GC, FPGA, everything).
It's connected to +3.3v (3.0v) and GND. Back then I thought that it helps for verifying but it failed again.

Why is pin 1 and 14 blue?

It's not mine I don't know. Don't wary you don't need them.

I'm using a M25P40

Me too.

What am I compiling?

If you use SPIPGM nothing.

Can I not just download the ready to go .bin from github?

It's not *.bin it's bit file. Different file for different "programmer".

/p claimed unexpected end of file. I think that's just simply because the flash is 4Mbit and the .bin is smaller.

Yes.

/v however, produced many errors.

First short JP1, program the chip and verify. Isolate JP1 and try if it works.

If you still get errors You can try shorter (thicker) wires.

At last you can remove one resistor for better communication.
But let mi check which one. You will burn the flash memory + other stuff (even GC) if you send 5v without voltage drop resistor.

Edit:
Make two dumps to see what fails:

Code: Select all

spipgmw /d file1.bin

Compare with hex editor if the files match programming fails if not verifying fails.

[TALANTO]

Do it on your own risk.
It may reduce errors while verifying:

[bytesaber]

The diagram you've found in my posts was for using the board only (not attached to GC). In your case don't put battery or other power source!

Fear not. I used the GC for power. I did not add any battery or additional voltage. I did ground parallel pin 18 though. I just attached it to the GC chassis. Good to know still.

Looks like I need to rebuild the cable based on your parallel port design. (4x 100ohms on different pins.)

You don't have to if you use happy_banny's app only. I've changed it because I wanted to use one programmer for both apps.

This is a valuable note to be made known. I did not realize this was the case.

I switched to SPIPGM. My flash erases fine. However during programming I get mismatched size warnings.

It expects 512K but the bin file is less memory. It's OK if you first erase than program. You also use hex editor and fill the file wit FF up to 512K.

Another really good point for people to be aware of. I can see this being perceived as an error. The OCD in me might fill in the space with FF

Where does a capacitor go in your diagram? I don't see one.

I don't think you need a capacitor in your setup. My setup was with lithium battery (without GC, FPGA, everything).
It's connected to +3.3v (3.0v) and GND. Back then I thought that it helps for verifying but it failed again.

I see. This diagram is used in other google search results, asking about the same topic. Those places also contain comments from people suggesting "Besure to use the capacitor!" So I was never able to see where they were adding it. Okay, so being powered by a Gamecube makes it irrelevant then.

If you still get errors You can try shorter (thicker) wires.

I will try shorter and larger gauge. Right now I am just using 30awg and long convenient lengths
I did have JP1 closed for all programming attempts. I opened JP1 during tests. I should just order a programmer However, I admit this can be fun.


I'll go over the other suggestions in the next day or so. Thanks again!

[Unseen]

I measured 2.1v at that pin to chasis ground.

I've expected 1.8v but never actually measure it without the PCB. I think this is the GC listening high and your board doesn't work. If works it should be 3.3v.

Although the table on the GameSX-Wiki says "pull high 1.8v", I found that this is actually just the threshold voltage at which the Cube starts to detect that the pin is pulled high. As far as I can tell it's just a standard 3.3V-logic-level input, so the GCVideo-DVI-FPGA outputs 3.3V there. Even in the Wii (which mostly runs on 1.8V signals) the equivalent signal is still pulled to 3.3V by the official component cable.

[TALANTO]

I did ground parallel pin 18 though. I just attached it to the GC chassis. Good to know still.

Is it soldered? You don't use your hand to make connection, right?
I don't know what the "chassis" means. Is it the metal shielding or ground edges around the motherboard? I wouldn't use the shielding.

Besure to use the capacitor!

I've tried with/without and lower value capacitor, the result was pretty much the same. But in the final product I have 1000uF capacitor.

I will try shorter and larger gauge.

You can use those pads for the thicker wires.


About the resistor. I meant if you remove wrong resistor you will burn at least the flash memory. My programmer doesn't have resistor on MISO line.

Although the table on the GameSX-Wiki says "pull high 1.8v", I found that this is actually just the threshold voltage at which the Cube starts to detect that the pin is pulled high. As far as I can tell it's just a standard 3.3V-logic-level input, so the GCVideo-DVI-FPGA outputs 3.3V there. Even in the Wii (which mostly runs on 1.8V signals) the equivalent signal is still pulled to 3.3V by the official component cable.

So 1.8v is the minimum. I was wondering if 3.3v is too much.

[bytesaber]

Still no verify success. Address results change too. Starting to wonder if my "old pc" is odd. The northbridge is an nforce 2 ultra, so the southbridge is one in that really old nvidia chipset series. I then tried another parallel port. A 1x pci-e card in my 1st gen i7 system. I bound a Windows XP VM to use it (since the host is Windows 10), and it had parity errors.

Anyhow, I ordered a xilinx programmer. Noticed it did not have any LED's on it. Is this one "less cool"?

I will go back to the beginning of this thread, and follow the original poster's journey.

[bytesaber]

Connected my programmer. Followed steps from Xilinx documentation, linked earlier in this thread. I was able to make the proper .mcs file, from the original .bit file. Using gcvideo-dvi-shuriken-v3-2.3.bit

Once loaded up, Flash fails to erase.

Swapped the flash mem for another. Same result.

[bytesaber]

Still tyring to program this. Thought I would post a log. I would appreciate any suggestions. This log contains some errors at the top, where I did not have my power connected well. Onec that was tight, I proceeded to attempt erasing the flash. It fail. I tried it several times. I also then attempted to click "program" on both flash and the fpga itself.

Initialize chain, detecting the FPGA succeeded just fine. I manually added the SPI Flash.

I am using an xc3S200a.
.bit file = gcvideo-dvi-shuriken-v3-2.3.bit
.mcs file = Followed the iMpact documentation, and created the .mcs file from the .bit, to match my flash size. 4Mb.

Here is my log. Thanks.

Code: Select all

Welcome to iMPACT
iMPACT Version: 14.7
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bs
GUI --- Auto connect to cable...
// *** BATCH CMD : setCable -port auto
INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.4
INFO:iMPACT - Digilent Plugin: no JTAG device was found.
AutoDetecting cable. Please wait.
*** WARNING ***: When port is set to auto detect mode, cable speed is set to default 6 MHz regardless of explicit arguments supplied for setting the baud rates
PROGRESS_START - Starting Operation.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
 Driver file xusb_emb.sys found.
 Driver version: src=1029, dest=1029.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
 Cable PID = 0008.
 Max current requested during enumeration is 74 mA.
Type = 0x0004.
 Cable Type = 3, Revision = 0.
 Setting cable speed to 6 MHz.
ERROR:Cse - A reference voltage has not been detected on the ribbon cable interface to the target system ( pin 2 ).  Check that power is applied to the target system and that the ribbon cable is properly seated at both ends.  The status LED on Platform Cable USB will be GREEN if target voltage is in the proper range and applied to the correct pin.
Cable connection failed.
Connecting to cable (Parallel Port - LPT1).
Checking cable driver.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
 LPT base address = 0378h.
 ECP base address = 0778h.
Cable connection failed.
Connecting to cable (Parallel Port - LPT2).
Checking cable driver.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
Cable connection failed.
Connecting to cable (Parallel Port - LPT3).
Checking cable driver.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
Cable connection failed.
Connecting to cable (Parallel Port - LPT4).
Checking cable driver.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
Cable connection failed.
PROGRESS_END - End Operation.
Elapsed time =      2 sec.
Cable autodetection failed.
WARNING:iMPACT:923 - Can not find cable, check cable setup !GUI --- Auto connect to cable...
// *** BATCH CMD : setCable -port auto
INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.4
INFO:iMPACT - Digilent Plugin: no JTAG device was found.
AutoDetecting cable. Please wait.
*** WARNING ***: When port is set to auto detect mode, cable speed is set to default 6 MHz regardless of explicit arguments supplied for setting the baud rates
PROGRESS_START - Starting Operation.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
 Driver file xusb_emb.sys found.
 Driver version: src=1029, dest=1029.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
 Cable PID = 0008.
 Max current requested during enumeration is 74 mA.
Type = 0x0004.
 Cable Type = 3, Revision = 0.
 Setting cable speed to 6 MHz.
ERROR:Cse - A reference voltage has not been detected on the ribbon cable interface to the target system ( pin 2 ).  Check that power is applied to the target system and that the ribbon cable is properly seated at both ends.  The status LED on Platform Cable USB will be GREEN if target voltage is in the proper range and applied to the correct pin.
Cable connection failed.
Connecting to cable (Parallel Port - LPT1).
Checking cable driver.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
 LPT base address = 0378h.
 ECP base address = 0778h.
Cable connection failed.
Connecting to cable (Parallel Port - LPT2).
Checking cable driver.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
Cable connection failed.
Connecting to cable (Parallel Port - LPT3).
Checking cable driver.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
Cable connection failed.
Connecting to cable (Parallel Port - LPT4).
Checking cable driver.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
Cable connection failed.
PROGRESS_END - End Operation.
Elapsed time =      2 sec.
Cable autodetection failed.
WARNING:iMPACT:923 - Can not find cable, check cable setup !GUI --- Auto connect to cable...
// *** BATCH CMD : setCable -port auto
INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.4
INFO:iMPACT - Digilent Plugin: no JTAG device was found.
AutoDetecting cable. Please wait.
*** WARNING ***: When port is set to auto detect mode, cable speed is set to default 6 MHz regardless of explicit arguments supplied for setting the baud rates
PROGRESS_START - Starting Operation.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
 Driver file xusb_emb.sys found.
 Driver version: src=1029, dest=1029.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
 Cable PID = 0008.
 Max current requested during enumeration is 74 mA.
Type = 0x0004.
 Cable Type = 3, Revision = 0.
 Setting cable speed to 6 MHz.
ERROR:Cse - A reference voltage has not been detected on the ribbon cable interface to the target system ( pin 2 ).  Check that power is applied to the target system and that the ribbon cable is properly seated at both ends.  The status LED on Platform Cable USB will be GREEN if target voltage is in the proper range and applied to the correct pin.
Cable connection failed.
Connecting to cable (Parallel Port - LPT1).
Checking cable driver.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
 LPT base address = 0378h.
 ECP base address = 0778h.
Cable connection failed.
Connecting to cable (Parallel Port - LPT2).
Checking cable driver.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
Cable connection failed.
Connecting to cable (Parallel Port - LPT3).
Checking cable driver.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
Cable connection failed.
Connecting to cable (Parallel Port - LPT4).
Checking cable driver.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
Cable connection failed.
PROGRESS_END - End Operation.
Elapsed time =      2 sec.
Cable autodetection failed.
WARNING:iMPACT:923 - Can not find cable, check cable setup !GUI --- Auto connect to cable...
// *** BATCH CMD : setCable -port auto
INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.4
INFO:iMPACT - Digilent Plugin: no JTAG device was found.
AutoDetecting cable. Please wait.
*** WARNING ***: When port is set to auto detect mode, cable speed is set to default 6 MHz regardless of explicit arguments supplied for setting the baud rates
PROGRESS_START - Starting Operation.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
 Driver file xusb_emb.sys found.
 Driver version: src=1029, dest=1029.
 Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 X86 32bit SYS 14:35:41, version = 1021.
 Cable PID = 0008.
 Max current requested during enumeration is 74 mA.
Type = 0x0004.
 Cable Type = 3, Revision = 0.
 Setting cable speed to 6 MHz.
Cable connection established.
Firmware version = 1029.
File version of C:/Xilinx/14.7/LabTools/LabTools/data/xusb_xlp.hex = 1303.
Firmware hex file version = 1303.
Downloading C:/Xilinx/14.7/LabTools/LabTools/data/xusb_xlp.hex.
Downloaded firmware version = 1303.
PLD file version = 0012h.
 PLD version = 0012h.
PROGRESS_END - End Operation.
Elapsed time =      0 sec.
Type = 0x0004.
 ESN device is not available for this cable.
Attempting to identify devices in the boundary-scan chain configuration...
INFO:iMPACT - Current time: 10/14/2016 12:34:15 AM
// *** BATCH CMD : Identify -inferir 
PROGRESS_START - Starting Operation.
Identifying chain contents...'0': : Manufacturer's ID = Xilinx xc3s200a, Version : 0
INFO:iMPACT:1777 - 
Reading C:/Xilinx/14.7/LabTools/LabTools/spartan3a/data/xc3s200a.bsd...
INFO:iMPACT:501 - '1': Added Device xc3s200a successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
done.
PROGRESS_END - End Operation.
Elapsed time =      3 sec.
// *** BATCH CMD : identifyMPM 
// *** BATCH CMD : assignFile -p 1 -file "C:/Documents and Settings/kreg/Desktop/gcvideo-dvi-shuriken-v3-2.3.bit"
'1': Loading file 'C:/Documents and Settings/kreg/Desktop/gcvideo-dvi-shuriken-v3-2.3.bit' ...
done.
INFO:iMPACT:2257 - Startup Clock has been changed to 'JtagClk' in the bitstream stored in memory,
but the original bitstream file remains unchanged.
UserID read from the bitstream file = 0xFFFFFFFF.
INFO:iMPACT:501 - '1': Added Device xc3s200a successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
Selected part: M25P40
// *** BATCH CMD : attachflash -position 1 -spi "M25P40"
Unprotect sectors: FALSE
// *** BATCH CMD : assignfiletoattachedflash -position 1 -file "C:/Documents and Settings/kreg/Desktop/kreg.mcs"
// *** BATCH CMD : attachflash -position 1 -spi "M25P40"
INFO:iMPACT - Current time: 10/14/2016 12:34:50 AM
// *** BATCH CMD : Erase -p 1 -spionly 
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 10000000.
Validating chain...
Boundary-scan chain validated successfully.
'1': SPI access core not detected. SPI access core will be downloaded to the device to enable operations.
INFO:iMPACT - Downloading core file C:/Xilinx/14.7/LabTools/LabTools/spartan3a/data/xc3s200a_spi.cor.
'1': Downloading core...
 LCK_cycle = NoWait.
LCK cycle: NoWait
done.
'1': Reading status register contents...
INFO:iMPACT:2219 - Status register values:
INFO:iMPACT - 0000 0000 0000 0000 
INFO:iMPACT:2492 - '1': Completed downloading core to device.
PROGRESS_END - End Operation.
Elapsed time =      1 sec.
INFO:iMPACT - Current time: 10/14/2016 12:34:56 AM
// *** BATCH CMD : Program -p 1 -spionly -e -v -loadfpga 
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 10000000.
Validating chain...
Boundary-scan chain validated successfully.
'1': SPI access core not detected. SPI access core will be downloaded to the device to enable operations.
INFO:iMPACT - Downloading core file C:/Xilinx/14.7/LabTools/LabTools/spartan3a/data/xc3s200a_spi.cor.
'1': Downloading core...
 LCK_cycle = NoWait.
LCK cycle: NoWait
done.
'1': Reading status register contents...
INFO:iMPACT:2219 - Status register values:
INFO:iMPACT - 0000 0000 0000 0000 
INFO:iMPACT:2492 - '1': Completed downloading core to device.
INFO:iMPACT - '1': Flash was not programmed successfully.
PROGRESS_END - End Operation.
Elapsed time =      1 sec.
INFO:iMPACT - Current time: 10/14/2016 12:37:31 AM
// *** BATCH CMD : Erase -p 1 -spionly 
ERROR:Cse - A reference voltage has not been detected on the ribbon cable interface to the target system ( pin 2 ).  Check that power is applied to the target system and that the ribbon cable is properly seated at both ends.  The status LED on Platform Cable USB will be GREEN if target voltage is in the proper range and applied to the correct pin.
INFO:iMPACT - Current time: 10/14/2016 12:37:36 AM
// *** BATCH CMD : Erase -p 1 -spionly 
ERROR:Cse - A reference voltage has not been detected on the ribbon cable interface to the target system ( pin 2 ).  Check that power is applied to the target system and that the ribbon cable is properly seated at both ends.  The status LED on Platform Cable USB will be GREEN if target voltage is in the proper range and applied to the correct pin.
INFO:iMPACT - Current time: 10/14/2016 12:37:46 AM
// *** BATCH CMD : Erase -p 1 -spionly 
ERROR:Cse - A reference voltage has not been detected on the ribbon cable interface to the target system ( pin 2 ).  Check that power is applied to the target system and that the ribbon cable is properly seated at both ends.  The status LED on Platform Cable USB will be GREEN if target voltage is in the proper range and applied to the correct pin.
Attempting to identify devices in the boundary-scan chain configuration...
INFO:iMPACT - Current time: 10/14/2016 12:37:51 AM
// *** BATCH CMD : Identify -inferir 
ERROR:Cse - A reference voltage has not been detected on the ribbon cable interface to the target system ( pin 2 ).  Check that power is applied to the target system and that the ribbon cable is properly seated at both ends.  The status LED on Platform Cable USB will be GREEN if target voltage is in the proper range and applied to the correct pin.
Attempting to identify devices in the boundary-scan chain configuration...
INFO:iMPACT - Current time: 10/14/2016 12:38:25 AM
// *** BATCH CMD : Identify -inferir 
PROGRESS_START - Starting Operation.
Identifying chain contents...'0': : Manufacturer's ID = Xilinx xc3s200a, Version : 0
INFO:iMPACT:1777 - 
Reading C:/Xilinx/14.7/LabTools/LabTools/spartan3a/data/xc3s200a.bsd...
INFO:iMPACT:501 - '1': Added Device xc3s200a successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
done.
PROGRESS_END - End Operation.
Elapsed time =      0 sec.
// *** BATCH CMD : identifyMPM 
// *** BATCH CMD : assignFile -p 1 -file "C:/Documents and Settings/kreg/Desktop/gcvideo-dvi-shuriken-v3-2.3.bit"
'1': Loading file 'C:/Documents and Settings/kreg/Desktop/gcvideo-dvi-shuriken-v3-2.3.bit' ...
done.
INFO:iMPACT:2257 - Startup Clock has been changed to 'JtagClk' in the bitstream stored in memory,
but the original bitstream file remains unchanged.
UserID read from the bitstream file = 0xFFFFFFFF.
INFO:iMPACT:501 - '1': Added Device xc3s200a successfully.
----------------------------------------------------------------------
----------------------------------------------------------------------
Selected part: M25P40
// *** BATCH CMD : attachflash -position 1 -spi "M25P40"
Unprotect sectors: FALSE
// *** BATCH CMD : assignfiletoattachedflash -position 1 -file "C:/Documents and Settings/kreg/Desktop/kreg.mcs"
// *** BATCH CMD : attachflash -position 1 -spi "M25P40"
INFO:iMPACT - Current time: 10/14/2016 12:38:44 AM
// *** BATCH CMD : Erase -p 1 -spionly 
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 10000000.
Validating chain...
Boundary-scan chain validated successfully.
'1': SPI access core not detected. SPI access core will be downloaded to the device to enable operations.
INFO:iMPACT - Downloading core file C:/Xilinx/14.7/LabTools/LabTools/spartan3a/data/xc3s200a_spi.cor.
'1': Downloading core...
 LCK_cycle = NoWait.
LCK cycle: NoWait
done.
'1': Reading status register contents...
INFO:iMPACT:2219 - Status register values:
INFO:iMPACT - 0000 0000 0000 0000 
INFO:iMPACT:2492 - '1': Completed downloading core to device.
PROGRESS_END - End Operation.
Elapsed time =      0 sec.
INFO:iMPACT - Current time: 10/14/2016 12:38:55 AM
// *** BATCH CMD : Erase -p 1 -spionly 
ERROR:Cse - A reference voltage has not been detected on the ribbon cable interface to the target system ( pin 2 ).  Check that power is applied to the target system and that the ribbon cable is properly seated at both ends.  The status LED on Platform Cable USB will be GREEN if target voltage is in the proper range and applied to the correct pin.
INFO:iMPACT - Current time: 10/14/2016 12:39:01 AM
// *** BATCH CMD : Erase -p 1 -spionly 
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 10000000.
Validating chain...
Boundary-scan chain validated successfully.
'1': SPI access core not detected. SPI access core will be downloaded to the device to enable operations.
INFO:iMPACT - Downloading core file C:/Xilinx/14.7/LabTools/LabTools/spartan3a/data/xc3s200a_spi.cor.
'1': Downloading core...
 LCK_cycle = NoWait.
LCK cycle: NoWait
done.
'1': Reading status register contents...
INFO:iMPACT:2219 - Status register values:
INFO:iMPACT - 0000 0000 0000 0000 
INFO:iMPACT:2492 - '1': Completed downloading core to device.
PROGRESS_END - End Operation.
Elapsed time =      0 sec.
INFO:iMPACT - Current time: 10/14/2016 12:39:05 AM
// *** BATCH CMD : Program -p 1 -spionly -e -v -loadfpga 
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 10000000.
Validating chain...
Boundary-scan chain validated successfully.
'1': SPI access core not detected. SPI access core will be downloaded to the device to enable operations.
INFO:iMPACT - Downloading core file C:/Xilinx/14.7/LabTools/LabTools/spartan3a/data/xc3s200a_spi.cor.
'1': Downloading core...
 LCK_cycle = NoWait.
LCK cycle: NoWait
done.
'1': Reading status register contents...
INFO:iMPACT:2219 - Status register values:
INFO:iMPACT - 0000 0000 0000 0000 
INFO:iMPACT:2492 - '1': Completed downloading core to device.
INFO:iMPACT - '1': Flash was not programmed successfully.
PROGRESS_END - End Operation.
Elapsed time =      0 sec.
INFO:iMPACT - Current time: 10/14/2016 12:39:11 AM
// *** BATCH CMD : Program -p 1 -spionly -e -v -loadfpga 
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 10000000.
Validating chain...
Boundary-scan chain validated successfully.
'1': SPI access core not detected. SPI access core will be downloaded to the device to enable operations.
INFO:iMPACT - Downloading core file C:/Xilinx/14.7/LabTools/LabTools/spartan3a/data/xc3s200a_spi.cor.
'1': Downloading core...
 LCK_cycle = NoWait.
LCK cycle: NoWait
done.
'1': Reading status register contents...
INFO:iMPACT:2219 - Status register values:
INFO:iMPACT - 0000 0000 0000 0000 
INFO:iMPACT:2492 - '1': Completed downloading core to device.
INFO:iMPACT - '1': Flash was not programmed successfully.
PROGRESS_END - End Operation.
Elapsed time =      0 sec.
INFO:iMPACT - Current time: 10/14/2016 12:39:16 AM
// *** BATCH CMD : Program -p 1 
PROGRESS_START - Starting Operation.
Maximum TCK operating frequency for this device chain: 10000000.
Validating chain...
Boundary-scan chain validated successfully.
'1': Programming device...
 LCK_cycle = NoWait.
LCK cycle: NoWait
done.
'1': Reading status register contents...
CRC error                                                                  :         0
IDCODE not validated while writing FDRI                                    :         0
DCM Locked                                                                 :         0
status of GTS_CFG_B                                                        :         0
status of GWE                                                              :         0
status of GHIGH                                                            :         0
value of VSEL pin 0                                                        :         0
value of VSEL pin 1                                                        :         0
value of VSEL pin 2                                                        :         0
value of MODE pin M0                                                       :         0
value of MODE pin M1                                                       :         0
value of MODE pin M2                                                       :         0
value of CFG_RDY (INIT_B)                                                  :         0
DONEIN input from Done Pin                                                 :         0
SYNC word not found                                                        :         0
INFO:iMPACT:2219 - Status register values:
INFO:iMPACT - 0000 0000 0000 0000 
INFO:iMPACT:579 - '1': Completed downloading bit file to device.
INFO:iMPACT:188 - '1': Programming completed successfully.
 LCK_cycle = NoWait.
LCK cycle: NoWait
INFO:iMPACT - '1': Checking done pin....done.
'1': Programming terminated. DONE did not go high.
PROGRESS_END - End Operation.
Elapsed time =      1 sec.

[zeldaxpro]

BUMP UPDATE: It looks like other people have been using this thread lol. I ended up making a new board, and programmed it successfully as shown:



I seem to have another problem (hopefully my last). So I disconnected JP1 after programming, installed a 4.7uF capacitor as stated. The Shuriken is connected to my gamecube. I power on the gamecube and the hdmi cable is plugged in. However, I don't get a pop up for the hdmi nor is it showing on my inputs. So I decide to do some probing with my multimeter and found this:

1: all resistors are reading correctly

2: when plugged in GameCube and powered up, Pin 1 reads around 2.19v. When I power the shuriken from a separate 3.3v and GND power supply, pin 1 I get 3.3v. The pin 1 I'm talking about is the DetectCable (pull high 1.8V). Is that normal?

3: 12v is going through when powered by GameCube and I get 5v output on the regulator

I still don't get a pop up for hdmi when powered on. The only thing I'm thinking is resolder the hdmi port. There may be a bridge or cold joints that are not making proper contact. I am not seeing any bridges on the FPGA but I can upload pics if anyone else wants to confirm that.

Does anyone know what else it could be? Thanks!

[bytesaber]

I need help making sure I am setting up a SPI flash correctly in impact.

I am using the Gamecube to power the board. I have 3.3v where expected on the M25P40.

JP1 with 4.7K Resistor:
With Impact, I initialize chain. It detects the xcs200a. Good start!
It the asks me to load the .bit file. I load gcvideo-dvi-shuriken-v3-2.3.bit
After this it informs me that I can now load an SPI flash. I choose gcvideo-dvi-shuriken-v3-2.3-spirom.mcs and set it to M25P40.
So far no errors that I can see in the log.

JP1 CLOSED:
I go to Erase the SPI. Fail.
I go to Program the SPI. Fail

JP1 with 4.7K Resistor:
I go to Program the FPGA. Fail

Can someone please advise? I don't know what to do. Am I using JP1 correctly??

[bytesaber]

@zeldaxpro I think you and I are at the exact same point. I successfully programmed tonight with the same results. I checked the same points for voltages as you. If younare also following my other thread on assembler, you can see more details about how I programmed. (I know, I'm spamming alot) At the least, I hope its helpful commenting for someone or yourself.

[zeldaxpro]

@zeldaxpro I think you and I are at the exact same point. I successfully programmed tonight with the same results. I checked the same points for voltages as you. If younare also following my other thread on assembler, you can see more details about how I programmed. (I know, I'm spamming alot) At the least, I hope its helpful commenting for someone or yourself.

Hello, When measuring PIN 1 and GND, are you getting 2.1-2.2v as well? That is my current issue. Mine programmed successfully using the SPI method from happy_bunny using the LCSOFT board and the converted .bin file. I do not know what else it could be. Other people have been saying it is a short, but everything looks good on my end. I will have to further inspect it with a microscope to confirm that though.

[bytesaber]

Yes, I have 2.1v there also. happy_bunny mentioned that I trace c_sel and clk for a good connection to the fpga.

I built a 2nd Shuriken v3, so I may swap to that soon.

[bytesaber]

What specific points on the Shuriken itself did you connect your programmer to, when you programmed it?

[zeldaxpro]

Yes, I have 2.1v there also. happy_bunny mentioned that I trace c_sel and clk for a good connection to the fpga.

I built a 2nd Shuriken v3, so I may swap to that soon.

Alright I should check my connections there as well. Is c_sel and clk pins on the FPGA that trace to what? And in regards to programming I just used the serial pads (the 2 rows of 3 next to U2) and corresponded the pinout with the SPI Flash and Schematic.

[bytesaber]

If you zoom in on the schematic (make sure it's the V3 schematic), the gamecube mainboard video connector is on the left. CSEL is pin 3, and CLK is pin 22. Looks like they connect to FPGA pin 5 and pin 41 respectively.

I am going to try to trace these paths back toward someplace on the gamecube side also, just to really make sure these 2 paths are crossing the connector and making it to the Shuriken. happy_bunny says these should at least make somekind of "noise" on the TV.

You mentioned seeing 5v at the voltage regulator for the HDMI connector. Do you also measure 5v on pin 18 of HDMI connector? Might be good to check if that path is making it the whole way.

Your pictures showed you using a Xilinx programmer. So I bought one too. I asked about where you connected your programmer to, because it only dawned on me last night, that direct SPI programming might not be done through the JTAG connection. Your earlier posts showed using JTAG. I have been maybe misunderstanfing that direct SPI programming, was when you right click on the SPI after initializing the chain from a boundry scan. I never could sucessfully erase or program this way.

Yesterday I recalled someone mentioning connecting to the 6 pins by U2. I realized I could connect my Xilinx programmer to there instead. I could not do a boundry scan now, since it's not hooked up to JTAG this way. So I manually added an SPI under the menu option "Direct SPI Programming" and it was able to erase, verify, and program sucessfully. JP1 was closed with this method. Not when using JTAG though.

I did as you, and just traced the corresponding pins to the the flash, from the 2 rows of pins by U2. In my case I am using impact and a Xilinx programmer. So my software only liked .mcs files. Not sure how to make my programmer use a .bin file. Do you think I programmed it right?

I have no idea if anything I said is correct thinking. So if someone can verify what I described is true or not, please let me know.

[bytesaber]

Impact's Direct SPI feature was dropped after 11.x So I downgraded from 14.x to 11.x to program it without using the JTAG connection.

[zeldaxpro]

I never ended up programming with the Xilinx programmer and IMPACT. I followed happy_bunny's method on his website to flash it. It verified and flashed so I'm pretty sure it's good.

[bytesaber]

Right. I was just offering it up as a possible explanation for why your Xilinx programmer never managed to work over JTAG. Mine never did over JTAG either. Yours might have over serial like mine did.

[zeldaxpro]

Right. I was just offering it up as a possible explanation for why your Xilinx programmer never managed to work over JTAG. Mine never did over JTAG either. Yours might have over serial like mine did.

Oh ok cool. I still don't understand the 2.1-2.2v on Pin 1 and GND when connected. When I disconnect it from the GC and power it separately with a 3.3v and GND supply, I get 3.3-3.4v at PIN 1, which is what is should be when connected to the cube in order for it to work. Have you thought of anything else to test? Please keep me updated if you find out the issue. Thanks.