So what information is needed if a rom doesn't work? Like crc32, rom name etc.
as much information as you wish to provide. they simply asked for a list. however, fully debugging and checking by crc is probably a good idea before something is reported as not working.
GBA Games:
- classic nintendo series super mario bros - bottom row of pixels flashes. happens with both the rom and actual cartridge.
- classic nintendo series excitebike - bottom HUD flashes, as does the "nintendo" logo.
- wario ware twisted - actual cart does not function on the k1 gba sp
- rayman advance - the higher notes of the musical score to not play
- classic nintendo series the legend of zelda - some slow-down, happens on screens with lots of graphics/enemies/etc
- gba video strawberry shortcake - video lag and sound stuttering
GBA Homebrew:
- 3 weeks in paradise - after having the header patched, black screen, does not load
- barbarian - black screen, does not load
- dangerous xmas - loads, but fails to start
- G.O.R.F. - black screen, does not load
- uranus zero ev - fails to initialize
Firmware:
- gba homebrew headers should be automatically patched so homebrew will run on actual hardware
- game art doesn't work for some files, even tho the art with the correct game id is present
- game art for retail roms appears for some homebrew, those homebrew files use the same game id. perhaps a crc check should be implemented
- an update to allow users to set their own function shortcuts. always using the only backlight button seems like a bad idea.
-another world