A lot of the Forth community hated the ANSI standard, but this is what happens when you throw a committee of experts together, especially corporate experts, they end up trying to be all things for everyone, producing a "Homer" car, and over engineering the "language" rather than delving in under the bonnet and overhauling it where it really mattered. Sadly too, the standard is almost PC-centric, not surprising considering who were on the committee, and it does not really address realtime control IMO.
@"Mike Green" - I use BST and it works on the Prop tool, but I will check to see what I need to change to make it run with openspin. Failing that, I will get rid of local labels.
Don't worry, I will just remove the local labels and you can try again in a few minutes.
A lot of the Forth community hated the ANSI standard, but this is what happens when you throw a committee of experts together, especially corporate experts, they end up trying to be all things for everyone, producing a "Homer" car, and over engineering the "language" rather than delving in under the bonnet and overhauling it where it really mattered. Sadly too, the standard is almost PC-centric, not surprising considering who were on the committee, and it does not really address realtime control IMO.
@"Mike Green" - I use BST and it works on the Prop tool, but I will check to see what I need to change to make it run with openspin. Failing that, I will get rid of local labels.
Don't worry, I will just remove the local labels and you can try again in a few minutes.
It's amazing the committee didn't patent it and charge $$$$ to buy the spec, and then more $$$$ to have it certified. Perhaps this happened a few years ago before they realised there was $$$$ in it ;(
@Peter Jakacki - Thanks, that did the trick ... openspin for compiling, proploader for downloading binaries, CoolTerm for downloading .FTH files with line delays
I'm having trouble getting EXTEND to fully install.
v5r2 seems to be loaded OK but when I transfer EXTEND with Tera Term it goes fine until line "3045" where it just stops with a blinking cursor.
All other numbered lines either have an "OK" or nothing.
There is still something goofy about my setup... I just don't know what.
I setup a completely new PC dual booted: Win 7 and Ubuntu 18.04.
I'm using Prop Tool 1.3.2 and TeraTerm 4.9.8 in Win 7 for all of this.
I have teraterm set to 115200, 8,n,1 HW flow OFF.
12ms LINE delay
To load EXTEND, I am using the "Send File" option in TeraTerm.
I'm using the latest versions of Tachyon v5r2 and EXTEND, both redownloaded today to be sure I have clean files.
Everything seems to work just dandy until it stops at line 3045.
If there was a terminal setting wrong or the speed was wrong, I wouldn't even get this far.
Is there something goofy with the flash on my board?
Is there static electricity messing things up? (probaby not. The issue is way too consistant)
Is there a process i should be doing after I transfer Tachyon to the board? Some sort of cleanup routine or something?
Maybe I could cut down EXTEND to be smaller and contain only what I need right now, which is servo/PWM stuff.
Its like there's some kind of buffer that overflowed and there just isn't anymore data to send at that point.
I'm looking now, but are there any buffer size, cut&paste limits that TeraTerm has?
There have been times when I have had such strange errors yet the same code would work fine on other boards. It turns out that there was a batch of Prop chips that did not have the same kind of testing as others and there were areas in hub memory which were faulty. Perhaps this is the case here.
You can increase your line delay to 20ms just to double check but it shouldn't need it. I use FT232R chips for USB serial and I check the windows settings which were still at the default for those chips including 16ms latency (advanced in device manager). I used WINXP running in VirtualBox but I do have a WIN7 machine I will double check on.
Make sure your editor is not converting CRLF line endings to LF though but if you are using the original file that shouldn't be the case. I didn't have the binary option ticked in TeraTerm either btw. I tried both pasting and sending the file.
If there seems to be strange errors that occur during load then run this little memory test to see if it can spot any defective hub memory locations.
: MEMTEST
HERE 16 + 4 ALIGN $8000 OVER -
SWAP FROM
FOR <CR> I .WORD SPACE I C@
8 FOR I MASK J C! J C@ I MASK <>
IF CR ." ERROR: " J .WORD SPACE I . CR THEN
NEXT
I C!
NEXT
;
There is still something goofy about my setup... I just don't know what.
I setup a completely new PC dual booted: Win 7 and Ubuntu 18.04.
I'm using Prop Tool 1.3.2 and TeraTerm 4.9.8 in Win 7 for all of this.
I have teraterm set to 115200, 8,n,1 HW flow OFF.
12ms LINE delay
To load EXTEND, I am using the "Send File" option in TeraTerm.
I'm using the latest versions of Tachyon v5r2 and EXTEND, both redownloaded today to be sure I have clean files.
Everything seems to work just dandy until it stops at line 3045.
If there was a terminal setting wrong or the speed was wrong, I wouldn't even get this far.
Is there something goofy with the flash on my board?
Is there static electricity messing things up? (probaby not. The issue is way too consistant)
Is there a process i should be doing after I transfer Tachyon to the board? Some sort of cleanup routine or something?
Maybe I could cut down EXTEND to be smaller and contain only what I need right now, which is servo/PWM stuff.
did you try both ?
"Send File" and Cut&Paste ?
for Cut&Paste there is a seperate line delay setting !! in TeraTerm
next a thing to try - do cut & paste in chunks -
you can comment out the line TACHYON V5 ... then you get a more verbous output
which has helped me a few times.
OK. I did the memory test and it looks good! It went all the way to 7FFF and ended with an OK.
I Copy & Pasted the file in chunks and got right to the end with no errors but it just stayed at the line numbers with a cursor.
No summaries of any kind, so i sent a Break to reboot it.
Upon rebooting, again, no summaries of any kind. No ROM or Modules lists.
I listed the WORDS to see if I could find anything from EXTEND and I found them!
My plan is to work with a servo first, so i will test that (probably not today though) and I will see how that goes :-)
If I write a word that uses numerous other words, it will still be executing in a threaded fashion right?
Is it possible to compile that word to an all assembly blob?
Some Forths do this but does Tachyon? And if not, is it something you are planning to add?
What is the threading model used in Tachyon by the way?
@thej - Actually I'm never sure what threading model describes it since it is a mix of address pointers, both machine code, or further threaded code, and also encoded operations such as conditional branches etc. Those encoded wordcodes also include ones which have a machine code instruction field for common 2 parameter to 1 result such as AND, +, etc.
But right from the beginning I set out to avoid inline assembly code which of course for the P1 can only work as LMM or copied to cog memory anyway. However besides making it fast enough so that it could bit-bash at sub-microsecond speeds (400ns @80MHz), I also included instructions and cog modules for many common I/O operations such as SPI etc so that there is never any need for special assembly routines. In fact it is possible to bit-bash WS2812 timing in high level code.
Also to support inline assembly code, even if it is LMM or a small cog module, then an assembler is needed which would add quite a few kB to the code base.
Don't forget that Tachyon has a HELP word, which decompiles the code but may also include some additional features as it is refined.
Create a simple demo
... : DEMO 10 FOR CR I . SPACE I I * . NEXT ;
Then type HELP DEMO
511E 4F26 2 DEMO
4F26: 10
4F28: FOR
4F2A: CR
4F2C: I
4F2E: .
4F30: SPACE
4F32: I
4F34: I
4F36: *
4F38: .
4F3A: NEXT
4F3C: EXIT
Looking at the wordcode for 10 we can see that it has the literal embedded with the msb of the word set since addresses from $8000 are unusable anyway, so this allows us to embed a 15-bit literal into a 16-bit instruction.
... $4F26 W@ .WORD 800A ok
Actually, I can see where I can add some improvements to HELP which I may just do right now..
The HELP word has been updated to autostop at the end of a definition by relying upon the CFA of the next header before the current header. This works for anything compiled from EXTEND onwards but not for the kernel so this will still pause and continue. HELP now also reports a GOTO <name> when the lsb jump bit is set.
Finally caving out time to work with Tachyon :-)
I'm starting with servos.
It looks like I have the PWM words from extend loaded in 5r2 on my P1 board.
...but I'm not sure what tachyon wants to make PWM work.
I tried a few of the words but I'm getting ??? after them so it does not appear to recognize them. Do I need to do something to setup the PMW32 module first?
@thej - PWM.START starts up a cog to run up to 32 channels of PWM at up to 7.6kHz. You need to specify the I/O mask (up to 32 pins), the 1kB table area that the PWM task will use, and the frequency (normally 7600 max).
If you look at EXTEND.FTH you will find all the information there.
Allocate 256 longs (1kB) and start up the PWM cog using 24 PWM channels from P0..P23
256 longs pwms
$00FFFFFF pwms 7600 PWM.START
Do this once at start-up and thereafter to vary an individual PWM, say P4 for 25%:
25 4 PWM%
or specify an 8-bit value:
64 4 PWM
BTW, I just changed PWM% in EXTEND as before it only calculated the 8-bit value, now it also sets the PWM.
You can also set a range of I/O to the same PWM value with PWM! ( duty8 mask -- )
Tachyon appears to boot fine and even work fine, but it then forgets to entire dictionary; even words like "WORDS" and "+" !
The problem seems to be degrading over time.
Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
Cold start - no user code - setting defaults
Setting up dictionary
... [PWM32] ok
... 256 longs pwms
... $00FFFFFF pwms 7600 PWM.START ??? ok
... 25 1 PWM% ??? ok
... 2 ok
... 3 ok
... + ok
... . 5 ok
... words
... WORDS ???
... words ???
... 2 3 ok
... + ???
I tried the MEMTEST again and it worked but then I tried to run it immediately again and Tachyon could not even find the word MEMTEST !
7FFC
7FFD
7FFE
7FFF ok
... words
... MEMTEST ???
...
The dictionary is stored in eeprom right? Purhaps a problem there.
This is looking more and more like a hardware problem.
I think I'm just going to buy a new P1 board.
Your cold start indicates that EXTEND has not been loaded, you only have the Prop tool compiled kernel. Although the kernel does know WORDS unfortunately it also knows "words", not as a lower-case version of WORDS, but one that takes a parameter and a name and allocates words of data memory. It seems this misuse caused the corruption of memory. Perhaps I should rename bytes/words/longs to avoid this confusion.
In your case a simple ^C (control C) will reset the Prop, then try WORDS, which will work of course. But you need to load EXTEND with a line delay of around 15ms after which you will have a complete Tachyon kernel. BTW, there is no need to use [PWM32] directly, that is all taken care of by PWM.START.
EXTEND also has an enhanced version of WORDS called WWORDS which also formats and color codes the words according to their attributes (if you have ANSI color enabled).
I'm guessing that you might only have an old 32kB EEPROM (24LC256) on board? Practically every system has at least 64kB EEPROM and Tachyon saves the ROMs to upper EEPROM. It shouldn't try to save those ROMs on a 32kB EEPROM but I haven't tested that out in a long time.
If you comment out TACHYON V5 by typing a "\ " before you load the file (no need to actually edit it), it will echo everything but that may also slow down the compile speed so you may need to increase the line delay a little to compensate.
In the meantime I will dig up a board with 32kB of EEPROM and check it.
@thej - I can only guess that maybe if you load it without commenting out TACHYON then it should be fine. If not, then what terminal and line delays are you using?
It's the same problem I've been having trying to load Extend.
It stops at the same spot everytime. This is the first time I have actually tried commenting out the TACHYON line.
Right now I'm using CoolTerm on the Mac with 115200/8/n/1 and line delay of 15ms.
I have also tried TeraTerm in Win7.
Peter,
I am working my way through starting up a prop with Tachyon. In the Introduction, you go through the procedure for down loading extend.fth, but you do not mention 'Backup' until you introduce it in the I2C discussion. should backup be run immediately after downloading extend? Also need to go back to drawingboard in learning how to get Teraterm to remember its settings.
Jim
Peter,
further update, after setting the teraterm setting to 8n1,115200 and copying and pasting extend.fth to teraterm I get the following:
3024 ok 12 bytes
at this point, I get nothing I reboot the Prop and I get this:
CODE:$3E2A = 15402 bytes
NAME:$5888 = 7032 bytes
DATA:$764B = 315 bytes
FREE: = 6750 bytes
Data Stack (0)
Mon, 01 Jan 2001 00:00:00 UTC
... : +LCD : +KEY : +VGA ; ( precede line with \ space to comment and leave out modules )
... TACHYON V5 Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
0100 ok
0200
0300 ok
0400 ok
0500 ok
0600
0800 ok
0900 ok
1000 ok
1200 ok
1300
1400 ok
1500 ok
1600
1700 ok
1800
1900 ok
2100 ok
2200 ok
2300 ok
2400 ok
2500
2600
2700
2800
3000
3024 ok 12 bytes
CODE:$3E2A = 15402 bytes
NAME:$5888 = 7032 bytes
DATA:$764B = 315 bytes
FREE: = 6750 bytes
Data Stack (0)
Mon, 01 Jan 2001 00:00:00 UTC
...
Now what? Extend came from the dropbox.
Jim
Peter,
further update, after setting the teraterm setting to 8n1,115200 and copying and pasting extend.fth to teraterm I get the following:
3024 ok 12 bytes
at this point, I get nothing I reboot the Prop and I get this:
CODE:$3E2A = 15402 bytes
NAME:$5888 = 7032 bytes
DATA:$764B = 315 bytes
FREE: = 6750 bytes
Data Stack (0)
Mon, 01 Jan 2001 00:00:00 UTC
... : +LCD : +KEY : +VGA ; ( precede line with \ space to comment and leave out modules )
... TACHYON V5 Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
0100 ok
0200
0300 ok
0400 ok
0500 ok
0600
0800 ok
0900 ok
1000 ok
1200 ok
1300
1400 ok
1500 ok
1600
1700 ok
1800
1900 ok
2100 ok
2200 ok
2300 ok
2400 ok
2500
2600
2700
2800
3000
3024 ok 12 bytes
CODE:$3E2A = 15402 bytes
NAME:$5888 = 7032 bytes
DATA:$764B = 315 bytes
FREE: = 6750 bytes
Data Stack (0)
Mon, 01 Jan 2001 00:00:00 UTC
...
Now what? Extend came from the dropbox.
Jim
Comments
@"Mike Green" - I use BST and it works on the Prop tool, but I will check to see what I need to change to make it run with openspin. Failing that, I will get rid of local labels.
Don't worry, I will just remove the local labels and you can try again in a few minutes.
Never mind my previous post.
After more research found that the decompile stops when you hit "ENTER".
Thought it was the "any" key.
Just a newb.
Thanks for Tachyon
v5r2 seems to be loaded OK but when I transfer EXTEND with Tera Term it goes fine until line "3045" where it just stops with a blinking cursor.
All other numbered lines either have an "OK" or nothing.
I setup a completely new PC dual booted: Win 7 and Ubuntu 18.04.
I'm using Prop Tool 1.3.2 and TeraTerm 4.9.8 in Win 7 for all of this.
I have teraterm set to 115200, 8,n,1 HW flow OFF.
12ms LINE delay
To load EXTEND, I am using the "Send File" option in TeraTerm.
I'm using the latest versions of Tachyon v5r2 and EXTEND, both redownloaded today to be sure I have clean files.
Everything seems to work just dandy until it stops at line 3045.
If there was a terminal setting wrong or the speed was wrong, I wouldn't even get this far.
Is there something goofy with the flash on my board?
Is there static electricity messing things up? (probaby not. The issue is way too consistant)
Is there a process i should be doing after I transfer Tachyon to the board? Some sort of cleanup routine or something?
Maybe I could cut down EXTEND to be smaller and contain only what I need right now, which is servo/PWM stuff.
I'm looking now, but are there any buffer size, cut&paste limits that TeraTerm has?
You can increase your line delay to 20ms just to double check but it shouldn't need it. I use FT232R chips for USB serial and I check the windows settings which were still at the default for those chips including 16ms latency (advanced in device manager). I used WINXP running in VirtualBox but I do have a WIN7 machine I will double check on.
Make sure your editor is not converting CRLF line endings to LF though but if you are using the original file that shouldn't be the case. I didn't have the binary option ticked in TeraTerm either btw. I tried both pasting and sending the file.
did you try both ?
"Send File" and Cut&Paste ?
for Cut&Paste there is a seperate line delay setting !! in TeraTerm
next a thing to try - do cut & paste in chunks -
you can comment out the line TACHYON V5 ... then you get a more verbous output
which has helped me a few times.
I Copy & Pasted the file in chunks and got right to the end with no errors but it just stayed at the line numbers with a cursor.
No summaries of any kind, so i sent a Break to reboot it.
Upon rebooting, again, no summaries of any kind. No ROM or Modules lists.
I listed the WORDS to see if I could find anything from EXTEND and I found them!
My plan is to work with a servo first, so i will test that (probably not today though) and I will see how that goes :-)
If I write a word that uses numerous other words, it will still be executing in a threaded fashion right?
Is it possible to compile that word to an all assembly blob?
Some Forths do this but does Tachyon? And if not, is it something you are planning to add?
What is the threading model used in Tachyon by the way?
Jason
But right from the beginning I set out to avoid inline assembly code which of course for the P1 can only work as LMM or copied to cog memory anyway. However besides making it fast enough so that it could bit-bash at sub-microsecond speeds (400ns @80MHz), I also included instructions and cog modules for many common I/O operations such as SPI etc so that there is never any need for special assembly routines. In fact it is possible to bit-bash WS2812 timing in high level code.
Also to support inline assembly code, even if it is LMM or a small cog module, then an assembler is needed which would add quite a few kB to the code base.
Don't forget that Tachyon has a HELP word, which decompiles the code but may also include some additional features as it is refined.
Create a simple demo Then type HELP DEMO Looking at the wordcode for 10 we can see that it has the literal embedded with the msb of the word set since addresses from $8000 are unusable anyway, so this allows us to embed a 15-bit literal into a 16-bit instruction.
Actually, I can see where I can add some improvements to HELP which I may just do right now..
Of course you need keyboard with an "anykey".
Press any key to continue or any other to abort.
I'm starting with servos.
It looks like I have the PWM words from extend loaded in 5r2 on my P1 board.
...but I'm not sure what tachyon wants to make PWM work.
I tried a few of the words but I'm getting ??? after them so it does not appear to recognize them. Do I need to do something to setup the PMW32 module first?
Jason
If you look at EXTEND.FTH you will find all the information there.
Allocate 256 longs (1kB) and start up the PWM cog using 24 PWM channels from P0..P23 Do this once at start-up and thereafter to vary an individual PWM, say P4 for 25%: or specify an 8-bit value:
BTW, I just changed PWM% in EXTEND as before it only calculated the 8-bit value, now it also sets the PWM.
You can also set a range of I/O to the same PWM value with PWM! ( duty8 mask -- )
Tachyon appears to boot fine and even work fine, but it then forgets to entire dictionary; even words like "WORDS" and "+" !
The problem seems to be degrading over time.
Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
Cold start - no user code - setting defaults
Setting up dictionary
... [PWM32] ok
... 256 longs pwms
... $00FFFFFF pwms 7600 PWM.START ??? ok
... 25 1 PWM% ??? ok
... 2 ok
... 3 ok
... + ok
... . 5 ok
... words
... WORDS ???
... words ???
... 2 3 ok
... + ???
I tried the MEMTEST again and it worked but then I tried to run it immediately again and Tachyon could not even find the word MEMTEST !
7FFC
7FFD
7FFE
7FFF ok
... words
... MEMTEST ???
...
The dictionary is stored in eeprom right? Purhaps a problem there.
This is looking more and more like a hardware problem.
I think I'm just going to buy a new P1 board.
Any recommendations?
Jason
In your case a simple ^C (control C) will reset the Prop, then try WORDS, which will work of course. But you need to load EXTEND with a line delay of around 15ms after which you will have a complete Tachyon kernel. BTW, there is no need to use [PWM32] directly, that is all taken care of by PWM.START.
EXTEND also has an enhanced version of WORDS called WWORDS which also formats and color codes the words according to their attributes (if you have ANSI color enabled).
Everything goes fine until it hits the last 10 lines or so of the file.
\.
... . LEAVE
... . THEN
... . THEN
... . NEXT
... . DROP
... . ;
...
...
... $7510 @org W@ OVER - ERASE ok
...
...
... errors W@ 0= IF SAVEROMS THEN
...and that's where it stops.
Thoughts!?!
Jason
If you comment out TACHYON V5 by typing a "\ " before you load the file (no need to actually edit it), it will echo everything but that may also slow down the compile speed so you may need to increase the line delay a little to compensate.
In the meantime I will dig up a board with 32kB of EEPROM and check it.
The picture of the board shows a 24LC512.
It stops at the same spot everytime. This is the first time I have actually tried commenting out the TACHYON line.
Right now I'm using CoolTerm on the Mac with 115200/8/n/1 and line delay of 15ms.
I have also tried TeraTerm in Win7.
I will try TeraTerm again just to be thorough.
J
115200/8/n/1 NO flow control and line delay of 15ms.
It counts to 3045 and stops.
I send it a Break and I get the boot description/Tachyon version but no modules mentioned.
j
This is my screen dump when downloading with an 8ms line delay in minicom.
I am working my way through starting up a prop with Tachyon. In the Introduction, you go through the procedure for down loading extend.fth, but you do not mention 'Backup' until you introduce it in the I2C discussion. should backup be run immediately after downloading extend? Also need to go back to drawingboard in learning how to get Teraterm to remember its settings.
Jim
further update, after setting the teraterm setting to 8n1,115200 and copying and pasting extend.fth to teraterm I get the following:
3024 ok 12 bytes
at this point, I get nothing I reboot the Prop and I get this:
Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
*** MODULES *** Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
3770: TOOLS DEV TOOLS
34C8: CHARLCD BUFFERED CHARACTER LCD
3360: ANYKEYS ANYKEY KEYPAD 171005
30D6: VGATEXT VGA text driver (minimal) 180218-0000
1982: EXTEND Primary extensions to TACHYON V5.2 kernel - 180322-1300
AUTORUN BOOT 306E
FREQ = 80.00MHZ
*** INITS ***
*** ROMS ***
E01C: VGA32x15 848
E37C: UART 464
E55C: HSUART 560
E79C: F32 1900
*** I2C ***
$A0 EEPROM
I/O = 31 :UHU~ 27 :~~~~ 23 :~~~~ 19 :~~~~ 15 :~~~~ 11 :~~~~ 7 :~~~~ 3 :~~~~
INTERCOM:
CODE:$3E2A = 15402 bytes
NAME:$5888 = 7032 bytes
DATA:$764B = 315 bytes
FREE: = 6750 bytes
Data Stack (0)
Mon, 01 Jan 2001 00:00:00 UTC
... : +LCD : +KEY : +VGA ; ( precede line with \ space to comment and leave out modules )
... TACHYON V5 Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
0100 ok
0200
0300 ok
0400 ok
0500 ok
0600
0800 ok
0900 ok
1000 ok
1200 ok
1300
1400 ok
1500 ok
1600
1700 ok
1800
1900 ok
2100 ok
2200 ok
2300 ok
2400 ok
2500
2600
2700
2800
3000
3024 ok 12 bytes
Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
*** MODULES *** Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
3770: TOOLS DEV TOOLS
34C8: CHARLCD BUFFERED CHARACTER LCD
3360: ANYKEYS ANYKEY KEYPAD 171005
30D6: VGATEXT VGA text driver (minimal) 180218-0000
1982: EXTEND Primary extensions to TACHYON V5.2 kernel - 180322-1300
AUTORUN BOOT 306E
FREQ = 80.00MHZ
*** INITS ***
*** ROMS ***
E01C: VGA32x15 848
E37C: UART 464
E55C: HSUART 560
E79C: F32 1900
*** I2C ***
$A0 EEPROM
I/O = 31 :UHU~ 27 :~~~~ 23 :~~~~ 19 :~~~~ 15 :~~~~ 11 :~~~~ 7 :~~~~ 3 :~~~~
INTERCOM:
CODE:$3E2A = 15402 bytes
NAME:$5888 = 7032 bytes
DATA:$764B = 315 bytes
FREE: = 6750 bytes
Data Stack (0)
Mon, 01 Jan 2001 00:00:00 UTC
...
Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
*** MODULES *** Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
3770: TOOLS DEV TOOLS
34C8: CHARLCD BUFFERED CHARACTER LCD
3360: ANYKEYS ANYKEY KEYPAD 171005
30D6: VGATEXT VGA text driver (minimal) 180218-0000
1982: EXTEND Primary extensions to TACHYON V5.2 kernel - 180322-1300
AUTORUN BOOT 306E
FREQ = 80.00MHZ
*** INITS ***
*** ROMS ***
E01C: VGA32x15 848
E37C: UART 464
E55C: HSUART 560
E79C: F32 1900
*** I2C ***
$A0 EEPROM
I/O = 31 :UHU~ 27 :~~~~ 23 :~~~~ 19 :~~~~ 15 :~~~~ 11 :~~~~ 7 :~~~~ 3 :~~~~
INTERCOM:
CODE:$3E2A = 15402 bytes
NAME:$5888 = 7032 bytes
DATA:$764B = 315 bytes
FREE: = 6750 bytes
Data Stack (0)
Mon, 01 Jan 2001 00:00:00 UTC
...
Now what? Extend came from the dropbox.
Jim
further update, after setting the teraterm setting to 8n1,115200 and copying and pasting extend.fth to teraterm I get the following:
3024 ok 12 bytes
at this point, I get nothing I reboot the Prop and I get this:
Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
*** MODULES *** Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
3770: TOOLS DEV TOOLS
34C8: CHARLCD BUFFERED CHARACTER LCD
3360: ANYKEYS ANYKEY KEYPAD 171005
30D6: VGATEXT VGA text driver (minimal) 180218-0000
1982: EXTEND Primary extensions to TACHYON V5.2 kernel - 180322-1300
AUTORUN BOOT 306E
FREQ = 80.00MHZ
*** INITS ***
*** ROMS ***
E01C: VGA32x15 848
E37C: UART 464
E55C: HSUART 560
E79C: F32 1900
*** I2C ***
$A0 EEPROM
I/O = 31 :UHU~ 27 :~~~~ 23 :~~~~ 19 :~~~~ 15 :~~~~ 11 :~~~~ 7 :~~~~ 3 :~~~~
INTERCOM:
CODE:$3E2A = 15402 bytes
NAME:$5888 = 7032 bytes
DATA:$764B = 315 bytes
FREE: = 6750 bytes
Data Stack (0)
Mon, 01 Jan 2001 00:00:00 UTC
... : +LCD : +KEY : +VGA ; ( precede line with \ space to comment and leave out modules )
... TACHYON V5 Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
0100 ok
0200
0300 ok
0400 ok
0500 ok
0600
0800 ok
0900 ok
1000 ok
1200 ok
1300
1400 ok
1500 ok
1600
1700 ok
1800
1900 ok
2100 ok
2200 ok
2300 ok
2400 ok
2500
2600
2700
2800
3000
3024 ok 12 bytes
Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
*** MODULES *** Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
3770: TOOLS DEV TOOLS
34C8: CHARLCD BUFFERED CHARACTER LCD
3360: ANYKEYS ANYKEY KEYPAD 171005
30D6: VGATEXT VGA text driver (minimal) 180218-0000
1982: EXTEND Primary extensions to TACHYON V5.2 kernel - 180322-1300
AUTORUN BOOT 306E
FREQ = 80.00MHZ
*** INITS ***
*** ROMS ***
E01C: VGA32x15 848
E37C: UART 464
E55C: HSUART 560
E79C: F32 1900
*** I2C ***
$A0 EEPROM
I/O = 31 :UHU~ 27 :~~~~ 23 :~~~~ 19 :~~~~ 15 :~~~~ 11 :~~~~ 7 :~~~~ 3 :~~~~
INTERCOM:
CODE:$3E2A = 15402 bytes
NAME:$5888 = 7032 bytes
DATA:$764B = 315 bytes
FREE: = 6750 bytes
Data Stack (0)
Mon, 01 Jan 2001 00:00:00 UTC
...
Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
*** MODULES *** Propeller .:.:--TACHYON--:.:. Forth V5r2 NEON 520180323.2200
3770: TOOLS DEV TOOLS
34C8: CHARLCD BUFFERED CHARACTER LCD
3360: ANYKEYS ANYKEY KEYPAD 171005
30D6: VGATEXT VGA text driver (minimal) 180218-0000
1982: EXTEND Primary extensions to TACHYON V5.2 kernel - 180322-1300
AUTORUN BOOT 306E
FREQ = 80.00MHZ
*** INITS ***
*** ROMS ***
E01C: VGA32x15 848
E37C: UART 464
E55C: HSUART 560
E79C: F32 1900
*** I2C ***
$A0 EEPROM
I/O = 31 :UHU~ 27 :~~~~ 23 :~~~~ 19 :~~~~ 15 :~~~~ 11 :~~~~ 7 :~~~~ 3 :~~~~
INTERCOM:
CODE:$3E2A = 15402 bytes
NAME:$5888 = 7032 bytes
DATA:$764B = 315 bytes
FREE: = 6750 bytes
Data Stack (0)
Mon, 01 Jan 2001 00:00:00 UTC
...
Now what? Extend came from the dropbox.
Jim