xboxscene.org forums

Pages: 1 ... 4 5 [6]

Author Topic: Matrix Glitcher 360  (Read 904 times)

vimann

  • Archived User
  • Newbie
  • *
  • Posts: 6
Matrix Glitcher 360
« Reply #75 on: November 13, 2011, 08:47:00 AM »

Redid the wiring, checked everything, wrote ecc, black screen with a solid green light again. Wires are routed accordingly. This is killing me...
Logged

Vilpo

  • Archived User
  • Newbie
  • *
  • Posts: 11
Matrix Glitcher 360
« Reply #76 on: December 14, 2011, 05:36:00 AM »

kloenie: I had the exact same issue you did, saw your post and got to thinking about the coils.. My underside B,F-lines were ok, but my A-line was going between two coils, so i moved it about 1/2 inch to the right and now it works perfect!
Thanks for pointing this issue out, i wouldn't have thought about that otherwise.. smile.gif
Logged

Gazc0igne

  • Archived User
  • Sr. Member
  • *
  • Posts: 284
Matrix Glitcher 360
« Reply #77 on: December 15, 2011, 05:02:00 PM »

got two of these, wouldnt program over JTAG

went back to the source he had got a bad batch none of them would program.

cheap ass crap!!
Logged

heartshacker

  • Archived User
  • Newbie
  • *
  • Posts: 23
Matrix Glitcher 360
« Reply #78 on: December 19, 2011, 12:18:00 PM »

For my case, Xlink is able to detect the cable but getting following error.

Welcome to iMPACT
iMPACT Version: 12.2
Project: C:\Xilinx\12.2\LabTools\\auto_project.ipf created.
// *** 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
AutoDetecting cable. Please wait.
PROGRESS_START - Starting Operation.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
 Source driver files not found.
The Platform Cable USB is not detected. Please connect a cable.If a cable is connected, please disconnect
and reconnect to the usb port, follow the instructions in the 'Found New Hardware Wizard', then retry
the Cable Setup operation.
Cable connection failed.
Connecting to cable (Parallel Port - LPT1).
Checking cable driver.
 Driver windrvr6.sys version = 8.1.1.0. WinDriver v8.11 Jungo © 1997 - 2006 Build Date: Oct 16 2006 X86 32bit SYS 12:35:07, version = 811.
Cable connection failed.
Connecting to cable (Parallel Port - LPT2).
Checking cable driver.
 Driver windrvr6.sys version = 8.1.1.0. WinDriver v8.11 Jungo © 1997 - 2006 Build Date: Oct 16 2006 X86 32bit SYS 12:35:07, version = 811.
Cable connection failed.
Connecting to cable (Parallel Port - LPT3).
Checking cable driver.
 Driver windrvr6.sys version = 8.1.1.0. WinDriver v8.11 Jungo © 1997 - 2006 Build Date: Oct 16 2006 X86 32bit SYS 12:35:07, version = 811.
 LPT base address = 0378h.
 ECP base address = FFFFFFFFh.
Cable connection established.
PROGRESS_END - End Operation.
Elapsed time =      1 sec.
Attempting to identify devices in the boundary-scan chain configuration...
INFO:iMPACT - Current time: Sun Dec 18 22:33:09 2011
// *** BATCH CMD : Identify -inferir
PROGRESS_START - Starting Operation.
Identifying chain contents...done.
ERROR:iMPACT - A problem may exist in the hardware configuration. Check that the cable, scan chain, and power connections are intact, that the specified scan chain configuration matches the actual hardware, and that the power supply is adequate and delivering the correct voltage.
PROGRESS_END - End Operation.
Elapsed time =      0 sec.
// *** BATCH CMD : identifyMPM

"360gcProg" is not detecting the cable. I would like to send it back. But before that, is there any way to check from  my end that the chip is bad?
Logged
Pages: 1 ... 4 5 [6]