-
Hey, I'm trying to build this with custom changes for myself (chainloading firm1 when installed to firm0 as bootloader, not something that should be in an official build for obvious reasons), but I don't seem to be able to make functional builds these days. Is there anything I could check to figure out what might be causing incompatibilities? I'm building on Arch, I install firmtool by cloning the repo and using Latest devkitARM, Python 3.12.4, the build succeeds just fine and I get a .firm, but booting this firm on console leads to a black screen. firmtool says it depends on pycryptodome but it would make the firm just fine even though I hadn't installed that. I installed it and re-built (make clean --> make firm) just in case missing pycryptodome could have caused firmtool to build the firm wrong or something, but this didn't make a difference. Has anyone else run into this issue? Clearly it's something on my end, and not the code in the repo, but because I don't get any errors anywhere during the build, I can't really troubleshoot anything. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Not trying to be rude, but github is generally for reporting bugs and collaboration, and not a help forum. This is better left for discord and/or an actual forum such as gbatemp. |
Beta Was this translation helpful? Give feedback.
-
Are you using the latest-est commit? There's a known issue that's been fixed a few weeks ago regarding the latest dkA toolchain (r64-2 iirc) |
Beta Was this translation helpful? Give feedback.
Are you using the latest-est commit? There's a known issue that's been fixed a few weeks ago regarding the latest dkA toolchain (r64-2 iirc)