00:00:00 --- log: started forth/20.05.09 00:25:09 --- nick: jedb_ -> jedb 00:25:30 --- quit: WickedShell (Remote host closed the connection) 00:37:22 --- quit: dys (Ping timeout: 256 seconds) 00:37:56 --- quit: xek (Ping timeout: 246 seconds) 00:40:45 --- join: dys joined #forth 00:47:00 --- quit: proteus-guy (Ping timeout: 256 seconds) 00:47:04 --- quit: proteusguy (Ping timeout: 260 seconds) 00:59:04 --- join: proteus-guy joined #forth 00:59:55 --- join: proteusguy joined #forth 00:59:55 --- mode: ChanServ set +v proteusguy 01:09:33 --- quit: reepca (Remote host closed the connection) 01:09:46 --- join: reepca joined #forth 02:54:49 --- join: tp joined #forth 03:08:30 lol, how is this for convoluted ? I was dreaming that I was writing important Forth code, and became aware I was dreaming, so I woke up to go and write the code, but as I awoke I realised I don't have any important Forth code to write! 03:09:32 Inception? 03:14:44 that's an excellent film 03:15:26 I have definitely experienced dreams where I get a eureka moment and wake up and realise I had been thinking something totally stupid and my regular unconscious brain halucinations had tricked me 03:15:51 veltas, heheh, our minds are things of wonder indeed! 03:16:00 --- quit: proteus-guy (Remote host closed the connection) 03:16:19 I like watching dogs sleep and wondering what they're dreaming about 03:17:25 I prefer to "let sleeping dogs lay" 03:17:42 ;-) 03:18:29 --- join: proteus-guy joined #forth 03:20:37 Probably they're dreaming that they have the solution to tp's forth problem and then wake up and remember they're just a dog 03:21:58 hahah 03:22:06 --- join: proteus-dude joined #forth 03:22:10 I didnt have a Forth problem :) 03:22:24 I may have had a XSLT problem tho 03:22:58 technically, it's impossible for me to have a Forth problem 03:25:32 because every complex Forth problem can be reduced to the most simple form and interactively tested 03:28:45 --- join: iyzsong joined #forth 04:19:09 --- quit: reepca (Read error: Connection reset by peer) 04:19:26 --- join: reepca joined #forth 04:40:19 --- quit: iyzsong (Ping timeout: 260 seconds) 04:42:21 --- join: iyzsong joined #forth 06:27:46 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 07:13:57 --- quit: reepca (Read error: Connection reset by peer) 07:15:03 --- join: reepca joined #forth 07:38:07 --- quit: proteus-dude (Quit: Leaving) 07:43:10 --- join: jpsamaroo joined #forth 08:25:32 --- quit: Zarutian_HTC (Ping timeout: 246 seconds) 08:27:39 --- join: deesix_ joined #forth 08:29:34 --- quit: deesix (Ping timeout: 272 seconds) 08:37:13 --- join: dddddd joined #forth 09:05:00 --- join: Zarutian_HTC joined #forth 09:06:02 --- quit: dave0 (Quit: dave's not here) 09:24:43 --- join: karswell joined #forth 11:28:56 --- quit: jsoft (Ping timeout: 246 seconds) 11:49:12 tp: is "The Definitive Guide to the ARM® Cortex-M3" worth reading? 11:50:01 because my problem is that the stm32f103 is so much more capable and complex configure than the 8bit avrs i've used before 11:50:18 that a lot of the time i don't know which question to ask 11:51:12 and i don't want to fall victim to cargo cult programming 12:39:59 --- quit: Zarutian_HTC (Ping timeout: 246 seconds) 12:44:58 --- quit: dys (Ping timeout: 256 seconds) 13:27:32 --- join: dys joined #forth 13:29:39 seven leds are too much for the ft232 3.3v regulator *cough* 13:30:31 with all seven active the voltage drops from 3.4v to 2.4v and the leds are noticable dimmer than with just one 13:30:39 transistor time 13:30:41 even the blue pill's power led dimms 13:31:33 MrMobius: i did use a small npn transistors with a 1.5k ohm resistor to protect the gpio pins 13:32:13 but i powered the whole bread board from the usb serial converter 13:32:50 the usb to serial converter chip got a bit warm as well 13:35:02 that should at least keep the current per gpio pin to less than 2 mA 13:35:57 but beeing a naiv programmer i forgot that the microcontroller is not the only part with current limitation 13:49:09 --- join: Zarutian_HTC joined #forth 14:20:26 --- quit: gravicappa (Ping timeout: 272 seconds) 15:11:14 --- quit: Zarutian_HTC (Ping timeout: 256 seconds) 15:14:12 --- join: Zarutian_HTC joined #forth 15:29:01 is there a cortex m3 assembler for mecrisp stellaris? 15:33:30 crazy ideas ... add a sd card to one blue pill board and use can bus to provide blocks to the other boards 15:36:28 as long as all boards use lower addresses for requests use lower addresses than responses a simple round robin scheduler could provide fairness 16:06:46 crest, Ive never read it, my arm knowledge comes from building projects etc 16:07:26 crest, no, just a m0 one 16:07:32 (assembler) 16:09:46 crest 7 leds with high value series resistors should be ok, say 2k7 and 'high intensity' leds 16:10:28 just a bunch of random green leds with diffusor 16:10:39 they are bright enough to be easily visible in a well lit room 16:11:10 iirc i measured them as between 80mA and 110mA at 3.3v 16:11:53 thats WAY too much current 16:12:09 did you use a series resistor with them ? 16:12:54 a hi intensity led will be bright enuf to see at 5 ma 16:13:24 --- quit: dddddd (Ping timeout: 260 seconds) 16:13:40 but random cheap leds will be quite dim 16:14:51 no 16:15:01 crest, the *total* current allowed by *all* at once GPIOS is 80 mA and it's 20mA per gpio max 16:15:05 3.3v -> led -> npn transistor -> gnd 16:15:34 ahh, if you add a series resistor per led your ft232 3.3v regulator will be fine 16:15:36 than used a 1.5k ohm resistor between 3.3v and the transistor 16:16:09 the gpio can drive a led with 1k5 resistor directly, no problem 16:16:44 but how many leds can i connect per gpio port? 16:17:22 you only need a transistor and external psu if you exceed the GPIO ratings or 500mA total from the ft232 3.3v regulator 16:17:53 how many leds directly = 80mA/each led on current 16:18:17 say 8 leds on at once = 10mA each 16:18:51 measure the voltage across a led with the 1.5k resistor in series and use that to calculate 16:19:03 the only resistor values i have right now are 150 and 1.5k ohm 16:19:17 with 150ohm they are barely visible 16:19:18 generally led on voltage is about 2.5 volts 16:19:36 well 150 ohm will have to do 16:19:43 let me put a second one in parallel 16:20:08 measure the current thru the led, thats the critical factor 16:22:08 9,000mcd brightness 16:22:08 Standard size - T1 3/4 5mm 16:22:08 2.4V forward drop 16:22:08 Max current 20mA 16:22:19 https://www.sparkfun.com/products/528 16:22:40 thats similar to what i use, they are easy to see with almost no current 16:24:17 looks like some idiot blew the fuse in the multimeter *sigh* 16:24:35 Id buy 30 of those leds and throw away all the old ones 16:24:54 heheh, thats what the fuse is for 16:24:55 it doesn't work in current measurement mode (led stays dark) 16:25:07 oops 16:25:14 well calculate it then ? 16:25:39 3.3 - 2.7 / 150 16:25:59 thats about what the led will use as green has a higher voltage per led 16:27:31 i just switched to the unfused 10A connector 16:28:06 unfused! 16:28:10 oh man 16:28:38 the power supply (ftdi 232) is rated for less than 200mA 16:28:47 that will make a big bang oneday if you ever decide to see how many amps are inside the mains power 16:29:18 ahh yes, it's only a serial dongle 16:29:34 i wouldn't try that with lead acid batteries 16:30:13 they're great for spot welding connectors :-P 16:30:15 thats all I use to power the bluepill projects i feature on my site 16:32:54 according to my multimeter the led draws 1.1mA when attached to the 3.3v without any series resistor 16:33:39 which is a lot more reasonable but i no longer trust the multimeter 16:34:07 after all i'm going through the unfused (up to 10A) connector 16:34:57 i could measure the current through some known resistor to double check 16:35:06 that reading is definitely wrong 16:36:25 it has to be. the power led on the blue bill gets noticeably darker 16:39:01 because it's exceeding 200mA 16:39:44 the regulator folds back at 200mA being current limited 16:40:10 and then it starts to heat up, obviously it has good heat sinking on the board 16:40:26 .oO( beware of programmers with soldering irons ) 16:40:40 whats your clock speed on the bluepill ? 16:41:04 crest, but ya gotta deal with a soldering iron in embedded sooner or later 16:41:29 probably 8mhz unless the default stm32f103-ra image configures the PLL 16:41:44 i'm supprised it didn't crash as well 16:42:32 given that the voltage dropped to at by about one volt 16:42:56 the stm32's are really quite amazing 16:43:18 the default is the internal 8MHz internal RC oscillator 16:44:08 is the internal rc oscillator is good enough for a reliable serial connection at 115200 baud? 16:44:42 easily 16:45:05 the f103 mcu will run at 2.0 v 16:45:29 and internally it's running at 1.8v via a internal LDO regulator 16:45:33 (3.3 - 2.7) / 150 = .004 16:45:45 yeah, 4mA 16:46:22 a hi intensity led will be seen across the room at that level, a cheap/old led, not so much 16:47:21 there is some diffuser on the leds 16:47:37 which probably eats most of the light output 16:48:10 the efficiency of the led is the problem 16:48:58 they just emit a dim green glow 16:49:29 your leds are like a car that goes 20kph max and uses 100l of fuel per km 16:51:10 sure but they're good enough to test the gpio port 16:52:26 heheh, yeah with a series resistor and dim the lights :) 16:53:20 i'm to lazy to remove the transitors 16:54:35 dosnt matter 16:54:51 with two 150 ohm resistors in parallel its bright enough that i don't have to dim the lights 16:54:59 all you need is that 150R or perhaps 2 in parallel 16:55:08 so thats 8mA per led 16:56:58 26mW per led 16:57:48 and as you have 1.5K resistors into the bases of the transistors, (BJT's ?) then thats only 1.7mA per GPIO 16:58:14 BC337 16:58:19 but the 1500 R led is too low, it should be at least 10k 16:58:46 1.7mA is massive for the base-emitter current of a BC337 16:59:15 but it will all work ok 17:00:09 the only other value i had available was 10k ohm and that dimmed the leds noticeable 17:00:54 10k is a good base series resistor for the bc337 17:01:31 dimmed the leds noticeable ?? 17:01:36 yes 17:01:42 what do you mean ? 17:02:02 they are brighter with a 1.5k ohm base series resistor 17:02:18 ahh 17:02:54 i can pull the transistor out and put my multimeter in hFE mode 17:02:57 thats odd, is all this stuff from china ? 17:03:24 measure the transistor gain ? good idea 17:03:24 it is stuff left over from random projects in my local hackerspace 17:03:45 could you have the collector and emitter transposed ? 17:05:43 according to my multimeter hFE is 261 17:06:33 which is about right 17:07:01 with that kind of gain 10k should be fine 17:07:04 ah well 17:07:40 hey I was just thinking, if you looked at the F103 technical notes and found it daunting, then that means you actually understood what you saw 17:07:54 because it IS daunting 17:08:37 Ive been working on the f051 (baby cousin of the F103) since 2016 and there is still mountains I dont know 17:08:50 and I work on it almost every day 17:10:10 just let me double check if i'm too stupid to get the polarity right 17:10:50 looking at flat side of the transitor left pin is the emitter and it should be connected to gnd 17:11:08 base is in the middle 17:11:09 BCxxx have funny pinouts 17:12:21 left pin is collector 17:13:00 *facepalm* 17:13:31 did i really abuse the transitor as diode? 17:13:39 why not ? 17:14:03 I abused a bc547 so badly once the top blew off and hit me between the eyes 17:14:37 i just put my nose over the transistor and noticed a slight smell 17:14:58 hot 17:15:12 touch it with a fingertip ? 17:15:21 cold 17:15:31 it should be room temp at those current levels 17:15:58 it is 17:16:15 it should switch the led fine with a 10k base resistor 17:21:33 so the only thing that protected my poor parts was my that i fucked up twice and used an a usb <-> serial converter as power source 17:22:33 heheh, yeah if youd used a psu with grunt, you may have had the "BCxxx hit between the eyes" experience also 17:23:07 which demostrates why you want a current limited power supply 17:23:19 I have PSU's here (of my own design) that will do 0 - 30v at up to 30 amps 17:24:13 yes and USB has helped a lot here for hobbyists 17:24:24 limited to 500mA or 1A 17:25:49 iirc, when I built my first ever MCU project (a nucleonic ore flow guage) in 1974, the MCU, a National 16 bit Pace, that MCU needed 3 voltages inclucing a negative one 17:26:17 negative?!? did to erase some flash? 17:26:34 and at $270 per cpu in 1974, the fear of blowing one up was real 17:26:50 --- join: dave0 joined #forth 17:26:51 the devices of the day used multiple supplies 17:27:05 *did it use that to 17:27:37 i believe that flash uses negative supplies to this day, it's just that the chips generate it themselves on chip 17:27:51 no that was just the cpu 17:28:24 the proms were fusible link, no eprom or flash back then 17:36:14 did the pace have the same crazy indirect pointer handling as the dg nova? 17:37:57 i dont know, I only ever added 1 and 2 to get 3 on that dev system 17:38:15 i was the tech assisting the engineer, I built al the hardware 17:38:44 the National 'Pace' development system lived in his office 17:38:59 if us used indirect addressing on a nova the hardware would load a 16bit word 17:39:26 and if the lowest bit in the address was set it would indirect again 17:40:22 on the original nova there was no way to break out of this if you created a circular datastructure 17:40:35 the only micro I knew fairly well was the 6800 17:40:39 the cpu would just deadlock in the microcode loop 17:41:00 --- join: jsoft joined #forth 17:41:21 back in those days, but that was a decade after the Pace chip 17:41:44 i only saw one at the vintage computing assembly at 34c4 17:42:07 or was it at 33c3? 17:42:34 back in 1974, there was no internet, I had no databooks on the PACE cpu 17:42:41 but supposedly the system could even handle interrupts in that state 17:42:54 and the engineer wouldnt have let me take his one home 17:43:00 what was intersting about those systems with their core memory is the power failure interrupt 17:43:18 if you pull the power the system raises a power failure interrupt 17:43:30 and you have about 4000 cycles to halt the system 17:43:32 and at work I was supposed to be building hardware, not hanging out in the engineers office reading the PACE technical manuals 17:44:10 which can be used to save the registers in core memory and halt transfers and save the i/o state as well 17:44:30 allowing the system to continue as if nothing happend 17:44:45 the PACE didnt have core afaik 17:45:07 which was nice if the bootstrap requires the operator to enter a bootloader from the frontpanel 17:51:56 and yes there is a forth for the dg nova 17:52:27 i think there is a Forth for *everything* 17:54:29 --- join: iyzsong joined #forth 17:55:31 i just wanted to return to the topic 17:55:48 :) 17:56:11 crest, so all your leds sorted out now ? 17:56:57 yes 17:57:19 awesome 17:57:40 I have a new svd2forth bitfields almost ready 17:57:58 what changed? 17:58:03 ill put it up for the f103 on my site when it's done 17:58:21 more intelligence in the xslt transform 17:58:45 I've finishing a change that does this 17:58:56 does it improve the generated code? 17:59:25 \ GPIOC_BSRR (write-only) Reset:0x00000000 17:59:26 : GPIOC_BSRR_BR15-CLR ( -- ) 31 bit GPIOC_BSRR ! ; \ GPIOC_BSRR_BR15, Port x reset bit 17:59:49 you're generating a word for every pin?!? 17:59:57 always have 18:00:21 the bitfields are a template file, one pastes what they want into their program 18:01:00 i transform the entire CMSIS-SVD file for any stm32 18:01:26 and that file includes every single bitfield 18:02:28 couldn't that be simplied to 15 port-c gpio-unset-pin 18:03:04 it is 18:03:19 plus it's atomic 18:03:36 because it uses BSRR instead of the normal data register 18:03:39 ? 18:03:46 correct~! 18:04:01 made for the job 18:04:09 why didn't they include atomic operations in the instruction set 18:04:19 or at least on address per atomic operation 18:04:25 i didnt design cortex-m :) 18:04:52 iirc this is the stm part and not part of cpu core 18:05:24 it would have been so much nicer to at least make the operation part of the adress 18:05:26 could well be! 18:05:40 one for atomic and,or,xor 18:05:59 programmers dream, tech use whats there 18:06:39 or even better provide two views of the gpio port 18:06:55 one with all state of a single port in one address 18:07:09 and a second one with a bitmap per pin 18:07:12 *single pin 18:07:26 it's probably germain to mention that the STM32F103 design is now 16 years old 18:07:40 even the 8bit avrs did it better 18:07:51 you may find more modern capabailties in more modern stm32 18:07:54 they do provide atomic single bit set, unset and toggle 18:08:18 I've no idea, the MCU I use was released in 2011 18:08:20 even if toggle abuses the atomic single bit set on the port input address 18:08:54 they probably did it because it was easier to connect the gpio port to the bus that way 18:09:20 probably the gpio port has expects the set/unset as single 32bit word 18:09:31 s/has// 18:09:38 I'm still amazed with the capabilities of the old F103 18:09:58 it's too bad that you can't use usb and can at the same time 18:10:00 the fact it could even be made is astounding 18:10:07 you can in later chips 18:10:15 otherwise the blue pill would make a nice usb<->can adapter 18:10:19 **** 16 years old ***** 18:10:22 :) 18:10:54 but its the cheap crap^Wstuff i ordered half a year ago and forgot about 18:11:28 --- join: boru` joined #forth 18:11:31 --- quit: boru (Disconnected by services) 18:11:34 --- nick: boru` -> boru 18:11:40 hey the stm32f103 is still incredibly popular, especially with arduino users to whoom the stm32 is so advanced, it's like alien tech 18:11:57 programmers always bitch and moan about hardware designs 18:12:18 the fact it's 16 years old only demonstrates how ancient the MEGAxxx are 18:12:24 yeah I know 18:14:37 they tend to forget that hardware has to be build $n times but software just once 18:15:13 if you can replace a part of hardware with a few lines of (annoying) code ... 18:15:33 it's always easier to just do what you want in software, the hardware is hard to do 18:15:46 yes, I agree 18:16:24 e.g. i've seen old schematics for m68k boards with dram refresh in software 18:16:25 it cost $1 billion a decade ago to make a new semi fab plant 18:16:37 it must have have been a pain in the ass to debug those boards 18:16:55 if your software crashes the dram is no longer refreshed 18:16:58 maybe they had a Forth guy on the staff ? 18:17:28 maybe the testing jig generated the refreshes ? 18:17:34 anythings possible 18:17:54 or they made their copper wires by pinching pennies hard enough? 18:18:05 I have testing gear here that changes logic states of chip outputs with brute force 18:18:37 called 'logic pulseing' 18:18:42 pulsing 18:19:11 it gets away with this because the pulse is so short the logic driver in the chip can take it 18:19:23 and the detection gear can detect it 18:19:35 it's saved me man years of time 18:19:51 --- quit: Zarutian_HTC (Read error: Connection reset by peer) 18:19:52 back in the TTL and CMOS days 18:19:55 --- join: Zarutian_HTC| joined #forth 18:20:07 how did it save so much time? 18:27:08 because the only alternative was to remove the chip 18:27:16 which was always soldered in 18:30:07 tp: with 75 ohm in series with the leds the supply voltage still drops to 2.9v if all seven are on 18:30:52 thats ok 18:31:05 for the stm32 maybe 18:31:20 for the usb<->serial convert powering it... 18:31:35 it will be fine 18:31:50 2.9 is close enough to 3.0 for the hardware 18:32:03 they dont stop because of a 0.1v drop 18:32:19 that's the danger with absolute numbers 18:32:50 it drops from 3.4v to 2.9v. a 0.5v drop 18:32:57 life was safer and fore fun with analog numbers ;-) 18:33:18 well 3.4 is much higher than you need, and I doubt it's accurate 18:33:39 these regulators are spot on nowadays 18:33:58 well the american ones are 18:34:03 it jumps a bit between 3.3v and 3.4v 18:34:08 not so sure about the Chinese stuff 18:34:57 it could be a fake ft232 given the adapter cost 1,x € with shipping in batches of five 18:34:59 crest, you have a ADC on that chip, go and measure it ? 18:35:21 your chip has a highly accurate voltage ref you can measure with the adc 18:35:32 along with the supply voltage 18:35:33 you can measure your supply voltage without an external voltage regulator? 18:35:38 sure 18:36:18 so it doesn't need a external reference voltage like the stupid avrs for that 18:36:31 the adc uses the reference for accuracy and you just use a resistive divider for the supply 18:36:53 I cant remember what they did in the 8 bit stone age 18:37:04 the adc on a stm32 is 12 bits 18:39:47 i didn't use AVRs because they're a good modern design 18:40:03 but they're accessible 18:42:23 yeah and they had areduino ! ;-) 18:42:32 even before that happend 18:42:45 I hate AVR's myself 18:42:54 i got started with avr-gcc, avrlibc and avrdude 18:42:58 have ever since I had to use them 18:43:12 and after a while i used them without the (bloated) libc 18:43:26 there is no disputing their hobby popularity 18:43:50 i think hobyists have kept the MEGAxxxx alive the last decade 18:43:51 all they needed is a 5v supply and a quartz 18:44:12 and a stm32 costing $0.56 needs neither 18:44:36 those hobbists go on and use what they know in other projects 18:44:42 yeah I know 18:44:55 hobbyists arent what they used to be 18:45:07 hmm, I feel a rant article coming on 18:45:12 until they complain that there is no avr with more than 8kB ram and 64kB flash for their code 18:45:18 hehe 18:45:35 what is so bad about the avr? 18:45:45 what is so good about the avr ? 18:46:19 their ease of to use with little documention 18:46:38 I'm fairly sure you cant think of one good technical reason that I cant show is not easily bettered by stm32 18:46:47 thats not a good thing 18:46:59 a rock needs no documentation to use as a weapon 18:47:18 a single chapter from a single pdf is enough to get you started on each periphery 18:47:39 but a m16 will easily and rapidly kill 30 people with rocks, per magazine 18:47:54 the hardware is easy enough to use that the documentation includes code samples in c and assembler for most things 18:48:07 the hardware is NOT easy to use 18:48:24 there is no easy to use GDB 18:48:30 ie no debugging 18:49:12 by themselves your reasons sound ok, but stm32 is vastly better 18:49:29 the debugging support sucks compared to what the m3 has to offer 18:49:29 and whats this about 'easy to use' ? 18:50:05 printf doesn't work in timing critical code 18:50:26 and toggling pins requires a logic analyzer 18:50:31 when was 'easy to use' a requirement for any hitech skill ? 18:50:49 when hobbists just want to have fun? 18:51:15 'easy to use' is for morons and retarded children, people with a brain *figure it all out* 18:51:35 and there is avr gdb but you need a jtag adapter to use it 18:51:38 no, todays 'hobbysists' are not the hobbysists of yesterday 18:51:54 ? 18:52:11 remember, it was 'hobbysists' who discovered that UHF was in fact very useful 18:52:25 when governments considered UHF utterly usless 18:52:57 until they proved them wrong 18:54:21 and ham radio lost most of it to other users 18:56:16 sure 18:56:22 but feel free to write your avr rant 18:56:45 it's not a avr rant, it's a 'hobbysists' rant :) 18:56:52 i should go to bed before the birds get too annoying 18:57:03 lol 18:57:14 thanks for another excellent chat 18:57:43 (i configured my lights for 4k color temperature and drank to much mate tea) 18:59:15 if fell like writing it down i would like to know why you dislike avr so much 18:59:33 *feel 19:00:40 2.2k color temp and 10% brightness is a lot better 19:01:31 i really should find out if there is a way to control the screen brightness as well 19:01:49 because i often forget to adjust my screen brigthness manually 19:02:08 --- quit: X-Scale (Quit: HydraIRC -> http://www.hydrairc.com <- It'll be on slashdot one day...) 19:05:06 hey guys 19:05:31 tabemann: hi 19:08:53 hey tabemann how goes Zeptoforth ? 19:09:10 still working on the disassembler 19:09:18 crest, I'll do a 'why I dont like AVR' on my site sometime 19:09:44 tabemann, goodness ... tell me it isnt true ;-) 19:10:11 I've been working rather slowly on it 19:10:29 same here with XSLT 19:10:50 there is something absolutely nummbing about enter masks, opcodes, and parsers for each instruction and addressing mode 19:12:11 tabemann which now does stuff like :- "\ GPIOF_BSRR (write-only) Reset:0x00000000 19:12:11 : GPIOF_BSRR_BR15->0 ( -- ) 31 bit GPIOF_BSRR ! ; \ GPIOF_BSRR_BR15, Port x reset bit" 19:12:59 tabemann, grunt work ? 19:16:29 yeah, the disassembler is definitely grunt work 21:28:13 --- quit: Keshl (Quit: Konversation terminated!) 21:41:01 --- join: Keshl joined #forth 22:23:25 --- join: gravicappa joined #forth 22:42:24 crest> couldn't that be simplied to 15 port-c gpio-unset-pin ? 22:42:42 crest, sorry I missed that question earlier 22:43:14 crest, sure it could, this is Forth and anything is possible, but the question is why do that ? 22:44:34 --- quit: jsoft (Ping timeout: 272 seconds) 22:45:42 crest, even at this point the language is quite low level as that instruction may end up as "motor-on" 23:59:59 --- log: ended forth/20.05.09