Public_Skunkworks/f256
Public_Skunkworks/f256
1
0
Fork 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

Fixed a few errors in the manual.

Browse source
This commit is contained in:
Scott Duensing 2024-06-19 19:50:09 -05:00
parent de881b1b3e
commit b6488dcdee
1 changed files with 9 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
distro/f256lib.adoc
View file

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