Omnimaga
Calculator Community => Other Calculators => Topic started by: ExtendeD on November 06, 2010, 11:55:52 am
-
Ncubate - Enhanced TI-Nspire emulator
http://www.omnimaga.org/index.php?action=downloads;sa=view;down=595
Ncubate is a custom version of Goplat's nspire_emu enhanced with features useful to developers, such as state saving/reloading, additional debugger commands and support for the GDB debugger.
-
Woah this already got 18 downloads o.o
And if you check the now defunct RPG sections, the top downloads are all Nspire stuff. That shows how high the Nspire popularity got over here.
I'm glad you made this, since this can be very helpful for developers
-
Was this an automatic post triggered by the file upload?
-
Yeah that happens when we add an upload. I can merge it with the other topic if you want.
Btw, should we split your update and the discussion that ensued in the news section?
-
Btw, should we split your update and the discussion that ensued in the news section?
Well I really don't know, how do you usually do? Do you keep a project page in "Other Calc-Related Projects And Ideas" and feature some updates in dedicated topics in "Other calculator discussion and news"?
-
I've been having trouble building files from eclipse. :(
I installed it and put MSYS's /bin in my path, but when I go to build I get:
**** Build of configuration Default for project ChipsChallenge ****
make -k all
make: Interrupt/Exception caught (code = 0xc00000fd, addr = 0x425073)
For a while, it was complaining that it could not find os.h, but I directly put that in the project folder. Is there anything else I have to do to get this to work? I followed the instructions exactly as they were on the video.
-
Btw, should we split your update and the discussion that ensued in the news section?
Well I really don't know, how do you usually do? Do you keep a project page in "Other Calc-Related Projects And Ideas" and feature some updates in dedicated topics in "Other calculator discussion and news"?
It depends, when a release of such software occurs, I usually move the topic in the news section on the front page, but in your case, that would mean splitting the topic.
I could simply use this topic and move it, then edit it a bit with a more info link to the other one, though.
EDIT: Actually nvm, the other topic only got one reply anyway, so I'll split your update post in the news section.
-
apcalc: So "make" crashes, weird...
I suppose you have installed Eclipse CDT 7.0.1. Which version of MSYS are you using?
Before you moved os.h, did nspire-gcc throw an error, or are you talking about the warning underlined by the IDE? The latter is harmless.
Can you try to "make" on a DOS command line, from your project's directory in the Eclipse workspace?
-
I am using the latest version of MSYS from the download page on their website. For os.h, eclipse said something like "invalid inclusion"; it was not from nspire-gcc. "Make"ing directly from MSYS works fine.
Do I need to set anything to tell it to use MSYS to compile, or is adding to my path all I need to do?
-
For os.h, eclipse said something like "invalid inclusion"; it was not from nspire-gcc.
Ok, don't worry about that.
"Make"ing directly from MSYS works fine.
Could you try in a standard DOS console? This would be closer to what Eclipse tries to do.
Do I need to set anything to tell it to use MSYS to compile, or is adding to my path all I need to do?
Changing your PATH should be the only configuration required.
-
When I try to "make" in the Windows Command Prompt, I get the same error that Eclipse is giving.
-
Could you check if your problem is the one described in the following topics?
http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=64657#623996
http://hdrlab.org.nz/articles/windows-development/make-interrupt-exception-caught-code-0xc00000fd-addr-0x4217b/
The configuration which would make "make" crash is a 64-bit OS, YAGARTO installed in "C:\Program Files (X86)\..." and/or a "C:\Program Files (X86)\" preceding YAGARTO's bin/ directory in the PATH directory list.
If this is your configuration, could you please try the solution suggested in the topics:
- Reinstall YAGARTO in C:\yagarto instead of Program Files or create a symbolic link pointing from C:\yagarto to the version in Program Files.
- Make YAGARTO's bin directory the first of the PATH directory list.
-
That seems to have been the problem. 64-bit OS strikes again...
Thank you very much for your help, ExtendeD :)
Now, to go and try the debugger...
-
How did you fix this? We should add the tip to Hackspire.
-
All I did was move yagarto to C:\Yagarto from C:\Program Files (x86)\Yagarto.
EDIT: I added this to Hackspire :)
-
Thanks!
Were you able to use the Eclipse debugger?
-
Bit of a necropost, sorry 'bout that... :P
But I have a question concerning ncubate, eclipse, and gdb.
I'd really like to be able to use ncubate and gdb as a debugging tool, but I can't seem to set it up properly.
I've already watched the tutorial, and I've been able to do everything up to the part selecting the "GDB (DSF) Remote Process Launcher." For some reason, eclipse does not want to let me do remote debugging - it does not even show in the window! (See the picture below - there should be a third option, but there are only two.)
I know that ncubate does not work with ndless 3.1, but I still would like to be able to use it. Any thoughts?
Thanks in advance
MM
-
There seems to have been changes in the menus of the latest Eclipse CDT version for this option, could you please check if this helps? http://wiki.eclipse.org/CDT/User/NewIn80#C.2FC.2B.2B_Remote_Application_launch
We are also planning to update Ncubate with Ndless v3.1 compatiblity.
-
We are also planning to update Ncubate with Ndless v3.1 compatiblity.
That is great news! Thanks :)
-
There seems to have been changes in the menus of the latest Eclipse CDT version for this option, could you please check if this helps? http://wiki.eclipse.org/CDT/User/NewIn80#C.2FC.2B.2B_Remote_Application_launch
Thank you very much! I think I figured out what needs to be done instead, and this helped quite a bit.
Goto the Remote Debugging tab -> click Select Other... -> check the box and change it to Manual Remote Debugging.
Everything else should work the same.
We are also planning to update Ncubate with Ndless v3.1 compatiblity.
That is great news! Thanks :)
Indeed, this will be awesome when complete!