<tp>
crc, I'm still loving being able to do a 'fossil update' on you, it's a sheer pleasure!
<crc>
:)
<tabemann>
hey guys
<tp>
hey tabemann, how goes Zeptoforth
<tp>
still working on the disassembler i see
<tabemann>
yep
<tp>
yousaid it would take a while
<tabemann>
it's long, back-breaking labor
<tp>
caring loaded baskets of assembly syntax on your head ?
<tp>
carrying
<tabemann>
yep
<tp>
I can picture it
<tp>
if you imagine the vista of infinity, reaching out into time unknown .... that's how long it would take me to write one
<tp>
so I'll just do doc and svd2forth plus make forth powered gear I think
<tabemann>
lol
<tabemann>
actually working on the disassembler is just a simple matter of programming - almost all coding and very little thought
boru` has joined #forth
boru has quit [Disconnected by services]
boru` is now known as boru
<tp>
tabemann, I looked at your elaboration of using lambdas, but I'm still confused, perhaps you could write a blinky using them if you get the time ?
<tp>
tabemann, i'll be happy to assist with any hardware related issues you may run into
* tp
finds not thinking while coding a perplexing conundrum
<tabemann>
well it's primarily significant when one has registers with multiple fields where one wants to modify only certain fields and not others
<tp>
which is what one does when blinking a led
<tp>
or infact any peripheral use
<tp>
it's *all* about bitfields to me
<tabemann>
note that for many purposes they aren't necessary, e.g. ones where one can use bic! and bis!
<tp>
I still believe that trying to work with registers and not bitfields is totally wrong for embedded, but so far I'm debating programmers that have never actually made a working blinky, ie their theories are as yet untested
<tp>
tabemann, even bic! and bis! are often not needed as cortex-m has atomic single bit manipulation commands
<tp>
tabemann, meaning that there is no need to read and mask before setting particular peripheral bits
<tp>
tabemann, for data there are no such aids
<tp>
tabemann, but thats what makes embedded different, the MCU manufacturers anticipate and design for this kind of need
<tabemann>
my lambda approach is useful when one wants to set multiple bits both on and off simultaneously as a single write
<tp>
rdrop-exit, perhaps I have a different understanding of the word 'mask' to you, that could be a cause of confusion here
<tp>
to me, "2 bit" = %100
<rdrop-exit>
yes
<tp>
i dont see it as a 'mask' at this point in my lacklustre programming career
<tp>
but Im often wrong
jsoft has joined #forth
<tp>
I always understood a 'mask' to be a number used to 'filter' another number to remove undesired bits
<tp>
usually by oring or anding etc
<rdrop-exit>
that too
<rdrop-exit>
anyway I'm not sure why you bought up, GPIOB_BSRR
<tp>
what dont you understand about it ?
<rdrop-exit>
why you brought it up
<tp>
<rdrop-exit> sure, you're overwriting an entire register, that's fine
<tp>
thats why
<rdrop-exit>
yes, and your code and mine are identical in that case, as seen above
<tp>
your comment indicated you didnt understand that GPIOB_BSRR is designed for this use
<tp>
no, your code is abstract, there is no 'xreg' in a cortex-m
<tp>
our code has nothing in common
<tp>
(apart from the !)
* tp
orders another bottle of Kahlua Coffee Liqueur so he can withstand rdrop-exit's programmer only viewpoint!
<rdrop-exit>
wow
<tp>
luckily they reduced the price but this tactic forced me to buy a 1l bottle :)
<tp>
ah well, I'll do my best to cope
<rdrop-exit>
maybe the kahlua will help
<tp>
one can hope ...
<rdrop-exit>
it can only help
* tp
is out for some exercise, bbl
<rdrop-exit>
have fun
<rdrop-exit>
tabemann, as a rule of thumb if you're producing a combinatorial explosion of words you're not facttoring
<rdrop-exit>
combinatorial explosions only show up at the lowest level, e.g. 16@ 32@ etc...
<rdrop-exit>
* factoring
<rdrop-exit>
bbl
rdrop-exit has quit [Quit: Lost terminal]
tp has left #forth ["I'm leaving to find peace with my inner stack !"]
jedb_ has joined #forth
jedb has quit [Ping timeout: 264 seconds]
gravicappa has joined #forth
<jsoft>
Look at the usual suspects being nerds in here again :P
jedb_ is now known as jedb
WickedShell has quit [Remote host closed the connection]
dys has quit [Ping timeout: 256 seconds]
xek has quit [Ping timeout: 246 seconds]
dys has joined #forth
proteus-guy has quit [Ping timeout: 256 seconds]
proteusguy has quit [Ping timeout: 260 seconds]
proteus-guy has joined #forth
proteusguy has joined #forth
reepca has quit [Remote host closed the connection]
reepca has joined #forth
tp has joined #forth
<tp>
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!
<DKordic>
Inception?
<tp>
that's an excellent film
<veltas>
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
<tp>
veltas, heheh, our minds are things of wonder indeed!
proteus-guy has quit [Remote host closed the connection]
<veltas>
I like watching dogs sleep and wondering what they're dreaming about
<tp>
I prefer to "let sleeping dogs lay"
<tp>
;-)
proteus-guy has joined #forth
<veltas>
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
<tp>
hahah
proteus-dude has joined #forth
<tp>
I didnt have a Forth problem :)
<tp>
I may have had a XSLT problem tho
<tp>
technically, it's impossible for me to have a Forth problem
<tp>
because every complex Forth problem can be reduced to the most simple form and interactively tested
iyzsong has joined #forth
reepca has quit [Read error: Connection reset by peer]
reepca has quit [Read error: Connection reset by peer]
reepca has joined #forth
proteus-dude has quit [Quit: Leaving]
jpsamaroo has joined #forth
Zarutian_HTC has quit [Ping timeout: 246 seconds]
deesix_ has joined #forth
deesix has quit [Ping timeout: 272 seconds]
dddddd has joined #forth
Zarutian_HTC has joined #forth
dave0 has quit [Quit: dave's not here]
karswell has joined #forth
jsoft has quit [Ping timeout: 246 seconds]
<crest>
tp: is "The Definitive Guide to the ARM® Cortex-M3" worth reading?
<crest>
because my problem is that the stm32f103 is so much more capable and complex configure than the 8bit avrs i've used before
<crest>
that a lot of the time i don't know which question to ask
<crest>
and i don't want to fall victim to cargo cult programming
Zarutian_HTC has quit [Ping timeout: 246 seconds]
dys has quit [Ping timeout: 256 seconds]
dys has joined #forth
<crest>
seven leds are too much for the ft232 3.3v regulator *cough*
<crest>
with all seven active the voltage drops from 3.4v to 2.4v and the leds are noticable dimmer than with just one
<MrMobius>
transistor time
<crest>
even the blue pill's power led dimms
<crest>
MrMobius: i did use a small npn transistors with a 1.5k ohm resistor to protect the gpio pins
<crest>
but i powered the whole bread board from the usb serial converter
<crest>
the usb to serial converter chip got a bit warm as well
<crest>
that should at least keep the current per gpio pin to less than 2 mA
<crest>
but beeing a naiv programmer i forgot that the microcontroller is not the only part with current limitation
Zarutian_HTC has joined #forth
gravicappa has quit [Ping timeout: 272 seconds]
Zarutian_HTC has quit [Ping timeout: 256 seconds]
Zarutian_HTC has joined #forth
<crest>
is there a cortex m3 assembler for mecrisp stellaris?
<crest>
crazy ideas ... add a sd card to one blue pill board and use can bus to provide blocks to the other boards
<crest>
as long as all boards use lower addresses for requests use lower addresses than responses a simple round robin scheduler could provide fairness
<tp>
crest, Ive never read it, my arm knowledge comes from building projects etc
<tp>
crest, no, just a m0 one
<tp>
(assembler)
<tp>
crest 7 leds with high value series resistors should be ok, say 2k7 and 'high intensity' leds
<crest>
just a bunch of random green leds with diffusor
<crest>
they are bright enough to be easily visible in a well lit room
<crest>
iirc i measured them as between 80mA and 110mA at 3.3v
<tp>
thats WAY too much current
<tp>
did you use a series resistor with them ?
<tp>
a hi intensity led will be bright enuf to see at 5 ma
dddddd has quit [Ping timeout: 260 seconds]
<tp>
but random cheap leds will be quite dim
<crest>
no
<tp>
crest, the *total* current allowed by *all* at once GPIOS is 80 mA and it's 20mA per gpio max
<crest>
3.3v -> led -> npn transistor -> gnd
<tp>
ahh, if you add a series resistor per led your ft232 3.3v regulator will be fine
<crest>
than used a 1.5k ohm resistor between 3.3v and the transistor
<tp>
the gpio can drive a led with 1k5 resistor directly, no problem
<crest>
but how many leds can i connect per gpio port?
<tp>
you only need a transistor and external psu if you exceed the GPIO ratings or 500mA total from the ft232 3.3v regulator
<tp>
how many leds directly = 80mA/each led on current
<tp>
say 8 leds on at once = 10mA each
<tp>
measure the voltage across a led with the 1.5k resistor in series and use that to calculate
<crest>
the only resistor values i have right now are 150 and 1.5k ohm
<crest>
with 150ohm they are barely visible
<tp>
generally led on voltage is about 2.5 volts
<tp>
well 150 ohm will have to do
<crest>
let me put a second one in parallel
<tp>
measure the current thru the led, thats the critical factor