00:00:00 --- log: started forth/16.06.26 00:38:33 --- quit: proteusguy (Ping timeout: 244 seconds) 02:16:18 --- quit: wa5qjh (Remote host closed the connection) 02:16:47 --- join: wa5qjh (~Thunderbi@203.111.224.39) joined #forth 02:36:15 --- quit: mnemnion (Remote host closed the connection) 02:46:02 --- join: tg9541 (95acac53@gateway/web/freenode/ip.149.172.172.83) joined #forth 02:47:21 Hi - I just started playing with eForth on STM8. Is there anybody around with eForth experience? 03:03:52 tg9541: might be better to just ask your question and see who answers 03:05:02 I'm looking for resources that help me understand how to get from an interactive to an embedded system 03:05:31 especially how to deal with VARIABLES 03:08:39 this was my starting point: http://www.forth.org/svfig/kk/07-2010.html 03:09:09 but I'm working with the SDCC tool chain 03:22:08 --- join: true-grue (~true-grue@176.14.216.104) joined #forth 03:38:07 tg9541: okay, so I'm not sure how a programme for a talk relates to embedded systems 03:38:14 tg9541: what exactly are you trying to do? 03:42:15 --- join: JDat (JDat@89.248.91.5) joined #forth 03:57:22 hi gordonjcp 03:59:24 I'm trying to create a framework for programming very cheap hardware with 80s/90s technology, just to see how far one can get 04:02:59 I managed to port stm8ef.asm from a 32 KiB flash 2 KiB RAM STM8 Discovery to a 8 KiB flash 1 KiB $0.79 stm8s103f3 breakout board 04:04:10 I'm quite surprised by the performance - an empty FOR NEXT loop runs in about 1.5 us 04:06:48 I'm aware that eForth with Dr. Ting's "last stance" on popularizing an easy to use embeddable Forth system. Unfortunately the Forth community didn't provide "recipes" for building a teathered Forth around the eForth core. 04:13:47 --- quit: wa5qjh (Read error: Connection reset by peer) 04:17:35 --- join: wa5qjh (~Thunderbi@203.111.224.39) joined #forth 04:23:29 --- quit: dram (Quit: dram) 04:24:27 in eForth, user- ans system variables are merged, that's not a big deal. What I don't like is that the access to system variables like BASE appears to be hand coded. I guess that I'll have to refactor that 04:26:55 --- quit: wa5qjh (Remote host closed the connection) 04:37:15 tg9541: the general principle is that if your platform is pretty close it's easy to "port" stuff 04:37:28 tg9541: but frankly if you're doing anything deep to the code you may as well write your own 04:43:08 eForth is actually a rather solid foundation, and it's very well documented (may dialects build on it). Writing something around it also isn't a problem, but this little project isn't really about creating new things. It's about getting a better understanding of the achievements of a generation of Forth programmers. 05:08:00 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 06:47:58 --- join: bedah (~bedah@dyndsl-037-138-050-047.ewe-ip-backbone.de) joined #forth 07:11:19 --- join: mnemnion (~mnemnion@2601:643:8103:f9d0:507f:94f5:f1a3:eaaf) joined #forth 07:15:38 --- quit: mnemnion (Ping timeout: 250 seconds) 07:36:14 bye 07:36:19 --- quit: tg9541 () 08:02:42 --- quit: JDat (Ping timeout: 244 seconds) 08:09:46 --- join: proteusguy (~proteusgu@180.183.101.187) joined #forth 08:09:46 --- mode: ChanServ set +v proteusguy 08:31:49 --- join: impomatic_ (~digital_w@54.39.114.87.dyn.plus.net) joined #forth 08:35:15 --- quit: impomatic (Ping timeout: 244 seconds) 08:36:13 --- join: impomatic (~impomatic@20.122.208.46.dyn.plus.net) joined #forth 08:37:25 --- quit: impomatic_ (Ping timeout: 258 seconds) 08:48:14 --- join: JDat (~JDat@89.248.91.5) joined #forth 09:33:47 --- join: mnemnion (~mnemnion@2601:643:8103:f9d0:2411:1ffb:f03a:95c0) joined #forth 09:35:40 --- join: vsg1990 (~vsg1990@pool-173-64-14-42.bflony.fios.verizon.net) joined #forth 09:49:17 --- join: real-grue (~true-grue@176.14.216.104) joined #forth 09:53:00 --- quit: true-grue (Ping timeout: 246 seconds) 09:53:46 --- join: Kumool (~kumool@adsl-64-237-237-89.prtc.net) joined #forth 10:37:27 --- quit: JDat (Ping timeout: 246 seconds) 11:41:00 --- join: JDat (JDat@89.248.91.5) joined #forth 12:01:27 --- quit: JDat (Ping timeout: 240 seconds) 12:01:34 --- join: JDat` (~JDat@89.248.91.5) joined #forth 12:19:47 --- join: tg9541 (95acac53@gateway/web/freenode/ip.149.172.172.83) joined #forth 12:20:00 Hi 12:21:11 is anybody with some eForth experience around? 12:57:57 tg9541: well, I ported it to the DCPU-16þ 12:58:05 s/þ/./ 12:58:27 ran suprisingly quickly even at 100kHz 12:58:30 great :-) 12:59:54 to be honest, I had to look up DCPU-16 13:01:07 I've been spending some time to figure out how RAM is used in the eforth implementation I have 13:02:27 it took me some time to understand why in the middle of free RAM some ASCII character show up 13:03:08 you are talking about the pad here? 13:03:29 yes, right 13:03:40 I now understand the code 13:04:41 but this makes me wonder how much more I need to figure out by reverse engineering eforth before I can put it in a ROM 13:05:20 PAD, QAD, RAD 13:06:24 QAD and RAD are not implemented in my eforth 13:08:22 the size of the PAD area is 0x80 bytes - hmm 13:08:51 do you know how the interpreter deals with that space? 13:10:24 ah, I got that wrong - it's just 0x50 bytes 13:14:38 ok, got it. That's WORD 13:57:50 --- quit: nighty (Quit: Disappears in a puff of smoke) 14:13:32 tg9541: you need to understand each and every word/colon definition, why it is as it is and such 14:14:12 you are making rom for what kind of architecture? z80? 6502? RTX2000? 14:21:43 Zarutian: you're right. I'm about to dive into it. 14:22:09 Zarutian: stm8 14:23:49 my guess is that I have to traverse the vocabulary, and extract the required words for the ROM 14:52:38 bye 14:52:41 --- quit: tg9541 () 14:52:55 --- quit: bedah (Quit: Ex-Chat) 15:12:48 --- nick: Skuzzzy -> Skuzzy 15:14:17 --- quit: JDat` (Ping timeout: 244 seconds) 15:21:19 --- join: wa5qjh (~Thunderbi@203.111.224.39) joined #forth 16:09:17 --- quit: real-grue (Read error: Connection reset by peer) 16:25:40 --- quit: mnemnion (Remote host closed the connection) 16:28:17 --- join: mnemnion (~mnemnion@2601:643:8103:f9d0:2411:1ffb:f03a:95c0) joined #forth 16:37:13 daily reminder that forth is a terrible language 16:37:18 and noone should use it :) 16:51:46 --- quit: wa5qjh (Ping timeout: 244 seconds) 16:53:52 --- quit: Kumool (Ping timeout: 240 seconds) 16:57:37 --- join: malyn (~malyn@54.201.34.233) joined #forth 17:07:12 --- join: wa5qjh (~Thunderbi@203.111.224.39) joined #forth 17:07:22 --- quit: wa5qjh (Remote host closed the connection) 17:10:26 --- join: wa5qjh (~Thunderbi@203.111.224.39) joined #forth 17:12:15 --- quit: Zarutian (Quit: Zarutian) 17:22:12 --- join: dram (~Thunderbi@112.65.46.78) joined #forth 17:47:20 --- join: Kumool (~kumool@adsl-64-237-238-25.prtc.net) joined #forth 18:08:44 --- quit: dram (Remote host closed the connection) 18:09:03 --- join: dram (~Thunderbi@112.65.46.78) joined #forth 18:56:58 --- join: karswell (~user@31.185.131.182) joined #forth 19:01:29 --- quit: Kumool (Ping timeout: 258 seconds) 19:26:52 --- quit: wa5qjh (Ping timeout: 252 seconds) 19:45:13 --- quit: karswell (Remote host closed the connection) 19:46:22 --- join: karswell (~user@31.185.131.182) joined #forth 19:53:13 --- join: wa5qjh (~Thunderbi@203.111.224.39) joined #forth 20:23:26 --- quit: impomatic (Read error: Connection reset by peer) 20:23:57 --- join: impomatic (~impomatic@20.122.208.46.dyn.plus.net) joined #forth 20:41:04 --- join: dram1 (~Thunderbi@112.65.46.78) joined #forth 20:42:25 --- quit: dram (Ping timeout: 240 seconds) 20:43:01 --- nick: dram1 -> dram 20:54:33 --- join: Kumool (~kumool@adsl-64-237-238-153.prtc.net) joined #forth 21:41:14 --- join: bb010g (uid21050@gateway/web/irccloud.com/x-lfrqmgjehxvusaoy) joined #forth 22:44:53 --- quit: vsg1990 (Quit: Leaving) 23:01:35 --- quit: Kumool (Read error: Connection reset by peer) 23:13:50 --- join: dram1 (~Thunderbi@112.65.46.78) joined #forth 23:15:53 --- quit: dram (Ping timeout: 272 seconds) 23:15:53 --- nick: dram1 -> dram 23:33:25 --- quit: proteusguy (Ping timeout: 260 seconds) 23:59:59 --- log: ended forth/16.06.26