From b6488dcdeea1d6da1a1099300db8a92e99a11b77 Mon Sep 17 00:00:00 2001 From: Scott Duensing Date: Wed, 19 Jun 2024 19:50:09 -0500 Subject: [PATCH] Fixed a few errors in the manual. --- distro/f256lib.adoc | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/distro/f256lib.adoc b/distro/f256lib.adoc index 6c0e9cc..892c3f3 100644 --- a/distro/f256lib.adoc +++ b/distro/f256lib.adoc @@ -313,7 +313,7 @@ would be longer than anyone cares to read. For the ugly details, please see the following: * `f256dev\f256lib\f_api.h` contains kernel information. -* `f256dev\include` is full of header files containing handy contants. +* `f256dev\include` is full of header files containing handy constants. === Types @@ -1147,11 +1147,11 @@ Currently not supported by IEC drives. NOTE: Not all IEC devices support subdirectories. -NOTE: Pathnames on the F256 use the backslash (`\`) to delimit +NOTE: Pathnames on the F256 use the forward slash (`/`) to delimit subdirectories. Similar to Windows, the F256 uses the concept of a "drive". Unlike Windows, drives are numbered, not lettered, and start at `0` which is the built-in SD card reader. An example path with a drive and subdirectory -looks like this: `0:\DOCS\README.TXT` +looks like this: `0:/DOCS/README.TXT` IMPORTANT: Do not mix kernel access with file I/O. Using file I/O inside a kernel event loop will cause the loop to miss events! @@ -1264,6 +1264,12 @@ memory code. It always starts at `0x10000` and increments the address `0x2000` for each additional segment. When using overlays, be careful to not overwrite this memory with other data! +NOTE: Segment names can be anything you like. `SEGMENT_MAIN` is predefined and +refers to the near 64k accessable by the CPU. + +NOTE: The `SEGMENT_` defines are per-C file. Placing one into a header file that +is included into a C file will have no effect. Each C file starts in `SEGMENT_MAIN`. + NOTE: At the moment, you can only move code into far memory, not variables.