Jtag Breakout Board Help

[CyberAxe]

i just got the breakout board and after laods of seraching around for paralel cables and a long enough serial cable i go to jtag and it doesnt work

ive got a model 2 (not a mk2) and have done like it said in the manual ive hooked up an adapter to the board and the red lights turns on and ive put rechargable batteries in the gp2x

but when i run the GP2XRecovery.exe this is all that happens

JTAGProbe - JTAG interface to the ARM9TDMI/ARM7TDMI
DIGNSYS Inc. (www.dignsys.com)
Modified by Kane. September 2004

Jtag - Using port 0x378
failure: CreateService, ERROR_SERVICE_EXISTS
failure: StartService (0x4fb)
Can't get a handle to \\.\giveio
1 file(s) copied.
failure: CreateService, ERROR_SERVICE_EXISTS
failure: StartService (0x4fb)
Can't get a handle to \\.\giveio
failure: CreateService, ERROR_SERVICE_EXISTS
failure: StartService (0x4fb)
Can't get a handle to \\.\giveio
Couldn't access giveio device

help please

 

[oneandoneis2]

Firstly: Does your parallel cable have all 25 pins wired up? They often don't if they're sold as "Printer cables" or some such. . .

Secondly: Did you plug the BoB in & power it up before booting your PC? If you didn't, Windows will probably have decided to ignore the parallel port at bootup because there's nothing plugged in. It has to have detectable hardware in place at bootup.

 

[diegor]

i just got the breakout board and after laods of seraching around for paralel cables and a long enough serial cable i go to jtag and it doesnt work

ive got a model 2 (not a mk2) and have done like it said in the manual ive hooked up an adapter to the board and the red lights turns on and ive put rechargable batteries in the gp2x

but when i run the GP2XRecovery.exe this is all that happens

JTAGProbe - JTAG interface to the ARM9TDMI/ARM7TDMI
DIGNSYS Inc. (www.dignsys.com)
Modified by Kane. September 2004

Jtag - Using port 0x378
failure: CreateService, ERROR_SERVICE_EXISTS
failure: StartService (0x4fb)
Can't get a handle to \\.\giveio
1 file(s) copied.
failure: CreateService, ERROR_SERVICE_EXISTS
failure: StartService (0x4fb)
Can't get a handle to \\.\giveio
failure: CreateService, ERROR_SERVICE_EXISTS
failure: StartService (0x4fb)
Can't get a handle to \\.\giveio
Couldn't access giveio device

help please

Simple question: do you have installed the device driver before launching .exe?

 

[CyberAxe]

Firstly: Does your parallel cable have all 25 pins wired up? They often don't if they're sold as "Printer cables" or some such. . .

Secondly: Did you plug the BoB in & power it up before booting your PC? If you didn't, Windows will probably have decided to ignore the parallel port at bootup because there's nothing plugged in. It has to have detectable hardware in place at bootup.

i am not sure but ivew tried a few differnet cables the one i am suing at the moment is a belkin lead it says "high speed data transfere" but couldnt find any model nums or that i think i used to use it for networking between 2 pcs eons ago

i didnt have it powerd on before boot i will reboot now thanks

i just got the breakout board and after laods of seraching around for paralel cables and a long enough serial cable i go to jtag and it doesnt work

ive got a model 2 (not a mk2) and have done like it said in the manual ive hooked up an adapter to the board and the red lights turns on and ive put rechargable batteries in the gp2x

but when i run the GP2XRecovery.exe this is all that happens

JTAGProbe - JTAG interface to the ARM9TDMI/ARM7TDMI
DIGNSYS Inc. (www.dignsys.com)
Modified by Kane. September 2004

Jtag - Using port 0x378
failure: CreateService, ERROR_SERVICE_EXISTS
failure: StartService (0x4fb)
Can't get a handle to \\.\giveio
1 file(s) copied.
failure: CreateService, ERROR_SERVICE_EXISTS
failure: StartService (0x4fb)
Can't get a handle to \\.\giveio
failure: CreateService, ERROR_SERVICE_EXISTS
failure: StartService (0x4fb)
Can't get a handle to \\.\giveio
Couldn't access giveio device

help please

Simple question: do you have installed the device driver before launching .exe?

i didnt know there was any

 

[CyberAxe]

i hard booted and i get the same error i also checked the bios and changed the parallel port mode from ecp to normal

 

[BradN]

"i think i used to use it for networking between 2 pcs eons ago"

This cable won't work. Test it with a multimeter and you should find the wires don't go straight through.

 

[CyberAxe]

i have looked everywhere i cant find the right wire anywhere

 

[CyberAxe]

anyone know where i could order one from?

 

[oneandoneis2]

I got mine from PC world - there's a thread here on a place to order one online, search should find it..

 

[CyberAxe]

thanks for all previous help i finally got a cable (www.netshop.co.uk for those who like me are in the uk and cant find any)

anyway mostly working now but still some problems heres the output for the GP2x Recovery

