Goomba Color update 2019-05-04

It's really awesome to see an update after so many years. Out of curiosity what version of devkitarm are you using? When I tried to use r48 (yea, I know, really old), I got some errors about DoDma and new_dma_packet having conflict definitions (VRAM_CODE) which was easy enough to fix. The real problem is the compiling fails with "(.iwram.1+0xed0): additional relocation overflows omitted from the output". If I get this compiling, I'll probably release a custom version of Goomba Color for the EZ Omega to wait ~5 seconds of waitframe() calls after every writeconfig() call since, AFAIK, that's the last SRAM write.

 

Is there an official changelog? I know this is just one change, but I'm curious about the other revisions' changes.

 

Oh damn, nice! I didn't expect to see an update to goomba.

 

Much love and thanks for still contributing to this scene. You are a work horse.

 

hm, I think I'll add this to my homebrew archive.

 

Sorry, my mistake. I had devkitARM symlinked to an earlier version (r26) as I was recently recompiling some old Pogoshell plugins. Version r48 works (though I did have to change makefile to Makefile in Makefile). Thanks for checking though. I do wish the whole push towards pacman wasn't a think with devkitpro. :/

Edit - So, ended up ditching adding a framecounter thing (because oddly it wasn't working and exit_ calls writeconfig() anyways, so might as well just always do a 5 second wait). Anyways, here's an attached version for EZ Omega users using my or Sterophonick's version with Pogoshell plugin support.

 

Yea, I noticed that, changed it to "05-04-18 EZ Omega" and found out the hard way about "EWRAM_BSS char str[32]; //ZOMG global variable!". Ended up using 05-04-18K to differentiate it since that fits with "Crap" and "Prot". (And now just remembered it's 2019....) So, fixed link.

 

out of the woodwork, nice to see any update to this good ol bit of love for the gba!

 

The EZ Omega has a chip (FPGA or something) that monitors SRAM/EEPROM/Flash and will continuously write out to the inserted microSD card whenever it sees a change*. The 5 second delay is merely to give said chip time to complete the write out since, unfortunately, there's no way to actually query the chip if a write is in-progress/done--for a while there was some discussion of including some text or audio cue. It's a shame, too, since I don't fully trust their claim that it only takes "a few seconds" to write out as a consistent number; I merely chose 5 seconds because that should hopefully be long enough.

* EZ Flash Team ended up making a kernel patch for one of the Fire Emblem games so it wouldn't change the SRAM every step because that was apparently causing problems. They actually nopped out the writeconfig() in exit_ for pocketnes and goomba color included with the standard kernel to try to avoid the whole problem. Of course, that still translates into requiring the user to wait several seconds after loading the menu just to be careful.

 

Wow that's great to see you all at this again after so long. Last year I conceded it was just too toxic with games anymore and went towards going into kits on most the stuff I've retained, including that EZ Flash Omega which is fantastic and having your emulator as part of it was excellent as I had been used to making my pre built files like a decade earlier. It was nice to do this as it's fun having those nice GB/GBC games working on a thing like a GB Micro I use. The other day I scored an immaculate black dslite for almost nothing, so now I'm considering a flash kit for that 15 years too late I guess. I know a good many GBA started projects moved to the more hefty hardware so that should be nice if I can track down something that works.

 

Dang, a Goomba Color update in 2019? You just made my day, dude. Shame PocketHeaven isn't alive anymore to see this update, I miss that site.

In any case, thanks for never giving up on the GBA Dwedit, both you and Kuwanger here.

I still think Plugin2GBA and a specific "jpg.bin" plugin is the best way to view image files too big to otherwise fit in the popular GBA JPEG Viewer app.

And I still love showing people "Hey, you remember the TI-83 calculators we used in math class? I'm playing the TI-83 version of Tetris, in glorious 96x64 black-OR-white output, right here on my Game Boy Advance, in more-or-less full-screen with fully working controls!"

"...but why?" "Just because."

 

I wish we could get multiplayer somehow

 

Auto-sleep setting doesn't save properly. Still auto-sleeps after 5 minutes even though it's off in the settings.

Works fine if I specifically bring up the settings menu and enable then re-disable auto-sleep, but if I power off and reload the game later, it'll still auto-sleep after 5 minutes, even though I can bring up the menu and see that auto-sleep is off.

 

I cannot compile any file with Goomba Front, it says it is compiled but no file is created... Is Goomba Front compatible with Windows 10 ?

 

Outside of what I've read of Pokemon games being bad on Goomba, do you guys find Goomba to be accurate and compatible enough to be a replacement for ED GB (or similar Jr) native playing carts on gameboy hardware?

I dont like the idea of emulating on hardware that can natively play stuff, but its nice to have the option on GBA flashcarts if its not within reach

plus save state is a leg up on pretty much all GB carts except the x7 which has it for those password progress games

 

Does everyone elses' menu (brought up by L+R) still show 12-14-14?

Also, I can't seem to play one of the classic roms I unfortunately got rid of - X-Men: Mutant Academy, it just shows a white screen. Is there any way to fix? The rom runs fine in Visualboy Advance on my PC.