00:00:00 --- log: started forth/19.12.27 00:20:56 --- quit: smokeink (Read error: Connection reset by peer) 00:23:35 --- join: smokeink joined #forth 00:50:35 --- quit: rcabaco (Ping timeout: 248 seconds) 01:50:29 --- join: rcabaco joined #forth 02:26:12 --- join: iyzsong joined #forth 03:05:05 --- quit: jsoft (Ping timeout: 258 seconds) 03:32:47 --- quit: jimt[m] (Quit: killed) 03:33:00 --- quit: siraben (Quit: killed) 03:33:14 --- quit: nonlinear[m] (Quit: killed) 04:07:40 --- join: jedb_ joined #forth 04:10:26 --- quit: jedb (Ping timeout: 260 seconds) 04:22:51 --- join: dys joined #forth 04:26:04 --- join: jedb__ joined #forth 04:27:34 --- nick: jedb__ -> jedb 04:29:06 --- quit: jedb_ (Ping timeout: 260 seconds) 04:36:04 --- join: nonlinear[m] joined #forth 04:36:04 --- join: siraben joined #forth 04:36:04 --- join: jimt[m] joined #forth 05:18:06 --- quit: iyzsong (Ping timeout: 260 seconds) 05:31:16 --- join: dddddd joined #forth 05:47:37 --- quit: smokeink (Ping timeout: 240 seconds) 05:49:27 --- quit: X-Scale (Ping timeout: 265 seconds) 08:29:04 --- join: Keshl__ joined #forth 08:29:47 --- quit: Keshl_ (Ping timeout: 248 seconds) 09:10:49 --- quit: dave0 (Quit: dave's not here) 09:29:47 --- join: jsoft joined #forth 09:44:28 --- join: smokeink joined #forth 09:58:25 --- quit: smokeink (Ping timeout: 240 seconds) 10:40:45 --- join: smokeink joined #forth 10:51:28 --- quit: smokeink (Quit: Leaving) 10:56:27 --- quit: dys (Ping timeout: 248 seconds) 11:23:40 --- join: ryke joined #forth 12:22:55 --- join: X-Scale joined #forth 13:49:24 --- quit: gravicappa (Ping timeout: 265 seconds) 15:32:01 --- quit: ryke (Ping timeout: 240 seconds) 15:53:25 --- join: ryke joined #forth 16:30:01 --- quit: ryke (Ping timeout: 240 seconds) 17:17:50 --- join: rdrop-exit joined #forth 17:34:29 --- join: smokeink joined #forth 19:24:32 --- join: iyzsong joined #forth 19:28:35 --- join: ryke joined #forth 20:50:05 --- join: gravicappa joined #forth 20:53:05 --- quit: dddddd (Remote host closed the connection) 20:57:52 --- join: dave0 joined #forth 21:10:08 G'day Forthlanders, anyone working on any interesting tech ? 21:10:41 --- quit: ryke (Ping timeout: 258 seconds) 21:17:54 Hello tp! 21:18:52 g'day rdrop-exit ! 21:21:07 --- quit: smokeink (Remote host closed the connection) 21:21:14 source RISC-V - XDS - DM - DMI Bus Registers - Abstract Command 21:21:14 $ 17 constant command 21:21:14 31 24 bits constant %command.cmdtype 21:21:14 23 0 bits constant %command.control 21:21:47 --- join: smokeink joined #forth 21:21:56 (taking nots as I read) 21:23:10 is your RISC-V bursting at the debug seams ? 21:23:49 that looks like interesting hitech 21:23:53 I downloaded the debug spec, I'm making "code" notes as I read along 21:24:00 ah 21:25:25 I always make extensive notes in my Forth sourcecode but theyre all stripped before upload so the net slowdown is 0% 21:26:13 thats the BLOCKS equivalent of my 'semi tethered' Forth ;-) 21:26:21 :) 21:27:24 I'm just going to interactively control the cores via JTAG and the debug spec 21:27:40 it would make the standard 9600 baud terminal upload where the on chip Forth has to read and reject comments unbearably painful tho 21:28:00 No comments, no source 21:28:27 The source and comments stay on the host PC 21:28:36 yes I know you are. You do have comments and source somewhere tho before the binary hits the metal 21:28:54 Only on the host 21:29:06 yeah of course 21:29:47 I did do a test once and found that approx 17% of my source is comprised of comments 21:30:07 With the debug interface I'll be able to halt cores, write to their registers or memory without sending any source 21:31:01 All your cores are belong to us 21:31:03 sure, tho the binary commands you do send will hopefully be influenced by Forth source at the beginning ;-) 21:31:29 and hopefully they will a facility for all the comments you need 21:32:01 Im a monocore man myself, I have enough problems with only one core 21:33:11 Yes, it'll be Forth words on the host that lay down object code, and also Forth words on the host that control the target and write the object code to the target's memory 21:33:31 I tend to make gear that lives in the electromechanical world, where events proceed glacially from the viewpoint of even a 8Mhz mcu 21:33:34 (including flash) 21:34:18 sure, typical tethering, very similar to mecrisp-across (msp430) 21:34:46 I doubt I'll do anything but monocore, but it's nice to know that their debug interface handles multi-core sceanrios 21:34:57 * scenarios 21:36:15 altho I appreciate that your system is a self bootstrapping, homogeneous, leading edge historically based Forth, using the latest in phase locked dipthon retarding code 21:36:16 This all assumes I'm capable of decyphering this spec and make practical use out of it 21:36:41 (and then I still have to learn the ISA) 21:36:58 :)) 21:37:06 multicore debug will be a real noodle twister I think 21:38:42 it also assumes the spec is complete and implemented properly ... like always ;-) 21:39:02 As usual the problem with standards is all the optional stuff 21:39:17 I know there is a ton of RISC-V specs still not complete and may not be for years 21:39:21 absolutely 21:40:15 I'll probably do my initial tests with a board from SiFive, since their the most active players in producing the spec 21:40:25 good plan 21:40:27 * they're the most ... 21:41:00 --- join: ryke joined #forth 21:41:16 the Chinese RISC-V chips will come and go, I wouldnt put much effort into them until they have been around a decade or so 21:41:23 I'm in no rush, I don't have a killer app/product in mind anyway 21:41:37 I think those days are gone 21:42:15 these days the only real 'killer apps' are in missile guidance 21:42:25 shhh 21:43:09 mankind is jaded to the max now, not much surprises us anymore 21:43:31 I'm being called for late lunch, catch you later Forth Master Technician 21:43:43 --- quit: rdrop-exit (Quit: Lost terminal) 21:43:46 reusable first stage rockets ?... great, whats for dinner ? 21:43:58 cya layer Zen Forth Guru 22:54:14 --- quit: smokeink (Remote host closed the connection) 23:47:57 --- join: proteus-guy joined #forth 23:59:59 --- log: ended forth/19.12.27