00:00:00 --- log: started forth/20.05.08 00:08:49 --- quit: dys (Ping timeout: 260 seconds) 00:23:23 --- join: dys joined #forth 00:32:08 --- quit: WickedShell (Remote host closed the connection) 00:32:30 --- join: xek joined #forth 00:51:57 --- join: Zarutian_HTC joined #forth 03:19:24 --- join: dddddd joined #forth 03:45:48 --- join: iyzsong joined #forth 03:45:55 --- quit: iyzsong (Changing host) 03:45:55 --- join: iyzsong joined #forth 04:04:16 --- quit: jsoft (Ping timeout: 240 seconds) 04:04:21 --- quit: tp (Read error: Connection reset by peer) 04:05:15 --- join: rdrop-exit joined #forth 04:36:47 --- join: tp joined #forth 04:36:47 --- quit: tp (Changing host) 04:36:47 --- join: tp joined #forth 04:53:34 --- quit: rdrop-exit (Quit: Lost terminal) 05:04:33 --- join: jsoft joined #forth 05:35:02 --- quit: jsoft (Ping timeout: 256 seconds) 05:47:26 --- quit: irsol (Ping timeout: 256 seconds) 05:52:59 --- join: irsol joined #forth 06:06:48 --- join: TCZ joined #forth 06:26:28 --- quit: iyzsong (Ping timeout: 244 seconds) 07:29:10 --- join: jsoft joined #forth 07:29:54 --- quit: dave0 (Quit: dave's not here) 07:44:21 --- join: cmtptr joined #forth 07:44:55 hello i am just checking in to see how my forth friends are doing during this the end of times 07:46:33 --- quit: TCZ (Quit: Leaving) 07:55:48 --- quit: Zarutian_HTC (Ping timeout: 272 seconds) 08:13:31 cmtptr: That is just end of time_t. 08:15:01 so what you're saying is that coronavirus hasn't canceled forth? 08:15:15 forth lives on 08:16:30 inside our heart 08:16:44 What is with all the drive-by greetings 08:17:11 We have been preparing for an apocalypse ever since. But it seems COVID-19 was a false alert. 08:17:52 veltas, people are trapped in their homes and getting lonely 08:26:15 --- join: Zarutian_HTC joined #forth 08:26:59 cmtptr: You're right 08:31:46 --- quit: jsoft (Ping timeout: 256 seconds) 08:44:08 thank you for saying so 08:53:24 You know me I'm all about positive reinforcement 09:31:10 --- join: WickedShell joined #forth 10:14:12 --- quit: Zarutian_HTC (Quit: Bye) 10:28:09 --- quit: dys (Ping timeout: 240 seconds) 12:56:48 --- quit: cheers (Ping timeout: 246 seconds) 13:05:39 --- join: dys joined #forth 13:09:19 --- join: cheers joined #forth 13:46:04 --- quit: cheers (Ping timeout: 260 seconds) 14:04:34 --- join: cheers joined #forth 15:01:32 --- join: Zarutian_HTC joined #forth 15:03:56 --- quit: gravicappa (Ping timeout: 246 seconds) 15:42:09 --- join: dave0 joined #forth 15:50:25 --- join: TCZ joined #forth 15:59:02 --- quit: TCZ (Quit: Leaving) 17:40:16 I'm all for reinforcements 17:41:18 Hi tp 17:41:36 hey crc, how goes RETRO ? 17:42:07 it progresses nicely 17:42:16 crc, I'm still loving being able to do a 'fossil update' on you, it's a sheer pleasure! 17:43:27 :) 18:06:20 hey guys 18:07:30 hey tabemann, how goes Zeptoforth 18:08:00 still working on the disassembler i see 18:08:07 yep 18:08:12 yousaid it would take a while 18:08:30 it's long, back-breaking labor 18:08:54 caring loaded baskets of assembly syntax on your head ? 18:09:02 carrying 18:09:07 yep 18:09:20 I can picture it 18:10:26 if you imagine the vista of infinity, reaching out into time unknown .... that's how long it would take me to write one 18:11:06 so I'll just do doc and svd2forth plus make forth powered gear I think 18:11:37 lol 18:12:12 actually working on the disassembler is just a simple matter of programming - almost all coding and very little thought 18:13:01 --- join: boru` joined #forth 18:13:04 --- quit: boru (Disconnected by services) 18:13:07 --- nick: boru` -> boru 18:13:28 tabemann, I looked at your elaboration of using lambdas, but I'm still confused, perhaps you could write a blinky using them if you get the time ? 18:14:00 tabemann, i'll be happy to assist with any hardware related issues you may run into 18:14:35 * tp finds not thinking while coding a perplexing conundrum 18:17:44 well it's primarily significant when one has registers with multiple fields where one wants to modify only certain fields and not others 18:19:03 which is what one does when blinking a led 18:19:35 or infact any peripheral use 18:19:46 it's *all* about bitfields to me 18:21:06 note that for many purposes they aren't necessary, e.g. ones where one can use bic! and bis! 18:21:26 I still believe that trying to work with registers and not bitfields is totally wrong for embedded, but so far I'm debating programmers that have never actually made a working blinky, ie their theories are as yet untested 18:23:27 tabemann, even bic! and bis! are often not needed as cortex-m has atomic single bit manipulation commands 18:24:30 tabemann, meaning that there is no need to read and mask before setting particular peripheral bits 18:24:57 tabemann, for data there are no such aids 18:25:31 tabemann, but thats what makes embedded different, the MCU manufacturers anticipate and design for this kind of need 18:26:28 my lambda approach is useful when one wants to set multiple bits both on and off simultaneously as a single write 18:30:52 and thats useful 18:57:54 --- join: rdrop-exit joined #forth 18:58:26 good morning forthwrights c[] 19:01:07 Good evening rdrop-exit 19:01:22 hi crc :) 19:01:24 --- quit: dddddd (Ping timeout: 256 seconds) 19:03:46 http://dpaste.com/3C4BVJ3 19:04:43 hey rdrop-exit 19:04:53 hey crc 19:05:00 hi tabemann 19:05:15 tp: that's an example of what I as talking about 19:08:39 tabemann, thanks! 19:11:47 tabemann, did you test it ? I assume it's for your L476 disco ? 19:12:20 hey rdrop-exit, Zen Guru of Forth! 19:12:28 hi tp 19:14:15 a lot of jumping through hoops in that code 19:15:46 rdrop-exit, I'm keeping a open mind because my mind has a lot of unused dusty space for Forth concepts 19:16:26 what's wrong with 19:16:37 rdrop-exit, once that code is known to work I'll compare it against what I would do 19:16:43 set 19:16:58 clear 19:17:01 rdrop-exit, for a start no mask is needed 19:17:21 the mask is the field 19:17:46 14 11 bits constant %tickler 19:18:02 %tickler toggle 19:18:15 %ticker clear 19:18:18 bits can be set and cleared atomically with no mask 19:20:06 cortex-m has special hardware just for that purpose 19:20:22 you give the mask the name of the field it identifies 19:21:08 you may, I don't 19:21:49 %xreg-writable xreg %! 19:22:23 (a masked store to the writable fields of xreg) 19:23:05 1 2 lshift GPIOB_BSRR ! 19:23:22 or "2 bit GPIOB_BSRR !" 19:23:32 done 19:25:11 sure, you're overwriting an entire register, that's fine 19:25:21 xreg ! 19:25:34 no I'm not 19:25:38 2 bit xreg ! 19:25:58 you have ignored what I wrote earlier 19:26:17 I see a ! 19:26:38 so ? 19:26:49 what does a ! do? 19:27:16 if you're system is 32 bits a store overwrites 32 bits 19:27:20 the important question here is what does a "GPIOB_BSRR !" do ? 19:27:47 stores 32 bits somewhere, unless you're using bit-banding 19:28:09 true, still fine as written 19:28:21 cortex-m has special hardware just for that purpose 19:28:34 yes 19:28:43 rdrop-exit, you need to understand that GPIOB_BSRR is *special* 19:29:17 it's designed especially to set bits atomically, it cant even be read 19:29:46 youd be wasting your time trying to read it 19:30:04 I'm not trying to read it 19:32:43 and no point using a mask, it will ignore all cleared bits 19:33:55 what do you think your "2 bit" results in? it's a mask with the bit #2 set 19:34:07 you can understand it better by reading this doc: https://mecrisp-stellaris-folkdoc.sourceforge.io/_downloads/stm32f0x-reference_manual.pdf and searching for "BSRR" 19:35:35 rdrop-exit, perhaps I have a different understanding of the word 'mask' to you, that could be a cause of confusion here 19:36:18 to me, "2 bit" = %100 19:36:35 yes 19:37:03 i dont see it as a 'mask' at this point in my lacklustre programming career 19:37:13 but Im often wrong 19:38:04 --- join: jsoft joined #forth 19:38:07 I always understood a 'mask' to be a number used to 'filter' another number to remove undesired bits 19:38:54 usually by oring or anding etc 19:39:50 that too 19:40:24 anyway I'm not sure why you bought up, GPIOB_BSRR 19:42:44 what dont you understand about it ? 19:43:00 why you brought it up 19:43:16 sure, you're overwriting an entire register, that's fine 19:43:21 thats why 19:43:53 yes, and your code and mine are identical in that case, as seen above 19:44:03 your comment indicated you didnt understand that GPIOB_BSRR is designed for this use 19:44:53 no, your code is abstract, there is no 'xreg' in a cortex-m 19:45:23 our code has nothing in common 19:45:38 (apart from the !) 19:46:45 * tp orders another bottle of Kahlua Coffee Liqueur so he can withstand rdrop-exit's programmer only viewpoint! 19:47:13 wow 19:48:33 luckily they reduced the price but this tactic forced me to buy a 1l bottle :) 19:48:45 ah well, I'll do my best to cope 19:50:54 maybe the kahlua will help 19:51:18 one can hope ... 19:51:27 it can only help 19:53:19 * tp is out for some exercise, bbl 19:53:28 have fun 20:04:03 tabemann, as a rule of thumb if you're producing a combinatorial explosion of words you're not facttoring 20:05:23 combinatorial explosions only show up at the lowest level, e.g. 16@ 32@ etc... 20:06:00 * factoring 20:26:39 bbl 20:38:09 --- quit: rdrop-exit (Quit: Lost terminal) 22:32:30 --- part: tp left #forth 22:52:53 --- join: jedb_ joined #forth 22:56:59 --- quit: jedb (Ping timeout: 264 seconds) 22:58:28 --- join: gravicappa joined #forth 23:21:27 Look at the usual suspects being nerds in here again :P 23:59:59 --- log: ended forth/20.05.08