Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JP NAND file can't be found #195

Open
5 of 11 tasks
facaikotei opened this issue Mar 19, 2024 · 7 comments
Open
5 of 11 tasks

JP NAND file can't be found #195

facaikotei opened this issue Mar 19, 2024 · 7 comments
Labels
bug Something isn't working dsi For issues specific to DSi mode.

Comments

@facaikotei
Copy link

What version of melonDS DS are you using?

1.1.0

Does the problem happen in standalone melonDS?

No, it's a bug specific to melonDS DS.

What happened?

When I use JP NAND file, it say that none was found and ask me to place NAND file, but the file is already there. US, EU and CN NAND files can work normally.

What should've happened instead?

It should be found like US, EU or CN NAND file.

Which platforms do you see the problem on?

  • Windows
  • macOS
  • Linux
  • Android
  • iOS
  • tvOS
  • Other (specify below)

Which versions of the OS?

Android 13

Which libretro frontend are you using?

retroarch 1.17.0

Terms

  • I agree to follow the code of conduct.
  • I understand that melonDS DS is not developed or maintained by the authors of melonDS.
  • I understand that this form is for reporting bugs, not for requesting help.
  • I understand that the author develops this core in his spare time, and that he is under no obligation to respond to this bug report.
@facaikotei facaikotei added the bug Something isn't working label Mar 19, 2024
@JesseTG JesseTG added the dsi For issues specific to DSi mode. label Mar 19, 2024
@JesseTG
Copy link
Owner

JesseTG commented Mar 19, 2024

Could you please post a log file with debug-logging enabled? You'll want to set the logging options like so:
Screenshot 2023-12-20 084050

This will provide information that may help me reproduce this issue. Thank you!

@facaikotei
Copy link
Author

log file: retroarch.log

@facaikotei
Copy link
Author

I solved the problem myself.
I opened the NAND file in hex editor then copied the values from address 0xff800-0xff83f to address 0xf000000-0xf00003f then the core found the NAND file.
So could you describe in core option more detail about NAND file? Because not everyone knows the address of footer and how to check.

@JesseTG
Copy link
Owner

JesseTG commented Mar 21, 2024

I opened the NAND file in hex editor then copied the values from address 0xff800-0xff83f to address 0xf000000-0xf00003f then the core found the NAND file.

When you did this, did the NAND file size change? I don't currently validate the footer, I only check the file size. I suspect I may need to loosen this check.

@facaikotei
Copy link
Author

facaikotei commented Mar 22, 2024

Yes, from 240MB(251658240)(without footer) to 240MB(251658304)(footer merged).

@facaikotei
Copy link
Author

Maybe checking the file name is better? Like NO$GBA and melonDS do.

@JesseTG
Copy link
Owner

JesseTG commented Mar 23, 2024

Maybe checking the file name is better? Like NO$GBA and melonDS do.

I originally considered this, but decided against it. The convention is for DSi NAND images to end in .bin, right? Unfortunately a lot of other important system files (even for other cores) use .bin, so it wouldn't be enough to just use the name.

I'll give the GBATek docs a closer look to see if I can learn some more about NAND images.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dsi For issues specific to DSi mode.
Projects
None yet
Development

No branches or pull requests

2 participants