00:00:00 --- log: started forth/20.02.06 00:05:18 proteusguy, thanks for asking that question, it prompted me to go and find out how the Forth I use deals with exceptions 00:07:54 https://mecrisp-stellaris-folkdoc.sourceforge.io/common.html#exceptions 00:12:26 --- join: jedb joined #forth 00:13:20 --- quit: jedb__ (Ping timeout: 268 seconds) 00:16:51 --- quit: xek (Remote host closed the connection) 00:17:17 --- join: xek joined #forth 01:17:17 --- quit: WickedShell (Remote host closed the connection) 01:19:37 --- quit: X-Scale (Ping timeout: 240 seconds) 01:20:48 --- join: [X-Scale] joined #forth 01:21:02 --- nick: [X-Scale] -> X-Scale 02:04:19 --- quit: xek (Ping timeout: 268 seconds) 02:38:23 --- join: mtsd joined #forth 03:18:21 --- quit: dys (Ping timeout: 260 seconds) 03:37:01 --- quit: ryke (Ping timeout: 260 seconds) 05:19:13 --- quit: jhei (Ping timeout: 246 seconds) 05:21:55 --- quit: dave0 (Quit: dave's not here) 05:45:35 --- join: ryke joined #forth 05:52:21 --- join: dddddd joined #forth 05:54:22 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 05:56:55 --- quit: ryke (Ping timeout: 260 seconds) 06:03:16 --- join: jhei joined #forth 07:26:14 --- quit: jsoft (Ping timeout: 265 seconds) 07:34:40 --- quit: mtsd (Quit: Leaving) 07:40:50 --- quit: dddddd (Remote host closed the connection) 07:42:06 --- quit: tabemann (Ping timeout: 252 seconds) 08:23:46 --- join: deesix_ joined #forth 08:26:15 --- quit: deesix (Ping timeout: 260 seconds) 10:59:18 --- join: dys joined #forth 11:51:06 --- join: dddddd joined #forth 12:15:16 --- join: ryke joined #forth 12:29:39 --- join: WickedShell joined #forth 12:48:11 --- nick: deesix_ -> deesix 12:52:03 --- quit: a3f (*.net *.split) 12:52:15 --- join: a3f joined #forth 13:08:00 --- quit: gravicappa (Ping timeout: 240 seconds) 13:36:46 --- join: jsoft joined #forth 14:18:23 --- join: dave0 joined #forth 14:34:22 --- quit: ryke (Ping timeout: 268 seconds) 15:18:55 --- quit: dys (Ping timeout: 272 seconds) 15:22:05 --- quit: jsoft (Ping timeout: 272 seconds) 15:22:31 --- join: jsoft joined #forth 15:26:56 --- quit: dave0 (Read error: Connection reset by peer) 15:28:20 --- join: dave0 joined #forth 16:05:41 in the context of making an assembler, would it be reasonable to have e.g. R0 R1 R2 SUBr, where R0-Rn are just aliases for the literals 0-n and SUBr, figures out how to encode them? 16:06:20 or is there a better way that lets one continue to have prefix instructions, infer whether you need the register or immediate version of instructions, etc 16:06:54 I've seen the latter without an explanation, but idk if it was doing "real parsing" instead of just having a special dictionary 17:21:56 --- join: tabemann joined #forth 17:33:14 remexre, mecrisp-across now uses under-bar before all assembler mnemonics such as: 17:33:18 _srli x15 x15 2 17:33:18 _bne x15 zero - 17:33:18 _mv x8 x14 17:33:55 How is it doing the parsing tho? 17:36:57 --- join: ryke joined #forth 17:37:30 --- quit: tpbsd (Ping timeout: 248 seconds) 17:59:55 --- quit: dave0 (Read error: Connection reset by peer) 18:02:14 --- join: dave0 joined #forth 18:08:36 --- quit: tabemann (Ping timeout: 256 seconds) 18:09:15 --- quit: dddddd (Read error: Connection reset by peer) 18:39:37 --- join: rdrop-exit joined #forth 18:45:21 --- join: boru` joined #forth 18:45:25 --- quit: boru (Disconnected by services) 18:45:27 --- nick: boru` -> boru 19:10:27 --- join: iyzsong joined #forth 19:14:02 good morning Forthwrights c[] 20:11:02 --- join: tabemann joined #forth 20:19:06 --- join: gravicappa joined #forth 20:47:27 --- quit: proteusguy (Ping timeout: 268 seconds) 21:00:31 --- join: proteusguy joined #forth 21:00:31 --- mode: ChanServ set +v proteusguy 21:12:49 --- quit: ryke (Ping timeout: 240 seconds) 21:37:02 --- quit: Lord_Nightmare (Quit: ZNC - http://znc.in) 21:37:53 --- join: Lord_Nightmare joined #forth 21:45:36 --- join: tp joined #forth 21:45:36 --- quit: tp (Changing host) 21:45:36 --- join: tp joined #forth 23:08:20 rdrop-exit, 107 downloads of my Forth STM32F103C8-DIAGNOSTICS.bin now :) 23:08:44 That's a lot of forthing! 23:09:09 proteusguy, and 99% are by windows using arduino types 23:09:26 proteusguy, I doubt they even know it's a Forth system 23:09:42 kudos tp! 23:10:01 proteusguy, it's a diagnostic program to identify fake STM32F103 mcu's 23:10:16 rdrop-exit, I never thought it would get that high 23:10:28 rdrop-exit, I figured it would top out at 42 23:11:02 so rdrop-exit how is your flu, the volcano etc ? 23:11:12 there a lot of fakes going around or just rumours of fakes? 23:11:32 brb, have a call 23:11:34 proteusguy, tons of fakes, it's not a rumour 23:12:39 proteusguy, the one real fake is a chip marked "cks cs32f103C8", and not even the CKS factory lists it in their products, yet they're everywhere 23:13:27 proteusguy, it's been decapped and is not a copy, it's a clone, the big problem is it identifies itself as a STM32F103 in all it's ID registers 23:14:26 wow that would be annoying. so how do you tell? 23:15:08 proteusguy, another clone is the GD32F103, it's made by Giga Devices and marked accordingly, so it's a legit alternative implementation, but some unscrupulous sellers are sanding off the GD label and printing STM32F etc 23:15:42 so it's still identically functional just lying about the brand manufacturer? 23:16:25 the 'clones' are "compatible" definitely not identical, and thats the problem 23:17:27 one unexpected flag is that the original STM32F103 has a number of errata that were never fixed and never will be as that chip is long obsolete having been out since 2004 23:18:22 one of the most serious errata is that the debug register cannot be read from a user program running on the chip *unless* the debug hardware is attached 23:18:52 ironically the clones all seem to have fixed that issue! 23:19:55 so my V2 of this diagnostic binary tries to read that register, and if it cant, then the chip is very likely a bonafide STM32f103 23:28:57 haha 23:29:19 yeah, who'd have thunk it ? 23:31:25 proteusguy, to get an idea of how endemic counterfeit chips are, take a long look at this site https://zeptobars.com/en/ it's russian, but the pics are just awesome, and they also compare the clones to the bonafides, note it takes a few hours 23:31:54 but id very interesting if one is into clear chip die pics 23:32:34 proteusguy, they must have some *very* serious gear to make those pics 23:35:17 universities have such stuff and they let kids play on them. ;-) 23:35:57 impressive images indeed 23:37:39 I'm impressed, I have some good gear but my pics look lame in comparison 23:37:47 good hobby gear 23:48:43 --- quit: _whitelogger (Remote host closed the connection) 23:51:31 --- join: _whitelogger_ joined #forth 23:59:59 --- log: ended forth/20.02.06