Hey: I have another issue now, when I re-hooked up my GDEV, I can't get it to work. Basically, it knows if its connected because when I do odrun, it says its powered off, when its powered off, however, none of the demo's run on it??? It just flickers the screen and goes back to the checking.... image... any ideas?? is there any way to validate that its working properly? thanks Jeff.
If it helps, the screen is showing "Checking..." for a while, then says "Device not ready" .... what device?? the GDEv is obviously on
Mine does exactly the same Jeff. From what I understood it meant that the Gdev was waiting for a cart to be installed or data to reach it via the ODEM card. I could be wrong, but when mine initially did this I freaked as I also thought it spelt disaster! I've been too busy with work to do anything with mine since. Suffice to say my Gbox also produces the same message. I shall TRY this weekend to do something with the unit, I have everything I need (other than a cart). I'm sure the "Usual Suspects" with Nintendo knowledge will reply later, but I thought I'd allay your fears!
usual suspect here connect the serial port to ur PC, and u ll receive a message detailing ur GDEVs features over RS-232 and read through hyper terminal (provided u installed the sdk option) if there's info for each component then the uni is fine and problem free. other than that, send some .elf file over and watch it do magic. GCM files are also supported if u follow some instructions I posted a while ago.
Barcode: Thanks, Here's what I get when I hook up the Serial cable and turn on the GDEV: Dolphin OS $Revision: 36 $. Kernel built : May 28 2001 14:21:39 Console Type : Development HW3 Memory 48 MB Arena : 0x8156bf60 - 0x81700000 bootrom Bus Clock = 162000000 Hz Core Clock = 486000000 Hz So, if the machine is fine, why do all the demos I run from the SDK just flicker the screen and then goes back to Checking... When I run the demos, I see this: C:\DolphinSDK1.0\HW2\bin\demos\gddemo>OdemRun -enfw gd-light-gc-load.elf default-ddf = "C:\NPDP\GDEV\bin\OdemRun.ddf" user area = 00050000 - 57058000 LongFileNameSupport=1 Execute Time: 0.016 sec C:\DolphinSDK1.0\HW2\bin\demos\gddemo>odrun gd-init-gc-create.elf C:\DolphinSDK1.0\HW2\bin\demos\gddemo>OdemRun -enfw gd-init-gc-create.elf default-ddf = "C:\NPDP\GDEV\bin\OdemRun.ddf" user area = 00058000 - 57058000 LongFileNameSupport=1 Execute Time: 0.047 sec C:\DolphinSDK1.0\HW2\bin\demos\gddemo> If you notice the execute time is sooo tiny, these demos should be longer. Any ideas why its crapping out soo early? If we get that output from the GDEV unit, does that mean the SCSI cable is fine? Also, is there a way to check the memory maybe? Thanks Jeff.
Parris: Thanks, that does help! However, I HAD this working just a few days ago and now all of a sudden no demos will run and my game won't run.... I've tried everything short of replacing cables (which I'm thinking about doing)
well there's two "modes" the GDEV operates in. NPDP and GDEV. Yours seems to be in NPDP mode. I m pretty certain there's a way to change the mode using an .elf file or something.
Barcode, I looked through all the docs and found no mention of two "modes".... unless you call using the NPDP Catridges a mode vs PC emulation.... however, there's no catridges plugged in (I dont have any) and it seems to somewhat communicate with the device, it looks like its trying to run the game, but it just exits (and since I have a test game which prints out), it doesnt even hit that, so I'm guessing its never hitting the entry point of the app. I'm not sure why this would be. Anything else you guys can think of for me to try or check? There's not too many buttons on this thing. Thanks Jeff.
I think you're thinking of dev vs normal mode (which is changeable by running an .elf on the kit included in the sdk) but, that just controls if it starts up with the normal os (gamecube logo, memcard browser, etc.) versus dev mode that just skips all that so, you can boot faster. If you have an NPDP cart inserted it should immediately boot the cart with whatever image is currently selected. If you're getting the "Checking..." message its trying to boot over the ODEM interface and talk to OdemSrv. The message is normal until you run OdemSrv and then the screen should go black while waiting for you to launch an image / .elf.
I think I didn't phrase that correctly. NPDP mode refers to cart.based operation, whilst GDEV mode engages when you try and run an .elf either by cmd line or Odemsrv as amlicon said (in better words!)
I am not seeing this. When I run OdemSrv, it still says checking. Do you think its a SCSI cable problem? The only thing that shows it might NOT be a SCSI cable problem is that if I disconnect the SCSI cable, then I get a msg "GDEV is powered off", so can the cable sorda work? I dont have a spare to test, I'll have to order one, but let me know if you guys think that maybe the problem. thanks Jeff.
If you're still seeing "Checking..." while OdemSrv is running then something is wrong. I'd say: Verify that the device driver is properly installed. It should show up as "HUDSON SOFT NPDP-GDEV Odem Device Driver" under ODEMULC in the device manager. Go to properties and make sure Windows reports that its working properly and there are no device conflicts. You may want to try reinstalling it. It could be the cable. If I recall OldEngineer confirmed that while the interface itself is different the cable is still a standard SCSI cable. So, you can probably find one. Though I don't know the specific connector type. Regardless though NEVER remove a SCSI cable while the power is on! That can damage your equipment including GDEV, ODEM card and / or PC.
amlicon, thanks for your response. I did verify the device driver is installed properly with no conflicts. That is definately not the problem. I guess, I will start replacing peices by cheapest to most expensive, so I will try a different SCSI cable, its just a 68-pin connector, so I will try that, if not that, I will try and find another ODEM card, and if that doesn't do it, I have to assume its the GDEV unit (potentially if I pulled out the SCSI if it was turned on). I'll keep everyone informed, let me know if anyone has any other suggestions, but I'll start by purchasing another SCSI cable. Thanks for all your guys help so far. Jeff.
