Where CTR Toolkit sits in the scheme of things

Discussion in '3DS - Flashcards & Custom Firmwares' started by 3DSGuy, Aug 20, 2013.

  1. 3DSGuy

    3DSGuy No longer in scene

    May 22, 2012
    United States
    There is a thread about a legal open source 3DS Toolkit, sourced from here. It's presented as a "Work in Progress" 3DS SDK.

    There are some things which need to be set straight. First of all, it's not an SDK, or on the way to becoming one. I am in no way affiliated with GaryOpa, he wrote the article without contacting me to clarify my intentions.

    Just so you understand where I'm at, I started learning how to write computer programs last year. So I had an ambition to practice with tasks which caught my interest. Having a dev unit made re-implementing part of the 3DS SDK TOOLCHAIN, a desirable challenge. As the formats were, for the most part, documented. Re-implementing said tools had the added bonus of not having any restrictions imposed by Nintendo (ctr_makecia32 for example refuses to package CXIs, for which you didn't have the key). The other tools (like extdata_tool and rom_tool) do 3DS related tasks which are either not present in other tools, or (IMO) not done well enough in other tools.

    "But why is it called CTR Toolkit if it's not an SDK? Are you trying to deceive us, inflate your ego, etc" No. "SDK" stands for "Software Development Kit". The name "CTR Toolkit" implies that it's a series of various 3DS tools. It doesn't imply that it can be used for developing homebrew. I chose the name "CTR Toolkit" in lieu of "3DS Toolkit", because I felt that those able recognise "CTR" as the code name for the 3DS, are more likely to be in a position where tools would be of use to them.

    "Well then what does a homebrew 3DS SDK require?"
    It would require Libraries(API for the developer), an ARM compiler, and perhaps a method for running the compiled code.

    CTR Toolkit (ignoring that there's no Libraries or Compiler) provide (via the re-implemented SDK tools) only a part of the process "Official Developers", with access to "Development Kits" use to prepare the executable code into an acceptable form for the 3DS. (A process unfeasible to replicate on retail units without several RSA private keys, the AES key scrambler, AES keyX keyslots and KeyY calculating algorithms)

    The other tools, well they aren't at all related making homebrew:
    I thank those who defended/supported me/ctr_toolkit on the stark comments said on #3dsdev, but the truth is, it isn't and won't ever be an SDK. It'll take a better man than me to build 3DS libraries, and streamline a process for running homebrew. I apologise for any misunderstanding.
    skforty, cearp, Coto and 3 others like this.
  2. Syphurith

    Syphurith Beginner

    Mar 8, 2013
    Xi'an, Shaanxi Province
    I can't agree more. Yep. Good to see you, bump.
    SDK would provide those includes and libraries that needed in Compile Process, along with the related tools such as simulator/debugger/inspector and etc..
    However, due to the inability for us to get those binary that needed in link/compile process ..
    Oh well maybe we would face the problem of dumping that ram to get some raw codes and re-implement those.
    BTW, GW is using ROP chains.. Not real homebrew now - for me.
    Eh.. dear you can forget that PM i sent days ago. That is too dangerous to implement and not works with modern OS. yes forget that. thx
  3. GregoryRasputin

    GregoryRasputin The PS3 Scenes Most Hated Person

    Dec 12, 2012

    No surprise there, the guy is a scum bag.
  4. Coto


    Jun 4, 2010
    Just keep doing a good work. ;)

    I know you're one of those devs that take any challenge, even if it's a nightmare.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice