Code Snippets

2025-06-07T01:44:14Z

Eacontrerasd:

2025-05-16T04:04:00Z

Eacontrerasd:

Code Snippets

2025-05-16T03:57:16Z

Code Snippets

2025-05-15T05:05:03Z

Eacontrerasd: Code Snippets

Index of SUPERBASIC Code Snippets (Hopefully this will be sorted by Topic when they grow)

# [[Poking and Peeking memory in a different Bank]]
# Printing Text at a determined Row, Column

<ref>====== Poking and Peeking memory in a different Bank ======</ref>
SUPERBASIC uses a lot of the memory available, so when you want to store data on a different Bank you want to POKE or PEEK outside the normal memory range, to do so you can use the following PROCEDURES. PLease note that these are not by any means a fast way to do it since we reconfigure the memory LUT so that the memory under the registers location ($C000-$DF00) points to the address that we want to poke or peek on the fly, after that we get or set the content of the memory address and restore the segments so that the Kernel does not blow up after returning. Contrary to what I initially believed it works!.<blockquote>

REM "XPEEK - value is stored in peekvalue variable"

proc xpeek(addr)

local block:block=addr\8192:local prevblock

local offset:offset=addr%8192

?0=179:prevblock=?$E:?$E=block:?1=4

peekvalue=peek($C000+offset)

?1=0:?$E=prevblock

endproc </blockquote><blockquote>REM "XPOKE"

proc xpoke(addr,value)

local block:block=addr\8192:local prevblock

local offset:offset=addr%8192

?0=179:prevblock=?$E:?$E=block:?1=4

?($C000+offset)=value

?1=0:?$E=prevblock

endproc </blockquote>

SuperBASIC

2025-05-15T04:44:49Z

Eacontrerasd:

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:
<code>10 if a=0 then x=10</code>
* 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.
<code>10 if a=0 
20 x=1 
30 else 
40 x=2 
50 endif</code>
* If you do it in one line it needs to have some colons added, making it look weird like this:
<code>10 if a=0:x=1:else:x=2:endif</code>
* 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!-
<code>10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"</code>
* 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!!-
<code>10 if a=0 then : rem "<-- Error, THEN is not needed!!!" 
20 x=1 
30 else 
40 x=2 
50 endif</code>

''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 =====

* The <code>proc</code> keyword is only valid if it appears after an <code>end</code> statement.
* 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.
* mlcopy 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.

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

