Page 1 of 1

The rom-image has crashed

Posted: Sat Feb 20, 2010 3:53 am
by dranka
Hi!

I installed last version of devkitARM on windows Xp using autoinstaller and try to compile some examples. When I compile a gba example, it does work. The exemple runs great on emulators.

Now, when I compile a hello world example to NDS (or any other), it does compile without errors, but when I run the rom, it crashes Dualis and so no$gba. The last shows the above message (The rom-image has crashed).

Anyone can help?
Thanks!!!

Exit from programmer's notepad, when I compile hellow world to NDS:

Code: Select all

> "make" 
main.cpp
arm-eabi-g++ -MMD -MP -MF /c/devkitpro/examples/nds/hello_world/build/main.d -g -Wall -O2 -march=armv5te -mtune=arm946e-s -fomit-frame-pointer -ffast-math -mthumb -mthumb-interwork -I/c/devkitpro/examples/nds/hello_world/include -I/c/devkitpro/examples/nds/hello_world/build -I/c/devkitPro/libnds/include -I/c/devkitPro/libnds/include -I/c/devkitpro/examples/nds/hello_world/build -DARM9 -fno-rtti -fno-exceptions -c /c/devkitpro/examples/nds/hello_world/source/main.cpp -o main.o 
linking hello_world.elf
built ... hello_world.arm9
Nintendo DS rom tool 1.46 - Nov 30 2009
by Rafael Vuijk, Dave Murphy, Alexei Karpenko
built ... hello_world.nds

> Process Exit Code: 0
> Time Taken: 00:01

Re: The rom-image has crashed

Posted: Sat Feb 20, 2010 1:03 pm
by vuurrobin
there is nothing wrong with the compilers output, so the nds file is correctly created.

have you tried running the nds file on the nds?

Re: The rom-image has crashed

Posted: Sat Feb 20, 2010 7:03 pm
by dranka
Hi!

I did the test on nds. The "hello world" worked well. But no$gbad shows "Undefined opcode - with no debug vector defined". It is hard to do a dev without a debugger.

Some sugestions?
Thanks!

Re: The rom-image has crashed

Posted: Wed Feb 24, 2010 7:33 pm
by Izhido
Hmm... "hello world"-like applications usually don't crash on no$gba. Can you please post:

1) The version of the toolchain you're using actually;
2) The actual code of the app you're compiling

so we have a chance to see what might be missing?

P.D. That being said, do *not* trust emulators over actual hardware. If it works on hardware, but not on an emulator, your code has more chance of being right than if it was the other way around. no$gba development seems to be halted for a while, and it's only a matter of time for it to start *failing* to run apps created with the toolchain's latest version.