IRC Log - 2025-08-15 - ##forth

Channel: ##forth
Total messages: 14
Time range: 00:37:52 - 08:29:53
Most active: tpnix (9), veltas (4), xentrac (1)
00:37:52 ##forth <veltas> Congrats crc
02:04:09 ##forth <xentrac> I still don't have my personal computing system, but konilo is an inspiration
02:25:18 ##forth * tpnix just installed Swdcom on Nixos, so now I have my Mecrisp-Stellaris swd terminal back again :)
02:25:55 ##forth <tpnix> it's a Forth terminal that connects to the mcu via SWD, no usart needed
02:26:15 ##forth <tpnix> this makes the terminal independent of clock changes
02:26:32 ##forth <tpnix> it's also very fast, around 1Mbaud
02:27:53 ##forth <tpnix> because if the 512 char bufferm it can also print up to 512 chrs to the terminal in a couple of cpu clock cycles so 'printf' type debugging has no penality at all
08:04:09 ##forth <veltas> That sounds useful
08:07:12 ##forth <tpnix> it is massively useful on embedded systems
08:27:09 ##forth <veltas> I can attest to that, having had to do the workarounds for not having a seamless printf
08:28:00 ##forth <veltas> Although I've also encountered race conditions impacted by a few clock cycles!
08:28:29 ##forth <tpnix> yeah, I can imagine. Sadly it's always that way wether with Forth or C or whatever if the data is coming via a peripheral such as a USART
08:28:49 ##forth <tpnix> it screws everything up bigtime as you know
08:29:53 ##forth <tpnix> I saw that Segger offer a similar facility (printf over swd) with their very expensive products, but I get the same for free with Mecrisp-Stellaris and swdcom