Welcome to the Parallax Discussion Forums, sign-up to participate.

# TACHYON O/S V3.0 JUNO - Furiously Fast Forth, FAT32+LAN+VGA+RS485+OBEX ROMS+FP+LMM+++

• Posts: 6,399
proplem wrote: »
@Peter Jakacki,
you commented out ERASE$in (V3) EXTEND.FTH pub ERASE$ ( str -- \ Fully erase the string - reads max len from header )
DUP 3 - C@ ERASE
;

Is something wrong with it?

Mainly because not all strings are created equal, that is, those strings that were constructed with the STRING function had an additional field specifying the maximum string length which ERASE$could use but a common string is normally just a null terminated string without any special fields. Applying ERASE$ to these common null terminated strings would cause definite problems.

But there is the problem with any general erase string function for who knows how long a string is or can be.

Tachyon Forth - compact, fast, forthwright and interactive

Brisbane, Australia
• Posts: 757
Hi Peter,

I know how the OK word can be used to turn off the prompt
off OK


Is there a way to suppress the "ok" and just have a CR returned?

Thanks
• Posts: 888
edited April 26
@D.P
\\\ original
pub NOOP ;
pub OK ( on/off -- )		IF 0 ELSE ' NOOP THEN prompt 2+ W! ; \ enable/disable OK prompts including the autospace )

\\ so you can do:\
pub MYPROMPT CR ;

' MYPROMPT  prompt 2+ W!

\\to get the original prompt back:
prompt 2+ W~
\\ or simply
ON OK

TESTED !! ;-)
http://www.smmu.info (german) Source-Measure-Multiplex-Unit = professional test system for electronic components, sensors, assemblies
Tachyon code and documentation snippets from Tachyon thread
• Posts: 757
Okay, the ESP8266 front end is really close now. But if the ESP is connected to prop pins 31/30 during ESP boot it resets Tachyon?

The ESP bootloader produces this "init string" at 744000 baud before it engages the set baud rate.

While you can divert debug message to the aux ESP serial port you cannot divert this output _Until the ESP boots.

How can we prevent Tachyon V3 from rebooting from this initial "junk"?

Thanks

• Posts: 888
D.P wrote: »
Okay, the ESP8266 front end is really close now. But if the ESP is connected to prop pins 31/30 during ESP boot it resets Tachyon?

The ESP bootloader produces this "init string" at 744000 baud before it engages the set baud rate.

While you can divert debug message to the aux ESP serial port you cannot divert this output _Until the ESP boots.

How can we prevent Tachyon V3 from rebooting from this initial "junk"?

Thanks

is this 'junk' random or fixed?
if fixed, what is it exactly in hex? any ^C in there ??

http://www.smmu.info (german) Source-Measure-Multiplex-Unit = professional test system for electronic components, sensors, assemblies
Tachyon code and documentation snippets from Tachyon thread
• Posts: 757
edited May 17
The baud is 74880 and the message is constant for a given build. That ~ld could be the end load symbol perhaps
 ets Jan  8 2013,rst cause:1, boot mode:(3,0)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v3de0c112
~ld


UPDATE:
Setting the world to 74880 baud and testing is still causing a tachyon reboot even as I guard against this ESP8266 boot message. Time to sniff the stream for clues.
• Posts: 757
edited May 18
Decided to implement software serial on 2 of the 4 available io pins to handle just the Propeller serial interface to Tachyon. This avoids all the ESP kernel boot messages now. So now the ESP can reset independent of the Tachyon Machine.

Works well.

D.P wrote: »
The baud is 74880 and the message is constant for a given build. That ~ld could be the end load symbol perhaps

• Posts: 6,399
D.P wrote: »
Decided to implement software serial on 2 of the 4 available io pins to handle just the Propeller serial interface to Tachyon. This avoids all the ESP kernel boot messages now. So now the ESP can reset independent of the Tachyon Machine.

Works well.

D.P wrote: »
The baud is 74880 and the message is constant for a given build. That ~ld could be the end load symbol perhaps

Good stuff, can't wait to see how you are using it. Come to think of it, while you are on a roll, maybe you could get the F32 interface up and running! :)

Tachyon Forth - compact, fast, forthwright and interactive

Brisbane, Australia
• Posts: 757
edited May 19
D.P wrote: »
Decided to implement software serial on 2 of the 4 available io pins to handle just the Propeller serial interface to Tachyon. This avoids all the ESP kernel boot messages now. So now the ESP can reset independent of the Tachyon Machine.

Works well.

D.P wrote: »
The baud is 74880 and the message is constant for a given build. That ~ld could be the end load symbol perhaps

Good stuff, can't wait to see how you are using it. Come to think of it, while you are on a roll, maybe you could get the F32 interface up and running! :)

It seems that I should begin another journey and move my code bases to V4.4. That's probably gonna leave a mark. As for F32 some very basic pseudo code would help me unblock. On another note I'm currently implementing prooph and "event sourcing" on a complex phylogenic dataset with a mentor, the rabbit hole is deep here. So just a little pseudo code nudge would help F32 get to TOS. Also I am getting a non-critical intermittent websocket terminal disconnect that I need to debug on the ESP frontend. Now that the hardware serial port is "free" I've got the ability to debug the ESP again live. But no matter what happens to the ESP now it leaves the Tachyon machine running just fine i.e. leave the washing machine alone. Separation of concerns, my FONA module which is UI-ish will also get moved the the ESP.

• Posts: 131
I'm trying to make the jump from 2.7 to 4.4. Woopeee! I believe I read somewhere in the documentation that it can't be compiled in the PropTool. So I installed the Simple (Talk about a rich joke) IDE. I have been very comfortable working with the PropTool, TerraTerm and the SemWare Programming Editor -- but now SIDE wants to relieve me of that "burden" with projects and libraries etc. Ok, fine if we must, but how do I compile Tachyon V4.4-list.spin when I can't even load it? SIDE insists that I open a project but when I try to do so it requires a .c or .c++ extension. From the SIDE pdf file "New: Opens a dialog to select folder, project name, and project type (C or C++)."
HALP!
Gratitude is riches, complaint is poverty, and the worst I ever had was wonderful. - Brother Dave Gardener :innocent:
• Posts: 6,399
edited May 29
artkennedy wrote: »
I'm trying to make the jump from 2.7 to 4.4. Woopeee! I believe I read somewhere in the documentation that it can't be compiled in the PropTool. So I installed the Simple (Talk about a rich joke) IDE. I have been very comfortable working with the PropTool, TerraTerm and the SemWare Programming Editor -- but now SIDE wants to relieve me of that "burden" with projects and libraries etc. Ok, fine if we must, but how do I compile Tachyon V4.4-list.spin when I can't even load it? SIDE insists that I open a project but when I try to do so it requires a .c or .c++ extension. From the SIDE pdf file "New: Opens a dialog to select folder, project name, and project type (C or C++)."
HALP!

There was something at one time which was nothing more than a missing org which threw Proptool off but that was then fixed. Head on over to to the V4 thread if it is anything V4 specific.

edit - here's the proof 4.4 compiles fine on Proptool

Btw, I tried to paste Forth source into Mecrisp Forth on Arm M0 and boy do I have to slow it down to 1ms character delay and 50ms line delay for it to compile. Tachyon with 5ms line delay and zero character delay just positively zips along.
Tachyon Forth - compact, fast, forthwright and interactive

Brisbane, Australia
• Posts: 757
edited May 30
deleted