3dbrew - User contributions [en]

BCSAR

2014-10-22T09:42:17Z

GovanifY: /* Partitions */

[[Category:File formats]]
== Overview ==

The BCSAR (CTR Sound ARchive) format is the 3DS's equivalent of the Wii's BRSAR format. They're not the same structures, though, but they do have the same purpose.

BCSAR are located in the RomFS, this is usually stored under "romfs:/sound/<name>.bcsar". This contains various audio formats, such as CSTM, CWSD, and CWAV.

== BCSAR Header ==

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "CSAR"
|-
| 0x4
| 0x2
| Byte order mark (0xFEFF = Big Endian, 0xFFFE = Little Endian)
|-
| 0x6
| 0x4
| Length of BCSAR header
|-
| 0xA
| 0x2
| Version
|-
| 0xC
| 0x4
| Length of the entire BCSAR (starting from 0x0)
|-
| 0x10
| 0x4
| Amount of main partitions in the BCSAR [STRG + INFO + FILE = 0x03 (= 3)]
|-
| 0x14
| 0x4
| Partition header length [same for each partition? (ie STRG,INFO,and FILE header lengths)]
|-
| 0x18
| 0x4
| Location of STRG partition
|-
| 0x1C
| 0x4
| Length of STRG partition
|-
| 0x20
| 0x4
| Unknown (always 0x01200000?)
|-
| 0x24
| 0x4
| Location of INFO partition
|-
| 0x28
| 0x4
| Length of INFO partition
|-
| 0x30
| 0x4
| Location of main FILE partition
|-
| 0x34
| 0x4
| Length of main FILE partition
|-
| 0x38
| 0x4
| Reserved for 4th main partition location?
|-
| 0x3C
| 0x4
| Reserved for 4th main partition length?
|-
|}

== Partitions ==

=== STRG ===

STRG contains the names of the audio files in the BCSAR.

Header:

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "STRG"
|-
| 0x4
| 0x4
| Length of STRG partition (also in CSAR header)
|-
| 0x18
| 0x4
| Count of audio names (since each file should have a name you could also say this is essentially a file count)
|-
|}

Then for each name:

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| Type of the file...?
|-
| 0x4
| 0x4
| Offset of the filename...?
|-
| 0x8
| 0x4
| Size of the filename
|-
|}
Then every filename is rawly setted. You can set up a dictionary that contains, using a simple counter, the size of every filename in order. Then, using the same type of counter, get the values of the size of the filename in a correct order.
=== INFO ===

INFO presumably contains information on the audio files? Possibly used to connect names from STRG to data from FILE?

For now I only know some information in the header for this partition, but I'm working on figuring the rest out.

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "INFO"
|-
| 0x4
| 0x4
| Length of INFO partition (also in CSAR header)
|-
|}

=== FILE ===

FILE contains all of the audio data in the BCSAR.

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "FILE"
|-
| 0x4
| 0x4
| Length of FILE partition (also in CSAR header)
|-
|}

There isn't a whole lot else I can document about the FILE partition, since the data in it will most definitely vary depending on the game. (since audio is more than likely to change in each game)

There is no table in FILE so a different partition (presumably INFO) must be used to connect the data in FILE with the names from STRG.

