00:00:00 --- log: started forth/20.03.08
00:21:24 --- quit: _whitelogger (Remote host closed the connection)
00:24:27 --- join: _whitelogger joined #forth
01:37:03 --- join: xek_ joined #forth
01:42:24 --- quit: _whitelogger (Remote host closed the connection)
01:45:27 --- join: _whitelogger joined #forth
03:32:34 --- join: dys joined #forth
04:20:22 <tpbsd> whohoo I just answered a 1 yer old stackexchange tech question after becoming familiar with the subject in my latest Forth project, this could be my second right answer so far :P
04:20:26 <tpbsd> year
05:53:33 --- quit: iyzsong- (Quit: ZNC 1.7.1 - https://znc.in)
05:53:56 --- join: iyzsong joined #forth
06:00:53 --- join: MrMobius joined #forth
06:01:57 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in)
06:07:42 --- quit: jsoft (Ping timeout: 256 seconds)
06:09:52 --- join: [1]MrMobius joined #forth
06:11:06 --- quit: MrMobius (Ping timeout: 256 seconds)
06:11:07 --- nick: [1]MrMobius -> MrMobius
06:25:06 --- quit: MrMobius (Ping timeout: 265 seconds)
06:26:25 --- quit: xek_ (Ping timeout: 256 seconds)
06:32:18 --- join: MrMobius joined #forth
07:10:23 --- quit: dys (Ping timeout: 255 seconds)
07:27:24 --- quit: _whitelogger (Remote host closed the connection)
07:30:27 --- join: _whitelogger joined #forth
07:49:22 --- join: gravicappa joined #forth
07:52:50 --- quit: dave0 (Quit: dave's not here)
07:56:45 --- join: dddddd joined #forth
08:26:03 --- join: [1]MrMobius joined #forth
08:28:14 --- quit: MrMobius (Ping timeout: 256 seconds)
08:28:15 --- nick: [1]MrMobius -> MrMobius
08:30:44 --- join: [1]MrMobius joined #forth
08:32:48 --- quit: MrMobius (Ping timeout: 258 seconds)
08:32:49 --- nick: [1]MrMobius -> MrMobius
08:40:28 --- quit: jfe (Ping timeout: 258 seconds)
08:58:08 --- quit: tabemann (Ping timeout: 240 seconds)
09:05:01 --- join: [1]MrMobius joined #forth
09:13:35 --- join: jfe joined #forth
09:14:51 --- join: xek_ joined #forth
11:15:19 --- join: [2]MrMobius joined #forth
11:17:40 --- quit: MrMobius (Ping timeout: 256 seconds)
11:18:37 --- join: MrMobius joined #forth
11:21:28 --- quit: [2]MrMobius (Ping timeout: 258 seconds)
11:23:37 --- quit: MrMobius (Ping timeout: 240 seconds)
11:31:16 --- join: [2]MrMobius joined #forth
11:43:36 --- quit: [2]MrMobius (Quit:  HydraIRC -> http://www.hydrairc.com <- In tests, 0x09 out of 0x0A l33t h4x0rz prefer it :))
11:44:14 --- join: MrMobius joined #forth
12:00:11 --- join: tabemann joined #forth
12:00:35 <tabemann> I'm fucking pissed off
12:00:43 <tabemann> AT&T seems to be blocking port 6667
12:01:07 <tabemann> so I can't use my home-made IRC client, Amphibian, here
12:02:53 <MrMobius> are they blocking it for religious reasons?
12:03:53 <tabemann> nah, probably for "security reasons"
12:04:02 <tabemann> as IRC over port 6667 is typically not encrypted
12:28:34 --- quit: jfe (Ping timeout: 265 seconds)
12:51:57 <Kumool> ha!
12:52:29 <Kumool> cant you do tunneling or w\e
12:55:21 --- join: jfe joined #forth
13:07:41 --- quit: jfe (Ping timeout: 255 seconds)
13:45:12 --- join: jfe joined #forth
13:48:23 --- quit: [1]MrMobius (Quit:  HydraIRC -> http://www.hydrairc.com <- s0 d4Mn l33t |t'z 5c4rY!)
14:03:41 --- quit: Lord_Nightmare (Quit: ZNC - http://znc.in)
14:05:31 --- join: Lord_Nightmare joined #forth
14:10:46 --- join: [1]MrMobius joined #forth
14:13:13 --- quit: MrMobius (Ping timeout: 240 seconds)
14:13:13 --- nick: [1]MrMobius -> MrMobius
14:24:42 --- quit: tabemann (Ping timeout: 258 seconds)
14:31:58 --- quit: jfe (Ping timeout: 268 seconds)
14:37:14 --- quit: xek_ (Ping timeout: 255 seconds)
14:45:24 --- quit: gravicappa (Ping timeout: 258 seconds)
14:59:40 --- join: jackdangers joined #forth
15:05:28 --- part: jackdangers left #forth
15:23:14 --- join: tp___ joined #forth
15:23:14 --- quit: tpbsd (Read error: Connection reset by peer)
15:29:52 --- quit: MrMobius (Quit:  HydraIRC -> http://www.hydrairc.com <- Like it?  Visit #hydrairc on Freenode)
15:37:27 --- join: MrMobius joined #forth
15:45:49 --- join: tabemann joined #forth
16:16:42 --- quit: MrMobius (Ping timeout: 265 seconds)
16:19:47 --- join: MrMobius joined #forth
16:31:53 --- nick: tp___ -> tp
16:56:12 --- join: [1]MrMobius joined #forth
16:58:07 --- join: [2]MrMobius joined #forth
16:59:14 --- quit: MrMobius (Ping timeout: 265 seconds)
17:01:11 --- quit: [1]MrMobius (Ping timeout: 265 seconds)
17:22:33 --- quit: [2]MrMobius (Quit:  HydraIRC -> http://www.hydrairc.com <- Go on, try it!)
17:23:12 --- join: MrMobius joined #forth
17:43:00 --- join: jfe joined #forth
17:47:35 --- quit: X-Scale (Ping timeout: 255 seconds)
17:47:56 --- join: X-Scale` joined #forth
17:48:23 --- nick: X-Scale` -> X-Scale
18:27:02 <Croran> Has anyone read Alan Kay's 2009 paper about 'the reinvention of programming'?
18:27:09 <Croran> It reminds me of Forth
18:27:11 <Croran> http://www.vpri.org/pdf/tr2009016_steps09.pdf
18:28:28 <tp> Croran, thanks for the link :)
18:34:20 <Croran> You're welcome. One of the things that struck me was the 'Model-T-Shirt Programming' and how it seems related to Forth words or Forth 'Screens'.
19:03:31 <tabemann> hey guys
19:03:41 <tp> hey tabemann 
19:04:03 * tabemann is currently working on a multitasker for zeptoforth
19:04:14 <tp> tabemann, Ive just made my first really simple scheduler for Mecrisp-Stellaris 
19:05:34 <tp> tabemann, I needed something that didn't use many resources to schedule operations such as the Touch Sense Controller running under a interrupt
19:07:03 <tp> Mecrisp-Stellaris has a cooperative multitasker but it uses 800 bytes of ram per task which is way too much for me plus intertask comms is at your ad-hoc pleasure
19:07:34 <tp> a simple scheduler just runs words at set intervals
19:07:59 <tabemann> mine can use far less than that if the user wishes to use really small stacks
19:08:25 <tabemann> the user doesn't need to use 256 bytes per stack
19:08:35 <tp> Croran, I'm a user of a more modern embedded forth, I use files on my pc instead of screens
19:09:12 <tp> tabemann, with really small embedded it's usually not a matter of choice, everything has to be really small
19:09:33 <tp> i have 64kB of flash and 8kB of ram, thats it
19:09:57 <tp> your M4 has virtually unlimited resources from my pov
19:10:42 <Croran> tp: Yeah. I still think the concept can be useful. I think the human brain works better with relatively small pieces of code, and the concept of the 'screen' tends to enforce such a presciption.
19:11:26 <tp> Croran, I definitely agree
19:12:12 <tp> Croran, we tend to keep our Forth Words short 3 - 4 lines so they can be independently tested and easily understood
19:13:04 <tp> here is a example of my proto scheduler task
19:13:07 <tp> : task-1 ( u -- ) 
19:13:07 <tp>    now-time? task1-time @ - swap u>= if
19:13:07 <tp>    blue-on ." blue-on  " now-time. cr
19:13:07 <tp>    now-time? task1-time !
19:13:07 <tp>    then
19:13:08 <tp>  ;
19:13:53 <Croran> nice
19:14:07 --- quit: jfe (Read error: Connection reset by peer)
19:14:15 <tp> Croran, I'm a electronics tech not a proper programmer
19:14:26 --- join: jfe joined #forth
19:14:28 <tp> Croran, but I manage to scrape by ;-)
19:15:54 <tp> I find one of the challenges with using interrupts is keeping the interrupt handler as short as possible and then handling the result, hence my recent need for a scheduler
19:16:34 <Croran> I installed Mecrisp on an STM32. It was pretty neat getting the Forth interpreter responding over serial.
19:17:19 <tabemann> getting Mecrisp-Stellaris working was a breeze
19:18:01 <tp> tabemann, I came across a stack-exchange question that related to the stm32 TSC peripheral that was 12 months old, the few respondents advised using a library as dealing with registers 'is too complex'
19:18:27 <tp> Croran, yes, Mecrisp-Stellaris is excellent, Ive been using it since 2014
19:19:09 <tp> tabemann, no one actually supplied a answer. I looked at all the config and found one was wrong :)
19:19:10 <tabemann> tp: ugh
19:19:24 --- quit: jfe (Ping timeout: 265 seconds)
19:20:18 <tp> this is one of the reasons that I think C sucks
19:20:21 <tp> TSC->IOSCR |= 0x04; //enable G1_IO3 (PA2) as sampling capacitor ** WRONG this is enabling G1_IO4 (PA3) not PA2
19:20:54 <tp> this business of |= 0x04 for instance
19:21:37 <tp> |= 0x01  means 'set bit 0'
19:22:30 <Kumool> ha
19:22:37 <tp> very confusing, and although the designer had got the TSC configs correct, which is not trivial, he bumbled on this
19:22:45 <tabemann> I am used to twiddling bits in C, but I see how that'd be misleading
19:23:13 <tp> tabemann, and Kumool yeah, very error prone I think
19:23:24 <tabemann> note that a lot of compsci students these days don't even know how to manipulate bits
19:23:34 <Kumool> and why would you
19:23:40 <Kumool> you don't need to
19:23:45 <Kumool> to display shiny webpages
19:24:09 <tabemann> as if web pages were the end all and be all of computing
19:24:48 <tabemann> when I was in school I learned MIPS assembly and digital logic design (even got to design and test a microprocessor), but these days...
19:24:50 <MrMobius> |=BIT0 also means set bit 0 if your header has BITx defined
19:24:54 <tp> Kumool, hahah
19:25:08 <Kumool> tabemann: are you a whoosh man?
19:25:15 <tabemann> whoosh?
19:25:27 <Kumool> as in, things just zoom past you
19:26:04 <Kumool> sorry, I forgot a /s in my comment
19:26:05 <tabemann> these days I do web programming for a living, but I'd prefer to do something closer to the metal
19:26:22 --- join: jfe joined #forth
19:26:35 <tabemann> but my job is convenient and pays well, so I stick with it
19:27:02 <Kumool> but we all use chromium tabemann 
19:27:04 <Kumool> that's a metal
19:27:42 <Kumool> maybe a browser called iron needs to be made
19:29:43 <tp> MrMobius, yeah, but it's interesting that after 1 year on stack-exchange no one picked that error up
19:31:00 <tp> MrMobius, I prefer "0 bit TSC_IOSCR bis!" myself
19:35:03 <tp> Kumool, I don't use chromium, it's modern crap that can't print to a LPRNG print spooler
19:39:22 <Kumool> tp: another woosh
19:50:15 --- join: boru` joined #forth
19:50:19 --- quit: boru (Disconnected by services)
19:50:21 --- nick: boru` -> boru
20:18:56 <tabemann> g'night guys
20:19:15 <tp> night tabemann 
20:36:25 --- quit: _whitelogger (Remote host closed the connection)
20:39:26 --- join: _whitelogger joined #forth
20:51:33 <Croran> Everyone's set their clocks foward today?
20:51:56 <tp> not in Australia :)
20:52:12 <Croran> ah, a sane government.
20:53:31 <tp> no, we have 'daylight saving' but currently we are in our spring, summer just finished and daylight saving wont end for a while yet
20:54:44 <Croran> oh really? so you change clocks too?
20:54:48 <Croran> lame.
20:54:54 --- join: rdrop-exit joined #forth
20:55:02 <tp> yeah
20:55:19 <rdrop-exit> Good morning Forthwrights c[]
20:55:22 <tp> if we don't the curtains turn yellow and the milk curdles ;-)
20:55:38 <tp> morning Zen Guru of Forth!
20:55:52 <rdrop-exit> Hi Forth Master Technician (tm)!
20:56:39 <tp> rdrop-exit, Ive just finished my first ever FSS (Forth simple scheduler)
20:56:53 <Croran> tp: haha
20:56:53 <rdrop-exit> cool!
20:57:04 <Croran> If it were up to me, everyone would be on GMT.
20:58:09 <tp> rdrop-exit, 
20:58:12 <rdrop-exit> No DST here
20:58:13 <tp>   0 variable taskx-time
20:58:13 <tp>   : task-x ( u -- )   \ functional basic example
20:58:13 <tp>     now-time? task1-time @ - time-interval-to-run-task-x u>= if
20:58:13 <tp>     do-stuff
20:58:13 <tp>     now-time? task1-time !
20:58:14 <tp>     then
20:58:16 <tp>   ;
20:58:24 <Croran> rdrop-exit: Arizona?
20:58:29 <rdrop-exit> Manila
20:58:47 <Croran> rdrop-exit: nice
20:58:51 <tp> rdrop-exit, ignore stack comment it's wrong
20:58:59 <rdrop-exit> ok :)
20:59:46 <tp> rdrop-exit, as the time-interval-to-run-task-x in now a parameter in my latest version
20:59:55 <tp> in = is
21:00:28 <tp> rdrop-exit, doesn't your milk curdle if you don't have DST ?
21:00:45 <rdrop-exit> life is simpler without DST
21:01:02 <rdrop-exit> don't really need it in a tropical country
21:01:24 <tp> o don't really notice it as my sundial is DST aware
21:01:29 <rdrop-exit> we don't really have seasons in the traditional sense
21:01:54 <rdrop-exit> just rain or no-rain
21:01:56 <tp> rdrop-exit, you just have 100% humidity or heavy rain ;-)
21:02:04 <rdrop-exit> yup
21:02:17 <rdrop-exit> (downloading the Alan Kay paper)
21:02:42 <tp> fortunately it's raining a bit today here, 25,25 C / 77,67 F
21:03:27 <tp> we are exactly the same as you rdrop-exit ... except we dont have the rain part
21:03:39 <rdrop-exit> 34C today
21:03:57 <tp> with rain ?
21:04:06 <rdrop-exit> no rain, sunny
21:04:16 <tp> I think some cyclone is affecting our weather
21:04:19 <Croran> rdrop-exit: What got me interested in that was Alan Kay's talk at CMU. If you don't have the patience for the paper, the talk is interesting too.
21:04:24 <Croran> https://www.youtube.com/watch?v=PFc379hu--8
21:04:39 <tp> Croran, are you a Forth user ?
21:05:01 <rdrop-exit> Thanks Croran, will check it out
21:05:03 <Croran> tp: I play with Forth and read about it, but I haven't built anything useful with it. lol
21:05:53 <tp> Croran, you're not alone in the Forth community, most programmers never actually make any devices that run Forth (imho)
21:06:03 <rdrop-exit> I remember liking some of Kay's writings, but I'm not a fan of some of his OO related musings
21:06:34 <tp> I'm the odd one out being a electronics tech and not a programmer, which makes me a 'Forth user' rather than a coder
21:07:09 <tp> so instead of making my own Forth, I use someone elses Forth in my devices
21:08:26 <Croran> tp: what kind of devices do you build with Forth?
21:08:30 <rdrop-exit> I'm a fan of blocks
21:09:05 <Croran> rdrop-exit: blocks?
21:09:47 <tp> coloured ones ?
21:09:53 <tp> ;-)
21:10:24 <tp> Croran, at the moment Im making a device that measures the number of times it's been touched
21:10:26 <rdrop-exit> 1k block/screens
21:10:35 <rdrop-exit> TMI tp
21:11:19 <tp> Croran, to do that it uses the 'touch sensing' peripheral in a STM32F0 micro controller
21:11:21 <rdrop-exit> oh sorry, I thought it measured the number of times you've been touched
21:11:23 <Croran> rdrop-exit: oh right, like in ColorForth?
21:11:32 <tp> rdrop-exit, hahah
21:11:43 <rdrop-exit> kinda yes, like in traditional forths
21:11:44 <Croran> tp: nice. is that peripheral built-in?
21:12:04 <tp> Croran, yes, is one of the 33 inbuilt peripherals
21:12:16 <Croran> tp: 33 huh. i need to read up on that.
21:12:37 <tp> Croran, this my test output, low numbers are when the sensor is touched
21:12:40 <tp> 4587 touched-flag 0 
21:12:40 <tp> 523 touched-flag 1 
21:12:41 <tp> 503 touched-flag 1 
21:12:41 <tp> 501 touched-flag 1 
21:12:41 <tp> 506 touched-flag 1 
21:12:42 <tp> 652 touched-flag 1 
21:12:44 <tp> 4894 touched-flag 0
21:13:10 <tp> Croran, the f0 is a very minimal device by stm32 standards
21:13:12 <rdrop-exit> I don't use source files in my forths, just blocks
21:13:24 <Croran> tp: nice. how does it work? accelerometer? or electrometer?
21:13:27 <rdrop-exit> some hold data, some hod source
21:13:54 <tp> Croran, it works by detecting a change in capacitance
21:14:14 <tp> Croran, the sensor is a 10x10 mm square copper pad on a pcb
21:14:33 <tp> that's all there is to it
21:14:36 <Croran> tp: oh! you're saying it's a stm32 dev board with a bunch of inbuilt peripherals?
21:15:17 <tp> Croran, it's a stm32 discovery board but the touch sensor is external, it's something I made with some scrap pcb
21:15:46 <Croran> tp: That's cool. I was thinking it would be neat to build a logging voltmeter for my car's battery as a Forth project.
21:15:48 <tp> Croran, Ive made 4 different sensors to compare them
21:16:02 <tp> Croran, thats a perfect project
21:16:13 <Croran> I was thinking I could probably use some kind of resistor voltage divider and connect the battery directly to an analog pin.
21:16:26 <tp> Croran, absolutely 
21:17:04 <tp> Croran, tho be sure to attach a couple of small colored wooden blocks to it as rdrop-exit assures me that Forth is better with blocks!
21:17:15 <Croran> tp: my 'blue pill' board has like 64KB of flash, and I think Forth has access to store data in the flash...
21:17:33 <Croran> lol. https://wiki.c2.com/?ForthBlocks
21:17:40 <tp> Croran, more than likely your 'blue pill' has 128lb flash
21:17:44 <tp> 128kB
21:18:09 <Croran> tp: well when i plug it into my counterfeit st-link v2 and use stlink-gui it reports 20k sram and 64k flash
21:18:22 <tp> Croran, yeah, they lie :)
21:18:41 <tp> Croran, get my free Forth binary, it will tell you: https://sourceforge.net/projects/mecrisp-stellaris-folkdoc/files/stm32fxx-diagnostics-v1.3.bin
21:18:44 <Croran> ah nice. so anyway seems like i could store a lot of logs in 64/128k
21:19:00 <tp> it will also tell you if the chip isnt a genuine stm32f103
21:19:12 <Croran> cool i'll try it. how do i get the output?
21:19:16 <rdrop-exit> Blocks aren't necessarily a second address space
21:19:33 <Croran> i've been using the micro usb for serial with mecrisp/stellaris
21:19:34 <rdrop-exit> (as described in that article you posted)
21:19:38 <tp> Croran, there are about 4 different fakes used in the bluepills
21:19:58 <tp> Croran, use the same micro-usb
21:20:12 <Croran> tp: nice. still will show up as /dev/ttyACM0 ?
21:20:35 <tp> Croran, https://mecrisp-stellaris-folkdoc.sourceforge.io/stm32f1xx-diagnostics.html#stm32f103xx-diagnostics tells you more
21:20:48 <tp> Croran, yes it will
21:21:12 <tp> the usb id is "Mecrisp STM32F10x Forth Serial Port, class 2/0, rev 2.00/2.00, "
21:22:01 <tp> Croran, it's under 64kB so openocd will be happy to flash it
21:22:09 <Croran> rdrop-exit: oh ok. are yours accessed in a different way?
21:23:14 <tp> Croran, yes, rdrop-exit inputs code into his Forth with a 'etch-a-sketch'
21:23:29 <tp> ;-)
21:24:56 <tp> Croran, my binary is a full Mecrisp-Stellaris so outside the menu, you can use it.
21:25:52 <rdrop-exit> On a PC Forth I just treat all the Forth's RAM as blocks.
21:26:47 <tp> rdrop-exit, when you look at each ram chip in a pc, they do look like little black blocks ...
21:27:45 <rdrop-exit> I can point my block editor/viewer to any block within the Forth's RAM.
21:28:14 <rdrop-exit> The lower so many blocks are the dictionary.
21:28:33 <tp> rdrop-exit, you've permanently altered how I see Forth with a comment you made a while ago while refactoring one of my Words when you wrote here ... "the data is on the stack already"
21:28:47 <rdrop-exit> cool :)
21:29:39 <tp> rdrop-exit, my days of using the return stack as a local variable may be over as a result
21:29:47 <rdrop-exit> The blocks beyond the dictionary can hold source or data
21:31:09 <tp> rdrop-exit, is it true that "Forth blocks are just a C programmers attempt at abstraction" ?
21:31:30 <rdrop-exit> tp, never heard that
21:31:45 <tp> rdrop-exit, i just invented it :)
21:32:10 <rdrop-exit> For me Forth blocks are just a useful unit of memory, just as is a byte, or 16,32,64 bits
21:32:20 <tp> as a tech I see memory as having a start and end, I cant see it as 'blocks'
21:32:53 <rdrop-exit> It's just a convenient chunking
21:33:59 <rdrop-exit> 1k is a convenient chunking for some things, 64k for others, 8 bytes for others, etc...
21:34:33 <rdrop-exit> it just so happens that I find it the most convenient chunking for source, and for a small viewport into memory
21:34:39 <Croran> tp: I loaded your diagnostic
21:34:46 <tp> i do admit when I used 'riscy pygness' I quite enjoyed using blocks
21:34:48 <Croran> tp: It appears to have found another 64K of flash
21:34:56 <tp> Croran, told ya :)
21:35:10 <tp> Croran, what does it think the chip type is ?
21:35:27 <Croran> tp: yeah so that's cool. I spent the last 5 minutes trying to figure out what the chip said on the top... The writing is very tiny and faint.
21:35:55 <tp> reading chip numbers can be hard, especially if they are fakes
21:36:01 <Croran> tp: It thinks it's an STM32F1 series
21:36:19 <tp> ahh, then it is a genuine chip :)
21:36:25 <Croran> nice
21:36:30 <Croran> not bad for $1.98
21:36:38 <tp> it's a genuine STM32F103C8
21:37:04 <rdrop-exit> tp, I find the index card metaphor of blocks more to my liking than the scrolling parchment metaphor of files
21:37:16 <tp> hard to beat considering it has a 2x xtals, switch, headers, and mcu
21:38:05 <tp> rdrop-exit, I'll have you know that I use only the highest quality Egyptian papyrus in my files!
21:38:19 <rdrop-exit> snazzy
21:39:06 <tp> Croran, the interesting thing about the STM32F103C8 is that they all seem to have 128KB of flash, BUT STM marked them internally as only having 64kB
21:39:48 <Croran> tp: yeah. to make sure it wasn't going to compete with their more expensive parts maybe? i wonder.
21:39:53 <tp> Croran, so openocd reads the internal 'flashsize register' which says '64kB' and thats what it uses
21:40:07 <Croran> tp: I wonder if it's underprovisioned so that it can do wear-leveling...
21:40:41 <tp> Croran, we all asume it was a marketing thing and that STM used the same die for the STM32F103C8 and the more expensive 128kB STM32F103B8
21:41:09 <tp> Croran, nah, that chip was designed in 2004, it's ancient
21:41:35 <Croran> tp: I was thinking it would be cool to find a chip with 4x or even 8x UARTs and build a serial terminal server for my Cisco lab. 
21:41:50 <tp> Croran, fortunately, my binary allows you to use the full 128kB 
21:42:00 <Croran> but none of the cheap ones seem to have more than maybe 2 UARTs
21:42:16 <Croran> tp: oh yeah? your modified mecrisp/stellaris?
21:42:26 <tp> Croran, your chip has 3 uarts I think
21:42:44 <tp> Croran, some stm32's have 6 uarts I think
21:43:25 <tp> Croran, modyfing the Mecrisp-Stellaris ram or rom is very easy, it's in system.s
21:43:38 <tp> then just rebuild the binary and youre done
21:44:16 <tp> Croran, it also uses USART2 with hardware handshaking as a alternative to the USB terminal if you want
21:45:13 <tp> just enter "-usb" at the prompt (but you'll need a terminal attached to USART2)
21:45:38 <tp> from that terminal you can go back to the USB with "+usb"
21:46:33 <tp> Croran, here is a cool thing, at your terminal on the BluePill enter "gpioa." <-- note the trailing period
21:46:41 <tp> or "rcc."
21:47:49 <Croran> tp: what's all that?
21:48:22 <tp> it's the actual real time values of the bits in those registers
21:48:46 <Croran> nice. and what do those registers correspond to?
21:48:53 <tp> check the 'reference' PDF for the stm32F1xx
21:49:40 <tp> GPIOA. are all the Port A registers and control the I/O
21:50:10 <tp> RCC. is the 'clock' register and controls all the peripherals
21:50:28 <tp> the names are CMSIS-SVD compliant as well
21:50:48 <tp> https://mecrisp-stellaris-folkdoc.sourceforge.io/register-generator.html#svd2forth
21:51:46 <tp> although OLD, the STM32F1 has 53 peripherals on board,	722 registers and 4833 bitfields
21:52:09 <tp> it's also running at 72 MHz in my binary, so it's not slow
21:53:09 <Croran> is gpio a parallel port?
21:53:52 <tp> Croran, yes
21:53:59 <tp> 16 bits wide
21:54:25 <Croran> oh ok. i didn't realize that. 
21:55:21 <tp> Croran, because it's such a old chip the gpio's are HORRIBLE to configure, don't think the more modern ones are the same because theyre not
21:55:33 <Croran> weird that some of my gpio pins are high...
21:56:08 <tp> the stm32f0 for instance came out in 2011 and the GPIOS's are much nicer to configure
21:56:47 <tp> they are in input,floading mode by default and picking up stray charges etc
21:56:54 --- quit: dddddd (Remote host closed the connection)
21:57:02 <tp> therye very sensitive in that mode
21:57:13 <tp> tho some may actually be high
21:57:57 <tp> GPIOA is used or the USART2, so some pins will be configured high
21:58:33 <tp> Croran, if you enter "words4" youll see all the Words on that system now
22:00:18 <Croran> that's a lot.
22:01:12 <Croran> is words4 a custom word? I was using just 'words' and the format it outputs is pretty annoying.
22:01:31 <tp> yeah, thats one of mine
22:02:09 <tp> everything after "--- Flash Dictionary ---" is stuff Ive added
22:02:26 <tp> tho only a small amount are my own Words
22:03:49 <Croran> do you know of a definition for a 'see' word for this platform?
22:05:18 <tp> sure
22:05:33 <tp> I had to take it out of that image to keep it small
22:06:39 <tp> but you can upload mecrisp-stellaris-2.5.3-orig/common/disassembler-m3.txt  to it
22:06:56 <tp> or whatever version of the release you have
22:07:25 --- quit: proteus-guy (Ping timeout: 260 seconds)
22:07:29 <tp> when you upload disassembler-m3.txt youll have the word "see"
22:08:19 <tp> see 2+ 
22:08:19 <tp> 00002046: 3602  adds r6 #2
22:08:19 <tp> 00002048: 4770  bx lr
22:08:19 <tp> Bytes: 4 ok.
22:08:49 <tp> tho my mod adds tha "Byte: .. " at the end
22:12:02 --- join: gravicappa joined #forth
22:12:35 <tp> bbs
22:18:13 <Croran> tp: I posted to your sourceforge thread with the xml file for my board :)
22:25:05 <Croran> I tracked down that disassembler-m3.txt
22:25:35 <Croran> and got it working
22:27:09 <Croran> yours words4 makes it look like 'ok.' is a word :)
22:27:15 <Croran> your*
22:29:24 <Croran> How do you get 80 I/Os with only 48 pins?
22:33:23 --- join: dave0 joined #forth
22:37:28 --- join: [1]MrMobius joined #forth
22:40:05 --- quit: MrMobius (Ping timeout: 255 seconds)
22:40:05 --- nick: [1]MrMobius -> MrMobius
22:45:48 --- quit: proteusguy (Ping timeout: 265 seconds)
23:02:23 --- join: proteusguy joined #forth
23:02:23 --- mode: ChanServ set +v proteusguy
23:04:23 --- quit: jfe (Ping timeout: 255 seconds)
23:07:26 --- join: jfe joined #forth
23:12:23 --- quit: jfe (Ping timeout: 265 seconds)
23:13:53 --- join: [1]MrMobius joined #forth
23:14:24 --- join: proteus-guy joined #forth
23:15:46 --- quit: MrMobius (Ping timeout: 265 seconds)
23:15:46 --- nick: [1]MrMobius -> MrMobius
23:22:47 --- join: jfe joined #forth
23:26:27 <proteus-guy> Good news! A very basic initial implementation of ActorForth is available for your critique and curiosity at https://github.com/scherrey/ActorForth !
23:26:48 <tp> Croran, great!
23:27:04 <rdrop-exit> proteus-guy, congrats!
23:27:16 <proteus-guy> It's type system is fundamental to the architecture - it performs word lookup priority based on the type at TOS then goes to global dict if not found.
23:27:32 --- quit: jfe (Ping timeout: 256 seconds)
23:27:47 <tp> Croran, you buy a STM32F103 in a larger package with more pins, they go up to 180 pins I think
23:27:57 <tp> proteus-guy, awesome!
23:28:04 <proteus-guy> This makes adding new compilers very simple because you put a compiler type on the stack as you define the new word and now you have compile time behavior for every available word. 
23:28:29 --- join: dys joined #forth
23:28:56 <proteus-guy> Right now there are no flow control or loops - next priority is pattern matching and recursion. Then flow control and loops and at that point it will be a "working" language.
23:29:17 <rdrop-exit> sounds very sophisticated
23:29:40 <proteus-guy> Entire thing is written in python. It's pretty small. Eventually it will be self hosted and also target Ethereum EVM.
23:29:48 --- join: jfe joined #forth
23:30:09 <rdrop-exit> I still haven't gotten around to taking a look at Python
23:31:42 <proteus-guy> rdrop-exit, haha here's your chance... ;-)
23:32:01 <rdrop-exit> guess so :)
23:32:18 <proteus-guy> I'm using the runtime type checking feature of Python so my code will look different than most.
23:32:23 <proteus-guy> (as most don't use it)
23:41:45 <Croran> tp: is the stm32G series a good upgrade in terms of peripherals and lower power usage?
23:44:47 <tp> Croran, I don't know
23:45:11 <tp> Croran, I mainly deal with the STM32F051 released in 2011 I think
23:45:18 <Croran> tp: the 'readout protection' feature is interesting
23:45:23 <Croran> tp: "Level 2: chip readout protection: debug features (Cortex-M0+ serial wire), boot in
23:45:23 <Croran> RAM and bootloader selection are disabled. This selection is irreversible."
23:45:38 <tp> Ive read that the G is pretty fast and capable, tons more than what I use
23:46:52 <tp> Croran, thanks for you xml file :)
23:47:11 <Croran> tp: you're welcome. thanks for your diagnostic :)
23:47:54 <Croran> tp: you know what would be an interesting exercise is to add an SRAM test. like memtest86+ where it just reads and writes patterns to verify consistent operation.
23:50:25 --- quit: jfe (Ping timeout: 240 seconds)
23:53:53 <tp> hehe, feel free to write one :)
23:55:02 <tp> this diagnostic was only to test the actual MCU as there is a BIG counterfeit problem, and to test the 'hidden' second 64kB flash block
23:55:17 <tp> it has to fit in 64kB as well
23:55:39 <Croran> tp: how much SRAM does the forth interpreter + dictionary take up?
23:56:00 <tp> you can find that out by typing "free"
23:56:18 <tp> it varies of course bepending whats loaded etc
23:56:22 <tp> depending
23:56:30 <Croran> ah interesting.
23:56:31 --- join: jfe joined #forth
23:56:38 <Croran> Used: 9412
23:56:51 <tp> generally 1.5kB of ram for a base system
23:58:15 <tp> Croran, that bluepill has been out for a long time, but still no C or any other OS created binary like mine to diagnose it
23:59:12 <tp> Croran, there have been 180 downloads of my original diagnostic program, but it wasnt as useful at this new one which youve just downloaded
23:59:16 <Croran> tp: nice
23:59:40 <Croran> tp: how would i drop all the extra stuff from SRAM and leave just the base system?
23:59:44 <tp> Croran, you managed to upload the dissasembler-m3.txt ok ?
23:59:59 --- log: ended forth/20.03.08