Changes

The typical development flow using a Cat-DEV is to plug it into the network, and run "cafeon", or "caferun" from the Cafe SDK to emulate a full filesystem on the host PC. Developers could add, and remove directories dynamically to add titles and directories. Debug output is usually streamed over the network connection, but can also be gathered over a USB-Serial connection.

The typical development flow using a Cat-DEV is to plug it into the network, and run "cafeon", or "caferun" from the Cafe SDK to emulate a full filesystem on the host PC. Developers could add, and remove directories dynamically to add titles and directories. Debug output is usually streamed over the network connection, but can also be gathered over a USB-Serial connection.

==Known Versions==

==Known Versions==

</gallery>

</gallery>

*CAT-DEV V3 (July 2011, Latte A3X?) - transitioned from USB to Ethernet for host i/o, white casing, added internal hard disk; at this pointed all boards are referred to as "MION" in reference to the board that the host pc would communicate with, had the hard drive, and did all the emulation.  

*CAT-DEV V3 (July 2011, Latte A3X?) - transitioned from USB to Ethernet for host i/o, white casing, added internal hard disk; at this pointed all boards are referred to as "MION" in reference to the board that the host pc would communicate with, had the hard drive, and did all the emulation.

*CAT-DEV V4 (?, Latte A4X?) - "Increased Operating frequency of the CPU by 25%", "The speed for writing to memory when using locked-cache DMA is the same as final.", "Speed of transfer from MEM1 to MEM2 is final.", "L2 Cache Fetch doubled when using lock-cached DMA".  

*CAT-DEV V4 (?, Latte A4X?) - "Increased Operating frequency of the CPU by 25%", "The speed for writing to memory when using locked-cache DMA is the same as final.", "Speed of transfer from MEM1 to MEM2 is final.", "L2 Cache Fetch doubled when using lock-cached DMA".

<gallery>

<gallery>

File:cat-dev-v4-front.webp|alt=The Front of a White-Cased CAT-DEV version 4.

File:cat-dev-v4-front.webp|alt=The Front of a White-Cased CAT-DEV version 4.

There's also an "EV_Y" variant which was introduced with Latte A5X/CAT-DEV MP2.

There's also an "EV_Y" variant which was introduced with Latte A5X/CAT-DEV MP2.

== Boards ==

==Boards==

Known CAT-DEV MP2 Wii-U versions: WUP-DEV-X8, WUP-DEV-X9, and WUP-DEV-X10.

Known CAT-DEV MP2 Wii-U versions: WUP-DEV-X8, WUP-DEV-X9, and WUP-DEV-X10.

MION: "CATHDD-X5"

MION: "CATHDD-X5"

== Serial Port Settings ==

==Serial Port Settings==

Baud Rate: 57600

Baud Rate: 57600

       termios.c_cflag &= !libc::CSTOPB;

       termios.c_cflag &= !libc::CSTOPB;

== MION ==

==MION==

The CAT-DEV's from V3 onwards started featuring a "MION" board (short for "Multi I/O Network") that contained the internal hdd of the later units, as well as is the device that managed the LAN port connection. It is the real brains of driving the power, serial output, and filesystem (in certain boot modes) for the CAT-DEV. When developers are interacting with the CAT-DEV through tools in the SDK like "cafeon", "findbridges", etc. They're actually interacting with the MION board directly. There are three boot modes available on MION CAT-DEVs: "PCFS", "DUAL", and "HDD Reader Mode". HDD Reader Mode is the only mode that allows the actual Cafe OS, and "wii-u" portion to boot when first receiving power.

The CAT-DEV's from V3 onwards started featuring a "MION" board (short for "Multi I/O Network") that contained the internal hdd of the later units, as well as is the device that managed the LAN port connection. It is the real brains of driving the power, serial output, and filesystem (in certain boot modes) for the CAT-DEV. When developers are interacting with the CAT-DEV through tools in the SDK like "cafeon", "findbridges", etc. They're actually interacting with the MION board directly. There are three boot modes available on MION CAT-DEVs: "PCFS", "DUAL", and "HDD Reader Mode". HDD Reader Mode is the only mode that allows the actual Cafe OS, and "wii-u" portion to boot when first receiving power.

In "PCFS", or "DUAL" mode the MION will not power on the actual Cafe OS until a HTTP Request is received to power on the underlying OS. In many cases you must also spin up several TCP, and UDP services for the device to interact with, but every known MION has a series of flags you can set to force booting when 'PCFS' is turned on. MIONs are also how developers would 'find' the cat-dev on a network since there was no visual indicators when first powering them on. They did this through UDP Broadcast packets on port 7974. They also have support for fetching the internal memory, and disk state (although only 512 bytes at a time).

In "PCFS", or "DUAL" mode the MION will not power on the actual Cafe OS until a HTTP Request is received to power on the underlying OS. In many cases you must also spin up several TCP, and UDP services for the device to interact with, but every known MION has a series of flags you can set to force booting when 'PCFS' is turned on. MIONs are also how developers would 'find' the cat-dev on a network since there was no visual indicators when first powering them on. They did this through UDP Broadcast packets on port 7974. They also have support for fetching the internal memory, and disk state (although only 512 bytes at a time).

[[Category:Wii U]]

[[Category:Wii U]]