[lib] libgbpak - a Transfer Pak beta library and dumping-tool v0.63.2

[Mattroid]

I'd like to help test camera compatibility, but I can't get it to recognize the camera. I tested with a GBC game and everything there seems to work fine, but the camera continues to give a "check connection" message. First time it gave me error -4, I then cleaned the contacts on the camera. After that, it gave me error -1. Since then, it doesn't give me an error code at all, but has always simply said 'check connection' at the bottom.

So I'm not sure what's up with that. Anything else you can think of that I might try?

[saturnu]

hm this is strange, what version are you using?

Code: [Select]

if(_set_gbPower(0)!=0)
return -1;
   
//get power status 0=off 1=on
if(_get_gbPower()!=0)
return -2;

//set power off 0=off 1=on
if(_set_gbPower(1)!=0)
return -3;

//get power status 0=off 1=on
if(_get_gbPower()!=1)
return -4;


this is happening after starting the tool:

1. turn off power -> if it fails: error -1
2. check if power is off -> if it fails: error -2
3. turn on power -> if it fails: error -3
4. check if power is on -> if it fails: error -4

in your case:
first it could not check for power on
than it could not set the power off?
and than nothing?


- you have to power off the n64
- insert pak and cartridge
- than start the n64 and the tool

if you change or reinsert the cartridge, it's not enough to just reset the n64 or to go back to menu and start the tool over again

some guy already dumped his camera with the tool and it's more or less doing the same with the camera as with the normal cartridges :>
so i can't say that there is anything special you could try beside cleaning.

[Mattroid]

I tried both v0.5 and v0.6 (w/ram write), though with v0.6 I may not have shut down the N64 after testing the GBC game. I'll go try the camera from boot up now and report back.

EDIT: Same problem. Weird. I'll take the camera apart and clean it better when I can...I can't seem to find my triwing or technical screwdriver set so I'm kinda stuck at the moment.

[blueberries91]

I just received my everdrive 64 and went to boot up my pokemon silver when I noticed the battery died on my save  now I dont have a save and am having a hard time finding any .srm saves. Would it be possible to used a .sav file with this program, or could anyone post their .srm save for pokemon silver?

[saturnu]

gameboy saves are gameboy saves :>
i just named it .srm

-> just rename the file ending

[yoloswag420]

on the top left is my usb loader client in the terminal, dumping the ed64 sdram.
the ed64 is running alt64.
on the right you can see geany with the the library source. ^^
it's great that it's possible to use the ed64 sdram as extended ram, 'cause the n64 only has 4 or 8Mbyte rdram. :>



EDIT: today i implemented ram bankswitching and reading/writing (untested) :>

>dat wallpaper
>dat wm configuration

[saturnu]

i'm not sure what's happening if all the power commands are failing.
maybe the 3v3 power supply rail is a bit weak after all these years.

in my case i have some ripples on the 3v3 rail as well.
this could be fixed by recaping the power supply. :>
(it's making funny noises even with just the few mA more, the expansion pak needs, if i insert it ^^)

every device you add uses a few mA more and stresses the power supply

if you have some problems with the tool:
maybe it could help to replace the expansion pak with the jumper pak
or unpluging all other joypads...

the 3v3 rail starts at the power supply and goes
[power supply 3v3]->[n64]->[joypad]->[transfer pak (3v3->5v)]->[cartridge]

these are quit a few connectors and
if you want to try to reduce the impedance by cleaning them
these are the important points

isopropyl alcohol and a gum eraser are good tools for it

n64 side of the power supply connector


n64 side of the joypad connector


these are the more critical ones
even shaking the pak while using it could produce errors

as you can see gnd and 3v3 are split over a few pins

front of the pak pcb


back of the pak pcb


game boy carts, are transported in pockets, lying on the carpet...
there is a good chance for dust to cover the contacts and even to go over into the cartslot

for the cartslot on the tp, maybe you could use some cardboard ^^

(sandpaper isn't a good idea, think of corrosion ^^)

gb cart pcb (single sided)


happy cleaning :>

[asdfqwer426]

keep up the great work! i was so happy to find this program a few months back, as well as your write up for transfer pak with everdrive GB. in another thread about the GB camera, you mention maybe adding support for changing to port 2. I don't know how hard this would be, but i would love it for my handheld 64, as i like to use the second port for transfer pak.

[panzerwings]

Yeah, I got two transfer packs from ebay yesterday and immediately tried to back up my gameboy camera... I had the same check connection and -1 and -4 errors as the above posters.

I cleaned the connectors on the transfer packs with alcohol and normal gameboy games would immediately just work and get recognized. I was able to dump as well, but gameboy camera would never show up. Turning on and off would not get the camera to be recognized.

Perhaps like you said, maybe the power supply is dying. I will look into getting a 3rd party power adapter and try again.

Edit - Updated 1:51PM 5/27/2015-
I got it to work and was able to repeat it one or two more times. I have everdrive64 v2. Here are the steps I took:

1. System was turned off
2. Plugged both gb camera and transfer pack SNUGGLY into the controller on port 1.
3. Turn on and start  libgbpak beta v.6 (with sram write)
4. Libgbpak makes the gb ding sound and shows the "check connection" message on the bottom and NO -1 or -4
5. If requirements in step 4 has been met, then slightly pull the gb camera out JUST A LITTLE BIT instead of it being all the way in the transfer pack. I am talking about 1 or 2 mm.
6. Press the reset button on the system - not powering it off.
7. Start libgbpak again with a little prayer...
8. Once it shows the name of the game, press B to dump the SRAM, and be patient because it is about 128KB.

Thank you Saturnu for creating this awesome tool!

[saturnu]

hm it seems like it still is connection problem. but altering the position the connector makes contact is a nice little trick. ^^

[panzerwings]

hm it seems like it still is connection problem. but altering the position the connector makes contact is a nice little trick. ^^

Yeah, I will probably open the transfer packs up and clean the gameboy contacts with alcohol eventually. I have two: one for gameboy backups, and one to try the gbloader mod.

[Mattroid]

Nice trick, I'll have to try that. I usually try various things like that but didn't in this case for some reason. Thanks.

[Traveller]

Hey!

I've also now had success. I cleaned the camera pins again, plugged it all the way in, then tried the reset thing and it worked after a couple of tries.

I didn't have to do the pulling out slightly thing. I also used the version which apparently had the write function disabled to put my Pokemon save onto a cart, or was it only the camera that was locked out from doing that?

[saturnu]

same version - with camera ram write enabled (experimental: untested!)
gb64_v06_beta_cam_write.zip

yes, only camera writeback was disabled

[timmy]

Can you add support for dumping unadvertised sram?

I try to back up my Final Fantasy Legend 1 (aka Sa-Ga) game since it only has 1 save file. But I never could with Mega Memory Card or Monster Brain.

I try GB64 and it says the game has no sram! So I think it is a mistake in the rom header.

I think Final Fantasy Adventure (Seiken Densetsu) has same problem.

It is Ok to overdump the unadvertised sram I can fix it.

Thank you for this program.