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

Tools & Scripts

2026-01-30T07:14:52Z

Mcassera: /* Music Tools and Scripts */

== 000F256 Machines Game Development Tools ==

=== Sprite Creation Tools & Scripts ===

{| class="wikitable"
! Tool !! Link !! Notes
|-
| style="white-space:nowrap;"| Aseprite
| style="white-space:nowrap;"| https://www.aseprite.org/
| style="white-space:nowrap;" |Aseprite can be used to create sprites animation or Tiles Sets.
|-
|Scripts relevant to Aseprite usage
|
*[[Export Aseprite Tilemap]]
* [[Export Aseprite Tileset]]
* [[Export Aseprite Sprites]]
|If you use Aseprite, you can convert your tile drawings to tilesets and tilemaps using these scripts. The export to sprites will convert sprites to a 64tass compatible text file.
|-
|f256_sprite_cutter
|https://gist.github.com/digarok/57b096236a7fb1c76efef6cbb9f73a83
|Sprite cutter that cuts a PNG according to line-by-line instructions in a text file. Requires python and the PIL library, install with:
python -m pip install --upgrade pip

python -m pip install --upgrade Pillow
Run with:
python f256_sprite_cutter.py myimage.png mylist.txt sprites.s
where mylist.txt contains a series of lines containing x, y offset, width, name, where it's assumed the width is the same as the height since it's for square sprites supported for the F256xx, such as 8,16, or 32.

The output (named sprites.s in this above example) is a series of hex instructions with a list of hex values of a color picked from the CLUT.

In order to make it compatible with 64tass, I search replaced hex-> .byte and replaced every value I could find by swapping in a $ in front (ie 00 -> $00 and 01 -> $01, etc.)
|-
|Foenix Graphics Toolkit
|https://github.com/econtrerasd/F256-GraphicToolkit
|The Sprite Editor module in the Graphics Toolkit can help you draw sprites of different sizes in the F256 platform and save them as Spr files. The file format is documented in the manual
|-
|png2raw.py
|https://github.com/cmassat/EffenX/tree/dev/util
|python script by SprySloth, converts a grid png of sprite frames into individual bin (raw bitmap) and pal (palette) files, ready to be consumed by your project. A good source of these grid pngs can be from Aseprite above.
|}

=== Music Tools and Scripts ===

{| class="wikitable"
! Tool !! Link !! Notes
|-
|DOSBox VGM music extraction mini-guide
|[[Software#Music]] for playvgm.pgx
|DOSBox uses a YM3812 chip that outputs OPL2, this is a great, immense source of music that can leverage the OPL functionality of the F256K
1) run dosbox 0.74+, from the command line and mount your game as <code>dosbox -c "MOUNT C C:\YOURGAMEISHERE"</code> avoid spaces in folder names

2) before you get to the point where the music you want to extract plays, hit CTRL-ALT-F7 and you should see in the dosbox 'log' window that a music capture has started. I think it dumps your captures in /username/appdata/local/dosbox/capture but it will say where in the log window

3) reach the point where it plays and let it loop or run its course, hit CTRL-ALT-F7 to stop the capture.

4) this gives you a .DRO that you can analyze with https://www.jestarjokin.net/apps/drotrimmer/ . the analysis tool is supposed to find loops, but it didn't work well with the first tune I tried.

5) try to find the location of your first tune's note in the main window of drotrimmer and try to start the playback from there. delete superfluous notes that might surround your tune.

6) use dro2vgm command line tool: https://www.vgmpf.com/Wiki/index.php/DRO_to_VGM

7) open in a hex editor and chop off the bytes from 0x00 to 0xFF (it's the header)

8) transfer to your F256K (jr has no opl support!)

9) bload "yourtrimmed.vgm",$010000

10) run playvgm.pgx
|-
|Convert MIDI files into VGM files.
| https://github.com/SudoMaker/midi2vgm
| This is a Linux app, but does compile using Linux on windows under WSL.
Link to WSL install:
https://learn.microsoft.com/en-us/windows/wsl/install

'''Link to binaries'''

https://github.com/cmassat/midi2vgm/releases/tag/V1.0.0

libADLMIDI.a <- Required Library

midi2vgm_opl3 <- Executable
|-
|convert.py
|https://github.com/natebarney/playvgm-f256k/tree/master/util
|from NateBarney

convert.py : python script to read a VGM or VGZ, decompress it if needed, and strip off the VGM header and GD3 tag
|-
|Sekaiju
|https://openmidiproject.opal.ne.jp/Sekaiju_en.html
|Easily compose and sequence MIDI music. Supports score notation, piano roll and MIDI in if you have a MIDI interface.
|-
|GoatTracker
|[[GoatTracker|Guide to use GoatTracker for the F256.]]
|A SID tracker for DOS/MAC/LINUX that can create packed binary files for playback on the F256 computers.
|}

*

Tools & Scripts

2026-01-30T04:50:31Z

Mcassera: Added a link to the GoatTracker guide for the F256

== 000F256 Machines Game Development Tools ==

=== Sprite Creation Tools & Scripts ===

{| class="wikitable"
! Tool !! Link !! Notes
|-
| style="white-space:nowrap;"| Aseprite
| style="white-space:nowrap;"| https://www.aseprite.org/
| style="white-space:nowrap;" |Aseprite can be used to create sprites animation or Tiles Sets.
|-
|Scripts relevant to Aseprite usage
|
*[[Export Aseprite Tilemap]]
* [[Export Aseprite Tileset]]
* [[Export Aseprite Sprites]]
|If you use Aseprite, you can convert your tile drawings to tilesets and tilemaps using these scripts. The export to sprites will convert sprites to a 64tass compatible text file.
|-
|f256_sprite_cutter
|https://gist.github.com/digarok/57b096236a7fb1c76efef6cbb9f73a83
|Sprite cutter that cuts a PNG according to line-by-line instructions in a text file. Requires python and the PIL library, install with:
python -m pip install --upgrade pip

python -m pip install --upgrade Pillow
Run with:
python f256_sprite_cutter.py myimage.png mylist.txt sprites.s
where mylist.txt contains a series of lines containing x, y offset, width, name, where it's assumed the width is the same as the height since it's for square sprites supported for the F256xx, such as 8,16, or 32.

The output (named sprites.s in this above example) is a series of hex instructions with a list of hex values of a color picked from the CLUT.

In order to make it compatible with 64tass, I search replaced hex-> .byte and replaced every value I could find by swapping in a $ in front (ie 00 -> $00 and 01 -> $01, etc.)
|-
|Foenix Graphics Toolkit
|https://github.com/econtrerasd/F256-GraphicToolkit
|The Sprite Editor module in the Graphics Toolkit can help you draw sprites of different sizes in the F256 platform and save them as Spr files. The file format is documented in the manual
|-
|png2raw.py
|https://github.com/cmassat/EffenX/tree/dev/util
|python script by SprySloth, converts a grid png of sprite frames into individual bin (raw bitmap) and pal (palette) files, ready to be consumed by your project. A good source of these grid pngs can be from Aseprite above.
|}

=== Music Tools and Scripts ===

{| class="wikitable"
! Tool !! Link !! Notes
|-
|DOSBox VGM music extraction mini-guide
|[[Software#Music]] for playvgm.pgx
|DOSBox uses a YM3812 chip that outputs OPL2, this is a great, immense source of music that can leverage the OPL functionality of the F256K
1) run dosbox 0.74+, from the command line and mount your game as <code>dosbox -c "MOUNT C C:\YOURGAMEISHERE"</code> avoid spaces in folder names

2) before you get to the point where the music you want to extract plays, hit CTRL-ALT-F7 and you should see in the dosbox 'log' window that a music capture has started. I think it dumps your captures in /username/appdata/local/dosbox/capture but it will say where in the log window

3) reach the point where it plays and let it loop or run its course, hit CTRL-ALT-F7 to stop the capture.

4) this gives you a .DRO that you can analyze with https://www.jestarjokin.net/apps/drotrimmer/ . the analysis tool is supposed to find loops, but it didn't work well with the first tune I tried.

5) try to find the location of your first tune's note in the main window of drotrimmer and try to start the playback from there. delete superfluous notes that might surround your tune.

6) use dro2vgm command line tool: https://www.vgmpf.com/Wiki/index.php/DRO_to_VGM

7) open in a hex editor and chop off the bytes from 0x00 to 0xFF (it's the header)

8) transfer to your F256K (jr has no opl support!)

