gbadev.org forum archive

This is a read-only mirror of the content originally found on forum.gbadev.org (now offline), salvaged from Wayback machine copies. A new forum can be found here.

Announcements And Comments > devkitARM release 12

#43343 - wintermute - Sun May 22, 2005 1:37 pm

updated to gcc 3.4.4
updated to newlib 1.13.0
added nds crtls
improved gba crtls
added makefile fragments for gba/gp32/nds

devkitPro

alternative url for those having trouble with the .tk host

devkitPro


Last edited by wintermute on Fri May 27, 2005 1:01 am; edited 1 time in total

#43349 - Quirky - Sun May 22, 2005 4:49 pm

The new crt0 for the gba takes a long time to start compared to the r11 version.

Code:

  @---------------------------------------------------------------------------------
  SkipEWRAMClear:                                 @ Clear Internal WRAM to 0x00
  @---------------------------------------------------------------------------------
          mov     r0, #3
          lsl     r0, #24                         @ r0 = 0x3000000
          ldr     r1, =__iwram_end
          bl      ClearMem


this is the culprit. The ClearMem loop uses r1 as the number of words to clear at address r0, here the count is 0x3008000. In r11 it was __sp_usr_offset-16 = (__sp_usr - __iwram_start)-16 = 0x7ef0.

#43390 - wintermute - Mon May 23, 2005 12:28 am

oops, missing subtract. Fixed in cvs

Code:

  @---------------------------------------------------------------------------------
  SkipEWRAMClear:                                 @ Clear Internal WRAM to 0x00
  @---------------------------------------------------------------------------------
          mov     r0, #3
          lsl     r0, #24                         @ r0 = 0x3000000
          ldr     r1, =__iwram_end
          sub    r1, r0
          bl      ClearMem


to fix this in your install, edit as above, make sure ... devkitARM/bin is in your path, open msys shell, cd to ... devkitARM/arm-elf/lib and type make CRT=gba

#43607 - tepples - Wed May 25, 2005 2:55 am

Do you plan on making an updated binary release?
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.

#43612 - funkaster - Wed May 25, 2005 3:54 am

wintermute wrote:
oops, missing subtract. Fixed in cvs


cvs is not compiling... it stops when trying to compile gbafix.c (file not found).
I'll try again and post the log.
(the machine is a G4 box, running Debian sarge)

#43635 - funkaster - Wed May 25, 2005 7:11 am

funkaster wrote:
cvs is not compiling


nevermind... if you download just the buildscripts from cvs, and let the scripts to download everything, it works :-)

#43641 - Lord Graga - Wed May 25, 2005 8:48 am

Great, will get started with DS some time soon :)

#43673 - wintermute - Wed May 25, 2005 6:02 pm

tepples wrote:
Do you plan on making an updated binary release?


I'm currently debating an update package of some sort, perhaps a script to autoupdate the crtls.

#43674 - wintermute - Wed May 25, 2005 6:04 pm

funkaster wrote:
funkaster wrote:
cvs is not compiling


nevermind... if you download just the buildscripts from cvs, and let the scripts to download everything, it works :-)


what were you doing in the first place?

#43697 - funkaster - Wed May 25, 2005 7:56 pm

wintermute wrote:
what were you doing in the first place?


I did:
Code:
cvs co .

(checked out the root directory) all the projects downloaded to the working directory. The I entered the buildscripts dir and executed the shell script. It never complained about not finding the other directories, but failed when compiling the tools. libgba compiled fine though.

#43699 - wintermute - Wed May 25, 2005 8:28 pm

aha, yes, the tools module is embedded in the buildscripts module via some cvs trickery. Checking out the top level isn't necessary or recommended :)

#43832 - blueskies - Fri May 27, 2005 4:37 am

Thanks for the info. I noticed that it was taking a loong time to start a demo in vba, but in five minutes I had it fixed. :)
_________________
-Jonathan
http://juansuave.com

#44864 - tepples - Mon Jun 06, 2005 6:38 am

