00:00:00 --- log: started forth/14.08.20 00:14:37 --- join: true-grue (~grue@128-68-48-84.broadband.corbina.ru) joined #forth 00:19:16 --- quit: tangentstorm (Ping timeout: 255 seconds) 00:33:13 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #forth 01:31:05 --- quit: tangentstorm (Ping timeout: 240 seconds) 01:34:10 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #forth 02:42:01 --- join: Zarutian (~zarutian@194-144-22-152.du.xdsl.is) joined #forth 02:58:03 --- quit: true-grue (Read error: Connection reset by peer) 03:02:45 --- join: protist (~javery@152.225.69.111.dynamic.snap.net.nz) joined #forth 03:16:59 --- join: proteusguy (~proteusgu@ppp-110-168-229-245.revip5.asianet.co.th) joined #forth 03:29:31 --- quit: xyh (Remote host closed the connection) 03:46:42 --- quit: Zarutian (Quit: Zarutian) 03:51:46 --- quit: karswell (Remote host closed the connection) 03:52:07 --- quit: cataska (Remote host closed the connection) 03:52:13 --- join: karswell` (~user@87.113.161.27) joined #forth 03:54:43 --- join: cataska (~cataska@118-163-69-1.HINET-IP.hinet.net) joined #forth 04:00:38 --- join: _spt_ (~Jaat@unaffiliated/-spt-/x-5624824) joined #forth 05:10:23 --- join: nighty-_ (~nighty@hokuriku.rural-networks.com) joined #forth 05:11:12 --- join: saml_ (~saml@pool-71-190-11-242.nycmny.east.verizon.net) joined #forth 05:18:35 --- quit: saml_ (Ping timeout: 260 seconds) 05:21:47 --- join: dys (~user@2a01:1e8:e100:8296:21a:4dff:fe4e:273a) joined #forth 05:22:41 --- join: _spt2_ (~Jaat@host-92-12-216-141.as43234.net) joined #forth 05:25:13 --- quit: _spt_ (Ping timeout: 250 seconds) 05:30:09 --- join: Zarutian (~zarutian@194-144-22-152.du.xdsl.is) joined #forth 05:31:28 --- join: saml_ (~saml@pool-71-190-11-242.nycmny.east.verizon.net) joined #forth 05:35:00 --- quit: _spt2_ (Ping timeout: 245 seconds) 05:51:06 --- part: saml_ left #forth 06:03:51 --- join: Bahman (~Bahman@188.159.194.50) joined #forth 06:26:05 --- quit: joneshf-laptop (Ping timeout: 240 seconds) 06:37:25 --- quit: proteusguy (Ping timeout: 240 seconds) 06:42:04 --- join: joneshf-laptop (~joneshf@98.208.35.89) joined #forth 06:47:47 Are there any Forths that choose to focus on Streams and functional reactive programming? 08:03:58 --- join: pgomes (d4b9b9a4@gateway/web/cgi-irc/kiwiirc.com/ip.212.185.185.164) joined #forth 08:11:32 --- join: mr-foobar (~mucker@49.206.19.125) joined #forth 08:12:24 --- quit: pgomes (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client) 08:39:31 --- join: proteusguy (~proteusgu@ppp-110-168-229-245.revip5.asianet.co.th) joined #forth 08:48:08 --- join: true-grue (~grue@128-69-60-102.broadband.corbina.ru) joined #forth 09:08:04 OK so who's been building forths on rasberry-pi or arduinos lately? I've been away for a few years. :) 09:15:29 --- join: kumul (~mool@adsl-72-50-85-136.prtc.net) joined #forth 09:17:22 --- quit: protist (Quit: Konversation terminated!) 09:46:49 --- quit: kumul (Quit: Leaving) 09:52:11 --- join: c00kiemon5ter (~c00kiemon@foss-aueb/coder/c00kiemon5ter) joined #forth 09:54:25 --- join: Bahman_ (~Bahman@188.159.8.167) joined #forth 09:54:40 --- quit: Bahman (Disconnected by services) 09:54:46 --- nick: Bahman_ -> Bahman 10:32:31 i think there are a few arm forths (rpi) and also an avrforth 10:33:26 my own arm/thumb forth is still languishing in a broken state but ttmrichter seems to be making progress 10:33:47 and i had zero luck with the rpi and hand crafted asm 10:54:19 --- join: DKordic (~user@212-200-213-118.dynamic.isp.telekom.rs) joined #forth 11:09:40 --- quit: Zarutian (Quit: Zarutian) 11:30:04 Wow it sounds like there hasn't been much progress on that front since I was here a few years ago. Bummer. Got a link to ttmrichter's arm/forth? 11:31:07 --- quit: nighty-_ (Ping timeout: 240 seconds) 11:35:29 --- join: nighty-_ (~nighty@hokuriku.rural-networks.com) joined #forth 11:36:46 i don't think he's releasing it until he's happy with it. so unfortunately no. 11:37:02 bc i wanted to peek and see ifi could figure out what wasn't working with mine 12:25:08 is this a full system forth or something that runs on top of linux or some other os? 12:36:14 mine is not - i don't think his is either - we're targeting stm32 demo boards (at least i am and got the idea from him) 13:07:26 --- quit: karswell` (Read error: Connection reset by peer) 13:55:18 --- quit: Bahman (Quit: zzZZ) 14:11:16 --- quit: mr-foobar (Ping timeout: 245 seconds) 14:12:51 --- join: mr-foobar (~mucker@49.206.19.125) joined #forth 14:28:07 --- quit: mr-foobar (Ping timeout: 240 seconds) 14:29:17 --- join: mr-foobar (~mucker@49.206.19.125) joined #forth 14:45:07 --- quit: joneshf-laptop (Ping timeout: 240 seconds) 14:45:32 --- join: joneshf-laptop (~joneshf@98.208.35.89) joined #forth 14:51:09 proteusguy: http://quozl.linux.org.au/ ... not quite arduino and raspberry pi, but close. i doubt it would be difficult to port to rpi, the main task is build chain and uart. 14:52:21 general question: i'm looking for ideas on extending dictionary into EEPROM, so that definitions can be made in the field, so to speak. 15:00:25 --- quit: true-grue (Read error: Connection reset by peer) 15:21:13 --- quit: nighty-_ (Quit: Disappears in a puff of smoke) 15:35:23 --- join: ehaliewicz (~user@c-67-188-3-109.hsd1.ca.comcast.net) joined #forth 15:57:55 --- join: kumul (~mool@adsl-72-50-87-166.prtc.net) joined #forth 16:13:08 --- quit: proteusguy (Ping timeout: 264 seconds) 16:26:18 --- join: proteusguy (~proteusgu@ppp-110-168-229-245.revip5.asianet.co.th) joined #forth 16:30:51 --- quit: ehaliewicz (Remote host closed the connection) 16:31:42 --- join: ehaliewicz (~user@c-67-188-3-109.hsd1.ca.comcast.net) joined #forth 16:41:00 --- quit: ehaliewicz (Remote host closed the connection) 16:41:38 --- quit: MrMobius (Disconnected by services) 16:41:51 --- join: MrM0bius (~Joey@c-98-223-189-47.hsd1.in.comcast.net) joined #forth 16:42:04 --- join: nighty-_ (~nighty@hokuriku.rural-networks.com) joined #forth 16:58:52 --- quit: kumul (Ping timeout: 246 seconds) 17:00:34 --- quit: nighty-_ (Ping timeout: 255 seconds) 17:16:48 --- quit: danfinch (Quit: WeeChat 0.4.1) 17:22:02 Quozl`: Take a look at Mecrisp for extending into EEPROM. 17:22:07 --- quit: tangentstorm (Ping timeout: 240 seconds) 17:23:53 ttmrichter: thanks. 17:25:11 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #forth 17:25:40 --- join: kumul (~mool@adsl-72-50-87-166.prtc.net) joined #forth 17:30:11 --- quit: kumul (Ping timeout: 260 seconds) 17:59:50 --- join: beretta (~beretta@cpe-74-135-127-101.swo.res.rr.com) joined #forth 18:01:46 --- quit: beretta (Client Quit) 18:02:38 --- join: beretta (~beretta@cpe-74-135-127-101.swo.res.rr.com) joined #forth 18:07:09 join #raspberrypi 18:10:54 join #raspberrypi 18:11:21 --- join: danfinch (~danfinch@69.59.125.205) joined #forth 18:20:03 Why? 18:20:04 Why? 18:21:31 :) 18:22:12 I forgets me "/" 19:04:57 --- quit: TodPunk (Ping timeout: 240 seconds) 19:09:19 --- join: TodPunk (Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 19:12:50 --- join: kumul (~mool@adsl-72-50-87-166.prtc.net) joined #forth 19:23:08 --- quit: TodPunk (Ping timeout: 240 seconds) 19:25:06 I'd join #raspberrypi if I had a Raspberry Pi that actually worked. 19:25:22 I am thus far entirely underwhelmed by the RPi. 19:25:28 Worst piece of kit I've ever bought. 19:27:45 --- join: saml_ (~saml@pool-71-190-11-242.nycmny.east.verizon.net) joined #forth 19:29:32 --- join: TodPunk (~Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 20:14:19 --- join: MrMobius (~Joey@c-98-223-189-47.hsd1.in.comcast.net) joined #forth 20:16:40 dummer. mine was pretty cool. can't get asm working on it tho i'm sure that's my issue bc linux runs just fine 20:16:49 bummer*, even 20:16:57 --- quit: MrM0bius (Ping timeout: 260 seconds) 20:17:55 My issue is it doesn't display. 20:18:02 My monitor says there's no signal. 20:18:06 Makes it a wee tad hard to use... 20:18:54 i've never used it with a monitor. all i had to do was unpack an image onto an SD card, boot it with ethernet connected, and then ssh to it. 20:18:57 yeah. hrm, no clue. mine worked once i got the sd setup properly - something with the way i piped dd thru pv maybe - but once i stopped the fancy stuff it booted right up 20:19:08 i used pv with no trouble. 20:19:26 i also use the 3.3V serial without trouble. 20:19:30 bluekelp: The monitor issue is a known problem. 20:19:39 The basic problem is that the RPi wasn't engineered. 20:19:57 maybe that's why it's so cheap 20:20:07 Their "engineer" just took an SoC, a network chip and connected things up without paying much attention to, you know, actually having things work. 20:20:21 having tried to make a product with HDMI (the OLPC XO-4), i can well understand the NRE for RPi to achieve reasonably HDMI compatibility. 20:20:59 Seriously, if you look at the board it's just got traces from the SoC almost directly to the various peripheral pins. They have a few of the mandatory glue components here and there, but there's been no real thought put into making them work. 20:21:08 NRE? 20:21:46 If it doesn't work with just drawing a trace from the pin to the peripheral (with perhaps some mandatory minimalist glue) they don't bother. 20:22:08 huh. i guess this explains why the SoC they chose isn't fully open or documented (publicly) 20:22:32 i'm sure it's documented if you pay for a commercial license 20:22:40 The sloppiness shows in the pseudo-random placement of connectors, the uneven and random placement of external jacks, etc. 20:22:57 They chose the SoC they did because one of the RPi principals works/worked for Broadcom. 20:23:11 The RPi is basically an ad for Broadcom. 20:23:27 But ... right now it's a pretty negative ad. Because I sure as fuck won't be buying any Broadcom devices after this fiasco. 20:23:39 The Cubieboard? Made me look closer at the Allwinner line. 20:23:53 Assorted embedded kit made me look closer at STMicroelectronics. 20:24:13 A bunch of kit from TP-Link, plus some independents, made me look closer at Qualcomm. 20:24:21 i like the look of the beaglebone better than the rpi. nre, non-recurring engineering effort. 20:24:43 I've got a literally thumbnail-sized module that is a full Wifi router. 20:24:53 With a daughterboard that provides the connectors. 20:25:31 Works perfectly out of the box. Unlike the RPi. Even has the OS (OpenWRT) pre-flashed. Unlike the RPi. 20:26:03 i haven't found a use for my rpi yet. i did consider porting cforth to it, but the price per module kept making me think twice. 20:26:10 http://item.taobao.com/item.htm?id=36485130954 20:26:23 and i really don't need _that_ much memory. 20:27:03 I'm now really looking closer at the Atheros line because of that little toy module. 20:31:25 it really boils down to "good stuff" not being "popular stuff". nothing much new about that problem. 20:33:58 Indeed. 20:34:11 A lot of my favourite kit is wildly unpopular. :) 20:34:29 http://i.imgur.com/f7c3CTr.jpg 20:34:36 Here's some of my favourite kit put together. 20:34:47 You've probably never seen any of those components except possibly the ultrasound ranger. 20:35:07 This is my favourite dev board (and the current target for my Forth environment because it's so cramped): http://i.imgur.com/D9FKXnt.jpg 20:37:33 what is it called, and where can it be purchased from? 20:38:37 It's called the "STM32F030F4 Minimal System Board" (lovely name!) and I got it from Taobao. 20:39:02 http://item.taobao.com/item.htm?id=36481303532 20:39:04 There. 20:39:13 About $2.50 each. 20:39:24 thanks. cforth has an stm32l1xx discovery port. 20:39:42 MeCrisp has ports for even smaller chips. 20:39:59 I can almost fit a MeCrisp into that board. With a bit of surgery I think I could actually make it fit and have room for a small program. 20:40:14 yes. i'm reminded i choose cforth because of experience and familiarity. 20:40:17 (And with a TSSOP20 form factor a small program is pretty much all you're going to get.) 20:46:46 --- part: DKordic left #forth 20:49:49 --- quit: TodPunk (Read error: Connection reset by peer) 20:50:34 --- join: TodPunk (Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 21:06:07 --- quit: TodPunk (Read error: Connection timed out) 21:12:41 --- join: TodPunk (Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 21:34:11 ttmrichter, what are the cpus on your boards that you're playing with? 21:34:30 Currently they're mostly STM32s, a couple are STM8s. 21:36:19 --- quit: saml_ (Quit: Leaving) 21:38:00 --- quit: proteusguy (Remote host closed the connection) 21:52:16 --- quit: cataska (Remote host closed the connection) 22:08:22 --- join: cataska (~cataska@118-163-69-1.HINET-IP.hinet.net) joined #forth 22:18:52 --- quit: kumul (Quit: Leaving) 22:50:21 --- quit: tangentstorm (Ping timeout: 264 seconds) 22:51:45 i detect that i have resisted getting into jtag. all the jtag related trauma i've heard from others may have had something to do with it. 22:54:57 --- quit: TodPunk (Read error: Connection reset by peer) 23:10:26 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #forth 23:28:47 --- join: Bahman (~Bahman@188.159.8.167) joined #forth 23:30:44 --- join: proteusguy (~proteusgu@180.183.110.46) joined #forth 23:59:59 --- log: ended forth/14.08.20