osd-contiki/platform/apple2enh
2010-09-08 22:50:56 +00:00
..
lib Adjusted assembler to reference uip_aligned_buf instead of uip_buf. 2010-07-20 20:42:25 +00:00
sys Added clock_seconds() implementation. 2008-07-12 14:44:37 +00:00
contiki-conf.h Configure maximum number of Apple2 web server connections indirectly via maximum number of TCP connections. 2010-04-11 21:23:45 +00:00
contiki-main.c Up to now *all* Contiki apps for the Apple2 were built for maximal RAM - which means that they can't return to OS level but must reboot on exit. However many apps can get along well with 1kB less memory - which allows them to exit to the OS. 2010-09-08 22:50:56 +00:00
Makefile.apple2enh Up to now *all* Contiki apps for the Apple2 were built for maximal RAM - which means that they can't return to OS level but must reboot on exit. However many apps can get along well with 1kB less memory - which allows them to exit to the OS. 2010-09-08 22:50:56 +00:00
README Added some info on the Apple2 PFS (and AppleCommander). 2008-06-12 22:45:17 +00:00

The platform/apple2enh/ directory is used for targeting an Enhanced Apple //e
(or compatible) computer. Most things are shared between the 6502-based targets
so please consult cpu/6502/README for further details.


The following Apple II Ethernet cards are supported:

- Uther:   Use driver cs8900a.eth  with the address $C0x0 (x = 8 + slot number).
- LANceGS: Use driver lan91c96.eth with the address $C0x0 (x = 8 + slot number).


In most cases it is desirable to use an emulator for the development and testing
of a Contiki application. AppleWin is especially well suited as it emulates the
Uther Ethernet card in slot 3. It is available at http://applewin.berlios.de/.


The 'disk' make goal requires AppleCommander 1.3.5 or later. It is available at
http://applecommander.sourceforge.net/.


The apple2enh target supports a PFS that requires much less RAM than the POSIX
file system. However this benefit comes with the following restrictions:

- Only one file may be open at the same time.
- Only read operations are supported but no write operations.
- The files must be located in the same directory the application is located in
  (the ProDOS prefix may very well point to another directory).
- The network MTU size must be set at least to 1265 (the default is 1500).
- No network function may be called while a file is open.