User | Post |
Parasyte
Posts: 434/514 |
Unless Bebit worked on that before sending his latest source revision, no. I'm afraid I haven't done any research into the subject, either. So I'm not quite sure if it's something I'll be working on, or not. He did mention the reason for it, once or twice. Those reasons seem to have escaped me. ;\ I seem to have more free time than he, (I get each weekend to myself! Yay!) it's probably something I should consider. Anything else? |
dan
Posts: 512/782 |
Does the latest build have the Address Label logger working? As that part of the Code Data Logger dialog seems to do nothing in the v1.0 release. (I presume it's some kind of logger for indirect pointer things) |
Parasyte
Posts: 432/514 |
Dwedit, why can't you just use breakpoints and manually copy [some of] the assembly into notepad? All the cool kids are doing it... But really, I'm not sure why you would need 'conditional logging'? The logger in FCEUXD already does something similar, thanks to the CDL.
As for trouble making sense of the x-refs, yes, it can get confusing. I don't know if I want to do arrow highlighting, but I will definitely do special highlights on single click... (Yep! IDA style!) For example, you can click on an address, and all instances of that addresses will be highlighted with a special background color just for this type of highlighting. I suppose it MAY be possible to add arrow coloring, as well. But the main problem I foresee is that destination addresses with many x-refs will ALL have their arrows colored. That would probably not help things in a lot of cases. So rather than basing arrow highlighting on the addresses (x-refs) it might as well be done based on the 'selected' line of disassembly. In that way, it would disregard arrows pointing to the selected line, and color only the arrow leading from it. Hmm, that would actually work quite well in conjuntion with the single-click highlighter.
Blah, blah. I think I'm rambling now. It's all this lack-of-sleep, I tell you! |
Dwedit
Posts: 23/92 |
For the sound output, I could see using a patch map to translate it into general midi, or maybe just using some sample sets, or possibly even piping it directly into an actual miracle piano (which I have hooked up to my PC!).
If you have a MIDI keyboard plugged in, it should be an obvious choice for an input device. For stuff like Rhythm Practice or Robo Man, maybe even a joystick is enough. |
drjayphd
Posts: 943/1477 |
Holy crap, someone remembers the Miracle Piano?! How are you even using that? I'd imagine there's enough keys on a keyboard, never mind the controller. |
Dwedit
Posts: 22/92 |
I've mainly been using custom compiles of Nester to log all output on 4016 to a binary file. But it looks like all the piano IO is being written via register A rather than register X, so I'd like a way to log all output from register A to 4016. Then maybe I could somehow analyze it and try to find midi data in there or something. |
HyperLamer
Posts: 4152/8210 |
Kickass. Might help to colour the arrows though; I can't follow them very well in some of the more complicated-looking ones. ![](images/smilies/shiftleft.gif) |
Parasyte
Posts: 430/514 |
Apophis, I can't be any more specific; it could be sooner, could be later. Depends a lot on how I spend my free time. ;O
Dwedit, what exactly do you need? Using breakpoints and copying the addresses down should be enough to get you started, right? That's the method I use when hacking most everything. |
Googie
Posts: 334/624 |
Makin an already awsome program even better? Sign me up! I can't wait for the next release. ![](images/smilies/smile.gif) |
Apophis
Posts: 448/882 |
Any idea when we can expect it to be released? I know you said in the next few months, but can you be any more specific? |
Dwedit
Posts: 21/92 |
Conditional logging perhaps? I'd like to log all the output on controller 1's port so I can figure out how the Miracle Piano IO works. |
Setzer
Posts: 170/532 |
There's no reason not to get back into NES hacking now. the current debugger is fine; they're just re-writing it to be more awesomefull. |
Sokarhacd
Posts: 1130/1757 |
awesome, I might have to get back into nes hacking when this is released ![](images/smilies/smile.gif) |
Parasyte
Posts: 429/514 |
I suppose so!
Well, I tried adding the copy/paste functionality to the disassembler control, but got a bit side-tracked and added branch/jump x-ref (Cross-Reference) handling instead. It's a bit primative, at the moment, but it looks really nice.
Here's some eye candy: (Bigger images with the clickage!)
![](http://parasyte.panicus.org/projects/fceuxd/dis-xref.png)
![](http://parasyte.panicus.org/projects/fceuxd/dis-xref2.png)
![](http://parasyte.panicus.org/projects/fceuxd/dis-xref3.png) |
Kyoufu Kawa
Posts: 1410/2481 |
Well, that makes two acmlmboarders that write their own psuedocode and are proud of it. |
Parasyte
Posts: 427/514 |
I'm glad I'm not that one who had to point out the obvious. ;D
As for the not-so-obvious, I had no plans for <= or >=, because those can be done with JMPE and JMPL(G) together. Adding them wouldn't really hurt anything, though... Why were some defines skipped? Future expansion! As I mentioned in the initial post, PMC is missing some things, like pointer access. For that, I will probably use a MOVE instruction, located at 0x06... I don't see much use for bitwise logic or arithmetic instructions, but if they are needed, there's still plenty of room for expansion!
Also, I'm debating whether I should change the 'compiler specs' so it doesn't use the MSB for labels. Instead, it may be better to keep a local symbol table, with each label referencing it. Though that's a bit out of scope, as it's something the user will never see.
[D'oh!] Yes, the control source will be released. Afterall, the whole project always has (and always will be) open source via GPL. |
HyperLamer
Posts: 4113/8210 |
Originally posted by Parasyte Work register (operand) defined in LSB of all instructions. Instructions without register operands make no current use of LSB.
Come to think of it, that also answers my question as to why it skips all the odd numbers. (Though why are 6-F skipped? )
Are there going to be compares for >= and <= too? It'd help shorten the code a bit. |
Geiger
Posts: 350/460 |
02 20 00 LOAD r0,$0020 ;load 32 into r0 05 05 COPY r1,SCAN ;copy scanline counter into r1
How are you specifying r0 and r1 here?
---T.Geiger |
HyperLamer
Posts: 4111/8210 |
Have my baby.
I'll have to incorporate a lot of these into my GB emulator on the odd chance I ever finish it. You gonna release that control? ![](images/smilies/wink.gif) |
iamhiro1112
Posts: 369/487 |
I look forward to the new release. I hope you guys put in programmable keys. As in we can edit what button we can use to access certain features. Right now I use Joy 2 key so that I can save and load with my controller. |
This is a long thread. Click here to view it. |