In luma3ds if "Autoboot emunand" is true and there is no emunand partition what happens?
Does it just use sysnand?
Does it auto resize the fat32 partition and create one?
Does it write to 0x200(offset 512, just after mbr) and just destroy whatever is there?
I never formatted my sd card to have an emunand but had it enabled and now am worried that my firmware is a timebomb waiting to write to that address then everything will break.
I am using sysnand right now and only have zeros at offset 512 of the sdcard so it seems it just ignored the emunand settings.
I am using b9s so there is no concern about firmware updates so I dont even want an emunand.
Does it just use sysnand?
Does it auto resize the fat32 partition and create one?
Does it write to 0x200(offset 512, just after mbr) and just destroy whatever is there?
I never formatted my sd card to have an emunand but had it enabled and now am worried that my firmware is a timebomb waiting to write to that address then everything will break.
I am using sysnand right now and only have zeros at offset 512 of the sdcard so it seems it just ignored the emunand settings.
I am using b9s so there is no concern about firmware updates so I dont even want an emunand.