#9962 - johnny_north - Sat Aug 23, 2003 4:12 pm
I'm trying to build a multiboot image for the first time. I want to transfer this image from one gba to a second gba that is not using a cart. I've sucessfully managed to compile Jeff F's mbclient demo on dever's and I'd like to do the same with my own multiboot image.
I've included the following define in my gba.h file:
#define MULTIBOOT volatile const int __gba_multiboot = 1;
I'm using Jeff's Crt0 file. I've left the following line uncommented:
.equ __MultiBootInclude, 1
Here are my questions:
1) Jeff's instructions say to use MULTIBOOT at the top of the main file. This is a mutli file project though containing several .cpp and .h files. Do I need to use MULTIBOOT more that one time? Do I need to use it like this:
MULTIBOOT = what ever or just MULTIBOOT.
2) If creating a multiboot image is sucessful, should all of the code reside in the EWRAM portion when I look at the map file? ie all in the 0x02000000 area? After trying to compile this as a multiboot, the map file still shows code in the 0x08000000 area.
When I compile using one instace on MULTIBOOT in my main.cpp file, then that the image and transfer it, the stransfer seems to happen normally, but the second gba just displays a blank screen. The mb bin does execute by itself in VBA though, so I know there's nothing wrong with the code itself.
Can someone help me build this mb image correctly?
I've included the following define in my gba.h file:
#define MULTIBOOT volatile const int __gba_multiboot = 1;
I'm using Jeff's Crt0 file. I've left the following line uncommented:
.equ __MultiBootInclude, 1
Here are my questions:
1) Jeff's instructions say to use MULTIBOOT at the top of the main file. This is a mutli file project though containing several .cpp and .h files. Do I need to use MULTIBOOT more that one time? Do I need to use it like this:
MULTIBOOT = what ever or just MULTIBOOT.
2) If creating a multiboot image is sucessful, should all of the code reside in the EWRAM portion when I look at the map file? ie all in the 0x02000000 area? After trying to compile this as a multiboot, the map file still shows code in the 0x08000000 area.
When I compile using one instace on MULTIBOOT in my main.cpp file, then that the image and transfer it, the stransfer seems to happen normally, but the second gba just displays a blank screen. The mb bin does execute by itself in VBA though, so I know there's nothing wrong with the code itself.
Can someone help me build this mb image correctly?