Difference between revisions of "Talk:ExeFS"
Jump to navigation
Jump to search
(→Code binary?: new section) |
|||
| Line 2: | Line 2: | ||
What is the format of the "Code Binary"? Surely it's not a raw stream of ARM opcodes. There has to be data for the loader to work with!--[[User:Henke37|Henke37]] ([[User talk:Henke37|talk]]) 17:44, 22 July 2016 (CEST) | What is the format of the "Code Binary"? Surely it's not a raw stream of ARM opcodes. There has to be data for the loader to work with!--[[User:Henke37|Henke37]] ([[User talk:Henke37|talk]]) 17:44, 22 July 2016 (CEST) | ||
| + | :ExeFS:/.code ''is'' a raw stream of ARM opcodes, plus data/rodata sections. The beginning of ExeFS:/.code is just plain ARM code (starting in ARM mode), however. The location and size of the data/rodata sections is described in the [[NCCH/Extended_Header#Code_Set_Info|exheader]]. Look up the thing called "ctr-elf", which takes a decrypted NCCH and converts it to an ELF file. Besides, these talk pages are kind of deserted; join the relevant IRC channels instead. [[User:IReir|IReir]] ([[User talk:IReir|talk]]) 07:17, 23 July 2016 (CEST) | ||
Latest revision as of 07:17, 23 July 2016
Code binary?[edit]
What is the format of the "Code Binary"? Surely it's not a raw stream of ARM opcodes. There has to be data for the loader to work with!--Henke37 (talk) 17:44, 22 July 2016 (CEST)
- ExeFS:/.code is a raw stream of ARM opcodes, plus data/rodata sections. The beginning of ExeFS:/.code is just plain ARM code (starting in ARM mode), however. The location and size of the data/rodata sections is described in the exheader. Look up the thing called "ctr-elf", which takes a decrypted NCCH and converts it to an ELF file. Besides, these talk pages are kind of deserted; join the relevant IRC channels instead. IReir (talk) 07:17, 23 July 2016 (CEST)