v64jr with partner-n stubs debugging? I just realized something pretty obvious (happens alot to me, blame it on the the drug abuse in the youth years!): the v64jr CAN'T handle debugging hardware-steered because a) we don't know if it supports bidirectional communication b) debugging requires the N64 to be modded (as for example the Partner-n hardware requires). I wonder if the v64jr can use the same debug stub of the partner -n with a suitable monitor? I know, this should prolly be posted over at dextrose, but AG is my home . Im going to dig into this deeper. If anybody has some suggestion (calpis?) just let me know!
Who ever said the V64 Jr supported hardware debugging??? It doesn't come close to that, all it can do is load data to/from it's RAM and use that RAM to emulate a game ROM. The V64 Jr doesn't support ANY PC communication with the N64, the two can only communicate via the V64 Jr's RAM (software handshaking from polling) which they both can access half-duplex. Even a KuC N64 doesn't support hardware debugging! Hardware debugging requires direct supervision of the CPU through either an ICE or JTAG connection. I don't think anything except the Indy board could possibly support hardware debugging, all other debugging is through software in a game's linked library.
The KµC N64 has the CPU pin "int 4" available on the PI bus, and I believe the Partner N64 cart can use that to break code execution without the need for any debug-stub. The Psy-Q system on the other hand requires a debug-stub to be linked in for debugging....
