00:00:00 --- log: started forth/20.01.23 00:01:50 --- quit: siraben (Ping timeout: 250 seconds) 00:02:00 --- quit: jimt[m] (Ping timeout: 246 seconds) 00:03:20 --- join: gabc joined #forth 00:03:20 --- join: KipIngram joined #forth 00:03:20 --- mode: weber.freenode.net set +v KipIngram 00:43:36 --- quit: WickedShell (Remote host closed the connection) 00:46:09 --- join: iyzsong joined #forth 00:46:09 --- join: chunkypuffs joined #forth 00:46:09 --- join: heredoc joined #forth 00:46:09 --- join: diginet2 joined #forth 00:46:09 --- join: dzho joined #forth 00:46:09 --- join: newcup joined #forth 00:46:09 --- join: dbucklin joined #forth 01:10:13 --- join: xek joined #forth 01:54:11 --- quit: proteus-guy (Ping timeout: 265 seconds) 02:01:05 rdrop-exit: morning 02:01:48 good evening WilhelmVonW 02:03:09 how goes? 02:08:01 --- join: dys joined #forth 02:23:46 sorry, working 02:23:54 it's alright I suppose 02:24:25 really have a hankering to work on a Forth FPGA 02:24:41 cool 02:26:02 how art thou rdrop-exit 02:27:31 --- quit: jsoft (Ping timeout: 260 seconds) 02:28:59 --- quit: deesix_ (Ping timeout: 265 seconds) 02:29:51 gives you the freedom to have SRAM stacks 02:30:16 I'm good, working on a JTAG tether 02:31:18 I kind of want the main stack as a stack-cum-fifo 02:31:29 some kind of trigger word to switch processing mode 02:31:45 I like circular stacks 02:32:28 --- join: proteus-guy joined #forth 02:32:36 as do I, my university project was basically a Retro Forth rip-off with circular double-width stacks 02:32:45 but you could split the stacks at will 02:32:57 cool 02:33:01 so have one double-width stack or two single-width stacks 02:33:07 it was way too complicated to be useful. 02:34:27 For an FPGA based Forth, I like to have 2 pairs of hardware stacks and two IPs for 2 tasks hardware level cooperative tasks 02:35:56 1-bit task-select register to switch between them 02:35:58 --- join: deesix joined #forth 02:38:31 Only two tasks, foreground, background, any concurrency beyond that is handled by coroutines 02:42:02 (truly parallel stuff is in other circuits on the FPGA, the CPU is more for overall orchestration) 02:43:15 similar to the roll a shell plays on an OS 02:44:42 yeah 02:48:34 * role 02:50:12 For now I've kinda lost interest in FPGAs, focusing on grokking RISC-V 02:51:14 (at a very leisurely pace though, around an hour a day) 02:53:10 --- quit: proteus-guy (Ping timeout: 268 seconds) 02:56:29 Right now I'm focused on the tether for controlling and programming the target from a PC based Forth. 02:59:11 --- join: proteus-guy joined #forth 03:00:37 Basically you end up with two different Forths, a full-blown cross-assembling/compiling one on the PC, and a headerless one on the target. The headers for the target are on the PC. 03:01:19 The target just holds runtime code. 03:03:37 Basically the classic tethered/umbilical Forth setup except using JTAG as the underlying tether channel. 03:03:47 --- quit: proteus-guy (Ping timeout: 265 seconds) 03:16:56 --- join: proteus-guy joined #forth 03:18:24 Although classic tethered Forths don't need an onboard outer-interpreter/compiler or headers on the target, they do require having a serial monitor, the advantage of JTAG is that you don't even need that, you can interactively control and program the target via the JTAG pins and the debug infrastructure of the target. 03:25:19 --- join: dddddd joined #forth 03:55:07 --- join: siraben joined #forth 03:55:07 --- join: jimt[m] joined #forth 03:55:07 --- join: nonlinear[m] joined #forth 04:23:13 --- quit: jn__ (Ping timeout: 240 seconds) 05:48:58 --- quit: iyzsong (Ping timeout: 246 seconds) 05:58:42 --- quit: proteus-guy (Ping timeout: 258 seconds) 06:30:48 --- quit: rdrop-exit (Quit: Lost terminal) 06:54:54 --- quit: gravicappa (Ping timeout: 268 seconds) 07:00:46 --- join: proteus-guy joined #forth 07:16:39 --- quit: dave0 (Quit: dave's not here) 07:47:11 --- quit: dddddd (Ping timeout: 260 seconds) 07:51:47 --- join: ryke joined #forth 07:58:30 --- join: gravicappa joined #forth 09:47:21 --- quit: dys (Ping timeout: 245 seconds) 10:56:27 --- nick: [X-Scale] -> X-Scale 11:27:26 --- quit: cartwright (Ping timeout: 240 seconds) 11:27:54 --- quit: ryke (Ping timeout: 268 seconds) 11:30:04 --- join: dddddd joined #forth 11:31:41 --- join: cartwright joined #forth 11:34:47 --- join: dys joined #forth 12:05:27 --- join: WickedShell joined #forth 12:09:03 --- join: jn__ joined #forth 12:13:11 --- quit: dys (Ping timeout: 260 seconds) 12:25:34 --- quit: jn__ (Quit: leaving) 12:39:43 --- join: jn__ joined #forth 13:18:43 --- quit: WickedShell (*.net *.split) 13:18:43 --- quit: Keshl (*.net *.split) 13:18:45 --- quit: cheater (*.net *.split) 13:24:37 --- join: Keshl joined #forth 13:26:32 --- join: cheater joined #forth 13:40:29 --- quit: gravicappa (Ping timeout: 268 seconds) 13:42:12 --- join: dys joined #forth 13:52:44 --- quit: jn__ (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) 13:53:18 --- join: jn__ joined #forth 13:56:31 --- quit: jn__ (Client Quit) 13:56:48 --- join: jn__ joined #forth 13:57:49 --- quit: jn__ (Client Quit) 13:58:03 --- join: jn__ joined #forth 14:02:04 --- join: WickedShell joined #forth 14:06:11 --- join: ryke joined #forth 14:23:13 --- quit: xek (Ping timeout: 240 seconds) 14:28:21 --- join: jedb_ joined #forth 14:31:16 --- quit: jedb (Ping timeout: 265 seconds) 15:23:46 --- quit: ryke (Ping timeout: 265 seconds) 16:01:27 is there a way to get a long string of binary data into your forth program other than separating them by c, ? 16:16:40 --- nick: jedb_ -> jedb 16:22:20 --- quit: proteus-guy (Remote host closed the connection) 16:23:45 --- join: proteus-guy joined #forth 16:43:46 --- join: jedb_ joined #forth 16:46:01 --- quit: jedb (Ping timeout: 240 seconds) 17:00:59 --- join: dave0 joined #forth 17:07:01 --- nick: jedb_ -> jedb 17:34:45 --- quit: proteus-guy (Ping timeout: 265 seconds) 18:09:43 --- join: iyzsong joined #forth 19:01:02 --- join: jsoft joined #forth 19:02:33 --- join: jsoft_ joined #forth 19:06:38 --- quit: jsoft_ (Client Quit) 19:06:51 --- quit: jsoft (Quit: Leaving) 19:07:06 --- join: jsoft joined #forth 19:07:19 --- quit: jsoft (Client Quit) 19:07:38 --- join: jsoft joined #forth 20:49:02 --- join: tp joined #forth 20:49:02 --- quit: tp (Changing host) 20:49:02 --- join: tp joined #forth 20:49:48 37,25 C / 99,04 F at this desk :) 21:18:26 --- quit: dddddd (Read error: Connection reset by peer) 21:26:02 --- join: gravicappa joined #forth 22:17:23 --- join: X-Scale` joined #forth 22:17:52 --- quit: X-Scale (Ping timeout: 268 seconds) 22:18:36 --- nick: X-Scale` -> X-Scale 23:58:38 MrMobius: you can write your own immediate function that lets you enter a long stream of bytes 23:58:48 s/function/word/ 23:59:59 --- log: ended forth/20.01.23