9) bload "yourtrimmed.vgm",$010000

10) run playvgm.pgx
|-
|Convert MIDI files into VGM files.
| https://github.com/SudoMaker/midi2vgm
| This is a Linux app, but does compile using Linux on windows under WSL.
Link to WSL install:
https://learn.microsoft.com/en-us/windows/wsl/install

'''Link to binaries'''

https://github.com/cmassat/midi2vgm/releases/tag/V1.0.0

libADLMIDI.a <- Required Library

midi2vgm_opl3 <- Executable
|-
|convert.py
|https://github.com/natebarney/playvgm-f256k/tree/master/util
|from NateBarney

convert.py : python script to read a VGM or VGZ, decompress it if needed, and strip off the VGM header and GD3 tag
|-
|Sekaiju
|https://openmidiproject.opal.ne.jp/Sekaiju_en.html
|Easily compose and sequence MIDI music. Supports score notation, piano roll and MIDI in if you have a MIDI interface.
|-
|GoatTracker
|Guide to use [[GoatTracker]] for the F256.
|A SID tracker for DOS/MAC/LINUX that can create packed binary files for playback on the F256 computers.
|}

*

GoatTracker

2026-01-30T04:45:52Z

Mcassera: /* 3. Pitch and Timing (Important) */

= Using GoatTracker to Create F256K SID Music =

This guide explains how to use '''GoatTracker''' to compose SID music and generate a packed <code>.bin</code> file that plays correctly on the '''F256K / F256K2 FPGA SID'''.

This document focuses on SID-only usage (no PSG or other sound chips).

---

== 1. Getting GoatTracker ==

* GoatTracker is available for '''Windows, macOS, and Linux'''.
* Download page: https://cadaver.github.io/
* The stereo version (useful for dual SIDs on F256K2) is available on SourceForge under the files tab.

---

== 2. Creating a Song ==

# Create and edit your song in GoatTracker as you would for a C64.
# Most instruments, effects, and patterns work correctly on the F256K FPGA SID.
# GoatTracker was tuned for real C64 hardware, so FPGA SIDs may sound slightly different.

---

== 3. Pitch and Timing (Important) ==

Pitch and playback speed are '''related but separate settings'''.

* '''Playback speed''' is controlled by PAL vs NTSC timing (50 Hz vs 60 Hz).
* '''Pitch''' is controlled by the A-4 tuning value.

The F256K uses '''NTSC (60 Hz)''' timing so Goattracker must be configured accordingly.

---

=== 3.1 Editing and Previewing on Your Computer ===

When composing music on your computer, use NTSC timing and corrected pitch.

Recommended settings:

<code>
goattracker -N -G424 song.sng
</code>

* <code>-N</code> — NTSC timing (60 Hz)
* <code>-G424</code> — Correct pitch for NTSC preview

This setting is for '''editing only'''.

---

=== 3.2 Packing for Playback on the F256K ===

The F256K requires a different tuning to produce true 440 Hz pitch.

Tested value:

* '''A-4 = 454 Hz'''

When packing a song, always start GoatTracker with the correct tuning and the song loaded at startup:

<code>
goattracker -G454 song.sng
</code>

'''Important:''' <code>.sng</code> files store tuning. Loading after startup will overwrite the setting and result in an incorrectly tuned packed file.

---

== 4. Packing the Song ==

Songs must be packed into a self-playing binary for use on the F256.

---

=== Option A: Internal Pack (F9) ===

* Press <code>F9</code> in GoatTracker.
* Ensure it was started with <code>-G454</code> and the song loaded.
The internal packer always uses the '''current tuning'''.

---

=== Option B: External Packer (GT2RELOC.EXE) ===

Recommended method.

Example command:

<code>
GT2RELOC song.sng song.bin -N -G454 -LD400 -Wa0 -Z80
</code>

---

==== Parameter Explanation ====

* <code>song.sng</code> — Input song
* <code>song.bin</code> — Output binary
* <code>-N</code> — NTSC timing
* <code>-G454</code> — F256K tuning
* <code>-LD400</code> — SID base address
* <code>-Wa0</code> — Player load address ($A000)
* <code>-Z80</code> — Zeropage ($80/$81)

---

==== Notes ====

* <code>-Wxx</code> sets the high byte only
** Example:<code>-Wa0</code> = $A000
* <code>-Zxx</code> specifies the '''starting zeropage address'''
** uses two bytes
*** $80/$81 is tested and safe
*** Avoid $F0–$FF (kernel use)
* <code>-Wxx</code> and <code>-Zxx</code> are configurable based on your program's memory layout.

---

== 5. Playing the Music ==

---

=== 5.1 Initialization ===

Call the music player's init routine once. It is located at the player load address <code>(-Wxx)</code>.

<code>
JSR $A000 ; initialize song
</code>

---

=== 5.2 Per-Frame Playback ===

Call the playback routine '''once per frame''' (SOF / 60 Hz)'''.'''

* Playback routine address = <code>init + 3</code>

<code>
JSR $A003 ; play song for this frame
</code>

Repeat this call every frame for continuous playback.

---

== 6. Additional Notes ==

* Pitch and speed are '''not the same''':
** <code>-N</code> controls speed
** <code>-Gxx</code> controls pitch
* GoatTracker adjusts pitch tables when switching PAL/NTSC, but '''manual A-4 correction is still required.'''
* The packed <code>.bin</code> file is unchanged between the C64 and the F256 - compatibility comes from correct timing, tuning, and memory placement.

---

== Appendix: Minimal F256 SID Music Player Example ==

The following is a minimal working music player using kernel timers.

---

This example matches the configuration described in this wiki page:

* Player loaded at '''$A000''' (<code>-Wa0</code>)
* Player routine at '''$A003'''
* Zeropage usage at '''$80/$81''' (used internally by the player)
* NTSC / 60 Hz playback 
; ============================================================================
; music_min.asm - Minimal Music Player for Wildbits/K & /Jr
; ============================================================================

.cpu "65816"
MMU_IO_CTRL = $01
init_music = $A000
play_music = init_music+3
timer_cookie = $D0

*=$A0
.dsection zp
.cerror * > $AF, "Too many zero page variables"

.include "api.asm"

.section zp
event: .dstruct kernel.event.event_t
.send

*=$1000

start:
stz MMU_IO_CTRL

lda #<event
sta kernel.args.events
lda #>event
sta kernel.args.events+1

jsr init_music
jsr SetTimer

loop:
jsr handle_events
bra loop

handle_events:
lda kernel.args.events.pending
bpl done_handle_events
jsr kernel.NextEvent
bcs done_handle_events
jsr dispatch
jmp handle_events

done_handle_events:
rts

dispatch:
lda event.type
cmp #kernel.event.timer.EXPIRED
beq music_playback
rts

music_playback:
jsr SetTimer
jsr play_music
rts

SetTimer:
inc timer_cookie
lda timer_cookie
sta kernel.args.timer.absolute
sta kernel.args.timer.cookie
lda #kernel.args.timer.FRAMES
sta kernel.args.timer.units
jsr kernel.Clock.SetTimer
rts

*=$A000
.binary "testsong.bin"

---

== Cheat Sheet ==

=== Edit / Preview (NTSC, correct pitch) ===

<code>
goattracker -N -G424 song.sng
</code>

=== Pack for F256K ===

<code>
GT2RELOC song.sng song.bin -N -G454 -LD400 -Wa0 -Z80
</code>

=== Internal Pack ===

<code>
goattracker -G454 song.sng
</code>

Press <code>F9</code>

---

=== Playback in your program ===

<code>
JSR $A000

JSR $A003
</code>

---

=== Tested Defaults for the F256 ===

* SID: $D400
* Player: $A000
* Zeropage: $80/$81
* Timing: NTSC (60 Hz)

---

End of document.

GoatTracker

2026-01-30T04:24:19Z

Mcassera: /* 3. Pitch and Timing */

= Using GoatTracker to Create F256K SID Music =

This guide explains how to use '''GoatTracker''' to compose SID music and generate a packed <code>.bin</code> file that plays correctly on the '''F256K / F256K2 FPGA SID'''.

This document focuses on SID-only usage (no PSG or other sound chips).

---

== 1. Getting GoatTracker ==

* GoatTracker is available for '''Windows, macOS, and Linux'''.
* Download page: https://cadaver.github.io/
* The stereo version (useful for dual SIDs on F256K2) is available on SourceForge under the files tab.

---

