#87469 - lambi1982 - Wed Jun 14, 2006 1:40 am
please help, I am trying to update my Passme from Natrium42 to a passme2, my passme is a Version 1.4. (dont know if that makes a difference)
I get this when I try to connect:
Welcome to iMPACT
Quote: |
// *** 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 (Parallel Port - LPT1).
Checking cable driver.
Driver windrvr6.sys version = 7.0.0.0. LPT base address = 0378h.
ECP base address = 0778h.
Cable connection established.
PROGRESS_END - End Operation.
Elapsed time = 0 sec.
Attempting to identify devices in the boundary-scan chain configuration...Command: Identify
// *** BATCH CMD : Identify
PROGRESS_START - Starting Operation.
Identifying chain contents ....done.
ERROR:iMPACT:585 - 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.
Chain TCK freq = 0.
Validating chain...
Boundary-scan chain validated successfully.
PROGRESS_END - End Operation.
Elapsed time = 1 sec.
// *** BATCH CMD : identifyMPM |
I have traced the pins from the DB25 to the passme and all wires are where they should be, also I have to NEW batteries in the holster(3.1V)
does it need to be 3.3V??
Please help if possible. It will be greatly appreciated
_________________
Who, Me?
#87471 - Mr. Picklesworth - Wed Jun 14, 2006 1:59 am
Funny, I got exactly as far as you and am stumped.
Using a proper male 25-pin connector salvaged from an old computer as well as 2 working AA batteries and the appropriate resistor.
Connection to pads on the PassMe looks secure, although it's a bit more tricky than Natrium's to get working because the pads for the JTag cable are little round things.
It would be wonderful if that error message was a bit more specific.
_________________
Thanks!
MKDS Friend Code: 511165-679586
MP:H Friend Code: 2105 2377 6896
#87475 - lambi1982 - Wed Jun 14, 2006 2:11 am
I was getting sooooo pissed, I went and soldered the freakin wires to the passme to make sure they were secure, and I know they are.
I am just wondering if something is different with the passme that does NOT have the 45' angle chip.
Is there something I can do to double check the JTAG connections on the board, like when I have it all connected, is there supposed to be a certain voltage value on the board somewhere???
Damn things, I hate buying a new thing when I have something I can use now. I even bought a MK2, what good that does me.... it sits in a friggin box.
_________________
Who, Me?
#87555 - Lynx - Wed Jun 14, 2006 2:33 pm
Dang dude.. give people a little time to reply.. First.. I'm sure there is NO REASON to buy another one.. Unless you fried the CPLD somehow..
Anyway.
If you do a "get device ID" what does it come back with? Also, are you checking the "erase" box when trying to program? What version of the iMPACT software are you using?
_________________
NDS Homebrew Roms & Reviews
#87674 - lambi1982 - Thu Jun 15, 2006 12:00 am
Sorry, :)
I got all fired up when it wasnt working.
Xilinx ISE 8.1i and impact V1.24
it reads Quote: |
he idcode read from the device does not match the idcode in the bsdl File |
when I try to erase
well I hooked up the Passme back to my old DS and I am still able to get white screens. so I assume it works fine.
I have a feeling the wiring is different on the Passme with a non 45" angle CDLP. or is it something else
_________________
Who, Me?
#87761 - Lynx - Thu Jun 15, 2006 4:12 pm
Here is the proper pinouts for the strait (non 45 degree from dspassme.com) passmes:
http://www.dspassme.com/docs/html/pm_03_jtag_construction.html
Scroll down to the bottom.
_________________
NDS Homebrew Roms & Reviews
#88548 - Mr. Picklesworth - Tue Jun 20, 2006 4:16 am
Thanks for that link, Lynx!
My PassMe now appears to be detected (what a relief! These CPLDs must be invincible!), but when I choose to do anything with it (Program, Verify, etc.) I get the following error (and I have no idea what it means since I have a Very beginner knowledge of this stuff): Quote: |
ERROR:iMPACT:583 - '1': The idcode read from the device does not match the idcode in the bsdl File. |
This happens with both passme.jed from Natriums passme-serial and the PassMe download from Darkfader's site, so I'll assume that the problem isn't with the files I've downloaded.
Any ideas what is going wrong?
Edit:
Hmm... spoke too soon?
I guess I'll try those... I'll edit in the idcode in a sec.
A second later:
There: 00001111111111111111111111111111
Expecting: 00001001011000000100000010010011
IDcode loop Failed (elapsed time: 3 seconds... a good omen?)... Chain integrity test not happy and tells me to test everything I could possible test as posted above.
EEK!
Oh well, It's comforting that they haven't yet told me "your device is dead, y`idiot... Go back to your cave!" ;)
I guess the problem could be the cable's connection to the contacts on the passme.
How much do I have to worry about making contact with Lynx's passmes?
Right now I have wires passing through the appropriate holes that look like they are touching the metal bits and have tape on them. Is there metal all the way through (ie: Operation) or should I be a bit more precise with this and solder the wires in?
_________________
Thanks!
MKDS Friend Code: 511165-679586
MP:H Friend Code: 2105 2377 6896
#88562 - freemaan - Tue Jun 20, 2006 8:43 am
My friend tried to upgrade his Passkey into Passkey2 :)
[Images not permitted - Click here to view it]
I fixed it by soldering thin Cu wires directly to the CPLD's pins...
#88574 - jmk - Tue Jun 20, 2006 10:29 am
I just successfully flashed my DS Lite, which also involved an upgrade of a PassMe v1.5 to a PassMe2.
I had similar problems with the upgrade at first, but when I double-checked the wires, one of them had been jerked out by the weight of my battery pack. Once I soldered it back in, it worked on the first attempt.
I'd definitely check your wiring and try it again. Good luck!