00:00:00 --- log: started forth/20.03.28 01:22:13 --- quit: nonlinear (Ping timeout: 268 seconds) 01:31:37 --- join: nonlinear joined #forth 01:39:23 --- join: mtsd joined #forth 01:45:05 --- quit: mtsd (Quit: Leaving) 04:22:11 --- quit: rdrop-exit (Read error: Connection reset by peer) 05:59:08 --- quit: iyzsong (Ping timeout: 240 seconds) 07:07:15 --- join: dddddd joined #forth 07:23:10 --- join: xek joined #forth 08:32:08 --- quit: jsoft (Ping timeout: 265 seconds) 08:49:12 --- join: proteus-dude joined #forth 08:53:02 --- quit: proteus-guy (Ping timeout: 260 seconds) 09:21:56 tabemann, I find when I set the systick interrupt period too fast the mcu becomes unreliable as least as far as the terminal is concerned 09:29:33 I've found that too 09:30:05 what I was actually doing was slowing down the systick 09:30:33 currently my 75Mhz f0 interrupts every 0.1mS and is fine 09:30:43 same with a M3 at 75Mhz 09:31:20 because I had set the systick for what would be 10 KHz were the processor running at 8 MHz not 10 KHz as the processor is actually running at 48 MHz 09:31:28 understand 09:31:51 I was wondering why my blinkies were blinking so fast 09:31:53 there are a lot more clock options on the L series 09:31:55 hahah 09:32:25 that the cool thing about embedded, it's easy to verify stuff in the real world 09:33:22 I did an Hackaday aticle (ages ago) about using a old moving coil meter to indicate MCU load/usage which they actually published 09:33:36 but Forth wasnt mentioned as usual 09:35:16 well, now that I have gotten interrupt USART IO working, I should go on to port zeptoforth and its add-ongs to the F407 09:35:47 what you do is have a short blocking delay drive a gpio and adjustable series resistor into a microamp meter, set it to show full scale on the meter. After that as other things take up cpu time the meter indicates less 09:36:18 but unfortunately, I have work to do this weekend (does my boss have any clue about "work-life balance?") that will have to wait 09:36:31 what does the USART interrupt on ? 09:36:44 bosses generally dont 09:38:01 I'm thinking of making up a nice small box for my dev system which is just a Disco board with wires that easily fall off atm 09:38:13 USART2_ISR_TXE, USART2_ISR_RXNE, and USART2_ISR_ORE 09:38:40 i'll use my 32 pin QFN header for the chip, add a meter for cpu usage, decent pins or terminals for gpio etc 09:40:16 I'm really happy about getting interrupt IO with sleeping working 09:41:02 mind you it wakes up at a 10 KHz frequency.... 09:41:10 (thanks to systick) 09:41:23 --- part: Bunny351 left #forth 09:41:36 it's a milestone for sure 09:42:19 the nice part about this is that the interrupt IO does not interfere with multitasking 09:42:32 so it is safe to use within the multitasker 09:44:23 I'm still cautious of interrupts but so far no problems 09:46:39 yeah, some stuff was tricky 09:47:46 are you sure the interrupt is actually working ? 09:48:44 tp: my IO path now requires the interrupts to send or receive anything at all 09:49:15 because, unless you directly call the "legacy" serial driivers directly, everything goes through the interrupt 09:49:42 (the "legacy" serial driver is what is used on bootup) 09:50:24 unless the interrupt-driven one has been installed 09:51:27 aha 09:54:28 ugh 09:54:42 I still have occasional glitches on doing the install of all the standard code 09:54:50 occasionally the IO fucks up 09:55:46 it's complex stuff 09:56:42 and I did make sure to put disable-int ... enable-int in my interrupt handler... 09:58:32 when I try to elicit the issue now, though, it works just fine 09:59:01 perhaps some USART registers have junk in them ? 09:59:01 sometimes I just wonder if I'm accidentally hitting the keyboard - I do do that at times - and that causes it to fuck up 09:59:27 nah, because it's loading just fine before it installs the interrupt IO 09:59:42 or starts the multitasker 09:59:52 i think it's hard to test usart code on the usart one is using for the termina 10:00:25 perhaps test it on a second non terminal usart ? 10:00:45 ahh, you cant because you use the usb serial ? 10:00:52 yeah 10:01:51 well I could attach serial to a serial to USB converter, which I do own but would have to find 10:02:29 but I don't have a suitable cable, and don't want to solder anything into my board 10:02:52 *onto 10:03:07 good idea 10:03:39 you need a box of the cheap and crappy female to female jumper cables 10:03:52 so called 'dupont cables' 10:04:02 okay, I should get to work 10:04:08 okies, cya! 10:09:08 --- quit: tabemann (Ping timeout: 256 seconds) 10:58:54 --- join: xek_ joined #forth 11:01:29 --- quit: xek (Ping timeout: 265 seconds) 11:54:13 --- join: Zarutian_HTC joined #forth 14:26:18 --- quit: reepca (Read error: Connection reset by peer) 14:27:24 --- join: reepca joined #forth 14:32:04 --- join: tabemann joined #forth 14:35:07 --- quit: gravicappa (Ping timeout: 265 seconds) 15:59:20 --- quit: tabemann (Ping timeout: 256 seconds) 16:28:29 --- join: dave0 joined #forth 16:29:24 --- quit: xek_ (Ping timeout: 264 seconds) 18:03:19 --- join: boru` joined #forth 18:03:22 --- quit: boru (Disconnected by services) 18:03:25 --- nick: boru` -> boru 18:20:05 --- join: iyzsong joined #forth 18:34:04 --- join: jsoft joined #forth 18:34:17 --- quit: jsoft (Max SendQ exceeded) 18:34:44 --- join: jsoft joined #forth 18:37:24 --- quit: jsoft (Client Quit) 18:37:42 --- join: jsoft joined #forth 18:42:44 --- join: tabemann joined #forth 18:42:51 --- quit: jsoft (Quit: Leaving) 18:43:16 --- join: jsoft joined #forth 18:54:02 --- quit: Zarutian_HTC (Ping timeout: 258 seconds) 18:54:32 --- join: Zarutian_HTC joined #forth 18:54:48 --- quit: Zarutian_HTC (Client Quit) 18:59:58 --- join: boru` joined #forth 19:00:02 --- quit: boru (Disconnected by services) 19:00:04 --- nick: boru` -> boru 19:06:34 hey guys 19:08:57 hey tabemann 19:10:59 I'm having a strange problem with the f407 19:11:05 zeptoforth boots 19:11:12 but USART1 fails 19:11:21 USART1 pretends it works 19:11:40 e.g. USART1_SR reads $C0 19:12:03 which is what it'd say if it were ready to transmit data 19:12:15 you can compare to the Mecrisp-Stellaris f407 code ? 19:12:22 but it never actually transmits any data, including the welcome banner 19:12:36 the L model has a lot of differences 19:12:50 I basically took Mecrisp-Stellaris's F407 USART code verbatim 19:13:04 I have a L073 and everything is quite different 19:13:09 ahh ok 19:13:16 even the parts where it operates at 8 MHz 19:13:32 so you have received your F4 disco ? 19:13:38 yes 19:14:58 I think the F4 code also has a component in /common ? 19:15:07 unlike my f0 19:15:22 of mecrisp-stellaris? 19:15:25 yes 19:15:41 yeah, there's a source file for the USART that's in common 19:18:23 one difference I've observed is that the f407 takes much longer to erase its flash than the l476 19:19:40 I've noticed that the f407 flash is slow also 19:20:04 at least to erase and flash 19:20:15 well well well 19:20:20 via stlink 19:20:28 I flashed mecrisp-stellaris onto my f407 19:20:29 and 19:20:41 I havent made a single project on the F4 19:20:45 it doesn't show the banner 19:21:10 it doesn't respond 19:21:19 could that be a e4thcom thing ? 19:22:15 nope 19:22:23 just tried it with screen 19:22:48 it looks like a bug in mecrisp-stellaris that I copied into zeptoforth 19:23:53 could you use your documentation-fu and find me the same documents you found me for the l476 but instead for the f407? 19:25:33 the stm factory docs ? 19:26:08 https://sourceforge.net/projects/mecrisp/files/Target%20literature%20package%20for%20STM32F407.tar.gz 19:26:20 matthias has them in a bundle already 19:26:22 --- join: crab1 joined #forth 19:26:37 Hello forth gurus 19:26:40 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 19:27:04 --- join: iyzsong joined #forth 19:27:19 --- join: actuallybatman joined #forth 19:28:15 thanks 19:28:19 hey crab1 19:29:01 tabemann, plus the f407 may not work via the usb for the terminal 19:30:19 ugh 19:30:20 --- join: crab2 joined #forth 19:30:35 How is everyone? 19:32:10 tabemann, I just flashed mine and cant talk to it using my serial dongle 19:32:20 maybe it does use the usb, looking 19:33:59 - USART2 in STM32F407 (TX on PA2, RX on PA3) 19:34:22 oh it's USART2 for USB serial? 19:34:33 the code I have specifies USART1 19:35:59 Mecrisp-Stellaris RA 2.5.3 for STM32F407 by Matthias Koch 19:36:09 thats (TX on PA2, RX on PA3) 19:36:41 oh wait, the code does use USART2 19:36:58 .equ Terminal_USART_Base, 0x40004400 @ USART 2 19:37:08 yeah, he must be using a different AF 19:42:09 Alternate function 7 for TX and RX pins of USART2 on PORTA 19:51:57 back 19:53:03 tabemann, I've flashed your latest, no response from board that talks to Mecrisp-Stellaris 19:53:55 you've got Mecrisp-Stellaris working? 19:54:26 yeah 19:54:41 Mecrisp-Stellaris RA 2.5.3 for STM32F407 by Matthias Koch 20:00:02 are you using USB for your serial? 20:01:15 no 20:01:22 (TX on PA2, RX on PA3) 20:03:15 --- quit: crab2 (Read error: Connection reset by peer) 20:03:15 --- quit: crab1 (Read error: Connection reset by peer) 20:06:50 --- join: crab1 joined #forth 20:18:49 back 20:19:14 I've got a cheap Chinese what-is-probably-an-FTDI-clone here 20:19:36 the f407 cant do usb without a forth usb driver 20:19:52 so it's TX on PA2, RX on PA3 20:20:16 I've got TXD and RXD marked on my FTDI clone 20:20:31 that would work 20:21:02 does TXD on the clone go to PA3 on the board, and RXD on the clone go to PA2 on the board, or is it the other way around 20:21:11 I think the reason you have USB on your L476 is because of the V2 SWD ? 20:21:51 the actual L476 also needs a Forth USB driver to use USB natively 20:22:29 the L476 supports dropping files onto it (ugh) - I noticed that when I booted up my linux box once with the L476 attached it displayed a message about an sdb existing 20:22:44 the older F407 only had stlink V2 (oops the later one is V3 ? ) 20:23:05 mine says stlink V2-1 20:23:13 yeah, the latest stlink has a virtual com port and that stupid DnD thing 20:23:21 ahh, thats the version them 20:23:30 they should have named it V3 I think 20:23:43 how do I connect up my cheap chinese clone to my F407 board? 20:23:45 V2 had no virt com port or DnD 20:24:46 TX on PA2 - clone RX, RX on PA3 - clone TX 20:26:34 I also have it on my site: https://mecrisp-stellaris-folkdoc.sourceforge.io/terminal-connections.html?highlight=serial#serial-pin-connection-table-for-various-boards 20:26:34 --- quit: crab1 (Ping timeout: 250 seconds) 20:28:28 okay, I got Mecrisp working now 20:29:01 cool 20:29:01 HAH 20:29:06 zeptoforth lives 20:29:42 you can also connect the usb from the SWD programmer and flash that board with the serial line connected anytime 20:29:49 awesome 20:30:03 wonder why it doesnt on mine ? 20:30:23 I apparently made some changes 20:30:36 apparently 20:30:45 as one does 20:35:04 --- quit: dave0 (Quit: dave's not here) 21:10:21 just busy debugging zeptoforth for the f407 21:10:40 right now it's not properly detecting the end of the dictionary 21:18:42 --- join: rdrop-exit joined #forth 21:20:46 hey 21:20:59 hi tabemann c[] 21:23:01 --- quit: reepca (Read error: Connection reset by peer) 21:23:15 --- join: reepca joined #forth 21:26:14 --- join: gravicappa joined #forth 21:30:23 just read on clf that Matthias Trute, the author of AmForth has passed away. Rest in peace. 21:34:22 clf? 21:34:33 comp.lang.forth 21:34:50 usenet 21:42:34 --- quit: reepca (Read error: Connection reset by peer) 21:42:53 --- join: reepca joined #forth 21:46:44 rdrop-exit, oh man sorry to hear that. :-( 21:54:00 --- quit: dddddd (Remote host closed the connection) 22:21:25 --- quit: _whitelogger (Remote host closed the connection) 22:24:29 --- join: _whitelogger joined #forth 22:32:47 I'm sory to hear that as well, I always liked his work ... 22:35:04 but nothing on the Amforth site 22:35:21 http://amforth.sourceforge.net/ 22:36:57 "Welcome to zeptoforth ok" 22:39:10 2 2 + . 4 ok 22:50:44 kudos 22:51:39 thats tabemann's Forth :) 22:52:26 Cool, nothing beats that "It's alive!!" moment when bringing up a new Forth 22:53:02 would have been for tabemann for sure! 22:53:33 I'm just a user, I expect to see things I dl working ;) 22:54:25 I get the satisfaction of my hardware designs working, that's enuf for me, some people are easily pleased ;-) 22:54:56 rdrop-exit, Zen Guru, how goes the home detention ? 22:55:48 ok, stayed up until 3am watching videos with the wife 22:56:11 why not :) 22:57:58 I haven't been out of my compound since monday 23rd myself 22:58:57 it's toughest on the dogs I think 22:59:28 yeah, I was just thinking that as myneighbours dog huffed at my door about 30 seconds ag 22:59:48 he comes over for a pat and lays outside my flywire door 22:59:59 nice 23:00:30 but I havent patted him for a week when I realised he goes everywhere with the owner and makes a fuss of strangers that come into this compound 23:01:19 he will have to make do with everyone elses pats 23:39:25 --- quit: _whitelogger (Remote host closed the connection) 23:42:29 --- join: _whitelogger joined #forth 23:59:59 --- log: ended forth/20.03.28