00:00:00 --- log: started forth/13.08.13 00:05:50 --- join: nighty- (~nighty@TOROON12-1279662182.sdsl.bell.ca) joined #forth 00:08:24 --- quit: nighty-_ (Ping timeout: 264 seconds) 00:11:49 --- quit: nighty- (Read error: Connection reset by peer) 00:11:56 --- join: nighty- (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 00:19:55 --- nick: ASau` -> ASau 00:39:12 --- join: itsy (~digital_w@31.185.185.83) joined #forth 01:45:35 --- quit: tangentstorm (Ping timeout: 246 seconds) 01:48:30 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #forth 02:31:45 --- quit: kludge` (Ping timeout: 240 seconds) 02:37:12 --- join: kludge` (~comet@unaffiliated/espiral) joined #forth 03:24:33 --- quit: Bahman (Quit: Leaving.) 03:40:56 --- quit: newcup (*.net *.split) 03:40:56 --- quit: goingretro (*.net *.split) 03:40:57 --- quit: cataska (*.net *.split) 03:51:21 --- join: newcup (newcup@peruna.fi) joined #forth 03:59:00 --- join: Bahman (~Bahman@2.146.152.100) joined #forth 04:43:18 --- join: ASau` (~user@p4FF9682C.dip0.t-ipconnect.de) joined #forth 04:46:35 --- quit: ASau (Ping timeout: 248 seconds) 05:14:52 --- join: nighty^ (~nighty@lns-bzn-49f-62-147-170-46.adsl.proxad.net) joined #forth 06:33:47 --- join: fantazo (~fantazo@213.129.230.10) joined #forth 06:58:43 --- join: RodgerTheGreat (~rodger@c-98-202-115-133.hsd1.ut.comcast.net) joined #forth 07:33:08 --- quit: Bahman (Ping timeout: 256 seconds) 08:06:37 --- quit: fantazo (Ping timeout: 245 seconds) 08:33:46 --- nick: ASau` -> ASau 09:23:52 --- quit: tommytom (Quit: WeeChat 0.3.9.2) 09:25:49 --- join: ErhardtMundt (~Lawrence@adsl-ull-29-121.47-151.net24.it) joined #forth 10:20:02 --- quit: ErhardtMundt (Remote host closed the connection) 10:58:51 --- quit: c00kiemon5ter (Ping timeout: 248 seconds) 11:17:01 --- join: c00kiemon5ter (~c00kiemon@foss-aueb/coder/c00kiemon5ter) joined #forth 11:46:48 --- join: true-grue_ (~quassel@95-27-75-116.broadband.corbina.ru) joined #forth 11:49:24 --- quit: true-grue (Ping timeout: 240 seconds) 12:05:03 --- join: Tod-Work (~thansmann@50-202-143-210-static.hfc.comcastbusiness.net) joined #forth 13:32:57 --- quit: nighty^ (Remote host closed the connection) 13:42:31 --- join: Nisstyre-laptop (~yours@oftn/member/Nisstyre) joined #forth 13:43:02 --- nick: Nisstyre-laptop -> nisstyre 14:18:14 --- quit: true-grue_ (Read error: Connection reset by peer) 14:37:28 --- quit: dys (Remote host closed the connection) 16:22:13 --- join: dessos (~dessos@c-174-60-176-249.hsd1.pa.comcast.net) joined #forth 17:25:53 --- part: itsy left #forth 17:59:14 --- quit: Eth|cal (Read error: Connection timed out) 17:59:47 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 18:03:21 all this talk of gforth/etc has be wondering how many ppl use forth in user-land as "just" a language vs direct on hardware - i've yet to play with a "real" (hardware) forth except the sunos boot loader - the rest has been user-land 18:04:27 even my pure asm forth (a poor man's jonesforth) was written and debugged in userland 18:05:10 i booted colorforth back in the day in a vm - i guess that counts too; do most others stay in user or go bare metal? 18:09:56 --- join: _heqs (1000@201.80.238.134) joined #forth 18:16:05 --- quit: malyn (Quit: Disconnecting from stoned server.) 18:16:23 --- join: malyn (~malyn@unaffiliated/malyn) joined #forth 18:17:20 I've never used a userland Forth. 18:17:25 i edit my retro code in emacs and just run it from the shell.. same with yourforth now. 18:17:31 I mean aside from tinkering or testing little fragments. 19:03:15 --- quit: Eth|cal (Read error: Connection timed out) 19:06:10 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 19:10:39 I've tinkered with flashforth running on a PIC18 MCU 19:10:54 most of my forth is userland though 19:29:42 --- quit: Eth|cal (Read error: Connection timed out) 19:30:24 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 19:50:23 --- quit: _heqs (Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/) 20:06:12 --- quit: nisstyre (Ping timeout: 245 seconds) 20:23:51 --- quit: Eth|cal (Read error: Connection timed out) 20:24:28 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 21:04:06 --- join: cataska (~cataska@210.64.6.233) joined #forth 21:14:25 --- join: Bahman (~Bahman@2.146.4.169) joined #forth 21:15:44 --- join: msmith (~msmit297@23.31.147.162) joined #forth 21:16:53 hi all, anyone have experience with pygmy forth? 21:22:59 i played with the old dos version very briefly. 21:23:18 do you have a question about it, msmith ? 21:23:25 yes ... 21:23:49 so, I have set up a test environment using qemu ... 21:25:12 I have the thing running as far as I can tell, but can't get anything returned. trying to do something as simple as 2 2 + . 21:26:10 hrm 21:26:14 it seems to recognize illegal words 21:26:30 if I just type hello, I get hello ? 21:26:32 hrm. i don't seem to have it on this computer anymore. 21:26:52 oh. the "?" is indicating that it doesn't recognize the word. 21:27:04 correct 21:27:15 so it seems to be working 21:27:55 but I want to see what gets popped off the stack with dot 21:27:58 or something 21:28:21 does .s work? 21:28:53 nope, .s ? 21:29:17 .S maybe? 21:30:01 well .S seems to be something, but is not returning anything 21:30:41 been looking through the dictionary ... 21:32:12 all the words are being recognized apparently 21:35:55 note that if you hit an error ie something that gives you a ?, the stacks will probably be cleared 21:36:10 what version are you running? 21:36:12 so try 2 2 + .S again 21:36:49 RodgerTheGreat: no go 21:36:54 hm 21:37:06 i just fired up pygmy 1.4 in dosbox and 2 2 + . works fine 21:37:15 then I guess .S does something different than we expect 21:37:20 tangentstorm: I'm using riscy pygness 21:37:38 well, it may have something to do with my setup 21:37:45 oh 21:38:07 how the output is being directed from the qemu vm maybe? 21:38:08 it does print the result on the input line 21:38:22 so it looks like: 2 2 + . 4 ok 21:38:24 no 21:38:42 just goes to the next line with nothing returned 21:38:52 like it's waiting for more input 21:38:56 do you get an ok prompt at all? 21:39:02 no 21:39:37 --- quit: Eth|cal (Read error: Connection timed out) 21:39:44 yeah, that seems wrong... odd that it shows the "hello ?" though. 21:40:07 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 21:40:54 yeah, I may have to dig into whether or not qemu writes to the same port you set -serial to 21:41:00 it may not 21:41:25 I have the vm listening to ttyS0 21:42:46 how are you running it? 21:43:01 like what's the qemu command line you're using? 21:43:32 one sec ... 21:44:18 qemu-system-arm -M lm3s811evb -cpu cortex-m3 -nographic -kernel kernel-stm32.bin -serial pty 21:48:24 hrm.. i downloaded from http://www.utoh.org/riscy/ but i don't see that kernel-stm32.bin file 21:49:17 http://pygmy.utoh.org/riscy/cortex/ 21:52:11 huh. 21:52:40 that worked but i don't know what i'm doing now. I have a (qemu) prompt. 21:53:10 when i emulate dos i just get a dos screen 21:53:23 * tangentstorm reads the manual 21:53:49 well, then you have to run the riscy.tcl and set it to the correct port 21:54:10 then you should see what I see 21:56:12 in other words, edit the riscy.sh script to the correct port, (it is printed when the vm is started) then run the script 22:00:23 --- quit: Eth|cal (Read error: Connection timed out) 22:01:05 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 22:06:37 had to get tcl working. neat. 22:06:46 :-) 22:06:48 yeah 22:07:32 i get the same behavior 22:08:22 I'm looking in the help file, I'm wondering if I redirect monitor ... 22:11:07 nope, that was stupid 22:23:34 --- quit: Eth|cal (Read error: Connection timed out) 22:24:08 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 22:28:53 well as far as i can tell, this system is either just not sending the ACK character, or tcl isn't reading it. 22:29:04 you can turn debug on in the risc.tcl script to see it 22:29:13 ok 22:29:15 (line 23) 22:30:38 yeah, I see what you mean 22:31:15 i really like this setup, with the dictionary on the host machine like this... 22:32:40 yeah, I've seen others like this. I'm writing one myself ;-) 22:35:54 i like the word 'bicameral' for this setup... dunno what other people call it. 22:36:05 it allows you to execute complex programs on very small chips, if the instructions are qeued on the host machine 22:36:26 that's what has drawn me to build one 22:36:55 yeah, or to save bandwidth on a vm running in a web browser... :) 22:37:16 there's that 22:37:44 any suggestions about this ack character ? 22:40:03 when I get to checking registers and dumping memory, I'm afraid I've reached the upper limits of my powers at this point 22:41:36 I'm not sure the commands are getting to the vm 22:41:57 I need figure out how to monitor what's arriving 22:43:39 I think we (I) may have mis-understood the problem 22:47:05 I'm wondering if it is not waiting for an ack char from the vm but from the guest console, in which case I need to figure out what that is 22:51:58 tangentstorm: I'm going to bed, thanks for helping me look into this. I'll talk to you tomorrow 22:57:39 --- quit: Bahman (Quit: Leaving.) 23:03:24 --- quit: Eth|cal (Read error: Connection timed out) 23:04:11 --- join: Eth|cal (~sam@ppp59-167-172-238.static.internode.on.net) joined #forth 23:59:59 --- log: ended forth/13.08.13