After some more research, there are multiple FILE partitions, but only 1 of them is the 'main' FILE partition (it's the one you get from the BCSAR header). The 'main' FILE partition contains all of the other sub FILE partitions.

BCSAR

2014-10-22T09:35:37Z

GovanifY:

[[Category:File formats]]
== Overview ==

The BCSAR (CTR Sound ARchive) format is the 3DS's equivalent of the Wii's BRSAR format. They're not the same structures, though, but they do have the same purpose.

BCSAR are located in the RomFS, this is usually stored under "romfs:/sound/<name>.bcsar". This contains various audio formats, such as CSTM, CWSD, and CWAV.

== BCSAR Header ==

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "CSAR"
|-
| 0x4
| 0x2
| Byte order mark (0xFEFF = Big Endian, 0xFFFE = Little Endian)
|-
| 0x6
| 0x4
| Length of BCSAR header
|-
| 0xA
| 0x2
| Version
|-
| 0xC
| 0x4
| Length of the entire BCSAR (starting from 0x0)
|-
| 0x10
| 0x4
| Amount of main partitions in the BCSAR [STRG + INFO + FILE = 0x03 (= 3)]
|-
| 0x14
| 0x4
| Partition header length [same for each partition? (ie STRG,INFO,and FILE header lengths)]
|-
| 0x18
| 0x4
| Location of STRG partition
|-
| 0x1C
| 0x4
| Length of STRG partition
|-
| 0x20
| 0x4
| Unknown (always 0x01200000?)
|-
| 0x24
| 0x4
| Location of INFO partition
|-
| 0x28
| 0x4
| Length of INFO partition
|-
| 0x30
| 0x4
| Location of main FILE partition
|-
| 0x34
| 0x4
| Length of main FILE partition
|-
| 0x38
| 0x4
| Reserved for 4th main partition location?
|-
| 0x3C
| 0x4
| Reserved for 4th main partition length?
|-
|}

== Partitions ==

=== STRG ===

STRG contains the names of the audio files in the BCSAR.

Header:

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "STRG"
|-
| 0x4
| 0x4
| Length of STRG partition (also in CSAR header)
|-
| 0x18
| 0x4
| Count of audio names (since each file should have a name you could also say this is essentially a file count)
|-
|}

Then for each name:

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| Type of the file...?
|-
| 0x4
| 0x4
| Offset of the filename
|-
| 0x8
| 0x4
| Size of the filename
|-
|}

=== INFO ===

INFO presumably contains information on the audio files? Possibly used to connect names from STRG to data from FILE?

For now I only know some information in the header for this partition, but I'm working on figuring the rest out.

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "INFO"
|-
| 0x4
| 0x4
| Length of INFO partition (also in CSAR header)
|-
|}

=== FILE ===

FILE contains all of the audio data in the BCSAR.

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "FILE"
|-
| 0x4
| 0x4
| Length of FILE partition (also in CSAR header)
|-
|}

There isn't a whole lot else I can document about the FILE partition, since the data in it will most definitely vary depending on the game. (since audio is more than likely to change in each game)

There is no table in FILE so a different partition (presumably INFO) must be used to connect the data in FILE with the names from STRG.

After some more research, there are multiple FILE partitions, but only 1 of them is the 'main' FILE partition (it's the one you get from the BCSAR header). The 'main' FILE partition contains all of the other sub FILE partitions.

BCSAR

2014-10-22T06:04:06Z

GovanifY: /* BCSAR Header */

[[Category:File formats]]
== Overview ==

The BCSAR (CTR Sound ARchive) format is the 3DS's equivalent of the Wii's BRSAR format. They're not the same structures, though, but they do have the same purpose.

BCSAR are located in the RomFS, this is usually stored under "romfs:/sound/<name>.bcsar". This contains various audio formats, such as CSTM, CWSD, and CWAV.

== BCSAR Header ==

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "CSAR"
|-
| 0x4
| 0x2
| Byte order mark (0xFEFF = Big Endian, 0xFFFE = Little Endian)
|-
| 0x6
| 0x4
| Length of BCSAR header
|-
| 0xA
| 0x2
| Version
|-
| 0xC
| 0x4
| Length of the entire BCSAR (starting from 0x0)
|-
| 0x10
| 0x4
| Amount of main partitions in the BCSAR [STRG + INFO + FILE = 0x03 (= 3)]
|-
| 0x14
| 0x4
| Partition header length [same for each partition? (ie STRG,INFO,and FILE header lengths)]
|-
| 0x18
| 0x4
| Location of STRG partition
|-
| 0x1C
| 0x4
| Length of STRG partition
|-
| 0x20
| 0x4
| Unknown (always 0x01200000?)
|-
| 0x24
| 0x4
| Location of INFO partition
|-
| 0x28
| 0x4
| Length of INFO partition
|-
| 0x30
| 0x4
| Location of main FILE partition
|-
| 0x34
| 0x4
| Length of main FILE partition
|-
| 0x38
| 0x4
| Reserved for 4th main partition location?
|-
| 0x3C
| 0x4
| Reserved for 4th main partition length?
|-
|}

