This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - BuckeyeDude
Pages: 1 ... 10 11 [12] 13 14 ... 19
166
« on: September 23, 2010, 04:49:59 pm »
Assuming you use reg-free COM you can only use the DLL of wabbit, which means you have to roll your own GUI (you can grab a copy of the screen no worries). If you do use the exe, then yes the debugger does not open if you encounter a breakpoint and have defined your callback handle
168
« on: September 23, 2010, 04:13:15 pm »
It's not an emulator per-say, its more of a debugger. Technically, it is a debugger, but it won't be available outside of tiDE. It's sole purpose is to be a debugger that can integrate with the IDE. I would really rather integrate WabbitEmu, but it is not compatible with .NET without some *serious* porting work.
hmm i only happened to catch this from a random search, but wabbitemu provides a COM interface that is fully compatible with .NET. Better yet it should work with reg-free COM (read: no admin required  ). Netham45 is using this in webbitemu. Just something to consider...
EDIT: i should also mention that this is definitely a work in progress, so expect a little head banging frustration sometimes 
Interesting, does it allow me to programatically set breakpoints, access the memory, run a callback method when a breakpoint is hit, and read and modify the state of the hardware?
Also, perhaps more of a feature request than anything else, but can it emulate missing RAM pages or the LCD driver glitch?
Yes yes essentially yes (you provide a handle it sends the WM_USER message, so you can then do whatever you want with) and yes. it also allows you to step (in over and out) and more. As for the extra ram pages, it is #ifdefed i need to make an option for it. LCD update delay is on the to do, but I don't know what happens if you try to write too fast
169
« on: September 23, 2010, 04:35:05 am »
my point is that wabbit is already compatible. There is no need for him to rewrite anything in C++ he can basically plug and play with this system. In fact i've implemented the same sort of thing he wants to do with wabbit using the interface
170
« on: September 23, 2010, 01:56:54 am »
i think i fixed the mem leak on buttons, i made the mem map in hex, the gradient is drawn so it is easier to see the lines, the profiler doesnt hang when you close out of it, and the run menu actually does stuff. also i dont think maximizing jacks memory usage up anymore, or at least i cannot reproduce. Those The one i didn't fix is an issue with keys getting trapped in the down state when the debugger opens faster than you can release
171
« on: September 23, 2010, 01:53:25 am »
Just a little update for ThePenguin77, all but one of the things you reported to me is fixed. For normal users the cool part is the darkening keypresses are back! Powerusers, the debugger is a little more stable, i think i fixed the mem leak on buttons, i made the mem map in hex, the gradient is drawn so it is easier to see the lines, the profiler doesnt hang when you close out of it, and the run menu actually does stuff. also i dont think maximizing jacks memory usage up anymore, or at least i cannot reproduce. I should also note that a couple version ago i added more interrupt info (IM mode, i and r regs)
172
« on: September 23, 2010, 01:30:46 am »
It's not an emulator per-say, its more of a debugger. Technically, it is a debugger, but it won't be available outside of tiDE. It's sole purpose is to be a debugger that can integrate with the IDE. I would really rather integrate WabbitEmu, but it is not compatible with .NET without some *serious* porting work.
hmm i only happened to catch this from a random search, but wabbitemu provides a COM interface that is fully compatible with .NET. Better yet it should work with reg-free COM (read: no admin required ). Netham45 is using this in webbitemu. Just something to consider... EDIT: i should also mention that this is definitely a work in progress, so expect a little head banging frustration sometimes
173
« on: September 19, 2010, 07:20:55 pm »
That's my guess. I can't really say without getting some information from off your actual calc. If you have calcsys follow the instructions below, otherwise ignore it.
Run calcsys, and goto the VAT option (2nd page, 1st item). Go into programs (1st item), and then go through the pages till you find you program and select it. You should see information about the program. Press Alpha then V. It will go to the hex editor. Press left twice. I then need the number in the top left corner
Again, not crucial but it will tell me if its a TI connect problem or an issue with the program on calc
@Meishe the string had nothing to do with it if i understand correctly. By creating another program you corrected the version number and allowed the program to transfer.
174
« on: September 19, 2010, 07:15:25 pm »
TI uses a version number in their file header (to prevent sending something that uses tokens unavailable to some calcs eg: CheckTimer( on the 83+) that it checks when you transfer it. If the version number is higher than it can handle, it rejects the file.
175
« on: September 19, 2010, 07:09:09 pm »
I'm on it gents. Unfortunately its something wrong with the file itself, not wabbit. The version number directly after the name was way to high (0x43), dropping that down allowed TIOS to accept it. And yes i know wabbits error messages suck. Complain to spencer he implemented the protocol MRide what linking software do you use?
176
« on: September 19, 2010, 12:17:01 am »
I'm fairly sure Wabbit does allow unsigned apps because I'm pretty sure I've tried some and then later people are apologizing for not putting a signed one up.
Wabbit does indeed accept unsigned apps...were too lazy to write a validator (although i suppose i could steal code from spasm). If you would like to check to see if an app is properly signed without sending it to a calc (the calc actually writes it to flash then erases it if it fails to validate), you can reset all memory on wabbit then load the app. This will simulate sending the app the long way and the os will actually validate it
177
« on: September 17, 2010, 06:04:50 pm »
The ROM dumper is integrated directly in Wabbitemu? Does it require additional softwares such as Rom8x? I might test but I am unsure if I will have much time yet until next weekend.
correct. I've modified the rom8x source to work better and am using wabbit as a front end for it. Look under help->setup wizard to better see what i mean.
178
« on: September 17, 2010, 06:01:04 pm »
And there it is, dumping roms for the 83 plus series works. I will need some cooperation with other people to make the 73,82,83,85,86 work since I don't own them, but its a start!
I just uploaded to codeplex. If you guys could grab it and do some testing, make sure I didn't break anything important, test the new rom dumper see that it actually works for you, etc I'd be very grateful. If all goes well, I'll bang out a readme and submit to ticalc later tonight
179
« on: September 16, 2010, 09:48:18 pm »
Oh, I found another bug: If the "Goto" button in the debug window is forced to be secondary (you have to click >> button to get to it) it doesn't work. In fact, even if shown primarily, it won't work unless the disassembly section has focus. The right-click menu does not work either.
Ah yes thank you for reminding me Fixed fixed and fixed EDIT: i should also update a little on the release progress. i've modified rom8x to only require a single program now (and the same one works for all 8x models). Im currently coding the function to extract and send the file with TI Connect when you press a button, then i'll merge rom8x code to create a rom file. I would like people to test it, so if you can copy this to your calc and run it make sure there are no errors
180
« on: September 16, 2010, 05:12:06 pm »
Download Axe Parser 0.4.4. I had a crash occuring on that one. Also maybe a contest entry like guy602665.
Tested both of those and both ran fine. Do you have two calculators open when you try to send these files?
what do you mean?
I mean if you have the option to open a new core on send files checked it will not work right now. But if you only have one wabbitemu window open it doesnt matter, its not that. Does the program crash or give you an error message?
Pages: 1 ... 10 11 [12] 13 14 ... 19
|
Show Posts