== 2. Creating a Song ==

# Create and edit your song in GoatTracker as you would for a C64.
# Most instruments, effects, and patterns work correctly on the F256K FPGA SID.
# GoatTracker was tuned for real C64 hardware, so FPGA SIDs may sound slightly different.

---

== 3. Pitch and Timing (Important) ==

Pitch and playback speed are '''separate settings'''.

* Playback speed is controlled by PAL vs NTSC timing (50 Hz vs 60 Hz).
* Pitch is controlled by the A-4 tuning value.

The F256K uses '''NTSC (60 Hz)''' timing.

---

=== 3.1 Editing and Previewing on Your Computer ===

When composing music on your computer, use NTSC timing and corrected pitch.

Recommended settings:

<code>
goattracker -N -G424 song.sng
</code>

* <code>-N</code> — NTSC timing (60 Hz)
* <code>-G424</code> — Correct pitch for NTSC preview

This setting is for '''editing only'''.

---

=== 3.2 Packing for Playback on the F256K ===

The F256K requires a different tuning to produce true 440 Hz pitch.

Tested value:

* '''A-4 = 454 Hz'''

Always start GoatTracker with:

<code>
goattracker -G454 song.sng
</code>

'''Important:''' <code>.sng</code> files store tuning. Loading after startup will overwrite the setting.

---

== 4. Packing the Song ==

Songs must be packed into a self-playing binary.

---

=== Option A: Internal Pack (F9) ===

* Press <code>F9</code> in GoatTracker.
* Ensure it was started with <code>-G454</code> and the song loaded.

---

=== Option B: External Packer (GT2RELOC.EXE) ===

Recommended method.

Example command:

<code>
GT2RELOC song.sng song.bin -N -G454 -LD400 -Wa0 -Z80
</code>

---

==== Parameter Explanation ====

* <code>song.sng</code> — Input song
* <code>song.bin</code> — Output binary
* <code>-N</code> — NTSC timing
* <code>-G454</code> — F256K tuning
* <code>-LD400</code> — SID base address
* <code>-Wa0</code> — Player load address ($A000)
* <code>-Z80</code> — Zeropage ($80/$81)

---

==== Notes ====

* <code>-Wxx</code> sets the high byte only
** <code>-Wa0</code> = $A000
* <code>-Zxx</code> uses two bytes
** $80/$81 is tested and safe
** Avoid $F0–$FF (kernel use)
* <code>-Wxx</code> and <code>-Zxx</code> are configurable

---

== 5. Playing the Music ==

---

=== 5.1 Initialization ===

Call the init routine:

<code>
JSR $A000
</code>

---

=== 5.2 Per-Frame Playback ===

Call once per frame:

<code>
JSR $A003
</code>

---

== 6. Additional Notes ==

* <code>-N</code> controls speed
* <code>-Gxx</code> controls pitch
* Both are required
* The binary is C64-compatible
* Correct setup ensures compatibility

---

== Appendix: Minimal F256 SID Music Player Example ==

The following is a minimal working music player using kernel timers.

---

; ============================================================================
; music_min.asm - Minimal Music Player for Wildbits/K & /Jr
; ============================================================================

.cpu "65816"
MMU_IO_CTRL = $01
init_music = $A000
play_music = init_music+3
timer_cookie = $D0

*=$A0
.dsection zp
.cerror * > $AF, "Too many zero page variables"

.include "api.asm"

.section zp
event: .dstruct kernel.event.event_t
.send

*=$1000

start:
stz MMU_IO_CTRL

lda #<event
sta kernel.args.events
lda #>event
sta kernel.args.events+1

jsr init_music
jsr SetTimer

loop:
jsr handle_events
bra loop

handle_events:
lda kernel.args.events.pending
bpl done_handle_events
jsr kernel.NextEvent
bcs done_handle_events
jsr dispatch
jmp handle_events

done_handle_events:
rts

dispatch:
lda event.type
cmp #kernel.event.timer.EXPIRED
beq music_playback
rts

music_playback:
jsr SetTimer
jsr play_music
rts

SetTimer:
inc timer_cookie
lda timer_cookie
sta kernel.args.timer.absolute
sta kernel.args.timer.cookie
lda #kernel.args.timer.FRAMES
sta kernel.args.timer.units
jsr kernel.Clock.SetTimer
rts

*=$A000
.binary "testsong.bin"

---

== Cheat Sheet ==

=== Edit / Preview ===

<code>
goattracker -N -G424 song.sng
</code>

=== Pack for F256K ===

<code>
GT2RELOC song.sng song.bin -N -G454 -LD400 -Wa0 -Z80
</code>

=== Internal Pack ===

<code>
goattracker -G454 song.sng
</code>

Press <code>F9</code>

---

=== Playback ===

<code>
JSR $A000

JSR $A003
</code>

---

=== Tested Defaults ===

* SID: $D400
* Player: $A000
* Zeropage: $80/$81
* Timing: NTSC (60 Hz)

---

End of document.

GoatTracker

2026-01-30T04:21:02Z

Mcassera: /* Notes */

= Using GoatTracker to Create F256K SID Music =

This guide explains how to use '''GoatTracker''' to compose SID music and generate a packed <code>.bin</code> file that plays correctly on the '''F256K / F256K2 FPGA SID'''.

This document focuses on SID-only usage (no PSG or other sound chips).

---

== 1. Getting GoatTracker ==

* GoatTracker is available for '''Windows, macOS, and Linux'''.
* Download page: https://cadaver.github.io/
* The stereo version (useful for dual SIDs on F256K2) is available on SourceForge under the files tab.

---

== 2. Creating a Song ==

# Create and edit your song in GoatTracker as you would for a C64.
# Most instruments, effects, and patterns work correctly on the F256K FPGA SID.
# GoatTracker was tuned for real C64 hardware, so FPGA SIDs may sound slightly different.

---

== 3. Pitch and Timing ==

Pitch and playback speed are '''separate settings'''.

* Playback speed is controlled by PAL vs NTSC timing (50 Hz vs 60 Hz).
* Pitch is controlled by the A-4 tuning value.

The F256K uses '''NTSC (60 Hz)''' timing.

---

=== 3.1 Editing and Previewing on Your Computer ===

When composing music on your computer, use NTSC timing and corrected pitch.

Recommended settings:

<code>
goattracker -N -G424 song.sng
</code>

* <code>-N</code> — NTSC timing (60 Hz)
* <code>-G424</code> — Correct pitch for NTSC preview

This setting is for '''editing only'''.

---

=== 3.2 Packing for Playback on the F256K ===

The F256K requires a different tuning to produce true 440 Hz pitch.

Tested value:

* '''A-4 = 454 Hz'''

Always start GoatTracker with:

<code>
goattracker -G454 song.sng
</code>

'''Important:''' <code>.sng</code> files store tuning. Loading after startup will overwrite the setting.

---

== 4. Packing the Song ==

Songs must be packed into a self-playing binary.

---

=== Option A: Internal Pack (F9) ===

* Press <code>F9</code> in GoatTracker.
* Ensure it was started with <code>-G454</code> and the song loaded.

---

=== Option B: External Packer (GT2RELOC.EXE) ===

Recommended method.

Example command:

<code>
GT2RELOC song.sng song.bin -N -G454 -LD400 -Wa0 -Z80
</code>

---

==== Parameter Explanation ====

* <code>song.sng</code> — Input song
* <code>song.bin</code> — Output binary
* <code>-N</code> — NTSC timing
* <code>-G454</code> — F256K tuning
* <code>-LD400</code> — SID base address
* <code>-Wa0</code> — Player load address ($A000)
* <code>-Z80</code> — Zeropage ($80/$81)

---

==== Notes ====

* <code>-Wxx</code> sets the high byte only
** <code>-Wa0</code> = $A000
* <code>-Zxx</code> uses two bytes
** $80/$81 is tested and safe
** Avoid $F0–$FF (kernel use)
* <code>-Wxx</code> and <code>-Zxx</code> are configurable

---

== 5. Playing the Music ==

---

=== 5.1 Initialization ===

Call the init routine:

<code>
JSR $A000
</code>

---

=== 5.2 Per-Frame Playback ===

Call once per frame:

<code>
JSR $A003
</code>

---

== 6. Additional Notes ==

* <code>-N</code> controls speed
* <code>-Gxx</code> controls pitch
* Both are required
* The binary is C64-compatible
* Correct setup ensures compatibility

---

== Appendix: Minimal F256 SID Music Player Example ==

