Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[annson24]

Does anybody around here has the kips compiled? I'm kinda used to loading atmosphere's kips through hekate and doesn't feel like using fusee-primary and secondary just yet.

 

[tiliarou]

Does anybody around here has the kips compiled? I'm kinda used to loading atmosphere's kips through hekate and doesn't feel like using fusee-primary and secondary just yet.

Remember that for 6.2 you have to use fusee since hekate is not updated to derive keys with TSEC.

Old kips prior to 0.8.0 : http://bsnx.lavatech.top/atmosphere/

Ave needs to fix build for 0.8.x. If you are in a hurry, you can compile it yourself with "make dist" I believe.

 

[8BitWonder]

Does anybody around here has the kips compiled? I'm kinda used to loading atmosphere's kips through hekate and doesn't feel like using fusee-primary and secondary just yet.

I noticed from this issue and my own attempt that one of the kips (fatal) is pretty stubborn to compile atm.
Though all of the others can be compiled if you're interested in those.

 

[smf]

From what universe do you come from?
Atmosphère is a Coldboot CFW. RCM comes in before the firmware is booted, Hekate is pushed into RCM, then Atmosphère is booted. The OFW never boot in any part of the process.

What universe are you from? RCM is clearly part of the firmware. Atmosphere replaces parts of Horizon, which is an operating system.

