help with debug / status output for n64 dev board ... kammedo ?

Discussion in 'Nintendo Game Development' started by swcdx, Dec 16, 2012.

  1. swcdx

    swcdx Spirited Member

    Joined:
    Jan 26, 2009
    Messages:
    180
    Likes Received:
    0
    My indy r5k is up and running with Irix 5.3 and my dev board in it ... I think I have all the software loaded (casevision, workshop, IDO, OS2.0 from nintendo...)

    So I ran the standard "test" from the nekochan wiki:

    # gload -s quickprev.n64
    # niff2gfx -b niffprev.nif model.bin
    # gload -s -o0x200000 model.bin

    and it is just sitting there with no output. Which is good, I think - no errors, and gload is supposed to load and run the rom on the board...

    The problem is, I don't have an n64 video cable sitting around, so I can't actually tell if anything is running ... so until I can quickly ebay a cable to plug the dev board output back into the indy video-in, is there any way to tell what is going on ?

    I tried running 'dbgif', which is described as:

    "establishes a link between the host workstation and the game target. Specifically, it provides a link between [FONT=COURIER NEW,ARIAL]gvd[/FONT], the debugger running on the host development workstation, and the game system development board."

    ... but it fails with a gethostbyname error, which is weird since I have a hostname set on this system, and even added it to /etc/hosts ... not sure why it is failing like that.

    So, any other next steps I can use to just see what is going on ?

    Thanks.
     
  2. swcdx

    swcdx Spirited Member

    Joined:
    Jan 26, 2009
    Messages:
    180
    Likes Received:
    0
    So yeah ... I'm doing something wrong here. N64 board shows up at boot time, so it appears to be functioning, etc., but I don't know how to load a rom and execute it.

    I have my n64 dev board installed in an r5000 indy, as opposed to the r4300 processor indy that it was originally used with, and this is complicating compiling the sample programs ... the makerom utility, for instance, fails to run.

    So ... the first step is to figure out if the dev board on an r5k indy will work at all, and I need two things to test that:

    - a prebuilt "rom" for the n64 dev board ... this can be an actual n64 rom that has been "fixed" for the dev board, or a sample program that has been made into a rom ... basically, if anyone has a dev system up and running, can you send me over a known-working rom file ?

    - commands to run to load and execute the rom. I am suspicious of the gload/niff2gfx/gload commands in my previous post - I think these are for the external cartridge dev kit, and not for the development board, and I don't think niff2gfx is what I am supposed to be using...

    So basically: help!
     
  3. cmonkey

    cmonkey Rising Member

    Joined:
    Mar 29, 2012
    Messages:
    62
    Likes Received:
    20
    I believe Jackhead has a fully working R5K Indy/Ultra 64 setup. Maybe if you ask him nicely via a PM he'll be able to help you out a little.
     
  4. swcdx

    swcdx Spirited Member

    Joined:
    Jan 26, 2009
    Messages:
    180
    Likes Received:
    0
    Thanks - I will.
     
  5. kammedo

    kammedo and the lost N64 Hardware Docs

    Joined:
    Sep 24, 2004
    Messages:
    2,138
    Likes Received:
    12
    Hey;
    sorry for the late reply.
    I hope you got your answer by now, but in case you did not, if you have a composite cable you can just redirect the video out of the U64 board to the Video in of the Indy; then launch the capture program (from command line - i think the name was something like "capture"). Of course this assumes you have a SGI monitor for the indy *or* an adaptor (which should work with most new ACER LCDs):p. Also, once this is done, you might want to adjust the "capture" program to be configured for proper input capture (NTSC, size of capture etc).

    This is the way I made the Topgun videos.

    dbgif is only half the story; as you said, dbgif is the service bridge between the u64 board and the indy host.
    On top of that, you need some more utils but hell I can't remember the name :/ (i think dprint, doutput or something). They are in the kit tho, so it should be easy to find them (also there should be documentation for them).

    Ah, btw. There are test utilities for the RCP / RSP / RAM / CPU, which can be used to check the status of it. rcp-cmd or something. also in the dev kit ( in some /bin directory).

    Good luck and enjoy your u64 board adventure! :) It is an epic journey! :)
     
    Last edited: Dec 26, 2012
  6. swcdx

    swcdx Spirited Member

    Joined:
    Jan 26, 2009
    Messages:
    180
    Likes Received:
    0
    Ok, I will look for those other test/diag utilities that you mention - that is helpful.

    I need to get capture up and running - it is installed, and works, but somehow I don't have the package that enabled video capture, so that option is greyed out until I install it.

    PM'ing you with some more detailed questions...
     
sonicdude10
Draft saved Draft deleted
Insert every image as a...
  1.  0%

Share This Page