Cool! Fingers crossed that that's it for TashTalk bugs. =)
Also, some TashTalk Hat kits are back in stock in case anyone needs one.
-
Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.
TashTalk: Single-Chip LocalTalk Interface
- Thread starter Tashtari
- Start date
Also, some TashTalk Hat kits are back in stock in case anyone needs one.
I hope to finally make it to test it in LT2USB this coming weekend, free time has been elusive lately.
I have a centris 650 which fails almost all the time - got it to work one time only. Does this machine also use the chip above?
Forgive the cross-post advertisement:
Do any of you TashTalk owners have an AppleTalk ImageWriter, too? I'm looking for someone who has both and is willing to perform a small experiment for me for another project I'm working on...
68kmla.org
Do any of you TashTalk owners have an AppleTalk ImageWriter, too? I'm looking for someone who has both and is willing to perform a small experiment for me for another project I'm working on...
Anyone have an AppleTalk ImageWriter and a TashTalk or AirTalk?
If so, I wonder if you might be willing to do me a small favor... I'm seeking a trace of the AppleTalk network activity between Mac and ImageWriter when a print job is being sent. There are a few different ways to collect such a trace: If you have an AirTalk and Mini vMac v37 with LToUDP, you...
68kmla.org
The little 8pin socketted chip on the AirTalk is a TashTalk - it is that chip people are talking about. There was a recent firmware update that improves compatibility with first gen PPCs
Found the post by @RolandJuno about the ImageWriter II TashTalk issues with logs, wonder if 1.0.1 would improve things:
68kmla.org
Introducing (and interest check) AirTalk: Wireless plug-and-play LocalTalk dongles
That's a lot of framing errors. In order for TashTalk to flag a framing error, it has to have detected a zero on the line that it detects as the attempted beginning of a flag byte (0b01111110), followed by more than six ones, which seems a little too precise of an error to have been triggered...
68kmla.org
TashTalk 2 Hat kits are back in stock, and I'm also offering for sale a small number of fully-assembled and tested TashTalk 2 Hats for folks who'd rather not assemble their own and don't mind the extra cost. I don't know if I'll do another batch of the latter again, so get 'em while they're hot!
Should be soon, I've got the PCBs and I've ordered parts, so maybe a week from now. Will post in this thread when they're available again.
TashTalk 2 Hat kits are back in stock again in the Ko-fi shop! If you're interested, please get your orders in this week - after that, shop is going to be temporarily closed until the beginning of October.
Hi all,
do you know if tashtalk hat v1 supports low level programming? Trying to update firmware using the raspberry pi zero using the guide here:
Do you know if this will work, or is pickit3 the only option?
Thanks
do you know if tashtalk hat v1 supports low level programming? Trying to update firmware using the raspberry pi zero using the guide here:
Do you know if this will work, or is pickit3 the only option?
Thanks
Responding to my own post, I am coming to the conclusion that lvp is disabled on this pic chip. I have a ST-Line v2 and some bluepill boards. Could I maybe use those somehow?Hi all,
do you know if tashtalk hat v1 supports low level programming? Trying to update firmware using the raspberry pi zero using the guide here:
Do you know if this will work, or is pickit3 the only option?
Thanks
It doesn't, unfortunately - low-voltage programming requires that the RA3/!MCLR pin be used as !MCLR (reset), but TashTalk 1.x uses it as the LocalTalk input, so any PIC that has TashTalk 1.x on it will have low-voltage programming disabled (and it cannot be reenabled without use of a high-voltage programmer such as the PICkit). TashTalk 2.x should support low-voltage programming since it uses one pin for both LocalTalk input and output and uses RA3/!MCLR as !MCLR, but I've never tested this... perhaps I should.
@Tashtari, @NJRoadfan thank you for your replies. I bought a pickit 3 and managed to load version 1.01 successfully. Unfortunately it did not solve the problem that I had since day 1 of owning the tashtalk hat. Let me explain: I have a physical mac se 30 hooked up to a tashtari hat running tashrouter, and a mini vmac speaking ltoudp. Both vmac and se30 see both zones. Mini vmac can access shared folders on se30 but after some time starts to lag and fail. SE30 cannot connect to mini vmac shared folder, it times out right before asking for password.
Do you have any ideas? Using latest version of tashrouter.
Log FIle: https://pastebin.com/Rv27Me98
Do you have any ideas? Using latest version of tashrouter.
Log FIle: https://pastebin.com/Rv27Me98
Edit time is over: Log is here:
snippet.host
syemmx - snippet.host
2024-12-23 20:23:15,886 DEBUG: frame out LToUDP 255 254 type 01 b'\x00$\x02\x02\x02!\xc2\x00\x02\x16\xfd\x00\x01=\tAFPServer\x0bDanger Zon...
Similar threads