The following is a minimal working music player using kernel timers.

---

; ============================================================================
; music_min.asm - Minimal Music Player for Wildbits/K & /Jr
; ============================================================================

.cpu "65816"
MMU_IO_CTRL = $01
init_music = $A000
play_music = init_music+3
timer_cookie = $D0

*=$A0
.dsection zp
.cerror * > $AF, "Too many zero page variables"

.include "api.asm"

.section zp
event: .dstruct kernel.event.event_t
.send

*=$1000

start:
stz MMU_IO_CTRL

lda #<event
sta kernel.args.events
lda #>event
sta kernel.args.events+1

jsr init_music
jsr SetTimer

loop:
jsr handle_events
bra loop

handle_events:
lda kernel.args.events.pending
bpl done_handle_events
jsr kernel.NextEvent
bcs done_handle_events
jsr dispatch
jmp handle_events

done_handle_events:
rts

dispatch:
lda event.type
cmp #kernel.event.timer.EXPIRED
beq music_playback
rts

music_playback:
jsr SetTimer
jsr play_music
rts

SetTimer:
inc timer_cookie
lda timer_cookie
sta kernel.args.timer.absolute
sta kernel.args.timer.cookie
lda #kernel.args.timer.FRAMES
sta kernel.args.timer.units
jsr kernel.Clock.SetTimer
rts

*=$A000
.binary "testsong.bin"

---

== Cheat Sheet ==

=== Edit / Preview ===

<code>
goattracker -N -G424 song.sng
</code>

=== Pack for F256K ===

<code>
GT2RELOC song.sng song.bin -N -G454 -LD400 -Wa0 -Z80
</code>

=== Internal Pack ===

<code>
goattracker -G454 song.sng
</code>

Press <code>F9</code>

---

=== Playback ===

<code>
JSR $A000

JSR $A003
</code>

---

=== Tested Defaults ===

* SID: $D400
* Player: $A000
* Zeropage: $80/$81
* Timing: NTSC (60 Hz)

---

End of document.

GoatTracker

2026-01-30T04:17:39Z

Mcassera: Created page with "= Using GoatTracker to Create F256K SID Music = This guide explains how to use '''GoatTracker''' to compose SID music and generate a packed <code>.bin</code> file that plays correctly on the '''F256K / F256K2 FPGA SID'''. This document focuses on SID-only usage (no PSG or other sound chips). --- == 1. Getting GoatTracker == * GoatTracker is available for '''Windows, macOS, and Linux'''. * Download page: https://cadaver.github.io/ * The stereo version (useful for dua..."

= Using GoatTracker to Create F256K SID Music =

This guide explains how to use '''GoatTracker''' to compose SID music and generate a packed <code>.bin</code> file that plays correctly on the '''F256K / F256K2 FPGA SID'''.

This document focuses on SID-only usage (no PSG or other sound chips).

---

== 1. Getting GoatTracker ==

* GoatTracker is available for '''Windows, macOS, and Linux'''.
* Download page: https://cadaver.github.io/
* The stereo version (useful for dual SIDs on F256K2) is available on SourceForge under the files tab.

---

== 2. Creating a Song ==

# Create and edit your song in GoatTracker as you would for a C64.
# Most instruments, effects, and patterns work correctly on the F256K FPGA SID.
# GoatTracker was tuned for real C64 hardware, so FPGA SIDs may sound slightly different.

---

== 3. Pitch and Timing ==

Pitch and playback speed are '''separate settings'''.

* Playback speed is controlled by PAL vs NTSC timing (50 Hz vs 60 Hz).
* Pitch is controlled by the A-4 tuning value.

The F256K uses '''NTSC (60 Hz)''' timing.

---

=== 3.1 Editing and Previewing on Your Computer ===

When composing music on your computer, use NTSC timing and corrected pitch.

Recommended settings:

<code>
goattracker -N -G424 song.sng
</code>

* <code>-N</code> — NTSC timing (60 Hz)
* <code>-G424</code> — Correct pitch for NTSC preview

This setting is for '''editing only'''.

---

=== 3.2 Packing for Playback on the F256K ===

The F256K requires a different tuning to produce true 440 Hz pitch.

Tested value:

* '''A-4 = 454 Hz'''

Always start GoatTracker with:

<code>
goattracker -G454 song.sng
</code>

'''Important:''' <code>.sng</code> files store tuning. Loading after startup will overwrite the setting.

---

== 4. Packing the Song ==

Songs must be packed into a self-playing binary.

---

=== Option A: Internal Pack (F9) ===

* Press <code>F9</code> in GoatTracker.
* Ensure it was started with <code>-G454</code> and the song loaded.

---

=== Option B: External Packer (GT2RELOC.EXE) ===

Recommended method.

Example command:

<code>
GT2RELOC song.sng song.bin -N -G454 -LD400 -Wa0 -Z80
</code>

---

==== Parameter Explanation ====

* <code>song.sng</code> — Input song
* <code>song.bin</code> — Output binary
* <code>-N</code> — NTSC timing
* <code>-G454</code> — F256K tuning
* <code>-LD400</code> — SID base address
* <code>-Wa0</code> — Player load address ($A000)
* <code>-Z80</code> — Zeropage ($80/$81)

---

==== Notes ====

* <code>-Wxx</code> sets the high byte only
* <code>-Wa0</code> = $A000
* <code>-Zxx</code> uses two bytes
* $80/$81 is tested and safe
* Avoid $F0–$FF (kernel use)
* <code>-Wxx</code> and <code>-Zxx</code> are configurable

---

== 5. Playing the Music ==

---

=== 5.1 Initialization ===

Call the init routine:

<code>
JSR $A000
</code>

---

=== 5.2 Per-Frame Playback ===

Call once per frame:

<code>
JSR $A003
</code>

---

== 6. Additional Notes ==

* <code>-N</code> controls speed
* <code>-Gxx</code> controls pitch
* Both are required
* The binary is C64-compatible
* Correct setup ensures compatibility

---

== Appendix: Minimal F256 SID Music Player Example ==

The following is a minimal working music player using kernel timers.

---

; ============================================================================
; music_min.asm - Minimal Music Player for Wildbits/K & /Jr
; ============================================================================

.cpu "65816"
MMU_IO_CTRL = $01
init_music = $A000
play_music = init_music+3
timer_cookie = $D0

*=$A0
.dsection zp
.cerror * > $AF, "Too many zero page variables"

.include "api.asm"

.section zp
event: .dstruct kernel.event.event_t
.send

*=$1000

start:
stz MMU_IO_CTRL

lda #<event
sta kernel.args.events
lda #>event
sta kernel.args.events+1

jsr init_music
jsr SetTimer

loop:
jsr handle_events
bra loop

handle_events:
lda kernel.args.events.pending
bpl done_handle_events
jsr kernel.NextEvent
bcs done_handle_events
jsr dispatch
jmp handle_events

done_handle_events:
rts

dispatch:
lda event.type
cmp #kernel.event.timer.EXPIRED
beq music_playback
rts

music_playback:
jsr SetTimer
jsr play_music
rts

SetTimer:
inc timer_cookie
lda timer_cookie
sta kernel.args.timer.absolute
sta kernel.args.timer.cookie
lda #kernel.args.timer.FRAMES
sta kernel.args.timer.units
jsr kernel.Clock.SetTimer
rts

*=$A000
.binary "testsong.bin"

---

== Cheat Sheet ==

=== Edit / Preview ===

<code>
goattracker -N -G424 song.sng
</code>

=== Pack for F256K ===

<code>
GT2RELOC song.sng song.bin -N -G454 -LD400 -Wa0 -Z80
</code>

=== Internal Pack ===

<code>
goattracker -G454 song.sng
</code>

Press <code>F9</code>

---

=== Playback ===

<code>
JSR $A000

JSR $A003
</code>

---

=== Tested Defaults ===

* SID: $D400
* Player: $A000
* Zeropage: $80/$81
* Timing: NTSC (60 Hz)

---

End of document.

Code Snippets

2025-08-09T08:21:40Z

Mcassera: /* Calculate SIN of an angle */

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

===== Poking and Peeking Memory in a different Bank =====
Contributed by Ernesto (econtreras in Discord)

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!.

<code>REM "XPEEK - value is stored in peekvalue variable" 
proc xpeek(addr) 
local block:block=addr\8192:local prevblock 
local offset:offset=addr&$1fff 
?0=179:prevblock=?$E:?$E=block:?1=4 
peekvalue=peek($C000+offset) 
?1=0:?$E=prevblock 
endproc 
 
