#57353 - jun - Sat Oct 15, 2005 4:31 am
Ive decidd to just use eclipse for devkit advance instead od DevC++ and VC++. Can anyone point to a tutorial on how to configure this? :)
#57382 - Cearn - Sat Oct 15, 2005 1:14 pm
AFAIK, there isn't one for devkit advance. But there is one for devkitARM, which is the preferred toolchain nowadays anyway.
Linky.
The rest of the FAQ should have other interesting info on compiling platforms and devkits as well.
#57405 - NoMis - Sat Oct 15, 2005 5:01 pm
I have done some plugins to make development with Eclipse easier. Althought it uses DevKitArm it can still be easily used with DevKitAdv. Althought I would suggest using DevKitArm anyway since devkitadv was not updated for a while.
Handheld Dev Env
Take a look at the Feature Page to see what this plugins can do for you.
If you just want to use Eclipse without my plugins you should take a look at this guide.
NoMis
_________________
www.gamedev.at - The austrian gamedev site
hde.gamedev.at - The Handheld Dev Env plugins for Eclipse
#57586 - jun - Mon Oct 17, 2005 4:09 am
excellent help, right on target, thanks!
#59038 - jun - Fri Oct 28, 2005 10:39 am
Hi again, I am just having trouble configuring for debugging. Bruce sinner has posted a great tutorial, but the link on the GDB command file is down, I have searched for command files but cant find any for this situation. Does anyone know how to create these files? or have an example?
P.S.
Also when i downloaded devkitARM from devkitpro.tk, i cannot find the GDB executable...what is the name of the debugger for DEvkitARM? I may have just missed the name!
Thanks!
#59040 - NoMis - Fri Oct 28, 2005 10:57 am
To debug with DevkitArm you need to download Insight-Gdb from the Devkitpro Sourceforge site.
Extract it to somewhere you want and optionally set the path environment variable to it's bin directory.
Then you need to open your launch configuration within eclipse. On the debugger tab change the gdb executable to "arm-elf-gdb". If you did not set the path you will need to use the whole path.
Althought this is the version with the insight frontend, eclipse will start arm-elf-gdb withouth the frontend automatically.
Also note that Thumb Code compiled with any version newer than R8 of Devkitarm will not be able to be debbuged correctly. As far as I know this is the fault of GDB not handling the eabi change in GCC.
NoMis
_________________
www.gamedev.at - The austrian gamedev site
hde.gamedev.at - The Handheld Dev Env plugins for Eclipse
#59041 - jun - Fri Oct 28, 2005 11:01 am
hi NoMis, thanks ofr the help. do you have any yahoo messenger or AOL? :) my YM is ticked2 and my AOL is ticked2x.
#59231 - jun - Sun Oct 30, 2005 4:26 pm
I can get to debug mode, my program stops on a break point, however the step/f5/f6 and disabled. could this be because of how i compiled my rom? i did specify the -g option.
#59304 - NoMis - Mon Oct 31, 2005 10:14 am
Normally the -g option should be all you need to debug your code. The debugging seems to work if it can stop on a breakpoint correctly. Thats why I have no idea why it should disable the ability to step through the code.
Maybe you should check out the GDB console.
NoMis
_________________
www.gamedev.at - The austrian gamedev site
hde.gamedev.at - The Handheld Dev Env plugins for Eclipse