The 8.0.0-18 system update was released on July 7, 2014.
Change-log
Official change-log:
- Further improvements to overall system stability and other minor adjustments have been made to enhance the user experience.
System Titles
eShop, NVer, CVer, and the NZone hotspots list were updated. The 0004009B00012302 USA title(and the equivalent titleIDs for the other regions) was updated. The "masterkey.bin" file in the CVer RomFS was updated(different ID and different random data). The "cup_list" file was removed from the CVer RomFS as well.
All non-SAFE_MODE system modules were updated.
ErrDisp, eShop mint applet(used for accessing eShop outside of the eShop application, like DLC), and SNOTE_AP were updated, these now use the v7.0 NCCH encryption. None of the other updated titles use the v7.0 NCCH encryption(besides the ones which use it already). Due to ErrDisp being updated, this likely breaks booting 8.0.0-18 on physical <=v4.x systems where the key-data for the v7.0 NCCH crypto wasn't initialized correctly.
FIRM
NATIVE_FIRM was updated. Process9, the ARM11-kernel, and all of the ARM11 FIRM-modules were updated.
Process9 had minor / various other changes, including gamecard-related code changes. Support for new exheader/accessdesc fields were implemented. FSPXI:GetSpecialContentIndex was updated to add support for a new value(unknown where the field for that originates). Process9 now uses VRAM size 0x600000 instead of 0x400000 for FIRM(during FIRM launch) section address+size verification, and for the memory-clear code for the FIRM-launch panic function.
Most of the ARM11 FIRM-modules changes are likely minor. In pm-module, code was updated which handles programIDs/etc.
ARM11 kernel changes(besides various other (minor) changes):
- Multiple SVCs were stubbed(that is, these only return an error now).
- The code for svcControlMemory was updated.
- The code for svcGetProcessInfo was updated: previously a total of 8 type values were handled, this now handles a total of 23 type values.
- The code for svcStartInterProcessDma was updated. When the DmaConfig userland->kernelmode data-copy fails(like when the DmaConfig address is not readable from userland), this SVC now returns an error. Certain fields in the DmaConfig structure are now validated.
- Code which checks for virtual-memory address 0x20000000(end-address of process-memory) was updated to use address 0x40000000 instead.
See Also
- System update report