REM "XPOKE" 
proc xpoke(addr,value) 
local block:block=addr\8192:local prevblock 
local offset:offset=addr&$1fff 
?0=179:prevblock=?$E:?$E=block:?1=4 
?($C000+offset)=value 
?1=0:?$E=prevblock 
endproc </code>

===== Print Text at X,Y Position =====
Contributed by Ernesto (econtreras in Discord)

Chances are that you need to print text at a specific position in the screen, SUPERBASIC doesn't have a LOCATE command, so the best next thing is to use this routine to print at a certain X,Y coordinate onscreen. Oh you are not not using an 80 column screen mode?, don't worry the routine will compensate automagically!

<code>proc printat(x,y,a$) 
col=(?$D001)&2:if col=0 then col=1 
local pos:pos=x+y*80\col:?1=2:rem "Set I/O to text memory" 
for c=0 to len(a$)-1:?(pos+c+$C000)=asc(mid$(a$,c+1,1)):next 
?1=0 
endproc</code>

===== Square Root =====
Contributed by Ernesto (econtreras in Discord)

You might need to calculate the square root of a number, it's very useful for a few algorithms, be aware that it will only work on numbers below 32768, square root is returned on the variable - ''guess#''

<code>REM "Newton's Method of Calculating Square Root" 
proc sqr(n) 
n#=n:guess#=n# 
while (0.001<abs(guess#*guess#-n#)) 
guess#=guess#+n/guess#)/2 
wend 
endproc</code>

===== Calculate SIN of an angle =====
Contributed by Raúl SQ

<code>50 input "Enter an angle in degrees (float): ";d#</code>

<code>100 sin(d#)</code>

<code>150 end</code>

<code>1200 proc sin(s#)</code>

<code>1250 deg_to_rad#=0.01745329</code>

<code>1260 s#=s#*deg_to_rad#</code>

<code>1300 x=6: rem "Factorial of 3"</code>

<code>1400 y=120: rem "Factorial of 5"</code>

<code>1500 z=5040: rem "Factorial of 7"</code>

<code>1600 pow2#=s#*s#:q#=pow2#*s#: rem "Power of 3"</code>

<code>1700 r#=q#*pow2#: rem "Power of 5"</code>

<code>1800 t#=r#*pow2#: rem "Power of 7"</code>

<code>1900 sine#=s#-(q#/x)+(r#/y)-(t#/z)</code>

<code>2000 print sine#</code>

<code>2100 endproc</code>

===== Loading and Launching another SUPERBASIC program =====
Contributed by Ernesto (econtreras in Discord)

Let's say that you want to do a menu or intro in a SUPERBASIC program and then after it plays out or you select something this program loads and executes another SUPERBASIC program!, sounds impossible?, no it's not, it's actually easy, we can use the functionality of SUPERBASIC that allows you to create your BASIC program (text file) on your PC and transfer it and execute it in your Foenix computer. (I bet you didn't know you could do that!). Use these two lines to load and execute your program, obviously this erases the current program from memory.

<code>
memcopy $28000,$8000 poke 0: rem "Clear transfer area for new program" 
a$="Program.bas":bload a$,$28000:xgo</code>

==== Renumbering a Program ====
Contributed by Mike (mcassera in Discord)

Here's a down and dirty basic routine you can use to renumber your program.

<code>
1000 rem "SuperBASIC renum routine" 
1010 a=$2000:b=1000:c=10 
1020 while peek(a)<>0 
1030 print peekw(a+1);" --> ";b 
1040 pokew a+1,b 
1050 b=b+c 
1060 a=a+peek(a) 
1070 wend 
</code><blockquote>'a' is the memory location of the basic line

'b' is the new line number

'c' is the interval between new line numbers</blockquote>

This little program just goes around and changes the word value that hold line numbers. This does not fix any GOTO or GOSUB statements, you'll have to update those on your own. (Use at your own risk).

==== Getting a Directory from BASIC ====
Contributed by Mike (mcassera in Discord)

I had written an ML program to work with BASIC to dump the directory into memory so I could then copy the filenames into an array. I've pulled it out here for a simple basic program you could use in your program. I've only extracted the names because at the time I didn't need file sizes. The basic program just prints the directory to the screen but you could modify it to place the names in an array

The machine language routine can be obtained from the following link:
https://github.com/mcassera/get_dir/blob/5bb017985793c89455746616493f092ef6a47045/get_dir.bin

The sample BASIC code is here:

<code>
10 bload "get_dir.bin",$7F00 
15 buffer=$7700:buffloc=$7FBB 
20 directory(buffer,0,"") 
30 for n=buffer to peekw(buffloc) 
40 cprint chr$(peek(n)); 
50 if peek(n)=0 then print 
60 next 
70 print 
80 end 
1000 proc directory(loc,len,path$) 
1010 buffloc=$7FBB 
1020 pathlength=$7FBD 
1030 pathloc=$7FBE 
1040 getdir=$7F00 
1050 pokew buffloc,loc 
1060 poke pathlength,len 
1070 for n=0 to len 
1080 poke pathloc+n,asc(mid$(path$,n+1,1)) 
1090 next 
1100 call getdir 
1120 endproc 
</code>

''Code Explanation''

* The basic program loads the binary and sets aside 2k of ram below BASIC rom for the directory buffer.
* Line 20 is where you call the directory routine. You send the buffer info (already set), the length of your path (if not reading the main directory) and the path.
* So if I was reading a directory called 'bitmaps' the command would change to : directory(buffer,7,"bitmaps")
* Lines 30 to 60 print the directory from memory. This is where you could read the data into an array. Files are separated with a zero byte hence line 50.
* The file names are stored in memory $7700 to $7eff. You can change the buffer location by changing the value of buffer in line 15, but 2k of ram will be cleared out after that address.
* The rest of the variables are (buffloc, pathlength,pathloc,getdir) are used by the ML routine and will break it if changed

__FORCETOC__

Code Snippets

2025-08-09T08:19:11Z

Mcassera:

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

===== Poking and Peeking Memory in a different Bank =====
Contributed by Ernesto (econtreras in Discord)

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!.

<code>REM "XPEEK - value is stored in peekvalue variable" 
proc xpeek(addr) 
local block:block=addr\8192:local prevblock 
local offset:offset=addr&$1fff 
?0=179:prevblock=?$E:?$E=block:?1=4 
peekvalue=peek($C000+offset) 
?1=0:?$E=prevblock 
endproc 
 
REM "XPOKE" 
proc xpoke(addr,value) 
local block:block=addr\8192:local prevblock 
local offset:offset=addr&$1fff 
?0=179:prevblock=?$E:?$E=block:?1=4 
?($C000+offset)=value 
?1=0:?$E=prevblock 
endproc </code>

===== Print Text at X,Y Position =====
Contributed by Ernesto (econtreras in Discord)

Chances are that you need to print text at a specific position in the screen, SUPERBASIC doesn't have a LOCATE command, so the best next thing is to use this routine to print at a certain X,Y coordinate onscreen. Oh you are not not using an 80 column screen mode?, don't worry the routine will compensate automagically!

<code>proc printat(x,y,a$) 
col=(?$D001)&2:if col=0 then col=1 
local pos:pos=x+y*80\col:?1=2:rem "Set I/O to text memory" 
for c=0 to len(a$)-1:?(pos+c+$C000)=asc(mid$(a$,c+1,1)):next 
?1=0 
endproc</code>

===== Square Root =====
Contributed by Ernesto (econtreras in Discord)

You might need to calculate the square root of a number, it's very useful for a few algorithms, be aware that it will only work on numbers below 32768, square root is returned on the variable - ''guess#''

<code>REM "Newton's Method of Calculating Square Root" 
proc sqr(n) 
n#=n:guess#=n# 
while (0.001<abs(guess#*guess#-n#)) 
guess#=guess#+n/guess#)/2 
wend 
endproc</code>

===== Calculate SIN of an angle =====
Contributed by Raúl SQ

<code>input "Enter an angle in degrees (float): ";d#</code>

<code>sin(d#)</code>

<code>end</code>

<code>proc sin(s#)</code>

<code>deg_to_rad#=0.01745329</code>

<code>s#=s#*deg_to_rad#</code>

<code>x=6: rem "Factorial of 3"</code>

<code>y=120: rem "Factorial of 5"</code>

<code>z=5040: rem "Factorial of 7"</code>

<code>pow2#=s#*s#:q#=pow2#*s#: rem "Power of 3"</code>

<code>r#=q#*pow2#: rem "Power of 5"</code>

<code>t#=r#*pow2#: rem "Power of 7"</code>

<code>sine#=s#-(q#/x)+(r#/y)-(t#/z)</code>

<code>print sine#</code>

<code>endproc</code>

===== Loading and Launching another SUPERBASIC program =====
Contributed by Ernesto (econtreras in Discord)

Let's say that you want to do a menu or intro in a SUPERBASIC program and then after it plays out or you select something this program loads and executes another SUPERBASIC program!, sounds impossible?, no it's not, it's actually easy, we can use the functionality of SUPERBASIC that allows you to create your BASIC program (text file) on your PC and transfer it and execute it in your Foenix computer. (I bet you didn't know you could do that!). Use these two lines to load and execute your program, obviously this erases the current program from memory.

<code>
memcopy $28000,$8000 poke 0: rem "Clear transfer area for new program" 
a$="Program.bas":bload a$,$28000:xgo</code>

==== Renumbering a Program ====
Contributed by Mike (mcassera in Discord)

Here's a down and dirty basic routine you can use to renumber your program.

<code>
1000 rem "SuperBASIC renum routine" 
1010 a=$2000:b=1000:c=10 
1020 while peek(a)<>0 
1030 print peekw(a+1);" --> ";b 
1040 pokew a+1,b 
1050 b=b+c 
1060 a=a+peek(a) 
1070 wend 
</code><blockquote>'a' is the memory location of the basic line

'b' is the new line number

'c' is the interval between new line numbers</blockquote>

This little program just goes around and changes the word value that hold line numbers. This does not fix any GOTO or GOSUB statements, you'll have to update those on your own. (Use at your own risk).

==== Getting a Directory from BASIC ====
Contributed by Mike (mcassera in Discord)

I had written an ML program to work with BASIC to dump the directory into memory so I could then copy the filenames into an array. I've pulled it out here for a simple basic program you could use in your program. I've only extracted the names because at the time I didn't need file sizes. The basic program just prints the directory to the screen but you could modify it to place the names in an array

The machine language routine can be obtained from the following link:
https://github.com/mcassera/get_dir/blob/5bb017985793c89455746616493f092ef6a47045/get_dir.bin

The sample BASIC code is here:

<code>
10 bload "get_dir.bin",$7F00 
15 buffer=$7700:buffloc=$7FBB 
20 directory(buffer,0,"") 
30 for n=buffer to peekw(buffloc) 
40 cprint chr$(peek(n)); 
50 if peek(n)=0 then print 
60 next 
70 print 
80 end 
1000 proc directory(loc,len,path$) 
1010 buffloc=$7FBB 
1020 pathlength=$7FBD 
1030 pathloc=$7FBE 
1040 getdir=$7F00 
1050 pokew buffloc,loc 
1060 poke pathlength,len 
1070 for n=0 to len 
1080 poke pathloc+n,asc(mid$(path$,n+1,1)) 
1090 next 
1100 call getdir 
1120 endproc 
</code>

''Code Explanation''

* The basic program loads the binary and sets aside 2k of ram below BASIC rom for the directory buffer.
* Line 20 is where you call the directory routine. You send the buffer info (already set), the length of your path (if not reading the main directory) and the path.
* So if I was reading a directory called 'bitmaps' the command would change to : directory(buffer,7,"bitmaps")
* Lines 30 to 60 print the directory from memory. This is where you could read the data into an array. Files are separated with a zero byte hence line 50.
* The file names are stored in memory $7700 to $7eff. You can change the buffer location by changing the value of buffer in line 15, but 2k of ram will be cleared out after that address.
* The rest of the variables are (buffloc, pathlength,pathloc,getdir) are used by the ML routine and will break it if changed

__FORCETOC__

Code Snippets

2025-08-09T08:14:17Z

Mcassera: Added Sin of an angle

SuperBASIC Memory Map

2025-01-12T04:01:56Z

Mcassera: /* Memory Map under BASIC */

=== 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 | Buffer area by Sound Command in BASIC (available if not using this command) || 470
|-
| $0400|| $041F|| Control Storage first 8 bytes control syntax highlighting || 32
|-
| $0420|| $0814|| Memory Storage || 1012
|-
|$0678
|$067F
|Keyboard Buffer (8 keys max)
|8
|-
|$0680
|$0680
|Pending key presses in Keyboard Buffer
|1
|-
|$07ea
|$07ea
|Y position of blinking cursor (***does not adjust the actual cursor position)
|1
|-
|$07eb
|$07eb
|X position of blinking cursor (***does not adjust the actual cursor position)
|1
|-
| $0814|| $0FFF|| Available Low Memory || 2027
|-
| $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 (or Available High Memory)|| 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 Expanded Memory (addresable only by CPU) || 256kb
|-
| $14:0000|| $1F:FFFF|| Future Expansions? || 768kb
|}

=== *Detail of Kernel Arguments in Zero Page (TBC!) ===
{| class="wikitable"
|+
!Initial Address
!End Address
!Description
!bytes
|-
|$F0
|$F1
|Kernel Event Struct Pointer - points to an 8 byte buffer with a "kernel event" structure
|2 bytes
|-
|$F3
|
|Kernel File stream number (Read or Write)
|1 byte
|-
|$F4
|
|Kernel File buffer length (Read or Write)
|1 byte
|-
|$F5
|$FA
|???
|6 bytes
|-
|$FB
|$FC
|Kernel Buffer Address Pointer - Multiple purpouse buffer area for recv/send data from Kernel Events
|2 bytes
|-
|$FD
|
|Kernel Buffer Length
|1 byte
|-
|$FE
|$FF
|Unknown
|2 bytes
|}

SuperBASIC Memory Map

2025-01-12T03:56:25Z

Mcassera: /* Memory Map under BASIC */ Added memory $7ea to $7eb for cursor location

=== 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 | Buffer area by Sound Command in BASIC (available if not using this command) || 470
|-
| $0400|| $041F|| Control Storage first 8 bytes control syntax highlighting || 32
|-
| $0420|| $0814|| Memory Storage || 1012
|-
|$0678
|$067F
|Keyboard Buffer (8 keys max)
|8
|-
|$0680
|$0680
|Pending key presses in Keyboard Buffer
|1
|-
|$07ea
|$07ea
|Y position of blinking cursor
|1
|-
|$07eb
|$07eb
|X position of blinking cursor
|1
|-
| $0814|| $0FFF|| Available Low Memory || 2027
|-
| $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 (or Available High Memory)|| 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 Expanded Memory (addresable only by CPU) || 256kb
|-
| $14:0000|| $1F:FFFF|| Future Expansions? || 768kb
|}

=== *Detail of Kernel Arguments in Zero Page (TBC!) ===
{| class="wikitable"
|+
!Initial Address
!End Address
!Description
!bytes
|-
|$F0
|$F1
|Kernel Event Struct Pointer - points to an 8 byte buffer with a "kernel event" structure
|2 bytes
|-
|$F3
|
|Kernel File stream number (Read or Write)
|1 byte
|-
|$F4
|
|Kernel File buffer length (Read or Write)
|1 byte
|-
|$F5
|$FA
|???
|6 bytes
|-
|$FB
|$FC
|Kernel Buffer Address Pointer - Multiple purpouse buffer area for recv/send data from Kernel Events
|2 bytes
|-
|$FD
|
|Kernel Buffer Length
|1 byte
|-
|$FE
|$FF
|Unknown
|2 bytes
|}

SuperBASIC

2024-11-27T02:29:09Z

Mcassera: /* Note */

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

2024-11-27T02:27:36Z

Mcassera: /* Note */

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]]
* 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
|}

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

2024-11-27T02:24:37Z

Mcassera: /* Note */

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]]
* 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
|}

