DS-Homebrew
Touch! Bomberman Land (K) (CRC32: E38A0183) doesn't boot
Flashcard or Exploits?
EZ Flash Parallel (latest kernel tested)
DLDI patch: EZDS_DLDI.dldi
Running on latest TWiLightMenu++ flashcard version
Base Console: Nintendo DSi (Japanese unit, unlaunched, booted via flashcard)
TWiLight Menu++ Version:
v27.17.2 (hotfix 2)
nds-bootstrap v2.8.2 (latest)
TWiLight Menu++ UI:
Nintendo DSi theme
Flashcard mode (running from SD on the flashcard)
Expected behavior
Game should boot normally after generating save file.
Actual behavior
After launching Touch! Bomberman Land (K) (clean dump verified), game shows white screen after save file is created and doesn't proceed.
Tested multiple times on clean SD, with and without apfixOverlays.bin (latest).
No IPS or AP patch was detected or applied. Game boots successfully when run with stock flashcard kernel.
Steps to reproduce
- Install latest TWiLight Menu++ on EZ Flash Parallel (27.17.2 / bootstrap 2.8.2)
- Launch
Touch! Bomberman Land (K)from ROM folder - Observe after save file creation → white screen lock-up
Notes
- ROM CRC32:
E38A0183 - No corresponding entry found in
apfixOverlays.bin - Runs perfectly on official EZ Flash Parallel kernel
- Suspect missing AP patch or bootstrap incompatibility
- No BIOS file involved (standard bootstrap)
Would appreciate guidance on whether an AP patch is required, and if possible, inclusion in future apfixOverlays.bin.
Thanks for maintaining this great project!
No AP-patch is required for that game. Also, apfixOverlays.bin only contains the patched overlays of the launched ROM, and is not an AP-patch database.
The most likely issue is that the game is just incompatible with nds-bootstrap on flashcards.
Thanks for the clarification.
Since the issue appears to be specific to running this game through nds-bootstrap on flashcards, I'm looking into bypassing it by launching the game via the flashcard's native kernel instead.
Currently, it seems that TWiLight Menu++ and nds-bootstrap do not support kernel-layer execution for the EZ-Flash Parallel card. If that's accurate, I'm exploring the possibility of manually enabling that route—similar to how kernel fallbacks are handled with other supported flashcards.
A few points:
- Is there any known reason why EZ-Flash Parallel is not supported at the kernel level within TWiLight Menu++?
- Could this be due to EZ-Flash not publicly releasing the Parallel kernel source code?
- From what I’ve checked, the Parallel model appears to follow a Wood-like kernel structure. If that’s the case, could the issue lie in the onboard FPGA handling, rather than the software layer?
If kernel fallback is feasible, I would like to modify the TWiLight Menu++ launcher to enable explicit kernel execution for selected titles via .argv or another override method. Please advise on which components of the codebase handle flashcard-specific kernel fallbacks and any constraints in doing so.