== Partitions ==

=== STRG ===

STRG contains the names of the audio files in the BCSAR.

For now I only know some information in the header for this partition, but I'm working on figuring the rest out.

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "STRG"
|-
| 0x4
| 0x4
| Length of STRG partition (also in CSAR header)
|-
| 0x18
| 0x4
| Count of audio names (since each file should have a name you could also say this is essentially a file count)
|-
|}

=== INFO ===

INFO presumably contains information on the audio files? Possibly used to connect names from STRG to data from FILE?

For now I only know some information in the header for this partition, but I'm working on figuring the rest out.

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "INFO"
|-
| 0x4
| 0x4
| Length of INFO partition (also in CSAR header)
|-
|}

=== FILE ===

FILE contains all of the audio data in the BCSAR.

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "FILE"
|-
| 0x4
| 0x4
| Length of FILE partition (also in CSAR header)
|-
|}

There isn't a whole lot else I can document about the FILE partition, since the data in it will most definitely vary depending on the game. (since audio is more than likely to change in each game)

There is no table in FILE so a different partition (presumably INFO) must be used to connect the data in FILE with the names from STRG.

After some more research, there are multiple FILE partitions, but only 1 of them is the 'main' FILE partition (it's the one you get from the BCSAR header). The 'main' FILE partition contains all of the other sub FILE partitions.

BCSAR

2014-10-22T05:59:12Z

GovanifY: /* BCSAR Header */

[[Category:File formats]]
== Overview ==

The BCSAR (CTR Sound ARchive) format is the 3DS's equivalent of the Wii's BRSAR format. They're not the same structures, though, but they do have the same purpose.

BCSAR are located in the RomFS, this is usually stored under "romfs:/sound/<name>.bcsar". This contains various audio formats, such as CSTM, CWSD, and CWAV.

== BCSAR Header ==

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "CSAR"
|-
| 0x4
| 0x2
| Byte order mark (0xFEFF = Big Endian, 0xFFFE = Little Endian)
|-
| 0x6
| 0x4
| Length of BCSAR header
|-
| 0xA
| 0x2
| Version
|-
| 0xC
| 0x4
| Length of the entire BCSAR (starting from 0x0)
|-
| 0x10
| 0x1
| Amount of main partitions in the BCSAR [STRG + INFO + FILE = 0x03 (= 3)]
|-
| 0x15
| 0x1
| Partition header length [same for each partition? (ie STRG,INFO,and FILE header lengths)]
|-
| 0x18
| 0x4
| Location of STRG partition
|-
| 0x1C
| 0x4
| Length of STRG partition
|-
| 0x20
| 0x4
| Unknown (always 0x01200000?)
|-
| 0x24
| 0x4
| Location of INFO partition
|-
| 0x28
| 0x4
| Length of INFO partition
|-
| 0x30
| 0x4
| Location of main FILE partition
|-
| 0x34
| 0x4
| Length of main FILE partition
|-
| 0x38
| 0x4
| Reserved for 4th main partition location?
|-
| 0x3C
| 0x4
| Reserved for 4th main partition length?
|-
|}

== Partitions ==

=== STRG ===

STRG contains the names of the audio files in the BCSAR.

For now I only know some information in the header for this partition, but I'm working on figuring the rest out.

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "STRG"
|-
| 0x4
| 0x4
| Length of STRG partition (also in CSAR header)
|-
| 0x18
| 0x4
| Count of audio names (since each file should have a name you could also say this is essentially a file count)
|-
|}

=== INFO ===

INFO presumably contains information on the audio files? Possibly used to connect names from STRG to data from FILE?

For now I only know some information in the header for this partition, but I'm working on figuring the rest out.

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "INFO"
|-
| 0x4
| 0x4
| Length of INFO partition (also in CSAR header)
|-
|}

=== FILE ===

FILE contains all of the audio data in the BCSAR.

{| class="wikitable" border="1"
|-
! OFFSET
! SIZE
! DESCRIPTION
|-
| 0x0
| 0x4
| MAGIC "FILE"
|-
| 0x4
| 0x4
| Length of FILE partition (also in CSAR header)
|-
|}