==== '''Note''' ====
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 bitmap off command. In order to restore the background control character function you will need to make sure the MMU is set to zero by using POKE 1,0 and then setting the text mode again by using POKE $d000,1.

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

2024-11-27T02:24:08Z

Mcassera: /* Control characters for cursor and colour control */

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]]
* 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
|}

=== '''Note''' ===
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 bitmap off command. In order to restore the background control character function you will need to make sure the MMU is set to zero by using POKE 1,0 and then setting the text mode again by using POKE $d000,1.

===== 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 Memory Map

2024-09-22T22:29:03Z

Mcassera: /* Memory Map under BASIC */ Added Keyboard Buffer info @$678-$680

=== 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 | Buffer area by Sound Command in BASIC (available if not using this command) || 470
|-
| $0400|| $041F|| Control Storage first 8 bytes control syntax highlighting || 32
|-
| $0420|| $0814|| Memory Storage || 1012
|-
|$0678
|$067F
|Keyboard Buffer (8 keys max)
|8
|-
|$0680
|$0680
|Pending key presses in Keyboard Buffer
|1
|-
| $0814|| $0FFF|| Available Low Memory || 2027
|-
| $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 (or Available High Memory)|| 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 Expanded Memory (addresable only by CPU) || 256kb
|-
| $14:0000|| $1F:FFFF|| Future Expansions? || 768kb
|}

