It's a LocalTalk interface, contained entirely within a single Microchip PIC12F1840 (8 pins, ~$1.50) microcontroller.
It handles all the time-sensitive aspects of LocalTalk, bidirectionally bitbanging the SDLC and FM0 (a.k.a. differential Manchester) based protocol at the data link and physical layers, sending and responding to control frames with CRC calculation and checking, and collision avoidance and retransmission. It can also respond to any number/combination of node IDs for use in bridging applications. It can be interfaced directly to user-mode software on a Raspberry Pi or BeagleBone or full PC, or it can be part of a larger embedded system. It slices, it dices, etc.
Stable and fairly battle-tested.
Because of the PIC12F1840's limited memory and the way its UART is used, the host's UART needs to be able to handle a baud rate of 1 Mbps. Conventional UARTs don't expect to be pushed beyond 115.2 kbps. In addition, the PIC has a 128-byte receiver queue, which is considerably smaller than the largest possible LocalTalk frame (605 bytes). As such, the host needs to respect when the CTS hardware flow control line is deasserted so the queue doesn't overflow and be quick about resuming transmission when CTS is reasserted so the queue doesn't underflow either.
Also, "single-chip" doesn't include the separate and necessary driver/receiver chip for RS-422/485. Sorry. =)
Building the firmware requires Microchip MPASM, which is included with their development environment, MPLAB. Note that you must use MPLAB X version 5.35 or earlier or MPLAB 8 as later versions of MPLAB X have removed MPASM.
- AirTalk by cheesestraws
- Plug-and-play WiFi-LocalTalk dongle
- Buy from airtalk.shop
- TashTalkHat by bdurbrow
- Raspberry Pi hat using v1.x firmware
- Pending release
- Forum post
- TashTalk 2 Hat by Tashtari
- Raspberry Pi hat using v2.x firmware
- Files
- See latest release in this repository for gerbers
- Buy fully assembled or as kit with regular or stackable header from Tashtari
- USB2LT by twelvetone12
- USB serial adapter using v2.x firmware
- Pending release
- Forum thread
- tashtalkd by Tashtari
- Simple LocalTalk (via TashTalk) to LToUDP bridge
- Files
- MultiTalk by sfiera
- Bridge between EtherTalk and LocalTalk (via LToUDP and TashTalk)
- Project page
- TashRouter by Tashtari
- Full-fledged AppleTalk router supporting EtherTalk and LocalTalk (via LToUDP and TashTalk)
- Project page
- PicoATP by Tashtari
- Tiny AppleTalk stack for PIC12F1840 and other 8-bit mid-range core PICs
- Project page
File a PR or an issue to add to these lists!
AirTalk users: do not upgrade your TashTalk PIC to v2.x, it will stop working because of the change in pinout. See the Compatibility Fix section below if you are having issues with Power Macintosh 6100 computers or certain LocalTalk printers.
| Version | Pinout | CRC Calculation |
|---|---|---|
| v1.0 | RA3 input, RA5 output | Self-generated frames only |
| v2.0 | RA3 !MCLR, RA5 input/output | Self-generated frames only |
| v2.1 | RA3 !MCLR, RA5 input/output | Self-generated frames, optionally all frames |
This change was made in order to enable applications where it is desirable to disable LocalTalk and allow other circuitry to use the RS-422 driver - pulling RA3/!MCLR low will hold the PIC in reset, tristating its outputs. Using RS-422 interface ICs such as the SN65HVD series, RA5 can be connected to both the receiver output and the driver input while RA4/Driver Enable is connected to both the (active low) receiver enable and the (active high) driver enable.
As of the time of this writing, the base UART protocol is unchanged between all available versions. v2.1 adds the "Set Features" command, but this can be ignored and is not used by tashtalkd.
v2.1 adds optional calculation and checking of the frame CRC. As of the time of this writing, this is known to be used only by PicoATP.
v2.1.3 adds a fix for compatibility with the Power Macintosh 6100 and certain LocalTalk printers (possibly other devices as well). This fix has also been backported to v1.x in v1.0.1 for AirTalk users and other users of devices based around the v1.x pinout. See the release notes for details.
