00:00:00 --- log: started forth/20.02.13 00:05:49 --- join: mtsd joined #forth 00:10:01 --- quit: WickedShell (Remote host closed the connection) 00:35:20 --- quit: mtsd (Ping timeout: 265 seconds) 00:51:23 --- join: dys joined #forth 01:22:37 --- quit: pierpal (Ping timeout: 268 seconds) 01:34:19 --- join: pierpal joined #forth 02:02:30 --- join: mtsd joined #forth 02:05:43 --- quit: smokeink (Ping timeout: 265 seconds) 02:11:20 --- join: iyzsong-x joined #forth 02:12:33 --- quit: iyzsong (Ping timeout: 260 seconds) 02:29:33 --- quit: proteus-guy (Ping timeout: 272 seconds) 02:51:43 --- quit: iyzsong-x (Ping timeout: 272 seconds) 03:00:22 --- join: iyzsong joined #forth 03:15:52 --- join: jsoft joined #forth 03:23:35 --- join: dave0 joined #forth 03:24:51 --- join: jedb_ joined #forth 03:27:49 --- quit: jedb (Ping timeout: 272 seconds) 03:30:21 --- quit: pierpal (Ping timeout: 272 seconds) 03:34:14 --- join: pierpal joined #forth 03:39:27 --- quit: pierpal (Read error: Connection reset by peer) 03:39:49 --- join: pierpal joined #forth 03:48:25 --- quit: deesix (Ping timeout: 240 seconds) 03:48:34 --- join: deesix joined #forth 03:50:23 --- quit: pierpal (Read error: Connection reset by peer) 04:14:19 --- join: pierpal joined #forth 04:18:25 --- quit: pierpal (Ping timeout: 240 seconds) 04:37:43 --- join: pierpal joined #forth 04:50:09 --- quit: jsoft (Ping timeout: 272 seconds) 04:50:31 --- quit: pierpal (Ping timeout: 246 seconds) 05:34:20 --- join: jsoft joined #forth 05:36:44 --- join: dddddd joined #forth 05:38:44 --- join: smokeink joined #forth 05:39:32 --- quit: iyzsong (Read error: Connection reset by peer) 05:56:03 --- join: pierpal joined #forth 06:05:40 --- quit: jsoft (Ping timeout: 268 seconds) 06:25:26 --- quit: cartwright (Ping timeout: 240 seconds) 06:31:46 --- join: cartwright joined #forth 06:36:52 --- quit: pierpal (Read error: Connection reset by peer) 06:37:03 --- join: pierpal joined #forth 06:47:53 --- quit: smokeink (Ping timeout: 260 seconds) 07:08:10 --- quit: mtsd (Quit: Leaving) 07:39:49 --- quit: tabemann (Ping timeout: 240 seconds) 08:12:56 --- quit: dave0 (Quit: dave's not here) 08:26:54 --- join: smokeink joined #forth 09:07:55 --- quit: smokeink (Ping timeout: 272 seconds) 09:12:56 --- join: smokeink joined #forth 09:17:13 --- quit: smokeink (Ping timeout: 240 seconds) 09:43:04 --- join: smokeink joined #forth 09:48:51 --- quit: pierpal (Quit: Poof) 09:49:10 --- join: pierpal joined #forth 10:00:26 --- quit: dys (Ping timeout: 248 seconds) 10:06:43 --- quit: pierpal (Read error: Connection reset by peer) 10:53:49 --- quit: smokeink (Ping timeout: 260 seconds) 11:44:30 --- join: pierpal joined #forth 12:07:52 --- join: WickedShell joined #forth 13:25:41 --- quit: xek (Ping timeout: 272 seconds) 13:50:23 --- quit: gravicappa (Ping timeout: 272 seconds) 14:39:24 --- join: dave0 joined #forth 15:52:41 --- quit: pierpal (Read error: Connection reset by peer) 15:59:40 --- join: veltas joined #forth 16:08:05 Am I misunderstanding UM/MOD or is gforth broken? 16:08:15 2147483648 S>D 2 UM/MOD 16:08:52 This should divide/mod by 2, on gforth I get a divide-by-zero 16:09:31 My reading of the standard is that this should be legal http://forth-standard.org/standard/core/UMDivMOD 16:11:30 I get 2147483648 S>D 2 UM/MOD u. 3221225472 16:11:41 thats using Mecrisp-Stellaris on a 32 bit micro 16:14:55 Oh I am making a silly mistake, S>D is of course treating it as a signed number 16:15:52 The result actually doesn't fit 16:16:02 s>d ( n - - d ) Makes a signed single number double length 16:17:44 This is an ambiguous situation because 2147483648 is negative with 32-bit integers, and so it becomes a very large unsigned double integer which the result of dividing by 2 does not fit into a single cell 16:18:07 I should just replace S>D with 0 16:19:04 to turn 2147483648 into a double ? 16:19:09 Yes 16:19:19 --- join: tabemann joined #forth 16:19:28 Given that I want to semantically treat it as an unsigned promotion 16:19:41 2147483648 0 2 m/mod u. 1073741824 16:20:07 m/mod ( d n1 - - n2 n3 ) d / n1 = n3 remainder r2 16:53:35 I'm frustrated by that there appears to be no 64-bit division instruction in thumb-2 16:56:41 pr`etty sure there is 64 bit result 16:57:02 but as it's only a 32 bit chip ... 17:37:41 but even x86 (not x86-64) supports 64-bit math (or else you wouldn't be able to use long long under gcc) 17:39:50 and how does mecrisp-stellaris do its 64-bit fixed numbers without support for 64-bit division? 18:01:00 --- quit: dddddd (Remote host closed the connection) 18:19:29 --- quit: proteusguy (Ping timeout: 240 seconds) 18:22:54 --- join: proteusguy joined #forth 18:22:54 --- mode: ChanServ set +v proteusguy 18:26:56 --- join: rdrop-exit joined #forth 18:38:29 --- join: boru` joined #forth 18:38:32 --- quit: boru (Disconnected by services) 18:38:34 --- nick: boru` -> boru 18:46:45 c[] good morning forthwrights 19:12:55 --- join: iyzsong joined #forth 19:20:07 tabemann: you can do long division with shifts and subtracts, but it's slow 19:21:11 it's also a lot of code compared do a simple "div" 19:24:17 even C doesn't provide it, you have to roll your own or use a non-standard compiler intrinsic 19:24:31 --- join: jsoft joined #forth 19:33:41 --- quit: Croran (Ping timeout: 260 seconds) 19:36:28 --- join: Croran joined #forth 19:44:13 --- quit: Croran (Ping timeout: 265 seconds) 19:46:54 --- join: Croran joined #forth 19:47:45 g'day Zen Forth Guru! 19:53:17 --- quit: actuallybatman (Ping timeout: 272 seconds) 19:54:01 hello Antipodean Master Forth Technician (tm)! 19:56:20 my forth diagnosic menu now has 3 sub menues and they integrate flawlessly! 19:56:42 kudos 19:56:54 my simple program has grown into a monster! 19:57:55 have you had a chance to do any coding or still slumming amid the ash ? 19:59:00 I coded the basic interface to JTAG last night. 20:00:10 Im glad that the Australian volcanoes are all so old they're worn out, and we have had so much rain that all but 29 fires are out now. Some were burning for 6 months 20:00:23 cool 20:00:50 excellent, you will have to get a real chip to test it against sometime ? 20:02:42 absolutely, for the moment I'm just going by what it says in the specs, I'm sure reality will be much messier 20:06:08 rdrop-exit, you my be interested in this post I saw today: https://www.eevblog.com/forum/microcontrollers/risc-v-microcontrollers-from-gigadevice/msg2917468/#msg2917468 20:06:29 this poster is having issues with risc-v jtag 20:12:12 It seems he's having issues with his tools 20:13:22 his last post says that on another computer with different tools it works 20:14:00 i think he is having jtag issues 20:14:18 (Note: On another computer, with another longan nano, with a jlink 10.1, with embedded studio for RISCV, blinky works). 20:14:48 I havent used jtag with my GD chip yet, Ive only programmed it via USB bootloader and even that has a mistake in silicon 20:15:24 yeah, one worked, one didnt, but that may be indicative of GD issues 20:15:48 the jtag tools world is very stable these days 20:16:24 my jtag adaptor is circa 2014 and I use it still 20:17:38 It's not just the adaptor, there's also the SW tools that use the adaptor 20:17:46 in fact I bought 2 units in 2014 from Olimex at about $65 each 20:17:55 yes, for sure 20:19:04 and the tool makers will most likely be reading the same docs you are 20:19:41 I won't be using any 3rd party software except the driver/library for the FTDI FT232H chip 20:20:27 I know 20:22:51 If the GD32VF103 is buggy, I will avoid it 20:25:06 it's pretty much the only useful risc-v chip around atm afaik 20:25:28 I have a couple, it's interesting, one can buy the boards but not the individual chips 20:25:41 and the boards are in the $5 range 20:27:14 I also received a ESP-vroom board as part of one of the GD boards, and that should run 'punyforth' which looks quite interesting 20:27:26 at around 200MHz 20:27:35 I'm not familiar with punyforth 20:28:14 it looks damn good from my pov, but I'm only curious. Its made by an Australian 20:28:24 cool 20:28:26 and been around a few years now 20:29:24 but Im not using anything in production that doesnt have the kind of dev support I have for Mecrisp-Stellaris on cortex-m 20:30:05 makes sense 20:31:08 to me it's *all* about development support 20:31:49 this is my current diags menu, but it's a 'smart menu' and alters depending on the chip 20:31:52 ------- 20:31:53 Summary 20:31:53 ------- 20:31:53 External Markings: STM32F103C8 20:31:53 Part: STM32F1 series 20:31:53 Serial Number: $D43BA754 20:31:57 Flash bytes, declared: 65536 20:31:59 128kB Flash present 20:32:49 It would have to be when you rely on someone else's Forth. 20:32:52 even tho it's serial, at 460800 bps the menu appears slmost instantly 20:33:02 cool 20:33:13 and someone elses chips ;-) 20:33:44 and someone elses soldering iron ... 20:34:03 well it's my iron, but designed and built by someone else 20:35:45 sure 20:35:46 i have finally done up the schematic info I needed to try the GD32VF jtag myself, all I need now is to hook up a olimex unit to it and see if it works 20:35:57 cool 20:42:25 --- quit: _whitelogger (Remote host closed the connection) 20:45:28 --- join: _whitelogger joined #forth 21:00:17 --- join: pierpal joined #forth 21:22:54 --- join: gravicappa joined #forth 23:38:15 --- join: X-Scale` joined #forth 23:38:45 --- quit: X-Scale (Ping timeout: 272 seconds) 23:39:09 --- nick: X-Scale` -> X-Scale 23:59:59 --- log: ended forth/20.02.13