deac/osd-contiki
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
osd-contiki/cpu/6502/README.md

101 lines
3.3 KiB
Markdown
Raw Normal View History

Update to markdown - Spellchecking - Update plain text to github markdown
2013-03-26 13:09:49 +01:00
6502
====
The cpu/6502/ directory is used for targeting 6502-based machines using the
Updated cc65 URL.
2014-03-15 16:55:39 +01:00
cc65 compiler [http://cc65.github.io/cc65/](http://cc65.github.io/cc65/).
Update to markdown - Spellchecking - Update plain text to github markdown
2013-03-26 13:09:49 +01:00
The Contiki network configuration for 6502-based targets is loaded from a
binary configuration file (by default named contiki.cfg). It has the following
Added SLIP support to retro platforms. The cc65 tool chain comes with V.24 drivers so it seems reasonable to use the existing Contiki SLIP driver to implement network access via SLIP as alternative to Ethernet. Some notes: - The Ethernet configuration was simplified in order to allow share it with SLIP. - The Contiki SLIP driver presumes an interrupt driven serial receiver to write into the SLIP buffer. However the cc65 V.24 drivers aren't up to that. Therefore the main loops were extended to pull received data from the V.24 buffers and push it into the SLIP buffer. - As far as I understand the serial sender is supposed to block until the data is sent. Therefore a loop calls the non-blocking V.24 driver until the data is sent. On all platforms there's only one V.24 driver available. Therefore V.24 drivers are always loaded statically. On the Apple][ the mouse driver is now loaded statically - independently from SLIP vs. Ethernet. After all there's only one mouse driver available. However there's a major benefit with SLIP: Here all drivers are loaded statically. Therefore the dynamic module loader isn't necessary at all. And without the loader the heap manager isn't necessary at all. This allows for a reduction in code size roughly compensating for the size of the SLIP buffer.
2017-02-15 23:43:28 +01:00
format for Ethernet:
Update to markdown - Spellchecking - Update plain text to github markdown
2013-03-26 13:09:49 +01:00
- Bytes 1 - 4: IP Address (HiByte first)
- Bytes 5 - 8: Subnet Mask (HiByte first)
- Bytes 9 - 12: Default Router (HiByte first)
- Bytes 13 - 16: DNS Server (HiByte first)
- Bytes 17 - 18: Ethernet card I/O address (LoByte first !)
- Bytes 19 - xx: Ethernet card driver name (ASCII / PETSCII)
Added SLIP support to retro platforms. The cc65 tool chain comes with V.24 drivers so it seems reasonable to use the existing Contiki SLIP driver to implement network access via SLIP as alternative to Ethernet. Some notes: - The Ethernet configuration was simplified in order to allow share it with SLIP. - The Contiki SLIP driver presumes an interrupt driven serial receiver to write into the SLIP buffer. However the cc65 V.24 drivers aren't up to that. Therefore the main loops were extended to pull received data from the V.24 buffers and push it into the SLIP buffer. - As far as I understand the serial sender is supposed to block until the data is sent. Therefore a loop calls the non-blocking V.24 driver until the data is sent. On all platforms there's only one V.24 driver available. Therefore V.24 drivers are always loaded statically. On the Apple][ the mouse driver is now loaded statically - independently from SLIP vs. Ethernet. After all there's only one mouse driver available. However there's a major benefit with SLIP: Here all drivers are loaded statically. Therefore the dynamic module loader isn't necessary at all. And without the loader the heap manager isn't necessary at all. This allows for a reduction in code size roughly compensating for the size of the SLIP buffer.
2017-02-15 23:43:28 +01:00
It has the following format for SLIP (based on RS232 driver coming with cc65):
Update to markdown - Spellchecking - Update plain text to github markdown
2013-03-26 13:09:49 +01:00
Added SLIP support to retro platforms. The cc65 tool chain comes with V.24 drivers so it seems reasonable to use the existing Contiki SLIP driver to implement network access via SLIP as alternative to Ethernet. Some notes: - The Ethernet configuration was simplified in order to allow share it with SLIP. - The Contiki SLIP driver presumes an interrupt driven serial receiver to write into the SLIP buffer. However the cc65 V.24 drivers aren't up to that. Therefore the main loops were extended to pull received data from the V.24 buffers and push it into the SLIP buffer. - As far as I understand the serial sender is supposed to block until the data is sent. Therefore a loop calls the non-blocking V.24 driver until the data is sent. On all platforms there's only one V.24 driver available. Therefore V.24 drivers are always loaded statically. On the Apple][ the mouse driver is now loaded statically - independently from SLIP vs. Ethernet. After all there's only one mouse driver available. However there's a major benefit with SLIP: Here all drivers are loaded statically. Therefore the dynamic module loader isn't necessary at all. And without the loader the heap manager isn't necessary at all. This allows for a reduction in code size roughly compensating for the size of the SLIP buffer.
2017-02-15 23:43:28 +01:00
- Bytes 1 - 4: IP Address (HiByte first)
- Bytes 5 - 8: Subnet Mask (HiByte first)
- Bytes 9 - 12: Default Router (HiByte first)
- Bytes 13 - 16: DNS Server (HiByte first)
- Bytes 17 - 21: struct ser_params (see cc65 serial.h)
Update to markdown - Spellchecking - Update plain text to github markdown
2013-03-26 13:09:49 +01:00
The build for 6502-based machines includes the 'disk' make goal which creates a
bootable floppy disk image containing the project binary, a sample
configuration file and the Ethernet card drivers.
The build for 6502-based machines supports so-called high-level configuration
macros which allow to customize Contiki on a per-project basis. They are set in
form of a comma-separated list as value of the make variable DEFINES on the
make command line. The value of DEFINES can be saved with the 'savedefines'
make goal. The values of the high-level configuration macros are not tracked by
the build so a manual rebuild is necessary on any change. The following
high-level configuration macros may be set:
Added SLIP support to retro platforms. The cc65 tool chain comes with V.24 drivers so it seems reasonable to use the existing Contiki SLIP driver to implement network access via SLIP as alternative to Ethernet. Some notes: - The Ethernet configuration was simplified in order to allow share it with SLIP. - The Contiki SLIP driver presumes an interrupt driven serial receiver to write into the SLIP buffer. However the cc65 V.24 drivers aren't up to that. Therefore the main loops were extended to pull received data from the V.24 buffers and push it into the SLIP buffer. - As far as I understand the serial sender is supposed to block until the data is sent. Therefore a loop calls the non-blocking V.24 driver until the data is sent. On all platforms there's only one V.24 driver available. Therefore V.24 drivers are always loaded statically. On the Apple][ the mouse driver is now loaded statically - independently from SLIP vs. Ethernet. After all there's only one mouse driver available. However there's a major benefit with SLIP: Here all drivers are loaded statically. Therefore the dynamic module loader isn't necessary at all. And without the loader the heap manager isn't necessary at all. This allows for a reduction in code size roughly compensating for the size of the SLIP buffer.
2017-02-15 23:43:28 +01:00
- WITH_SLIP
- Default: 0
- Purpose: Use SLIP (based on RS232 driver coming with cc65) instead of
Ethernet.
Update to markdown - Spellchecking - Update plain text to github markdown
2013-03-26 13:09:49 +01:00
- MTU_SIZE
- Default: 1500
- Purpose: Set the Maximum Transfer Unit size.
- CONNECTIONS
Reduced default for number of connections. Save some memory by reducing the the default for number of connections from 10 to 2.
2015-06-21 17:53:19 +02:00
- Default: 2
Update to markdown - Spellchecking - Update plain text to github markdown
2013-03-26 13:09:49 +01:00
- Purpose: Set the maximum number of concurrent TCP connections.
Revert to static Ethernet driver for the ATARI. After all there's no momentum for a W5100-based Ethernet solution on the ATARI. So I revert to static linkage of the CS8900A driver as this improves program load times.
2017-01-27 00:18:25 +01:00
- STATIC_DRIVER
Build static Ethernet drivers directly from source.
2014-06-09 23:14:11 +02:00
- Default: N/A
Revert to static Ethernet driver for the ATARI. After all there's no momentum for a W5100-based Ethernet solution on the ATARI. So I revert to static linkage of the CS8900A driver as this improves program load times.
2017-01-27 00:18:25 +01:00
- Purpose: Link device driver statically instead of loading it dynamically
Build static Ethernet drivers directly from source.
2014-06-09 23:14:11 +02:00
using the network configuration file.
Update to markdown - Spellchecking - Update plain text to github markdown
2013-03-26 13:09:49 +01:00
- WITH_LOGGING
- Default: 0
- Purpose: Have log_message() and UIP_LOG() write messages to the screen.
- WITH_BOOST
- Default: 0
- Purpose: Significantly improve troughput on sending full sized packets by
splitting them thus workarounding the "delayed acknowledge".
- WITH_FORWARDING
- Default: 0
- Purpose: Enable support for the 'IP forwarding' packet driver.
- WITH_CLIENT
- Default: 0
- Purpose: Enable support for outgoing TCP connections.
- WITH_DNS
- Default: 0
- Purpose: Enable UDP support and initialize resolver process on startup.
Made 80 column display a cc65 application attribute. So far 80 column display was an attribute of a cc65 platform. Now each cc65 application can ask for 80 column display by defining WITH_80COL. Of course this is ignored by platforms incapable of 80 column display. I see three types of application: * Applications not benefitting from 80 column at all and in fact looking better with 40 column display. These are now using 40 column display. Examples: ethconfig, ipconfig * Applications taking advantage of 80 column display if it is available without drawbacks. These stay as they were. Examples: Telnet server, web server, wget * Applications needing 80 column display so urgently that it is likely desirable even if the display becomes harder to read. These come now in both flavors allowing the user to choose. Examples: IRC, web browser Note: This change doesn't actually introduce any 80 column display with drawbacks. This if left to a subsequent change.
2015-10-30 12:42:58 +01:00
- WITH_80COL
- Default: 0
- Purpose: Enable 80 column screen.
Update to markdown - Spellchecking - Update plain text to github markdown
2013-03-26 13:09:49 +01:00
- WITH_GUI
- Default: 0
Made 80 column display a cc65 application attribute. So far 80 column display was an attribute of a cc65 platform. Now each cc65 application can ask for 80 column display by defining WITH_80COL. Of course this is ignored by platforms incapable of 80 column display. I see three types of application: * Applications not benefitting from 80 column at all and in fact looking better with 40 column display. These are now using 40 column display. Examples: ethconfig, ipconfig * Applications taking advantage of 80 column display if it is available without drawbacks. These stay as they were. Examples: Telnet server, web server, wget * Applications needing 80 column display so urgently that it is likely desirable even if the display becomes harder to read. These come now in both flavors allowing the user to choose. Examples: IRC, web browser Note: This change doesn't actually introduce any 80 column display with drawbacks. This if left to a subsequent change.
2015-10-30 12:42:58 +01:00
- Purpose: Initialize the CTK process on startup.
Update to markdown - Spellchecking - Update plain text to github markdown
2013-03-26 13:09:49 +01:00
- WITH_MOUSE
- Default: 0
- Purpose: Enable CTK mouse support and load a mouse driver.
Added SLIP support to retro platforms. The cc65 tool chain comes with V.24 drivers so it seems reasonable to use the existing Contiki SLIP driver to implement network access via SLIP as alternative to Ethernet. Some notes: - The Ethernet configuration was simplified in order to allow share it with SLIP. - The Contiki SLIP driver presumes an interrupt driven serial receiver to write into the SLIP buffer. However the cc65 V.24 drivers aren't up to that. Therefore the main loops were extended to pull received data from the V.24 buffers and push it into the SLIP buffer. - As far as I understand the serial sender is supposed to block until the data is sent. Therefore a loop calls the non-blocking V.24 driver until the data is sent. On all platforms there's only one V.24 driver available. Therefore V.24 drivers are always loaded statically. On the Apple][ the mouse driver is now loaded statically - independently from SLIP vs. Ethernet. After all there's only one mouse driver available. However there's a major benefit with SLIP: Here all drivers are loaded statically. Therefore the dynamic module loader isn't necessary at all. And without the loader the heap manager isn't necessary at all. This allows for a reduction in code size roughly compensating for the size of the SLIP buffer.
2017-02-15 23:43:28 +01:00
- STATIC_MOUSE
- Default: N/A
- Purpose: Link mouse driver statically instead of loading it dynamically.
Copied 'contiki_arg[c|v]' from 'native' to the other desktop targets. - On the retro targets support for 'contiki_arg[c|v]' is optional as accesing arg[c|v] is rather expensive.
2014-01-24 11:56:40 +01:00
- WITH_ARGS
- Default: 0
- Purpose: Enable support for contiki_argc / contiki_argv.
Update to markdown - Spellchecking - Update plain text to github markdown
2013-03-26 13:09:49 +01:00
- WITH_PFS
- Default: 0
- Purpose: Implement the CFS interface with a Platform-specific File System
instead of the POSIX file system.
Reference in a new issue Copy permalink