I'm sticking with devkitARM r11 for the time being, at least until a GCC 4 based version comes out. I tried upgrading from r11 to r12, including patching crt0 as described above, but when I compiled my newest project (using gba_mb.specs), it worked on VBA but not on hardware. It would either white-screen if flashed by itself or reboot the GBA if flashed as part of a PogoShell image. Switching back to r11 fixed the issue

It's just one data point, but for GBA-only developers such as myself, I don't see the benefit of the upgrade vs. the risk of things breaking unpredictably.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.

#44878 - wintermute - Mon Jun 06, 2005 1:52 pm

tepples wrote:
I'm sticking with devkitARM r11 for the time being, at least until a GCC 4 based version comes out. I tried upgrading from r11 to r12, including patching crt0 as described above, but when I compiled my newest project (using gba_mb.specs), it worked on VBA but not on hardware. It would either white-screen if flashed by itself or reboot the GBA if flashed as part of a PogoShell image. Switching back to r11 fixed the issue


At this point gcc 4 is liable to cause similar issues, 4.0.0 has been blacklisted by KDE due to a couple of wrong code bugs. 4.0.1 is due soon and may be more stable.

Quote:

It's just one data point, but for GBA-only developers such as myself, I don't see the benefit of the upgrade vs. the risk of things breaking unpredictably.


Please report bugs on the mailing list rather than moaning about problems in public and encouraging people not to upgrade. While I do attempt to visit the forums regularly I often miss issues here when skimming through posts. For the most part r12 appears to be behaving rather well.

Where possible a testcase should be given showing the problem and, if you have the homebrew licensed no$gba, it may show up where the problem is occurring.

#44886 - tepples - Mon Jun 06, 2005 3:07 pm

wintermute wrote:
tepples wrote:
It's just one data point, but for GBA-only developers such as myself, I don't see the benefit of the upgrade vs. the risk of things breaking unpredictably.


Please report bugs on the mailing list

At the time I found the problem, I didn't have time to make a minimal test case, and I don't want to publish the project's entire build tree for fear of disqualification from any future competition where I intend to use this project. I will try to make a reduced test case when I get a chance and post it to the mailing list. Are .o files OK, or do you need source code?

Quote:
rather than moaning about problems in public and encouraging people not to upgrade.

I was suggesting only that it might not be wise to upgrade in the middle of a project and expect everything to continue to work smoothly.

Quote:
if you have the homebrew licensed no$gba, it may show up where the problem is occurring.

How much does it cost to wire money from a U.S. bank to a German bank?
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.

#44890 - SimonB - Mon Jun 06, 2005 4:28 pm

tepples wrote:
How much does it cost to wire money from a U.S. bank to a German bank?


Depends on the bank, but it doesnt look like Martin wants you to wire money from the US...

no$gba website wrote:
From inside europe only (due to transfer fees).


Simon

#44900 - wintermute - Mon Jun 06, 2005 5:58 pm

tepples wrote:
At the time I found the problem, I didn't have time to make a minimal test case, and I don't want to publish the project's entire build tree for fear of disqualification from any future competition where I intend to use this project. I will try to make a reduced test case when I get a chance and post it to the mailing list. Are .o files OK, or do you need source code?


source is preferred but .o files may help if you have trouble tracking down the exact problem.

You inspired me to fiddle with the devkitPro web pages a little more. I've not added some basic instructions for bug reporting.

http://devkitpro.sourceforge.net/bugs.shtml

Quote:
I was suggesting only that it might not be wise to upgrade in the middle of a project and expect everything to continue to work smoothly.


Unfortunately this pretty much goes without saying - happily devkitPro has progressed to the point where most of the problems encountered can be traced back to the original FSF sources. A couple of devkitPro patches have even made it back into the FSF releases.

Quote:
if you have the homebrew licensed no$gba, it may show up where the problem is occurring.

How much does it cost to wire money from a U.S. bank to a German bank?[/quote]

go here :-

http://nocash.emubase.de/gba-dev.htm

Martin has finally got a paypal account and you can pay directly by credit/debit card without your own paypal account.

I know I consider the $15 money well spent and, if I was still involved in commercial GBA projects I would be moaning until I got the hll debugger :) no$gmb saved our bacon more than a few times on commercial gbc projects.