Hello all-
I've encountered the attached error while trying to load extend into tachyon. I've started this thread because the tachyon thread is, well, massive!
Sounds like it might simply be a problem with line delay (NOT character delay). Set this to 25m to be safe otherwise here are the current files that I have just checked
00:00:00 End of source code, 2484 lines processed and 0000 errors found
Load time = 12.903secs
MODULES LOADED:
1780: EXTEND.fth Primary extensions to TACHYON kernel - 160721-2200
VER: Propeller .:.:--TACHYON--:.:. Forth V3.0 JUNO 300160720.0000
FREQ: 96MHZ (PLLEN OSCEN XTAL1 PLL16X)
NAMES: $5B01...74C7 for 6,598 bytes (+3,978)
CODE: $0930...3526 for 11,254 bytes (+7,590)
RAM: 9,691 bytes free
BUILD: FIRMWARE BUILD DATE 000000:000000 BOOTS: 0 runtime 0
BOOT: EXTEND.boot ok
ok
IFDEF V3 ok
ok
--- ok
: SAVEROMS
" ROMS" U@ @NAMES 3 ANDN ' TACHYON 3 ANDN
DO I E@ OVER = ---
IF I 8 + E@ OVER = ---
IF
CR PRINT" COPY ROMS @" I .WORD
PRINT" for " I 4 + E@ .DEC
I roms I 4 + E@ romsz MIN ECOPY LEAVE
THEN
THEN
4 +LOOP
DROP
; ok
SAVEROMS
COPY ROMS @1780 for 6876 ok
0 U@ --- ok
FORGET SAVEROMS ok
} ok
ok
?BACKUP ok
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.
Looks like the OP is using Windows 10. I have built the current files with ZTerm, TeraTerm and Minicom on Window 8, and OSX 10.11. Haven't bothered installing stuff in my ubuntu VM just yet. My line delay is 23ms.
And in case anyone is using minicom on linux, you have to use command-line options to tell ascii-xfr to put in the line delay. The normal terminal settings don't apply when sending a file. If you paste the file into the terminal they do. At least this was my experience on a Raspberry Pi running Raspbian.
Usage: ascii-xfr -s|-r [-dvn] [-l linedelay] [-c character delay] filename
@MJB- I have downloaded Tachyon V3 juno. this Extend is the version on the front page of Tachyon links in Peter's links to files. Is there a more current one? Tachyon "Juno" loaded just fine with BST. I'm sorry if I am being kinda slow with this, but I'm trying to practice with these awesome tools Peter and everyone else have provided
@MJB- I have downloaded Tachyon V3 juno. this Extend is the version on the front page of Tachyon links in Peter's links to files. Is there a more current one? Tachyon "Juno" loaded just fine with BST. I'm sorry if I am being kinda slow with this, but I'm trying to practice with these awesome tools Peter and everyone else have provided
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).
Peter-
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:
That is the error I had originally a couple of weeks ago.
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
Peter-
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:
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?
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).
Yay! Success at last! Thanks so much peter and everyone for helping. Now to play with my DHT22
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).
Yay! Success at last! Thanks so much peter and everyone for helping. Now to play with my DHT22
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).
Peter-I downloaded the version of tachyon you listed in your posting https://www.dropbox.com/s/9skb8vwk8gzjy35/Tachyon V3.0 JUNO.spin?dl=0 then I downloaded the latest version of extend in the drop box. I did forget to set delay to 25ms, but after I realizedmy error extend went through without a hitch
Okay, maybe someone can help. I have Juno and extend loaded onto my prop (from a previous session). I'm opening up teraterm and trying to connect to the prop, but I'm getting nothing when I power down the board and power it up, or when I'm connected and I hit the reset button, or when I hit alt b (break). Is there a specific methodology to reconnecting to a prop loaded with tachyon?
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?
Not sure why you are having this problem but please make sure you do not have any hardware handshake enabled. The norm these days for all types of serials connections (not just Tachyon) is "no handshake" as it is normally a 3-wire connect with rx, tx, and ground and soft handshake is not an option either as the PC does not support this in real time as it should.
I have found that when using Teraterm on Pi's, Bones and Props any time you do a reset of the target board I must exit Tera and restart it. Seams once the connection is broke this happens.
I have found that when using Teraterm on Pi's, Bones and Props any time you do a reset of the target board I must exit Tera and restart it. Seams once the connection is broke this happens.
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 ... )
Mine is on Win 10 with several props, pi's etc. If I reboot I just restart tera. I dont know but that happens here. Taychon works fine for me here othe then this.....
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!