The operating system isn't firmware either, but because it's flashed to nand then it gets mislabelled (nintendo themselves don't call it firmware).

If atmosphere came as an nca and could be installed using choidujournx and booted up without tethering, then you could have a point.

Do we really care about the definition of CFW, cold boot and "LCFW" in this topic ?

Apparently so, it has to be CFW because that is what gets blood pumping to the genitals.

I only jumped in because someone was being pedantic because someone else didn't call it CFW.

 

[Manurocker95]

My error when booting is fixed with Atmosphere 0.8.1

 

[Y0sh1]

new binaries have just been published without incrementing the version </sad panda>

fixing the reboot to rcm apparently

 

[hippy dave]

new binaries have just been published without incrementing the version </sad panda>

fixing the reboot to rcm apparently

Yup check the hash in the filename, if you make sure you're using atmosphere-0.8.1-master-bd76e73 (or newer when available) from the release page then you will be able to use RCMReboot.

 

[ClickCLK]

RCM is clearly part of the firmware.

FYI, rcm is a very low level interface that runs from flash installed on tegra SoC itself and isn't a part of any switch-unique code, so it isn't a part of switch firmware - it is a part of SoC firmware. You can phisically disconnect emmc chip (where firmware is stored) and even disconnect RAM - rcm will still boot. Rcm mode is present on every devices with tegra SoC.

 

[smf]

so it isn't a part of switch firmware

Of course it's part of switch firmware, it's part of the switch. None of the firmware is provided by nintendo, they provide an OS.

Like on your PC, you have UEFI which is the firmware and Windows/Linux/MacOS which is the OS.

 

[ClickCLK]

Of course it's part of switch firmware, it's part of the switch. None of the firmware is provided by nintendo, they provide an OS.

Like on your PC, you have UEFI which is the firmware and Windows/Linux/MacOS which is the OS.

No, it's not, and your exple is wrong. On pc UEFI is stored in special spi eeprom chip on motherboard. Uefi boots after cpu and ram are initialised, then it initializes other hardware (such as drives) mounts partitions, and boots the os. Uefi can't boot without ram. And also, you got cpu microcode, which is a very small firmware that initializes cpu at the very low level and translates opcodes into machine language.

Switch, on the other hand, doesn't have this dedicated spi flash chip, and all basic loaders are stored inside the emmc, with very first loaders (in long chain) stored in boot partitions. This loaders initialize ram and then everything else, so this loaders act as uefi on pc ( but have no configuration interface, for security reasons and ease of use for end user). Rcm on the other hand is like part of cpu microcode (but in case with tegra it's not just cpu, it's whole SoC, so many of its components can be initialised with its firmware, such as usb bus). As I wrote earlyer rcm will still work even if no ram present on system.

Also SoC firmware, which contains rcm, is read only and can be flashed only while manufacturing.

And on embedded systems, such as game consoles, all software elements which make this systems work (all loader chains, OS and preinstalled applications) usually called firmware, especially on systems, where user is not able to install different OS.

 

[Ann0ying]

Does anybody around here has the kips compiled? I'm kinda used to loading atmosphere's kips through hekate and doesn't feel like using fusee-primary and secondary just yet.

Kosmos have them compiled.

 

[smf]

No, it's not, and your exple is wrong.

The example is correct.

Uefi boots after cpu and ram are initialised,

No it doesn't. Uefi handles the entire boot process, the first opcode executed by the cpu is part of Uefi.

then it initializes other hardware (such as drives) mounts partitions, and boots the os.

The firmware inside the Tegra does the same.

Uefi can't boot without ram.

It should boot enough to tell you that you have no ram.

And also, you got cpu microcode, which is a very small firmware that initializes cpu at the very low level and translates opcodes into machine language.

That isn't part of Uefi, it's an implementation detail of the cpu.

It doesn't do what you think or work how you think.

It's not like a piece of code that runs at startup to initialise the cpu, it's only called in specific circumstances. Like when a complex instruction needs to be decoded, simple instructions are hardcoded. It's nothing to do with firmware at all and isn't considered firmware by anyone.

Switch, on the other hand, doesn't have this dedicated spi flash chip,

That is an implementation detail & irrelevant. Uefi doesn't need to be stored on a flash chip, it could be stored on an SSD and loaded into some ram by dedicated hardware at bootup or it could be embedded into the CPU. Intel decided to store it one way, Nvidia decided to store it another.

Rcm on the other hand is like part of cpu microcode

No it's not, you clearly don't understand what microcode is.

Also SoC firmware, which contains rcm, is read only and can be flashed only while manufacturing.

Actually the hash is read only, you could apply patches to it if you could get a hash collision. Then you could patch out the signature checking & just patch the OS on nand to give what could accurately be described as CFW.

all software elements which make this systems work (all loader chains, OS and preinstalled applications) usually called firmware

Some people call it firmware, even though it isn't called that by nintendo & doesn't meet the industry standard for what firmware is.

The parts of the "system" (as nintendo call it) that atmosphere replaces is not any part which anyone would describe as firmware. Atmosphere doesn't install in the same way as the official updates either, which is how typically CFW is differentiated from a jailbreak.

Just look at PS3 scene evolution of PSJailbreak, CFW and HAN. The PS4 doesn't have CFW either, even though there is little conceptual difference between Atmosphere and the PS4 hen.

 

[ghjfdtg]

Firmware is not the right word for this. It's bootloaders + a full blown self written OS. The only part you can call firmware is the bootrom which does some of the same tasks BIOS/UEFI do.

And the bootrom is not just flash. It's often plain mask rom. The fact that they have factory programmable patches for it points to it beeing baked into the SoC as mask rom.

 

[hippy dave]

This is not the "tedious terminology debates" thread.

 

[TheFIrstAv3nger]

So does atmosphere load the required kips and layeredfs through fusee-2 now and are no longer required to be in the modules folder?

 

[Xana]

So does atmosphere load the required kips and layeredfs through fusee-2 now and are no longer required to be in the modules folder?

fusee-primary launches fusee-secondary, which contains all of the kips built-in. You only need the separate kips when launching atmos directly via hekate.

 

[satel]

how to update from Atmosphere 0.80 to 0.81 ? do you also need to flash the usb dongle with the 0.81 primary fusee bin or 0.80 is the same ?

 

[TheFIrstAv3nger]

fusee-primary launches fusee-secondary, which contains all of the kips built-in. You only need the separate kips when launching atmos directly via hekate.

Does that include the layeredfs kip? And does chainloading fusee primary through hekate work to load directly?

 

[ZachyCatGames]

how to update from Atmosphere 0.80 to 0.81 ? do you also need to flash the usb dongle with the 0.81 primary fusee bin or 0.80 is the same ?

Just copy the files from 0.8.1 and overwrite the old files if it asks you to. Yes, 0.8.1 updated fusee primary

--------------------- MERGED ---------------------------

Does that include the layeredfs kip? And does chainloading fusee primary through hekate work to load directly?

Fusee secondary includes sm, pm, fsmitm, loader, and exosphere. Yea you can chainload fusee-primary with Hekate

 

[satel]

Just copy the files from 0.8.1 and overwrite the old files if it asks you to. Yes, 0.8.1 updated fusee primary

thank you very much,also about the folders inside the titles folder of Atmosphere are they important,i usually replace them with my custom theme folders.