There isn't a whole lot else I can document about the FILE partition, since the data in it will most definitely vary depending on the game. (since audio is more than likely to change in each game)

There is no table in FILE so a different partition (presumably INFO) must be used to connect the data in FILE with the names from STRG.

After some more research, there are multiple FILE partitions, but only 1 of them is the 'main' FILE partition (it's the one you get from the BCSAR header). The 'main' FILE partition contains all of the other sub FILE partitions.

Makerom

2014-09-09T10:27:16Z

GovanifY:

{{Infobox homebrew
| title = makerom
| type = pc utility
| author = [[User:3dsguy|3dsguy]]
| download = https://anonfiles.com/file/2e954a4b954778e8bcd0c317f071c272
| source = https://github.com/3DSGuy/Project_CTR/tree/master/makerom
| version = 0.8
}}

makerom is a tool which can be used to created [[NCCH]] and [[NCSD|CCI]] and [[CIA]] files.

== Using Makerom ==

=== Command line ===
Since CCI and CIA are NCCH containers, makerom was built so CXIs could be built stand alone, or straight into a container format. It is also possible rebuild CXIs as easily building a CXI from an elf. As a result the are many combinations which can be used, and for simplicity specific functions will be explained by breaking them up into argument groups:

'''Creating CXIs from scratch:'''
-elf <elf path> -rsf <rsf path> [-icon <[[SMDH|icon]] path> -banner <banner path>]

'''Rebuilding CXIs:'''
-code <decompressed exefs .code> -exheader <exheader from original CXI> -rsf <rsf path> [-icon <[[SMDH|icon]] path> -banner <banner path> -romfs <cleartext romfs binary>]

'''Creating CFAs:'''
-f cfa -rsf <rsf path> [-icon <[[SMDH|icon]] path> -romfs <romfs binary>]

'''Creating CCIs:'''
-f cci [-content <path>:<index> ...]

'''Creating CIAs:'''
-f cia [-content <path>:<index>:<id> ...]

'''Using Desc presets:'''
-desc <app type>:<firm version>

* 'app type' can be SDApp / ECApp / Demo / DlpChild
* 'firm version' is the target kernel version minor for the intended 3DS system.

'''Examples:'''
Create a CCI, using a manual CFA, and a desc preset:
makerom -f cci -elf homebrew.elf -rsf app.rsf -desc sdapp:33 -icon homebrew.icn -banner homebrew.bnr -content manual.cfa:1 -o homebrew.cci

Create a CIA using an already built application CXI and manual CFA:
makerom -f cia -content homebrew.cxi:0:0 -content manual.cfa:1:1 -o homebrew.cia

Rebuild a CXI:
makerom -code code.bin -exheader exheader.bin -icon icon.bin -banner banner.bin -romfs romfs.bin -rsf app.rsf -desc sdapp:33 -o rebuild.cxi

=== Creating RSF files ===
Inspired by Nintendo's format for their makerom, is a yaml configuration file, required for creating NCCH files. CIA/CCI can be created without using a RSF file, but default settings will be used.

For CXI, RSF files can be used to specify permissions, and access control settings. However makerom can use default settings by use of the "-desc" option, which removes the requirement for specifing them in the RSF file.

Sample RSF to be used with "-desc": [https://gist.githubusercontent.com/3DSGuy/83e12e0ae3dcccb9827f/raw/sample0.rsf download]

Sample RSF to be used without "-desc": [https://gist.githubusercontent.com/3DSGuy/83e12e0ae3dcccb9827f/raw/sample1.rsf download]

=== Creating ELF files ===
ELF files created using the official SDK can be used with makerom. But ELF files created using [https://github.com/smealum/ctrulib ctrulib], can be used, provided they are linked with this linker script: [https://gist.github.com/yellows8/6da7984a80a825b10294 download]

== Compiling Source ==
For Windows use MinGW, 64bit versions of MinGW are supported also.

For Linux, gcc/g++/make must be installed.

All additional libraries used by makerom, are included in the source, and are linked statically.

== Issues ==

* Proper ticket index generation isn't complete (CIA tickets are valid for only one content)
* RomFs hasn't been completely implemented (But valid pre-built romfs can be used as substitute)