Releases · lampmerchant/tashtalk

10 Jan 14:28

v2.1.3

0e15b7d

v2.1.3 Latest

Latest

After TashTalk sends an RTS frame, require that external line activity contain a flag in order for a collision to be detected. Previously, any activity on the line would be detected as a collision, including the sync pulse sent by some Macs including the Power Macintosh 6100; this was preventing CTS frames from such Macs from being acted on properly and fully inhibiting data transmissions. With this change, it is possible for TashTalk to begin a transmission between the sync pulse and the frame that follows it, causing a collision, but the case is recoverable and the risk is negligible.

Assets 4

10 Jan 14:26

lampmerchant

v1.0.1

a2aa3f6

v1.0.1

This change is a backport of the change associated with release v2.1.3.

Assets 3

02 Dec 16:08

lampmerchant

v2.1.2

16178a1

v2.1.2

Further increases tolerance for transceiver setups where latency between TashTalk turning the driver off and the receiver returning to idle/high would cause a frame to be falsely detected, preventing transmission.
Node ID bitmap is initialized to zero, ensuring that no frames are inadvertently responded to between firmware startup and software startup.
UART receiver is not enabled until PIC's PLL is ready and instruction clock reaches full expected speed.

Assets 4

12 Nov 13:23

lampmerchant

v2.1.1

c7f052f

v2.1.1

Fixes an off-by-one bug that caused TashTalk to retry 33 times instead of 32.
Fixes a bug exposed by some transceiver setups where latency between TashTalk turning the driver off and the receiver returning to idle/high would cause a frame to be falsely detected, preventing transmission.

Assets 4