Jtag - Using port 0x378
CreateService SUCCESS
failure: StartService (0x02)
Can't get a handle to \\.\giveio
1 file(s) copied.
failure: CreateService, ERROR_SERVICE_EXISTS
StartService SUCCESS
CreateFile SUCCESS
jtag_reset();
JTAG interface reset.
jtag_idcode();
Device ID..0x10920F0F
MMSP2 Detected!
>> Start Flash update <<
1) Initialize...
JTAG interface reset.
2) Halt Device...
Requesting HALT..
System HALTED in 32bit State
R0 is 0xE51F90B8
PC is 0x000001A0
3) ID Code Check...
Device ID..0x10920F0F
4) Watch-Dog Disable...
registers read
Poke 0xC0000A14, 0x00000000, 0x00000001
5) Disable Interrupt...
Poke 0xC0000808, 0xFFFFFFFF, 0x00000001
6) Downloading Recovery Image...(SDRAM default base address: 0x3F00000)
Write Block 0x03F00000, length 0x00000400
Write Block 0x03F01000, length 0x00000400
Write Block 0x03F02000, length 0x00000400
Write Block 0x03F03000, length 0x00000400
Write Block 0x03F04000, length 0x00000400
Write Block 0x03F05000, length 0x00000400
Write Block 0x03F06000, length 0x00000400
Write Block 0x03F07000, length 0x00000400
Write Block 0x03F08000, length 0x00000400
Write Block 0x03F09000, length 0x00000400
Write Block 0x03F0A000, length 0x00000400
Write Block 0x03F0B000, length 0x00000400
Write Block 0x03F0C000, length 0x00000400
Write Block 0x03F0D000, length 0x00000400
Write Block 0x03F0E000, length 0x00000400
Write Block 0x03F0F000, length 0x00000400
Write Block 0x03F10000, length 0x00000400
Write Block 0x03F11000, length 0x00000400
Write Block 0x03F12000, length 0x00000400
Write Block 0x03F13000, length 0x00000400
Write Block 0x03F14000, length 0x00000400
Write Block 0x03F15000, length 0x0000013E
7) Please Wait...
Pausing for 0x00000003 seconds
8) Run Image...
registers written
Restarting at 0x03F00000
Done
9) Halt Device...
Requesting HALT..
System HALTED in 32bit State
R0 is 0xE51F90B8
PC is 0x054789BC
10) Rerun Image...
Restarting at 0x03F00000
Done
11) Terminate...
ControlService SUCCESS
DeleteService SUCCESS

also the serial output is giving this...

Flash chip found:ROR
Manufacturer ID: 0xEC, Chip ID: 0x76 (Samsung K9F1208 64Mb)te: device 0 offset 0x0, size 0x5c000 ... 0 bytes written:
1 flash chips found. Total na
Using default environmentset 0x0, size 0x5c000 ...

In: serialen: ERROR
Out: serial
Err: serial

SD found : SD Frequency is 2MHzce 0 offset 0x0, size 0x5c000 .
(with MBR) written:


!!!Warning!!! U-Boot Test Version...

GPIO C : 1ite: devic
UPDATE ...0x0, size
BOOT UPDATE ----------------------------
reading gp2xboot.img

NAND write:
READ START 3733480, size 0x5c000 .

373348 bytes read: ERROR
1 : g_filesize 5b264
gp2xboot.img Update 373348 0x5c000 device 0 offset 0x0, size 0x5c000

NAND write: device 0 offset 0x0, size 0x5c000 ... 0 bytes written: ERROR <--- this just constantly repeats

 

[oneandoneis2]

O-kay, well, GP2x Recovery seems to be working properly. Is that serial output what you're seeing when you're flashing, or what you see when rebooting afterwards?

And what happens when you do power up afterwards? Whitescreen? A logo?

 

[CyberAxe]

O-kay, well, GP2x Recovery seems to be working properly. Is that serial output what you're seeing when you're flashing, or what you see when rebooting afterwards?

And what happens when you do power up afterwards? Whitescreen? A logo?

the serial output comes after the gp2x recovery says its finished writing

and when i boot up it just has the same old white rainbow screen of death

 

[Blah]

O-kay, well, GP2x Recovery seems to be working properly. Is that serial output what you're seeing when you're flashing, or what you see when rebooting afterwards?

And what happens when you do power up afterwards? Whitescreen? A logo?

the serial output comes after the gp2x recovery says its finished writing

and when i boot up it just has the same old white rainbow screen of death

I don't have GP2X yet, but it looks like U-boot is trying to update your firmware from the SD card, maybe you should try it without the sd card.

 

[oneandoneis2]

No, GP2Xrecovery restores U-boot from the SD card - that's how it works.

Hummm... is there anything on the SD card but Uboot, Axe? And are you waiting the appropriate lengths of time at each step, and holding down the right buttons etc?

 

[BradN]

It looks like it's giving errors trying to write the first block of flash - it's possible the chip has developed a bad sector there, and it might not be possible for UBoot to work around it.

 

[CyberAxe]

No, GP2Xrecovery restores U-boot from the SD card - that's how it works.

Hummm... is there anything on the SD card but Uboot, Axe? And are you waiting the appropriate lengths of time at each step, and holding down the right buttons etc?

i had only the gp2ximage.img on it and did what i was supposed to do

It looks like it's giving errors trying to write the first block of flash - it's possible the chip has developed a bad sector there, and it might not be possible for UBoot to work around it.

djwillis was helping me and says thats what it looks like too

 

[Blah]

If I were you, I'd send it in for replacement. The NAND isn't supposed to just die like that.

 

[DJWillis]

If I were you, I'd send it in for replacement. The NAND isn't supposed to just die like that.

After some diagnoses (and no small amount of NAND poking) that is just what I said .

The 1st area of the NAND is one of the few areas that the specs say 'must be good'. The rest of the NAND you can map out if you really have too but it you can't get a boot-loader on there it is all a little bit of a pointless endeavour .

Also, the rest of Cyber_Axe's NAND seems flakier then I would expect so RMA'ing it is the only way to go unless you feel like mounting a new flash chip .

Interestingly this is only about the 7-8th time I have seen the NAND fail in the 1st few sectors (and one of those was my original devkit). Most units can be unbricked using jTAG or other methods just fine but when your unit becomes one of those statistics it must be a real kick in the teeth.