Foenix F256 / Wildbits/K2 Wiki - User contributions [en]

Kernel & SuperBASIC Updates

2026-04-27T15:31:04Z

Agurtovoy: /* Kernel and/or SuperBASIC Releases */

== Kernel and/or SuperBASIC Releases ==

Official firmware releases that routinely improve SuperBASIC, MicroKernel and other built-in software, are published at https://github.com/wildbitscomputing/firmware.

If you want to apply a Kernel and/or SuperBASIC update independently, you could do so piecewise by replacing only the SuperBASIC or only the MicroKernel flash blocks, available from the corresponding Github repos:
* [https://github.com/wildbitscomputing/MicroKernel/tree/master/bin Latest MicroKernel release]
* [https://github.com/wildbitscomputing/superbasic/releases SuperBASIC releases]

== USB Port ==

=== F256 Jr. / F256K ===
You will need to have the XR21B1411 USB Driver for PC/Linux. The MAC is outdated. (Note: Driver is not needed for the F256K2)
[https://www.maxlinear.com/product/interface/uarts/usb-uarts/xr21b1411]

=== F256K2 ===
On the F256K2 the XR21B1411 has been replaced by a FT4232, to allow direct use as a JTAG controller for the FPGA. There are 3 virtual serial ports (channels) enabled. The first connected to the Raspberry PI Nano (on-board) that manages the FPGA loading, the second one is the Debug port, and the third one is the system UART. This means that you only use a data supporting USB-C cable running from a modern computer to the back of the K2, no need for a specialty cable, nor a specialty adapter.

Therefore, on a F256K2 you want to select the second COM port that gets added to your system. As an example, on one Windows 10 system, the F256K2 USB-C connection added ports COM5, COM6 and COM7. All three coming up just as generic FTDI manufacturer USB ports.

=== Update batch file to point at correct port ===
To perform a full Kernel & SuperBASIC update, I simply downloaded the Complete Package (above) and edited the update.bat batch file to instead specify my system's COM6 (i.e. the 2nd added Port).

== Links to Software needed to do update with FoenixMgr (Python Script) ==
Python
[https://www.python.org/]

PySerial
[https://pyserial.readthedocs.io/en/latest/]

Foenix Manager (Collection of Python Scripts to use the USB Debug port)
[https://github.com/pweingar/FoenixMgr]

== Kernel and/or SuperBASIC Update Guide ==

Below, is a short video on how to install the software you will need to be able to reflash your Kernel and/or SuperBASIC.

==== How to Update your F256 Jr. / F256K Short ====

<youtube>Zgyhy_cBsM8</youtube>

==== How to Update your F256 Jr2 / F256K2 Video ====
<youtube>pOab0ocKqac</youtube>
Starting at 6:46, this video dives into updating the firmware for a specific core (each core have their pocket of 512K of flash memory, not shared).

Kernel & SuperBASIC Updates

2026-04-27T15:16:15Z

Agurtovoy: /* Kernel and/or SuperBASIC Releases */

== Kernel and/or SuperBASIC Releases ==

Official firmware releases that routinely improve SuperBASIC, MicroKernel and other built-in software, are published at https://github.com/wildbitscomputing/firmware.

If you want to apply a Kernel and/or SuperBASIC update independently, you could do so piecewise by replacing only the SuperBASIC or only the MicroKernel flash blocks, which available from the corresponding Github repos:
* [https://github.com/wildbitscomputing/MicroKernel/tree/master/bin Latest MicroKernel release]
* [https://github.com/wildbitscomputing/superbasic/releases SuperBASIC releases]

== USB Port ==

=== F256 Jr. / F256K ===
You will need to have the XR21B1411 USB Driver for PC/Linux. The MAC is outdated. (Note: Driver is not needed for the F256K2)
[https://www.maxlinear.com/product/interface/uarts/usb-uarts/xr21b1411]

=== F256K2 ===
On the F256K2 the XR21B1411 has been replaced by a FT4232, to allow direct use as a JTAG controller for the FPGA. There are 3 virtual serial ports (channels) enabled. The first connected to the Raspberry PI Nano (on-board) that manages the FPGA loading, the second one is the Debug port, and the third one is the system UART. This means that you only use a data supporting USB-C cable running from a modern computer to the back of the K2, no need for a specialty cable, nor a specialty adapter.

Therefore, on a F256K2 you want to select the second COM port that gets added to your system. As an example, on one Windows 10 system, the F256K2 USB-C connection added ports COM5, COM6 and COM7. All three coming up just as generic FTDI manufacturer USB ports.

=== Update batch file to point at correct port ===
To perform a full Kernel & SuperBASIC update, I simply downloaded the Complete Package (above) and edited the update.bat batch file to instead specify my system's COM6 (i.e. the 2nd added Port).

== Links to Software needed to do update with FoenixMgr (Python Script) ==
Python
[https://www.python.org/]

PySerial
[https://pyserial.readthedocs.io/en/latest/]

Foenix Manager (Collection of Python Scripts to use the USB Debug port)
[https://github.com/pweingar/FoenixMgr]

== Kernel and/or SuperBASIC Update Guide ==

Below, is a short video on how to install the software you will need to be able to reflash your Kernel and/or SuperBASIC.

==== How to Update your F256 Jr. / F256K Short ====

<youtube>Zgyhy_cBsM8</youtube>

==== How to Update your F256 Jr2 / F256K2 Video ====
<youtube>pOab0ocKqac</youtube>
Starting at 6:46, this video dives into updating the firmware for a specific core (each core have their pocket of 512K of flash memory, not shared).

Kernel & SuperBASIC Updates

2026-04-27T15:10:54Z

Agurtovoy: /* Kernel and/or SuperBASIC Update Links */

== Kernel and/or SuperBASIC Releases ==

Official firmware releases that routinely improve SuperBASIC, MicroKernel and other built-in software, are published on [https://discord.gg/K63fav2qHc Discord].

If you want to apply a Kernel and/or SuperBASIC update independently, you could do so piecewise by replacing only the SuperBASIC or only the MicroKernel flash blocks, which available from the corresponding Github repos:
* [https://github.com/wildbitscomputing/MicroKernel/tree/master/bin Latest MicroKernel release]
* [https://github.com/wildbitscomputing/superbasic/releases SuperBASIC releases]

== USB Port ==

=== F256 Jr. / F256K ===
You will need to have the XR21B1411 USB Driver for PC/Linux. The MAC is outdated. (Note: Driver is not needed for the F256K2)
[https://www.maxlinear.com/product/interface/uarts/usb-uarts/xr21b1411]

=== F256K2 ===
On the F256K2 the XR21B1411 has been replaced by a FT4232, to allow direct use as a JTAG controller for the FPGA. There are 3 virtual serial ports (channels) enabled. The first connected to the Raspberry PI Nano (on-board) that manages the FPGA loading, the second one is the Debug port, and the third one is the system UART. This means that you only use a data supporting USB-C cable running from a modern computer to the back of the K2, no need for a specialty cable, nor a specialty adapter.

Therefore, on a F256K2 you want to select the second COM port that gets added to your system. As an example, on one Windows 10 system, the F256K2 USB-C connection added ports COM5, COM6 and COM7. All three coming up just as generic FTDI manufacturer USB ports.

=== Update batch file to point at correct port ===
To perform a full Kernel & SuperBASIC update, I simply downloaded the Complete Package (above) and edited the update.bat batch file to instead specify my system's COM6 (i.e. the 2nd added Port).

== Links to Software needed to do update with FoenixMgr (Python Script) ==
Python
[https://www.python.org/]

PySerial
[https://pyserial.readthedocs.io/en/latest/]

Foenix Manager (Collection of Python Scripts to use the USB Debug port)
[https://github.com/pweingar/FoenixMgr]

== Kernel and/or SuperBASIC Update Guide ==

Below, is a short video on how to install the software you will need to be able to reflash your Kernel and/or SuperBASIC.

==== How to Update your F256 Jr. / F256K Short ====

<youtube>Zgyhy_cBsM8</youtube>

==== How to Update your F256 Jr2 / F256K2 Video ====
<youtube>pOab0ocKqac</youtube>
Starting at 6:46, this video dives into updating the firmware for a specific core (each core have their pocket of 512K of flash memory, not shared).

Kernel & SuperBASIC Updates

2026-04-27T15:10:00Z

Agurtovoy: /* Kernel and/or SuperBASIC Update Links */

== Kernel and/or SuperBASIC Update Links ==

Official firmware releases that routinely improve SuperBASIC, MicroKernel and other built-in software, are published on [https://discord.gg/K63fav2qHc Discord].

If you want to apply a Kernel and/or SuperBASIC update independently, you could do so piecewise by replacing only the SuperBASIC or only the MicroKernel flash blocks, which available from the corresponding Github repos:
* [https://github.com/wildbitscomputing/MicroKernel/tree/master/bin Latest MicroKernel release]
* [https://github.com/wildbitscomputing/superbasic/releases SuperBASIC releases]

== USB Port ==

=== F256 Jr. / F256K ===
You will need to have the XR21B1411 USB Driver for PC/Linux. The MAC is outdated. (Note: Driver is not needed for the F256K2)
[https://www.maxlinear.com/product/interface/uarts/usb-uarts/xr21b1411]

=== F256K2 ===
On the F256K2 the XR21B1411 has been replaced by a FT4232, to allow direct use as a JTAG controller for the FPGA. There are 3 virtual serial ports (channels) enabled. The first connected to the Raspberry PI Nano (on-board) that manages the FPGA loading, the second one is the Debug port, and the third one is the system UART. This means that you only use a data supporting USB-C cable running from a modern computer to the back of the K2, no need for a specialty cable, nor a specialty adapter.

Therefore, on a F256K2 you want to select the second COM port that gets added to your system. As an example, on one Windows 10 system, the F256K2 USB-C connection added ports COM5, COM6 and COM7. All three coming up just as generic FTDI manufacturer USB ports.

=== Update batch file to point at correct port ===
To perform a full Kernel & SuperBASIC update, I simply downloaded the Complete Package (above) and edited the update.bat batch file to instead specify my system's COM6 (i.e. the 2nd added Port).

== Links to Software needed to do update with FoenixMgr (Python Script) ==
Python
[https://www.python.org/]

PySerial
[https://pyserial.readthedocs.io/en/latest/]

Foenix Manager (Collection of Python Scripts to use the USB Debug port)
[https://github.com/pweingar/FoenixMgr]

== Kernel and/or SuperBASIC Update Guide ==

Below, is a short video on how to install the software you will need to be able to reflash your Kernel and/or SuperBASIC.

==== How to Update your F256 Jr. / F256K Short ====

<youtube>Zgyhy_cBsM8</youtube>

==== How to Update your F256 Jr2 / F256K2 Video ====
<youtube>pOab0ocKqac</youtube>
Starting at 6:46, this video dives into updating the firmware for a specific core (each core have their pocket of 512K of flash memory, not shared).

SuperBASIC

2026-04-27T14:58:26Z

Agurtovoy: /* Using procedures */

SuperBASIC is inspired by BBC BASIC but offers quite a bit more.
* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].
* [[SuperBASIC Memory Map]]
* SuperBASIC Mix Bag of [[Code Snippets]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].
* Read EMWhite's [https://apps.emwhite.org/shared-files/885/?Foenix-Rising-Issue-18-November-2024.pdf&download=1 Foenix Rising Issue 18] (November 2024) which goes into detail about a few of the gotchas of superbasic.

=== An informal list of tips, "gotchas": ===

===== IF, THEN, ELSE =====

====== Source of this tip: Ernesto ======
* A regular <code>if then</code> condition can't contain an <code>else</code> statement, as in this example:
10 if a=0 then x=10
* If you need to do an <code>if then else</code> structure, you actually have to do an <code>if else endif</code> structure like in the following example, skipping the <code>then</code> statement.
10 if a=0
20 x=1
30 else
40 x=2
50 endif
* If you do it in one line it needs to have some colons added, making it look weird like this:
10 if a=0:x=1:else:x=2:endif
* if you dare to omit the <code>endif</code> thinking that the <code>if</code> statement won't need it, (mmm.., everything is in one line, so no need, right?) -Nope...all hell breaks loose!-
10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"
* be careful not to add an extra <code>then</code> statement by mistake to an <code>if else endif</code> structure, if you do -All hell breaks loose again!!-
10 if a=0 then : rem "<-- Error, THEN is not needed!!!" <br />20 x=1 <br />30 else <br />40 x=2 <br />50 endif
''Debugging hint: If you encounter an error like "open structure" or "endproc without a proc": do not trust the line number that you are given. The root of the problem is probably in a structure earlier on in the code.''

===== Evaluating multiple conditions in IF statements =====
SUPERBASIC doesn't have the dedicated keywords AND , OR so you have to use the bitwise operators to evaluate multiple conditions, please consider the following examples:

* AND <code>if (a=1)&(b=2) then c=1</code>
* OR <code>if (a=1)^(b=2) then c=1</code>

This should work as long as you use parenthesis in all evaluated expressions (Since parenthesis makes bitwise operators behave like logical operators).

===== Using procedures =====

* When calling a procedure use the procedure name followed by parenthesis (), even if the procedure has no parameters.
* Avoid any space between the procedure name and the parenthesis, else it will produce an error.

===== Keyboard shortcuts =====
{| class="wikitable"
|+
!Key combination
!Effect
|-
|<code>ctrl-c</code> or <code>RUN STOP</code> on the F256K
|Stops a listing or a running program
|-
|<code>ctrl-l</code>
|Clears the screen
|-
|<code>ctrl-a</code> or <code>CLR/HOME</code> on the F256K
|Move cursor to the first character in the current line
|-
|<code>ctrl-e</code>
|Move cursor to the last character in the current line
|-
|<code>ctrl-i</code>
|Move cursor 8 characters to the right
|-
|<code>ctrl-k</code>
|Deletes characters from cursor position to line end
|}

===== Behaviour of load and bload =====

* The <code>bload</code> statement does not print <code>Completed</code> when loading is successfull whereas <code>load</code> does.
* bload can load anywhere on memory not just under the first 64k
* An exception is that bload can't load I/O parameters that reside in $C000 - $DFFF

===== Control characters for cursor and colour control =====
In BASIC the following character codes can be used with <code>print</code> to control the cursor position and colours on the screen.
{| class="wikitable"
!Code
!Effect
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(2)
|Cursor left
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|chr$(6)
|Cursor right
|-
|chr$(11)
|Deletes characters from cursor position to line end
|-
|chr$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(13)
|Move cursor to start of next line
|-
|chr$(14)
|Cursor down
|-
|chr$(16)
|Cursor up
|-
|chr$(128) - chr$(143)
|Set foreground color. Code 128 is black 143 is white. The rest follows the sequence given below
|-
|chr$(144) - chr$(159)
|Set background color. Code 144 is black 159 is white. The rest follows the sequence given below
|}
{| class="wikitable"
!Colour code
!Colour
!Colour code
!Colour
|-
|0
|Black
|8
|Dark grey
|-
|1
|Grey
|9
|Light grey (default foreground)
|-
|2
|Dark blue (default background colour)
|10
|Blue
|-
|3
|Green
|11
|Light green
|-
|4
|Purple
|12
|Light purple
|-
|5
|Brown
|13
|Red
|-
|6
|Orange
|14
|Yellow
|-
|7
|Light blue
|15
|White
|}The background colors do not work when the bitmap layer has been turned on. They will also not work if you have returned from the bitmap layer with a <code>bitmap off</code> command. In order to restore the background control character function you will need to make sure the MMU is set to zero by using <code>POKE 1,0</code> and then setting the text mode again by using <code>POKE $d000,1</code>.

==== Character Set / Text matrix ====
* Access to the full character set can be obtained by using the <code>CPRINT</code> command instead of the normal <code>PRINT</code> command.
* Characters can also be set on the screen text matrix using the <code>POKE</code> command starting at <code>$C000</code> providing the MMU I/O control is set to 2 by executing a <code>POKE 1,2</code> command first (remember to restore the MMU I/O once you're done).
[[File:Full char set.png|thumb|104x104px|F256 Character Set|none]]
* Color can also be set on the screen color matrix using the <code>POKE</code> command starting at <code>$C000</code> providing the MMU I/O control is set to 3 by executing a <code>POKE 1,3</code> command first (remember to restore the MMU I/O once you're done).
* When poking colors on the screen, the high nibble is the character color and the low nibble is the background color.

[[File:Colormatrix.png|alt=Default Colors|thumb|100x100px|Default Colors|none]]

===== Memcopy lockup =====

* In certain situations the <code><big>memcopy</big></code> command can lockup.
* A machine language utility that performs the same function as <code>memcopy</code> is available if <code>memcopy</code> fails.
* <u>mlcopy</u> is a short routine that replaces <code>memcopy</code> and is more reliable. It can be loaded into memory with a BLOAD command in your program, or with a basic loader that can be added to your program.
* In place of the <code>memcopy</code> command you would use 3 <code><big>POKEL</big></code> commands and a <code><big>CALL</big></code> command to engage the DMA engine.

POKEL $0903,data source
POKEL $0906,destination
POKEL $0909,number of bytes to copy
CALL $0900

* [https://github.com/mcassera/F256-mlcopy mlcopy github page]

===== Sprite Images =====

In BASIC you can access different SPRITE shapes through the IMAGE command as part of the sprite command: <code>SPRITE 0 IMAGE 1 TO 100,100</code>. Be aware that BASIC can only keep track of 64 Images, if you want to access and show more than 64 different shapes you need to poke the 3 bytes of the address where the image data resides into the correct sprite registers yourself.

===== Sprite Coordinates =====
In BASIC all sprites are centered on the coordinate specified, this might produce some counterintuitive effects when using different size sprites, for example if you want to align the sprite edge with the top left side of the screen you would need different values depending on the sprite size
SPRITE 0 IMAGE 1 TO 4,4: REM "8x8 Sprite"
SPRITE 1 IMAGE 1 TO 8,8: REM "16x16 Sprite"
SPRITE 2 IMAGE 2 TO 12,12: REM "24x24 Sprite"
SPRITE 3 IMAGE 3 TO 16,16: REM "32x32 Sprite"
Also, please note that you need to use the command <code>SPRITE X IMAGE Y</code> before setting the sprite coordinates or else BASIC will not know what size is the sprite, and will misalign it, for example the following code although it seems correct will misalign the sprite:
SPRITE 1 TO 8,8
SPRITE 1 IMAGE 1: REM "USe a 16x16 Sprite"

Building SuperBASIC itself

2026-04-27T14:57:28Z

Agurtovoy: /* Building SuperBASIC from Scratch */

= '''Building SuperBASIC from Scratch''' =

See the repository's README: https://github.com/wildbitscomputing/superbasic

Firmware

2026-02-02T04:42:22Z

Agurtovoy: /* RP2040 Firmware */

== System Flash ROM ==
The Foenix F256K, Jr., K2 and Jr2 computers contain 512K of flash memory which is intended to store software which should be available to the user without any media like SD-cards or IEC drives present. Think of it like a space traditionally occupied by ROM chips of 80's computers containing critical, often used programs and routines, but instead of being very rarely updated with scarce ROM chip revisions, it can be quickly updated with firmware revisions using the FoenixMgr python scripts.

'''Important Note''': for the F256K2, each core has its own dedicated area of 512K of flash memory. When switching to a new core, a separate dedicated area of 512K exists for that core and there's an expectation that the process of flashing the firmware has to be done for it.

This collection of software can be changed by the user by simply reprogramming the flash "ROM". At the moment (2025+) the following applications are stored in flash as a default loadout:
{| class="wikitable"
|+Collection of 6502/65816 firmware programs as of firmware release version 2025.13
!Absolute Block* in Memory Map
!Block* Offset in onboard Flash
!Name of program
!Description
|-
|0x40
|0x00
|'''''reserved'''''
|
|-
|0x41
|0x01
|xdev
|trampoline program meant to react to developper scripts from [[FoenixMgr]]: pcopy, runpgz, runpgx
|-
|0x42 to 0x45
|0x02 to 0x05
|superbasic
|if xdev has nothing to react to, superbasic is your default startup program
|-
|0x46
|0x06
|dos
|minimalistic file management and info shell
|-
|0x47
|0x07
|'''''free'''''
|
|-
|0x48
|0x08
|fcart
|allows a user to flash the 256K Flast Cart with 8kb prepared blocks. See [[CartFlasher|this for usage]]
|-
|0x49
|0x09
|'''free'''
|
|-
|0x4A
|0x0A
|help
|text help on screen for superbasic programming
|-
|0x4B to 0x4E
|0x0B to 0x0E
|'''''free'''''
|
|-
|0x4F
|0x0F
|wget
|web get, works only for gen1 K and Jr equipped with a feather wifi board
|-
|0x50 to 0x56
|0x10 to 0x16
|fm
|f/manager - a rather feature rich file manipulation, program launcher and memory exploration software
|-
|0x57
|0x17
|'''''free'''''
|
|-
|0x58 to 0x5B
|0x18 to 0x1B
|mless
|moreorless - a text editor. See [[Moreorless|here for more information.]]
|-
|0x5D to 0x7B
|0x1D to 0x3B
|'''''free'''''
|
|-
|0x7C to 0x7F
|0x3C to 0x3F
|microkernel
|the microkernel, gadget's masterpiece used by many programs
|}
<nowiki>*</nowiki>Block: each block of flash memory is 8kb is size

To reprogram the flash, you can start with the [https://github.com/FoenixRetro/f256-firmware/releases official firmware releases in this github.]

This repo is part the [https://github.com/FoenixRetro FoenixRetro] Github organisation which in turn is an attempt to gather forks of all projects which are part of the firmware and other resources relevant for the Foenix F256 new retro computers.

There are now two firmware loads available: Gen1 - for K and Jr and Gen2 - for K2 and Jr2. The only difference between these loads is the superbasic part of the firmware, in order to have a properly identified superbasic startup screen that reflects the exact computer and generation in the logo.

====== Video tutorial: ======
A part of a tutorial video covers updating the firmware as a follow up step to updating the FPGA core, check it at 6:45 and on.

<youtube>pOab0ocKqac</youtube>

==== 6809 firmware: ====
This core has specialized firmware - it is best to ask around in the appropriate channels of the [https://discord.gg/9vjUEGgcUS Foenix discord].

== RP2040 Firmware ==
This is a separate flash chip for the RP2040, which initializes the FPGA and uploads the core to it. These flash images are <code>.uf2</code> files.
[[File:Rp2040-cable.jpeg|thumb|Connector location, Switch S3 on the left, and cable orientation]]
Installation step:

* Install Cable as above (F256K2 Powered Off)
* Plug Cable in any PC that holds the new programming file.
* Keep 1 finger on the button
* Power the F256K2
* A new folder will appear on the PC's Desktop
* Drop the new file in the newly appeared folder.
* Power off F256K2
* Remove cable
* Reinstall the system as your heart's desire
* Power On the unit
* RP2040 is updated and running (because you need it to boot the unit)
* Bob's your uncle!

File:Rp2040-cable.jpeg

2026-02-02T04:41:32Z

Agurtovoy: Posted by Stefany on the discord

== Summary ==
Posted by Stefany on the discord

Main Page

2026-01-08T06:48:10Z

Agurtovoy: Update Wiki title

<div id="mainpage"></div> __NOTOC__ __NOEDITSECTION__


<div style="margin: 0 0 15px 0; padding: 1px; border: 1px solid #CCCCCC;">
{| style="width: 100%; margin: 0; padding: 0; border: 0; background-color: #FCFCFC; color: #000000; border-collapse: collapse;"
| align="center" style="vertical-align: top;"|
<div style="font-size: 150%;">Welcome to the Foenix F256x / Wildbits/K2 Wiki</div>
<div style="font-size: 100%; margin-top: 0.7em; line-height: 130%;">Dedicated to the WDC65C02/WDC65C816 or FNX6809 based F256x series of personal computers.</div>
|}
</div>


{| style="width: 100%; margin: 0; padding: 0; border: 0; border-collapse: collapse;"
| style="padding: 0; width: 25%; vertical-align: top;" |


{{NocatBox|subject=Getting Started|page=Main2/Getting_Started}}
{{NocatBox|subject=How To|page=Main2/How_To}}
{{NocatBox|subject=Technical Overview|page=Main2/Technical_Overview}}
{{NocatBox|subject=System Maintenance|page=Main2/System_Maintenance}}

| style="padding: 0 0 0 10px; width: 25%; vertical-align: top;" |


{{NocatBox|subject=Software Development|page=Main2/Software_Development}}
{{NocatBox|subject=Utility Software|page=Main2/UtilitiesPage}}
{{NocatBox|subject=W65C816 Processor|page=Main2/65816_Processor}}
{{NocatBox|subject=FNX6809 Processor|page=Main2/FNX6809_Processor}}
{{NocatBox|subject=Game Development|page=Main2/Game_Development}}
|}