=== *Detail of Kernel Arguments in Zero Page (TBC!) ===
{| class="wikitable"
|+
!Initial Address
!End Address
!Description
!bytes
|-
|$F0
|$F1
|Kernel Event Struct Pointer - points to an 8 byte buffer with a "kernel event" structure
|2 bytes
|-
|$F3
|
|Kernel File stream number (Read or Write)
|1 byte
|-
|$F4
|
|Kernel File buffer length (Read or Write)
|1 byte
|-
|$F5
|$FA
|???
|6 bytes
|-
|$FB
|$FC
|Kernel Buffer Address Pointer - Multiple purpouse buffer area for recv/send data from Kernel Events
|2 bytes
|-
|$FD
|
|Kernel Buffer Length
|1 byte
|-
|$FE
|$FF
|Unknown
|2 bytes
|}

SuperBASIC

2024-08-22T00:23:37Z

Mcassera: /* Character Set */

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]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== 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$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|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
|}

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

SuperBASIC

2024-08-22T00:17:04Z

Mcassera: /* Character Set */

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]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== 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$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|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
|}

===== Character Set =====

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

SuperBASIC

2024-08-22T00:10:22Z

Mcassera: /* Character Set */

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]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== 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$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|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
|}

===== Character Set =====

* 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 low nibble is the background color and the high nibble is the character 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]

SuperBASIC

2024-08-22T00:08:51Z

Mcassera:

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]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== 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$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|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
|}

===== Character Set =====

* 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 low nibble is the background color and the high nibble is the character 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]

SuperBASIC

2024-08-22T00:04:06Z

Mcassera: Added Character set information

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]]
* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].

=== 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$(12)
|Clear screen and set cursor to upper left corner
|-
|chr$(16)
|Cursor up
|-
|chr$(14)
|Cursor down
|-
|chr$(2)
|Cursor left
|-
|chr$(6)
|Cursor right
|-
|chr$(1)
|Set cursor to leftmost position in current line
|-
|chr$(5)
|Set cursor to righmost position in current line
|-
|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
|}

===== Character Set =====

