General Question About Boot-up And Bricking


Fivelo....I have a question regarding your simple circuit... Do you get an address of 0xFFFFFFFF or 0x00000000?
No matter what, I always get 0x00000000, I only get the F's if the cable is disconnected, which is different from Manwe... he actually got it to see the CPU, confirmed by the F's.

I'm going to keep trying to see if I can atleast get the F's, if so, then I should be able to re-flash this thing.

I'm sorry to say it but don't be so sure about that.... :(

Mine displays all F's when it's all connected up and the 2x is on (Makes sense as if my memory serves me correctly then F is the highest value a hex number can be)

When I turn the 2x off it goes to all 0's...

Either way I'm still getting the 'CPU not support' error :'(

Interestingly (to try and avoid the issue of rebooting with bootdisk each time,) I used VMWare to boot the floppy. When running jtagprobe there, although I still received the same error, the hex number changed erraticaly each time I ran it - on some occasions it even cause the screen of the 2x to go blank, then a couple of runs later it would go back to the 'rainbow effect.'

There's definitely communication there of some sort... :s
 
Last edited by a moderator:
But that's my point, I think I screwed something up becuase I never get the F's. So it's gotta be my cable. I'm not saying that simply getting the F's will mean it's fixable, but it's a huge step in the right direction... at least I think so.
 
I only get the F's if the cable is disconnected, which is different from Manwe.
What H-JTAG V0.2.rar said? Can it detect GP2X in autodetect mode? I think, that 0000s or FFFFs which "JTAG Tool" gives you, makes no matter, because this soft can't work with Olimex's device.
Anyway, even without GP2X connected, I got 0000s with JTAG Tool when ARM-JTAG is on the LPT port. And FFFFs when ARM-JTAG is not connected to the LPT port. Try to boot from the floppy and compare what JTAG Tool said in both cases. Better cut your External connector away to keep experiment clear :) And check LPT address in PC's BIOS again.

Thanks for all the investigation Manwe - much appreciated... You should put a guide on the wiki, would be great with all the necessary info in one place!
Good idea, I'll try to add an article there.

BTW Is this the same wiggler as yours?
Looks very equal :) Guess, it is exactly the same device, even with the same price :)

Would still be nice if someone could confirm a positive result with the simple circuit though!
Hmm, there are a lot of messages on the beginning of this topic, all about success with simple circuit, aren't they?
 
Last edited by a moderator:
Would still be nice if someone could confirm a positive result with the simple circuit though!
Hmm, there are a lot of messages on the beginning of this topic, all about success with simple circuit, aren't they?

Nope... Unless I'm illiterate, Kaos seems to be the only confirmed winner with the simple scheme... To be honest I could go and buy the Wiggler right now - it's no problem to - but I'm the stubborn type and want to see my god damn resistors, capacitors & diodes do their thing!!

Since the weekend I haven't really had a good look at the circuit... It may just be a simple mistake - when I can be bothered I'll give it a proper going over!

So in the end... Your solution went something like this:

Bricked 2X + TV Adaptor + Olimex JTAG Wiggler + OCD Commander = Fixed 2X?

:D
 
Last edited by a moderator:
Just a quick one...

1. H-JTAG Server displays 0xFFFFFFFF when the 2x is on and 0x00000000 when it's off (but the jtag dongle is still connected!) Once again proving something is happening...

2. Manwe / Juliodm - are/were you both getting coloured line syndrome on your 2x? Or was the bricking of a different nature?

Many Thanks

EDIT:
Messed about with the simple circuit for a bit... Can't be bothered with it anymore (guess I'm not that stubborn,) will salvage the components for another time. Just ordered the ARM-JTAG dongle and will use that as we actually have more than one occurence of a chipped setup working...

Will let you all know how it goes!
 
Last edited by a moderator:
Same here. I even waited a couple of weeks to receive the psu just to confirm that it wasn't a battery thing, and still, white screen, then lines, then paper weight.
 
Fixed!!!

BIG Thanks to Manwe & the chap on that other thread that helped Manwe... ;)

Only you left now Julio....

At which point are you having problems?
 
Fixed!!!

BIG Thanks to Manwe & the chap on that other thread that helped Manwe... ;)

Only you left now Julio....

At which point are you having problems?

My GP2X is being recognised by the computer at all.... I'm starting to think that it's fried. The computer never makes a connection with it.

I'm trying here are work. Question about Bios parallel port settings, should it be under normal or EPP, or ECP?
 
Last edited by a moderator:
My GP2X is being recognised by the computer at all.... I'm starting to think that it's fried. The computer never makes a connection with it.

I'm trying here are work. Question about Bios parallel port settings, should it be under normal or EPP, or ECP?

My BIOS was set to 'EPP+ECP' - I would imagine either will do alright but ECP is the most up to date.

Would you be able to take some high res pics of your various connectors so we can have a closer look at the situation. Let's not write it off yet!
 
Last edited by a moderator:
I think I got it. I'm trying to load in the u-boot file now.

Wish me luck.

I had a few things wrong. The J-tag connector is shown from top down, not from the perspective of the cennection itself, so I had all the pins wrong.

I changed the Port setting to Bi-directional. Right now the GP2X is showing the:
Firmware
upgrading

window. It's taking a long time though. I'm just going to leave it.

I got it to start the GP2X screen now...
Trying the 2.0 thing now...

[EDIT]
The screen started with what I'm guessing was supposed to be the upgrading firmware screen, but it only showed halfway.... Should I be woried?

[EDIT]
Now it says "Formating Please Wait"
 
What I found was that it would get to the Firmware Updating screen and then hang...

My procedure:

1. Format SD Card with FAT32, place entire contents of Firmware 2.0 archive in it - insert this into the 2x
2. Get OCDC open & ready
3. Connect JTAG, turn on 2x and hit okay on OCD splash screen ASAP
4. Upload the uboot.elf file
5. GO 0x03F00000 (or whatever it was)
6. Uboot should now start and begin updating firmware from SD
7. When it restarts hold select + start to continue FW upgrade, this will take 5-10 mins I believe.

et voila... Working 2x :)
 
What I found was that it would get to the Firmware Updating screen and then hang...

My procedure:

1. Format SD Card with FAT32, place entire contents of Firmware 2.0 archive in it - insert this into the 2x
2. Get OCDC open & ready
3. Connect JTAG, turn on 2x and hit okay on OCD splash screen ASAP
4. Upload the uboot.elf file
5. GO 0x03F00000 (or whatever it was)
6. Uboot should now start and begin updating firmware from SD
7. When it restarts hold select + start to continue FW upgrade, this will take 5-10 mins I believe.

et voila... Working 2x :)


I FREAKING GOT IT! It works.... It works..... I FREAKING GOT IT! Now I should break the !@#$%^&*( thing just to show it who's boss!
 
Last edited by a moderator:
Sweet :)

Instead of breaking it to show it who's boss you should just fill it with games til it explodes ;)

Gratzors!
 
Sweet :)

Instead of breaking it to show it who's boss you should just fill it with games til it explodes ;)

Gratzors!

Manwe / Fivelo / darkdave
THANK YOU GUYS! YOU ALL ROCK!
MAY THE SILICON GODS BLESS YOU WITH UNINTERUPTED CIRCUITRY TIL THE END OF YOUR DAYS!
 
Last edited by a moderator:
Back
Top