libretro / libretro/parallel-n64
Raspberry PI4 Illegal instruction on paper mario
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 407
- Forks
- 151
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 11
Description
hi i build using Raspberry PI4 32bit raspbian buster os with GLES and NEON and dynarec arm
when i try play paper mario it got Error when about the game when load
using any gfx the are same log :
context_reset.
ReadSpecialSettings: DEFAULT
plugin_start_gfx success.
Gfx RomOpen.
ReadSpecialSettings: DEFAULT
ReadSpecialSettings: PAPER MARIO
GL_ARB_texture_non_power_of_two supported.
GL_EXT_texture_format_BGRA8888 supported.
GL_ARB_texture_non_power_of_two supported.
GL_EXT_texture_format_BGRA8888 supported.
Illegal instruction
retroarch log:
[libretro DEBUG] set filtering mode...
[libretro INFO] mupen64plus: Starting R4300 emulator: Dynamic Recompiler
[libretro INFO] mupen64plus: Init new dynarec
[libretro INFO] mupen64plus: ARM CPU Features:, Half, Thumb, FastMult, VFP, ESDP, NEON, VFPv3, TLS, VFPv4, IDIVa, IDIVt
[libretro INFO] Glide64 ucode = 0x21f91834
[libretro INFO] Microcode 2 - F3DEX 2.XX (The Legend of Zelda: Ocarina of Time)
[libretro INFO] microcheck: old ucode: 2, new ucode: 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no source file, test, or entry point. Start by reproducing Paper Mario with the Raspberry Pi 4 32-bit Raspbian, GLES, NEON, and ARM dynarec configuration, then investigate the illegal-instruction point using the supplied emulator and RetroArch logs. Done means the failure is explained and a validated resolution is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, raspberry-pi
- Domain
- embedded-iot, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100