* 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 $C000 providing the MMU I/O control is set to 2 by executing a POKE 1,2 command first (remember to restore the MMU I/O once you're done).[[File:Full char set.png|left|thumb|104x104px|F256 Character Set]]

* Color can also be set on the screen color matrix using the POKE command starting at $C000 providing the MMU I?O control is set to 3 by executing a POKE 1,3 command first (remember to restore the MMU I/O once you're done).
* When poking colors on the screen, the high nibble is the background color and the low nibble is the character color.

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

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

File:Colormatrix.png

2024-08-22T00:01:19Z

Mcassera:

Color matrix of the default colors on the F256 computer

File:Full char set.png

2024-08-21T23:40:49Z

Mcassera:

F256 Character set

SuperBASIC

2024-08-21T23:39:28Z

Mcassera:

SuperBASIC

2024-08-21T19:49:32Z

Mcassera:

SuperBASIC

2024-08-21T19:44:37Z

Mcassera: Added memcopy lockup section

Tools & Scripts

2024-04-10T00:32:59Z

Mcassera:

== F256 Machines Game Development Tools ==

=== Sprite Creation Tools & Scripts ===

{| class="wikitable"
! Tool !! Link
! --- !! Notes
|-
| style="white-space:nowrap;"| Aseprite
| style="white-space:nowrap;"| https://www.aseprite.org/
|
| style="white-space:nowrap;" |Aseprite can be used to create sprites animation or Tiles Sets.
|-
|f256_sprite_cutter
|https://gist.github.com/digarok/57b096236a7fb1c76efef6cbb9f73a83
|
|Sprite cutter that cuts a PNG according to line-by-line instructions in a text file. Requires python and the PIL library, install with:
python -m pip install --upgrade pip

python -m pip install --upgrade Pillow
Run with:
python f256_sprite_cutter.py myimage.png mylist.txt sprites.s
where mylist.txt contains a series of lines containing x, y offset, width, name, where it's assumed the width is the same as the height since it's for square sprites supported for the F256xx, such as 8,16, or 32.

The output (named sprites.s in this above example) is a series of hex instructions with a list of hex values of a color picked from the CLUT.

In order to make it compatible with 64tass, I search replaced hex-> .byte and replaced every value I could find by swapping in a $ in front (ie 00 -> $00 and 01 -> $01, etc.)
|}

==== Scripts ====

=== Sprite & Tile Creation Tools & Scripts ===
If you use Aseprite, you can convert your tile drawings to tilesets and tilemaps using the following scripts:

* [[Export Aseprite Tilemap]]
* [[Export Aseprite Tileset]]
* [[Export Aseprite Sprites]] - Will convert sprites to 64tass compatible text file.

Tools & Scripts

2024-04-10T00:29:58Z

Mcassera:

Tools & Scripts

2024-04-10T00:27:37Z

Mcassera:

Export Aseprite Sprites

2024-04-10T00:19:21Z

Mcassera:

====== '''This LUA script file needs to be placed in Aseprite's "scripts" folder.''' ======
-- export_sprite_256.lua

<nowiki>local sprite = app.sprite

-- Check constraints
if sprite == nil then
app.alert("No Sprite...")
return
end
if sprite.colorMode ~= ColorMode.INDEXED then
app.alert("Sprite needs to be indexed")
return
end

local function getPaletteData(palette)
local ncolors = #palette
local res = string.format(";%i\n", ncolors)

for i=0, ncolors-1 do
local color = palette:getColor(i)
res = res .. " .byte " .. string.format("$%x,$%x,$%x,$%x\n", color.blue, color.green, color.red, color.alpha)
end

return res
end

local function getIndexData(img, x, y, w, h)
local res = ""
for y = 0,h-1 do
res = res .. " .byte "
for x = 0, w-1 do
if x > 0 then
res = res ..","
end
px = img:getPixel(x, y)
res = res .. string.format("$%x", px)
end
res = res .. "\n"
end

return res
end

local function exportFrame(frm,sFlag)
if frm == nil then
frm = 1
end

local img = Image(sprite.spec)
img:drawSprite(sprite, frm)

if frm == 1 or frm == nil or sFlag == 1 then
io.write(";Palette Indexed Picture\n")
io.write("CLUT:\n")
io.write(";begin palette\n")
io.write(getPaletteData(sprite.palettes[1]))
io.write(";end palette\n\n")
end
io.write("sprite")
io.write(frm)
io.write(":\n")
io.write(";begin Sprite\n")
io.write(getIndexData(img, x, y, sprite.width, sprite.height))
io.write(";end Sprite\n\n")
end

local dlg = Dialog()
dlg:file{ id = "exportFile",
label = "File",
open = false,
save = true,
--filename= p .. fn .. "pip",
filetypes = {"txt", "pip" }}
dlg:check{ id="onlyCurrentFrame",
text="Export only current frame",
selected=false }
dlg:modify{ title = "F256 Export Sprite" }
dlg:button{ id="ok", text="OK" }
dlg:button{ id="cancel", text="Cancel" }
dlg:show()
local data = dlg.data
if data.ok then
local f = io.open(data.exportFile, "w")
io.output(f)

if data.onlyCurrentFrame then
exportFrame(app.frame.frameNumber,1)
else
for i = 1,#sprite.frames do
exportFrame(i,0)
end
end

io.close(f)
end</nowiki>

Export Aseprite Sprites

2024-04-10T00:16:41Z

Mcassera:

====== '''This LUA script file needs to be placed in Aseprite's "scripts" folder.''' ======
<nowiki>local sprite = app.sprite

-- Check constraints
if sprite == nil then
app.alert("No Sprite...")
return
end
if sprite.colorMode ~= ColorMode.INDEXED then
app.alert("Sprite needs to be indexed")
return
end

local function getPaletteData(palette)
local ncolors = #palette
local res = string.format(";%i\n", ncolors)

for i=0, ncolors-1 do
local color = palette:getColor(i)
res = res .. " .byte " .. string.format("$%x,$%x,$%x,$%x\n", color.blue, color.green, color.red, color.alpha)
end

return res
end

local function getIndexData(img, x, y, w, h)
local res = ""
for y = 0,h-1 do
res = res .. " .byte "
for x = 0, w-1 do
if x > 0 then
res = res ..","
end
px = img:getPixel(x, y)
res = res .. string.format("$%x", px)
end
res = res .. "\n"
end

return res
end

local function exportFrame(frm,sFlag)
if frm == nil then
frm = 1
end

local img = Image(sprite.spec)
img:drawSprite(sprite, frm)

if frm == 1 or frm == nil or sFlag == 1 then
io.write(";Palette Indexed Picture\n")
io.write("CLUT:\n")
io.write(";begin palette\n")
io.write(getPaletteData(sprite.palettes[1]))
io.write(";end palette\n\n")
end
io.write("sprite")
io.write(frm)
io.write(":\n")
io.write(";begin Sprite\n")
io.write(getIndexData(img, x, y, sprite.width, sprite.height))
io.write(";end Sprite\n\n")
end

local dlg = Dialog()
dlg:file{ id = "exportFile",
label = "File",
open = false,
save = true,
--filename= p .. fn .. "pip",
filetypes = {"txt", "pip" }}
dlg:check{ id="onlyCurrentFrame",
text="Export only current frame",
selected=false }
dlg:modify{ title = "F256 Export Sprite" }
dlg:button{ id="ok", text="OK" }
dlg:button{ id="cancel", text="Cancel" }
dlg:show()
local data = dlg.data
if data.ok then
local f = io.open(data.exportFile, "w")
io.output(f)

if data.onlyCurrentFrame then
exportFrame(app.frame.frameNumber,1)
else
for i = 1,#sprite.frames do
exportFrame(i,0)
end
end

io.close(f)
end</nowiki>

Export Aseprite Sprites

2024-04-10T00:15:04Z

Mcassera: The Aseprite export script.

<nowiki>local sprite = app.sprite

-- Check constraints
if sprite == nil then
app.alert("No Sprite...")
return
end
if sprite.colorMode ~= ColorMode.INDEXED then
app.alert("Sprite needs to be indexed")
return
end

local function getPaletteData(palette)
local ncolors = #palette
local res = string.format(";%i\n", ncolors)

for i=0, ncolors-1 do
local color = palette:getColor(i)
res = res .. " .byte " .. string.format("$%x,$%x,$%x,$%x\n", color.blue, color.green, color.red, color.alpha)
end

return res
end

local function getIndexData(img, x, y, w, h)
local res = ""
for y = 0,h-1 do
res = res .. " .byte "
for x = 0, w-1 do
if x > 0 then
res = res ..","
end
px = img:getPixel(x, y)
res = res .. string.format("$%x", px)
end
res = res .. "\n"
end

return res
end

local function exportFrame(frm,sFlag)
if frm == nil then
frm = 1
end

local img = Image(sprite.spec)
img:drawSprite(sprite, frm)

if frm == 1 or frm == nil or sFlag == 1 then
io.write(";Palette Indexed Picture\n")
io.write("CLUT:\n")
io.write(";begin palette\n")
io.write(getPaletteData(sprite.palettes[1]))
io.write(";end palette\n\n")
end
io.write("sprite")
io.write(frm)
io.write(":\n")
io.write(";begin Sprite\n")
io.write(getIndexData(img, x, y, sprite.width, sprite.height))
io.write(";end Sprite\n\n")
end

local dlg = Dialog()
dlg:file{ id = "exportFile",
label = "File",
open = false,
save = true,
--filename= p .. fn .. "pip",
filetypes = {"txt", "pip" }}
dlg:check{ id="onlyCurrentFrame",
text="Export only current frame",
selected=false }
dlg:modify{ title = "F256 Export Sprite" }
dlg:button{ id="ok", text="OK" }
dlg:button{ id="cancel", text="Cancel" }
dlg:show()
local data = dlg.data
if data.ok then
local f = io.open(data.exportFile, "w")
io.output(f)

if data.onlyCurrentFrame then
exportFrame(app.frame.frameNumber,1)
else
for i = 1,#sprite.frames do
exportFrame(i,0)
end
end

io.close(f)
end</nowiki>

Tools & Scripts

2024-04-09T23:50:14Z

Mcassera: Added a link to the Aseprite export sprites script

== F256 Machines Game Development Tools ==

=== Sprite Creation Tools & Scripts ===

{| class="wikitable"
! Tool !! Link
! --- !! Notes
|-
| style="white-space:nowrap;"| Aseprite
| style="white-space:nowrap;"| https://www.aseprite.org/
|
| style="white-space:nowrap;" |Aseprite can be used to create sprites animation or Tiles Sets.
|-
|f256_sprite_cutter
|https://gist.github.com/digarok/57b096236a7fb1c76efef6cbb9f73a83
|
|Sprite cutter that cuts a PNG according to line-by-line instructions in a text file. Requires python and the PIL library, install with:
python -m pip install --upgrade pip

python -m pip install --upgrade Pillow
Run with:
python f256_sprite_cutter.py myimage.png mylist.txt sprites.s
where mylist.txt contains a series of lines containing x, y offset, width, name, where it's assumed the width is the same as the height since it's for square sprites supported for the F256xx, such as 8,16, or 32.

The output (named sprites.s in this above example) is a series of hex instructions with a list of hex values of a color picked from the CLUT.

In order to make it compatible with 64tass, I search replaced hex-> .byte and replaced every value I could find by swapping in a $ in front (ie 00 -> $00 and 01 -> $01, etc.)
|}

==== Scripts ====

=== Tile Creation Tools & Scripts ===
If you use Aseprite, you can convert your tile drawings to tilesets and tilemaps using the following scripts:

* [[Export Aseprite Tilemap]]
* [[Export Aseprite Tileset]]
* [[Export Aseprite Sprites]]

Getting Started

2024-02-11T18:19:51Z

Mcassera: /* SD Card */ Added note to Linux bullet

== 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**.
* Formatting with Windows 10/11 works fine, but make sure to force FAT32 (or use the command line: <code>format /FS:FAT32 H:</code>)
* Formatting with MacOS will only work using the <code>diskutil</code> command line utility. An example usage looks like this: <code>sudo diskutil eraseDisk FAT32 [DiskName] MBRFormat /dev/[DiskNumber]</code>. You can use <code>diskutil list</code> to get the disk number for the SD Card.
* Formatting and partitioning SD cards with Linux can be done using the <code>gnome-disk-utility</code> (known simply as Disks) and is installed on most mainstream distributions of Linux. Disks will access all the drives on the computer so be sure you have the SD card selected when editing. [https://wiki.gnome.org/Apps/Disks Gnome/Disks wiki]
* FAT32 only supports a maximum partition size of 32Gb, on larger cards you will need to create multiple partitions -- however, only the first is recognized by DOS.
* 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]
|}

=== Running PGZ Files ===

<pre>
/- "file.pgz"
</pre>
=== 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.

Getting Started

2024-02-11T18:13:34Z

Mcassera: /* SD Card */ - Added Linux utility that will partition and format SD cards.

== 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**.
* Formatting with Windows 10/11 works fine, but make sure to force FAT32 (or use the command line: <code>format /FS:FAT32 H:</code>)
* Formatting with MacOS will only work using the <code>diskutil</code> command line utility. An example usage looks like this: <code>sudo diskutil eraseDisk FAT32 [DiskName] MBRFormat /dev/[DiskNumber]</code>. You can use <code>diskutil list</code> to get the disk number for the SD Card.
* Formatting and partitioning SD cards with Linux can be done using the <code>gnome-disk-utility</code> (known simply as Disks) and is installed on most mainstream distributions of Linux. [https://wiki.gnome.org/Apps/Disks Gnome/Disks wiki]
* FAT32 only supports a maximum partition size of 32Gb, on larger cards you will need to create multiple partitions -- however, only the first is recognized by DOS.
* 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]
|}

=== Running PGZ Files ===

<pre>
/- "file.pgz"
</pre>
=== 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.