We need support for .firm!
--------------------- MERGED ---------------------------
Oh wait, nvm about my last post
Thanks for this info, now I might be able to build a firm version with this!If you successfully build a working copy, let me know. The file I get is 168K and gives me a black screen. I can't figure out why it's not working. But the build on page 3 works fine.
EDIT: I may have just figured it out. It gives a 168K file if I build it with devkitARM 47. But it gives a 110K file if I build it with devkitARM 45. I'll test that now.
EDIT 2: No, that only gives me a black screen also.
EDIT 3: I've tried devkitARM versions 43 through 47 now. It must need an older copy of libctru or something. I guess I'll keep using the build on page 3 until the next release.
Thanks for this info, now I might be able to build a firm version with this!
Thanks, good job!I don't see how it helps knowing that every version of devkitARM that comes with a "3ds_rules" file (thus is meant to be 3DS-compatible) fails, but you're welcome. However, you don't really have to build a firm version. It's right here if you're interested. I was trying to compile the source because there are some random errors that occur when running Luma. It's not a big enough issue to even warrant all of these build attempts I've made. I just have an obsession with trying to get things to work I guess. Again, if you figure anything out, let me know. But I think I'll just wait for the next release.
When holding select with the files on the root of my SD I get the error
Please help[PANIC] Failed to load the [DEFAULT] se
Press any key to continue
Thanks, good job!
--------------------- MERGED ---------------------------
When holding select with the files on the root of my SD I get the error
Please help
Oh yeah, I can't believe I didn't think of thatYou have to edit your boot_config.ini file to point to your copy of Luma (they both can't be boot.firm). If you would like some ready-made examples of how to set this up, I've got some here for you to check out (BootCTR9 folder for BootCTR9 config). They're from an older version of BootCTR9 and don't have a bunch of fancy extra stuff setup like animations, but they work, and you can refer to the copy of boot_config.ini you already have for examples on how to add animations if you want them.
YES IT WORKED THANKSYou have to edit your boot_config.ini file to point to your copy of Luma (they both can't be boot.firm). If you would like some ready-made examples of how to set this up, I've got some here for you to check out (BootCTR9 folder for BootCTR9 config). They're from an older version of BootCTR9 and don't have a bunch of fancy extra stuff setup like animations, but they work, and you can refer to the copy of boot_config.ini you already have for examples on how to add animations if you want them.
just curious, can it work with sound? just made a sweet old school gameboy start up boot and it would be even more nostalgic to hear the sound xD
The bottom screen is curently not supported, because I use it for logging, and I preffer to have one good working animation with higher fps, than two with low fps. But when I have more time I would like to add splash image support which could also be used as a background for the log und user infomations on the bottom screen.Not sure if anyone's answered this before, but I'm assuming BootCtr9 can't use the bottom screen or sound features because of limitations that B9S has and AL9H doesn't?
If so, is there any chance these features could make it here, or are the limitations "unavoidable"?
The bottom screen is curently not supported, because I use it for logging, and I preffer to have one good working animation with higher fps, than two with low fps. But when I have more time I would like to add splash image support which could also be used as a background for the log und user infomations on the bottom screen.
Sound is not supported because it is currently unkown how to initalise and use the sound hardware. This is needed, because the system does not initalise it until after the firmware boot is completed. But after somebody figured it out, I will be able to add sound support.
What's Shadow nand ?Because I will not derail another thread for my problems
I am using stock boot_config.ini
I made no deviations to the ini file or the file set up and I get the errorCode:Comments starts with ";" or "#", so you need to remove it first to the ;line actually do something. ;configuration with ascii boot Image ;You have also 1 sec to press the button for the payload you want to boot [BOOTCTR9] key_delay = 1000 boot_splash = 3 enableAutosoftboot = 1 enableArm9CompanionBoot = 1 ;Section to allow a9lh net companion payload auto booting [COMPANION] path = /a9nc.bin delay = 100 offset = 0 payload = -1 ;luma with BootAnimation and enabled Pathfix [DEFAULT] path = /Payloads/luma.bin delay = 1000 splash = 4 splash_image = /Animations/anim screenBrightness = 0x30 enablePathFix = 1 ;cakes.dat with splash screen and offset [KEY_R] path = /Cakes.dat delay = 1000 offset = 0x12000 splash = 3 splash_image = /Splashes/splash.bin ;Reinand.dat with offset and ascii splash [KEY_DUP] path = /ReiNand.dat delay = 1000 offset = 0x12000 splash = 1 ;Each key can be defined using a section, like the example below. Section ;names must be ALL caps, and between "[]". Valid keys: ;You MUST set at least "path" for each section, and it is the ONLY option you ;should set in the majority of cases. ;Double check the path, since it must be correct (including caps). ;Boot examples for almost every CFW out there. ;You can use only binary (.bin, .dat) payloads ;[KEY_A] ;path = /rxTools/sys/code.bin ;[KEY_B] ;path = /Cakes.dat ;[KEY_Y] ;path = /ReiNand.dat ;An important remark: the majority of CFWs set L button to show menu instead ;of autobooting. So it is generally a bad idea to set L button to CFW boot, ;but if you use a delay, you have time to release the key so the CFW menu will ;not be shown.
I am running shadowNAND, but this was tested with versions of A9LHv2Code:[PANIC] Error found in config file, err Press any key to shutdown
Isn't the same as luma installed in my CTR NAND too ?ShadowNAND was kind of the first method of running a CFW from the CTRNAND.
At that time it was a stripped down CFW without only the most basic of patches. So the modern equivalent would be be Luma3DS on the CTRNAND.Isn't the same as luma installed in my CTR NAND too ?
Here is another dev release, this should hopefully have the problem with som Text mode payloads fixed while also having the luma unsupported location bug fixed.