* [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

<code>SPRITE 0 IMAGE 1 TO 4,4: REM "8x8 Sprite"</code>
<code>SPRITE 1 IMAGE 1 TO 8,8: REM "16x16 Sprite"</code>
<code>SPRITE 2 IMAGE 2 TO 12,12: REM "24x24 Sprite"</code>
<code>SPRITE 3 IMAGE 3 TO 16,16: REM "32x32 Sprite"</code>

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:

<code>SPRITE 1 TO 8,8</code>
<code>SPRITE 1 IMAGE 1: REM "USe a 16x16 Sprite"</code>

SuperBASIC

2025-05-15T04:43:04Z

Eacontrerasd: Added a Code Snippets reference

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:
<code>10 if a=0 then x=10</code>
* 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.
<code>10 if a=0 
20 x=1 
30 else 
40 x=2 
50 endif</code>
* If you do it in one line it needs to have some colons added, making it look weird like this:
<code>10 if a=0:x=1:else:x=2:endif</code>
* 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!-
<code>10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"</code>
* 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!!-
<code>10 if a=0 then : rem "<-- Error, THEN is not needed!!!" 
20 x=1 
30 else 
40 x=2 
50 endif</code>

''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 =====

* The <code>proc</code> keyword is only valid if it appears after an <code>end</code> statement.
* 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.
* mlcopy 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.

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

* [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

<code>SPRITE 0 IMAGE 1 TO 4,4: REM "8x8 Sprite"</code>
<code>SPRITE 1 IMAGE 1 TO 8,8: REM "16x16 Sprite"</code>
<code>SPRITE 2 IMAGE 2 TO 12,12: REM "24x24 Sprite"</code>
<code>SPRITE 3 IMAGE 3 TO 16,16: REM "32x32 Sprite"</code>

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:

<code>SPRITE 1 TO 8,8</code>
<code>SPRITE 1 IMAGE 1: REM "USe a 16x16 Sprite"</code>

Getting Started

2024-01-14T20:56:15Z

Eacontrerasd: /* Native Code */

== Getting Powered Up ==

=== Powering your F256K ===

The F256K is powered via a standard 2.5mm DC Connector, which takes a centre-positive 12V 2A capable Power Supply.

This type of power supply is quite common. [https://www.amazon.com/Adapter-100-240V-Transformer-Charger-Security/dp/B091XSVV1Y Example 12V 2A capable power supply] (#)

(#) ''This specific power supply has not been verified (by the author) for use with the F256K. Please update this page with verified options!''

=== Powering your F256Jr ===

The F256Jr is supplied as a Mini-ITX form factor mainboard, with a standard 24 pin ATX power supply connector for power connectivity.

Since the F256Jr needs relatively little power, compared to a mini-ATX PC, a popular DC 12V 24pin Pico ATX PSU works well and is a compact solution.

* [https://www.amazon.com/dp/B08F57GKCL Pico PSU] - You power the Pico PSU via a 12V DC center-positive Power Supply source.
* [https://www.amazon.com/dp/B07MXXXBV8 12V DC center-positive A/C Adapter] - Commonly used to power the Pico PSU.

== Getting programs onto the F256 ==

=== SD Card ===

Both the F256K and F256JR have an SD card slot. The device software to read the SD card is a bit touchy (it's inherited from the Commander X16 project) and doesn't work with all SD cards

* Cards should support the V2 protocol (HC or XC); older cards that only support the V1 protocol (typically 2GB or less) won't work. By contrast, the kernels for the C256 machines generally only work with V1 cards. Note that, in both cases, this is a software limitation -- all of the Foenix machines are electrically capable of using both kinds of cards.
* Cards *MUST* be formatted FAT32 -- **NOT: FAT, FAT12, FAT16, or exFAT**. Note that while MacOS will read a FAT32 formatted card, the included disk utility won't format FAT32. Windows 10/11 works fine, but make sure to force FAT32 (or use the command line: <code>format /FS:FAT32 H:</code>)
* Some folks have had luck formatting cards with the [https://www.sdcard.org/downloads/formatter/sd-memory-card-formatter-for-windows-download/ Official SD Association formatter for Windows].

=== Demos Archive ===

* [https://github.com/FoenixRetro/Documentation/blob/main/f256/archive Download the most recent demos archive] and expand it to the root of the flash card.

=== Debug USB port ===

* This is what most developers use as it's the most convenient. Connect the debug USB port to your PC or Mac

* You can use:
** [https://github.com/pweingar/FoenixMgr FoenixMgr] - works on Windows, Mac, Linux
*** A Python script to manage the Foenix series of retro style computers through their USB debug ports. This tool allows uploading files of various formats to system RAM, and displaying memory through various means.

** [https://github.com/Trinity-11/FoenixIDE FoenixIDE] (Windows only)
*** Development and Debugging Suite for the C256 Foenix Family of Computers.

=== wget ===
If you have the [[wifi]] configured, you can use [https://github.com/ghackwrench/F256_wget wget] to pull programs and data right off the web!

== SuperBASIC ==

The machine boots to SuperBASIC. SuperBASIC is inspired by BBC BASIC but offers quite a bit more.

* Read the [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].

* Watch EMWhite's excellent intro series on Youtube:
** Full Playlist here: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR EMWhite's Intro Series - Full Playlist].
** Part 1 can be viewed here:
<youtube>G_S2c_MsqYA</youtube>

To get started, you can type in a sample program at the command prompt:

<pre>
10 for i=1 to 5
20 print "Hello world"
30 next
run
</pre>

SuperBASIC is similar to CBM (Microsoft) BASIC but has some differences. For example, note in the sample above it's just <code>next</code> not <code>next i</code>.

The first 15 or so pages of the [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual] are quite instructive.

SuperBASIC is actually much more powerful and supports structured programming (procedures, blocks etc.)

<code>dir</code> - Run this to display directory of SD card

Loading & running programs off of the SD card is similarly easy:

<pre>
load "JrWordl.bas"
run
</pre>

Similar to the C64, you can save time in loading programs from the <code>dir</code> listing by using your cursor keys to go up to the entry, typing <code>load "</code> (insert mode is active by default) etc. You can use <code>CTRL+E</code> to jump to the end of the line and use <code>CTRL+K</code> to delete any text from the cursor to the end of the line. Correctly place the closing <code>"</code> and hit <code>ENTER</code>.

<code>CTRL+C</code> acts as a "break" command and stops any running SuperBASIC program or <code>LIST</code> command.

Read built-in help/reference:

<code>/help</code> : But '''NOTE''', this erases BASIC memory! Use Backspace key to go back in menus and to exit.

Explore the included demo SuperBASIC programs:

{| class="wikitable"
! Program !! Notes !! Source
|-
| <code>JrWordl.bas</code> || Wordle game, guess 5 letter word ||
|-
| <code>mandel.bas</code> || Draws Mandlebrot set in graphics mode, takes between 2 and 3 hours || [https://github.com/Mu0n/F256KbasicBASICdoodles @Mu0n]
|-
| <code>rpg-demo.bas</code> || UI sample that shows Zelda like RPG game. Control the character with an Atari-joystick connected to JoyPort1 || @econtrerasd
|-
| <code>Problematic_Code.bas</code> || Displays scrolling starfield ||
|-
| <code>noelrl.bas</code> || Simple integer BASIC bench mark from Noel's retro lab. Completes < 3.5 seconds, compares very favourably to other retro systems! || [https://www.youtube.com/watch?v=H05hM_Guoqk Youtube]
|-
| <code>dance.bas</code> || Animates sprite of dancer || [https://github.com/Mu0n/F256KbasicBASICdoodles @Mu0n]
|-
| <code>luna.bas</code> || Displays simple scene ||
|-
| <code>blink.bas</code> || Blinks drive access light || [https://github.com/Mu0n/F256KbasicBASICdoodles @Mu0n]
|-
| <code>piano.bas</code> || Play some notes with the PSG || [https://github.com/Mu0n/F256KbasicBASICdoodles @Mu0n]
|}

=== Memory Map under BASIC ===
{| class="wikitable sortable"
|+ Caption text
|-
! Initial Address !! End Address !! Description !! Bytes
|-
| $0000|| -|| MMU Control Register || 1
|-
| $0001|| -|| I/O Control Register || 1
|-
| $0002|| $0007|| Free Zero Page Addresses || 6
|-
| $0008|| $000F|| MMU Control Addresses || 8
|-
| $0010|| $002F|| Free Zero Page Addresses || 32
|-
| $0030|| $003F|| Used Zero Page Addresses for (xx),Y Addressing || 16
|-
| $0040|| $0041 || Current Address on screen of start of line || 2
|-
| $0042|| $004F|| Avaliable Zero Page Addresses || 14
|-
| $0050|| $00AF|| Number / Floating Point Stack for 16 numbers || 96
|-
| $00B0||$00EF|| Available Zero Page || 64
|-
| $00F0|| $00FF|| Kernel Arguments in Zero Page || 16
|-
| $0100|| $01FF|| Hardware Stack of 6502 || 256
|-
| $0200|| $0228|| Basic mini-Kernel memory || 40
|-
| $0229|| $03FF|| Available Low Memory | Also used by Sound Command in BASIC || 470
|-
| $0400|| $041F|| Control Storage first 8 bytes control syntax highlighting || 32
|-
| $0420|| $0814|| Memory Storage || 1012
|-
| $0814|| $0FFF|| Available Low Memory || 2028
|-
| $1000|| $1FFF|| SuperBASIC Identifier Tables, allocated memory, string vars, stack || 4kb
|-
| $2000|| $77FF|| SuperBASIC Program Tokenized Code (grows Upward) || 22kb
|-
| $7800|| $7FFF|| Top 2k of SuperBASIC Program tokenize code or used for ML routines in low memory || 2kb
|-
| $8000|| $BFFF|| SUPERBASIC CODE || 16kb
|-
| $C000|| $DFFF|| I/O Memory Pages / Underlying Kernel Code (Selectable with I/O control Register)|| 8kb
|-
| $E000|| $FFEF|| KERNEL CODE || 8176
|-
| $FFF0|| $FFFF|| Reset Vectors and NMI / IRQ / BRK Vectors || 16
|-
| $01:0000|| $02:2BFF|| Default Memory used by BASIC bitmap graphics || 75kb
|-
| $02:2C00|| $02:7FFF|| Available High Memory || 21kb
|-
| $02:8000|| $02:F000|| Available High Memory | Used for BASIC Cross Development w/PC or MAC|| 32k
|-
| $03:0000|| $03:7FFF|| Used for Sprite Data in BASIC || 32kb
|-
| $03:8000|| $03:FFFF|| Available High Memory | Unless not running from Flash, Used for ROM Images|| 32k
|-
| $04:0000|| $07:DFFF|| Available High Memory || 248kb
|-
| $07:E000|| $07:FFFF|| Available High Memory | Being considered to be Reserved for Environmental Variables || 8Kb
|-
| $10:0000|| $13:FFFF|| Cartridge Expansion Memory (addresable only by CPU) || 256kb
|-
| $14:0000|| $1F:FFFF|| Future Expansions? || 768kb
|}

== More Resources ==

=== This Wiki ===

Explore all of the content of this Wiki, to expand your F256 series knowledge!

=== Discord ===

The [https://discord.com/invite/aAEQXZHXgM Foenix Retro Systems Discord] is the primary place to get questions answered.

Also, if you resolve your question, and you didn't find the answer here on the Wiki, '''''please consider contributing to the Wiki''''', for the benefit of others with the same question!

=== Foenix Retro Systems Newletter ===

Read back issues [http://apps.emwhite.org/foenixmarketplace/ here] (also a great source for sample programs).

Issues starting at #4 cover the F256 line. Issues 1-3 cover the previous version of the hardware (C256), although there are still many salient points.