Problem loading Extend.fth into tachyon
Shawn Lowe
Posts: 635
in Propeller 1
Comments
BTW, I am running v3.0 juno
Shawn, it has been good practice on this forum in general, even with Spin, to attach a zip of the files that were used when having software problems. This might not be a bad idea just to make sure we are exactly on the same page. It sounds like an older version of software mixed up with a newer version. There are also the files that I attached that I had just tested with too.
There is a possibility that for some other reason the 25ms is not enough although I cannot think why but it won't hurt to increase the delay BUT there would never be any need to go beyond 50ms line delay. Most of the time I just work with 15ms line delay with minicom in Linux on FT232R USB chips.
@Peter- My apologies, you are quite right. Attached is the Extend.fth I am trying to use.
It is 'very old' and will not work with Tachyon3
just use the files from latest dropbox together
Usage: ascii-xfr -s|-r [-dvn] [-l linedelay] [-c character delay] filename
The Tachyon Dropbox folder is always the most current, in fact sometimes it is too current as it reflects the very documents I actively work with but I try to minimize any disruptions. I've rearranged the sig to have the dropbox link prominent. There is a README in the Tachyon root folder that I need to update but otherwise check this.
btw, I use editors that alert me that an open file has changed and needs to be reloaded since I work on several different computers. If you do the same then you only need to reload/refresh to have the latest files (or just auto reload).
The first image is where I am getting the Extend file. I'm trying to use the file that is 102.65kb.When I paste that into tera term I get the error on the second photo. This is the version of tachyon I have loaded on my prop:
Propeller .:.:--TACHYON--:.:. Forth V3.0 JUNO 300160720.0000
Cold start - no user code - setting defaults
TACHYON Propeller .:.:--TACHYON--:.:. Forth V3.0 JUNO 300160720.0000
I am running teraterm with a 30 ms delay/line. I hope this gets us on the same page.
Thanks
Shawn
P.S. Does anyone else loading that version of extend into juno get an error?
The problem was solved (and I am using W10). I have been away for nearly a week.
I suggest you follow the Tachyon thread from here as it also discusses what the other FTH files do.
forums.parallax.com/discussion/comment/1383443/#Comment_1383443
That error is at "@word" which didn't exist in an earlier kernel which makes me think you are somehow either using a local copy of the kernel or you decided to load the binary which IS an earlier version with EXTEND already loaded. Don't use the binary if you want the latest, just compile and load the kernel with BST or PropellerIDE (apparently poor old Prop tool can't handle more than 1024 DAT symbols).
Shawn
Good, but what did you different this time? (remember that it's always good to share the what and why so that these problems can be avoided in future).
Edit: I have gotten around this problem by reloading tachyon into eeprom then reloading extend, but shouldn't I be able to just connect to the prop after cycling power using teraterm?
just load the EXPLORER image and you can play.
building your own system is 'advanced' ;-)
usually it just works, but sometimes ...
I am using TeraTErm on different windows versions all fine.
Ctl-C reboots as expected. (actually hate this since it is usually CUT and Prop reboots unwantedly -
so need to patch to reboot on an other Ctl-Char ... )
Peter solved this problem please see this thread:
http://forums.parallax.com/discussion/164763/dht22-not-giving-correct-results#latest
Thanks all for your help!