<tabemann>
that's because words is not in the kernel
<tp>
i found that, uploading basic.fs now
<tp>
so far so good
<tabemann>
int_io.fs doesn't work right now, btw
<tp>
no problemo
<tabemann>
I've essentially given up on interrupt-driven IO
<tabemann>
for the f407
<tp>
I'm using picocom with a 200ms EOL ... so slow
<tp>
good idea
<tp>
interrupt-driven usart you mean ?
<tabemann>
yeah
<tp>
i considered doing that to mine also, but realised that the polled usart is plenty, the hold up is in the compiling
<tp>
expecially with a 'slow' 75Mhz f0
<tp>
it's easily able to handle 460800 baud in polled mode
<tp>
ok, words is working :)
<tabemann>
back
<tp>
matthias version was like that, so I wrote a 4 column word lister I named words4
<tp>
words4
<tp>
2over 2tuck 2rot 2-rot
<tp>
--- MS RA 2.5.1 tpmod ---
<tp>
2>r 2r> 2r@ 2rdrop
<tp>
2dup 2drop 2swap 2nip
<tp>
d2/ d2* dshr dshl
<tabemann>
the reason why I'm trying to get some kind of asychronous IO working is getting multitasking working
<tabemann>
without constant PAUSEs trashing IO performance
<tabemann>
but I'm finding that IO performance is being trashed regardless
<tp>
ahh!
<tp>
the cooperative multitasker for Mecrisp-Stellaris works nicely (until overloaded) but uses too many resources for me
<tp>
I looked at some of the best OSS real time systems such as Freertos but they are huge for F0
<tp>
so I decided that a scheduler is all I want for f0
<tabemann>
okay
<tabemann>
I figured out that even when I comment out all my IO hooks, IO doesn't work with the multitasker on f407
<tp>
sure the F4 is very powerful compared to the F0 but it's still very,very limited compared to a pc
<tabemann>
maybe I should figure out some way to speed it up
<tp>
speed what up ?
<tabemann>
the f407
<tabemann>
from its default of 8 MHz
<tp>
oh yeah it's a slug at 8mhz
<tp>
there is Mecrisp-Stellaris user code to speed it up
<tp>
pll-120mhz.txt for the non RA
<tp>
I hear they go to 220 MHz and was going to try that sometime
<tp>
now that the basics are working I'll add RTS handshaking to your assembly code
<tp>
(or try to)
<tp>
and up the baud to my usual 460800
dave0 has quit [Quit: dave's not here]
<tabemann>
back
<tabemann>
okay, I got simpler IO working with multitasking at 168 MHz
<tabemann>
so I'm going to see of interrupt-driven IO works at 168 MHz
<tp>
168MHz will be a lot faster
iyzsong has joined #forth
jsoft has quit [Ping timeout: 246 seconds]
<tabemann>
yah
gravicappa has joined #forth
proteus-like has quit [Ping timeout: 240 seconds]
<tabemann>
ugh why is systick giving me trouble all of a sudden
reepca has joined #forth
gravicappa has quit [Ping timeout: 252 seconds]
<tabemann>
tp
<tabemann>
check out the code now
<tp>
ok
<tabemann>
it works... except that if you *slow down* the systick too much USART IO gets screwed up
<tabemann>
I get the impression it's due to the USART interrupt not waking up the code from sleep
<tabemann>
so it's relying upon the systicks to get wakeups so it can do IO
cartwright has quit [Write error: Connection reset by peer]
<tabemann>
so the systick goes too fast
<tp>
hmm
<tabemann>
overall it works, except that ms is broken
<tabemann>
I don't have this problem on the L476 though
<tp>
the L series have a lot of differences to ?
<tp>
tho
cartwright has joined #forth
<tabemann>
my guess is there is some interrupt wakeup mask thing going on that I don't know about that's only in the F4 MCUs
<tabemann>
anyways, I do have to get to bed
<tp>
interrupts can cause all kinds of weirdness, I think one has to specially instrument them
<tp>
np, it's working fine, Im just uploading basic.fs atm
<tabemann>
yes, I just confirmed it
<tabemann>
it's the sleep that causing the problem
<tabemann>
I'm going to turn off sleeping for the time being
Keshl has quit [Read error: Connection reset by peer]
Keshl has joined #forth
<tp>
ok, I'll use the latest commit
<tabemann>
just did a commit a second ago
<tabemann>
a simple test to make sure it works is:
<tabemann>
: test begin ." *" 1000 ms again ;
<tabemann>
' test 256 256 256 spawn constant test-task
<tabemann>
test-task enable-task
<tp>
ok
<tp>
btw I can do current measurements here when you like
<tp>
as we have the same f4 disco
<tabemann>
cool
<tabemann>
I do have to get to bed though
<tp>
just post what youd like done and I'll do the test and post the results
<tp>
sure
<tp>
we can work on it by leaving text here
<tp>
noght-o
<tp>
night-o
<tabemann>
I'll have to look in the irc-logs because my IRC client cuts off the log at a certain length
<tp>
it's pretty quiet here
<tabemann>
(I used to use a home-grown IRC client that had unlimited length logs but then my ISP blocked port 6667 for some reason so I had to switch to TLS and my IRC client doesn't support TLS)
<tabemann>
anyways good night
<tp>
night-o
<tabemann>
and let me know how much luck you have with zeptoforth
<tp>
will do
iyzsong- has joined #forth
iyzsong has quit [Ping timeout: 240 seconds]
gravicappa has joined #forth
gravicappa has quit [Ping timeout: 260 seconds]
jsoft has joined #forth
xek has joined #forth
xek_ has joined #forth
xek has quit [Ping timeout: 256 seconds]
mtsd has joined #forth
xek_ has quit [Remote host closed the connection]
xek_ has joined #forth
the_cuckoo has quit [Remote host closed the connection]
proteusguy has joined #forth
gravicappa has joined #forth
cheater has quit [Quit: leaving]
cheater has joined #forth
cartwright has quit [Remote host closed the connection]