gbadev.org forum archive

This is a read-only mirror of the content originally found on forum.gbadev.org (now offline), salvaged from Wayback machine copies. A new forum can be found here.

Beginners > problems using my xboo-cable

#70529 - hns - Tue Feb 07, 2006 2:14 am

hello there..

i've built an xboo cable, but im unable to use it on my linux box.
if i use xcomms, as soon i click on the "Send GBA ..." Button the application does segfault...
its segfault's without the cable connected too..

if i use strace, it says something like:

...
...
select(4, [3], [], [], {0, 0}) = 0 (Timeout)
select(4, [3], [], [], {0, 0}) = 0 (Timeout)
select(4, [3], [], [], {0, 0}) = 0 (Timeout)
select(4, [3], [], [], {0, 0}) = 0 (Timeout)
select(4, [3], [], [], {0, 0}) = 0 (Timeout)
select(4, [3], [], [], {0, 0}) = 0 (Timeout)
select(4, [3], [], [], {0, 0}) = 1 (in [3], left {0, 0})
ioctl(3, FIONREAD, [160]) = 0
read(3, "\10\0\377\0\204\233\36\0F\0\0\0\3\0\300\0\0\0\0\0\335\1"..., 160) = 160--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

I'm stuck... i've tried other tools like: mb, smcable etc.. but none of them work..
i'm pretty shure my cable is solderd correctly..

please help!!!

regards hns

#70635 - wintermute - Tue Feb 07, 2006 10:11 pm

New builds of Xboo Communicator are avaliable as announced http://www.devkitpro.org/index.php?action=fullnews&id=95

This may help with this problem, I think it may be related to the FLU fltk widget library which was used previously. This was the source of the problem with win98.

Failing that, Xboo Communicator may be started from the command line with the .gba file given as an argument.
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog

#70992 - hns - Thu Feb 09, 2006 9:59 pm

Thanks for the tips..

Yes, i can confirm, that the segfaults are gone, after installing the new version of xboo-communicator..

also, that the commandline usage did not cause the segfaults with the older version...


Now: if try to use the app and cable i get:

Xboo Communicator 1.22 - Jan 21 2006
Using Port Address 378
Port Initialisation

Reset and requesting Normal boot.
No response from GBA


I'm shure my par-port is configured to sit on adress 378 and the cable is soldered correctly, according to the no$gba schema..
(i "beeped"-it out 10 times..)

gba 2 -> par 10
gba 3 -> par 14
gba 5 -> par 1
gba 6 -> par 19

Now.. if i start the gba with the cable plugged in, i get a blank screen most of the times and the communicator says, as stated above:

No response from GBA

any more hints? for example what parallel port settings are to configure in my pc bios, or who knows...

Regards hns


P.S: btw. i've ordered an intelligent cable today.. so hope it works then..

#71044 - wintermute - Fri Feb 10, 2006 2:12 am

The schematic in the xcomms docs is probably not as clear as it could be. See this thread -> http://forum.gbadev.org/viewtopic.php?t=8001&postdays=0&postorder=asc&start=21
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog

#71053 - jake2431 - Fri Feb 10, 2006 3:46 am

Yeah, wintermutes right. It sounds like the exact same problem I had. Just reverse the soldering.

#71210 - hns - Sat Feb 11, 2006 12:45 am

sadly.. i guess its soldered correctly..

looking at the plug, the one hanging at the cable to the par-port:


/????\
| p2 p1--
| p4 p3 |
| p6 p5--
\____/

So... i guess its either my parallel port or the port on the gba itself..

please tell me i made a mistake while soldering the cable... ;) (hopefully)...

Regards hns...

#71222 - wintermute - Sat Feb 11, 2006 5:06 am

Assuming that pin numbering is looking into the plug on the end of the cable from the GBA side then it looks ok.

You could try deleting .xcomms from your home directory so it gets reset to defaults. Increasing the transfer delay may also help.

The transfer can be unreliable if the GBA is low on power so a fresh set of batteries, an AC adapter or recharge might help.

Another option would be to try adding pull up resistors as detailed in Martin's original docs -> http://www.work.de/nocash/gba-xboo.htm

Check if you have anything installed which may potentially be polling the parallel port and disable it.
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog