Zarutian_HTC has quit [Read error: Connection reset by peer]
Zarutian_HTC has joined #forth
Zarutian_HTC has quit [Quit: Bye]
<tabemann>
back
<tp>
tabemann, only 8pm! you finish tea early ? ;-)
<tabemann>
lol
<tp>
I installed debian 10.4 last night on a spare pc so I could compile blackmagicprobe
<tp>
debian failed at the HDD and asked me for a ISCSI and Im like WTF, and cursed it to high hell
<tp>
then I had an epiphany and looked inside the pc ... no hdd <doh>
<tp>
after that it was plain sailing, compiled BMP and it's working. Im just about to add RTS so I can use the virtual terminal for my serial connection
<tp>
but I gotta say, the C code in that is pretty frightening, I've no idea how people actually work with that stuff
<tabemann>
-D_DEFAULT_SOURCE was needed for the S_IFMT stuff and usleep
<crest>
that breaks the build on freebsd
<crest>
which operating systems are the broken ones?
<tabemann>
on the other hand, eliminating -std=c99 eliminates the need for those defines
<crest>
damn it i followed the opengroup docs
<tabemann>
so then the only thing that should break freebsd is the use of -lstlink
<crest>
which stlink version did you install?
<tabemann>
I'm on 1.6.0 right now
<tabemann>
compiled from source
<crest>
okay because i'm still on 1.5.0
<crest>
because 1.6.0 was never packaged for freebsd
<crest>
and 1.6.1 is too broken
<tabemann>
it's 1.6.1 which breaks things horribly, not 1.6.0
<crest>
yeah 1.6.1 is an embarrassing release
<tabemann>
it's embarrasing that the developers defend it pointlessly
<crest>
well they explained how it happend
<tabemann>
like seriously, if you don't want people using your shared library... don't make one
<tp>
but stink has a 'code of conduct' !!! so theyre the best!
<tabemann>
codes of conduct can go to hell
<crest>
tp: please let's not start this flamewar
<crest>
a code of conduct has valid uses
<crest>
but it can't replace quality code
<tp>
tabemann, I'm with you here
<tp>
ill leave you guys to it
<tabemann>
codes of conduct don't replace being a developer who listens to one's users, who tries not to break things, who fixes things when they inevitably get fucked up, who is not a stuckup asshole, and so n
<tabemann>
anyways
<tabemann>
saying "we don't support X" to every complaint reflexively is a good example of the kind of thing that gets me, code of conduct or not
<tp>
ok I found where to add RTS flow control to BMP
<tp>
almost there
<tabemann>
BMP?
<tp>
tabemann, times have changed, once FLOSS developers would respond with thanks for a bug report and fix it right away
<tp>
Blackmagic probe
<tabemann>
ah
<tp>
tabemann, it uses libopencm3
<tp>
tabemann, and at least it compiles under debian 10
* tabemann
would be happy that someone was actually using his software to the point that they could produce a bug report
<tp>
tabemann, it fails badly under FreeBSD and openindiana
<tp>
tabemann, exactly
<tp>
once I have RTS on the BMP then I have a virtual term plus a virtual gdb server on the one USB connection
<tp>
and it's ready to use in my existing system
<tp>
no need for stlink or swd on the pc
<tp>
all I need on the pc is gdb etc
<tp>
then my bluepill equivalent simply replaces my $0.99 usb-3.3v dongle
<tabemann>
right now the only issues I'm having are that I can't use stlink 1.6.1
<tabemann>
I haven't had any problems with serial aside from the lack of RTS/CTS
boru` has joined #forth
boru has quit [Disconnected by services]
boru` is now known as boru
<tp>
well you have your ack/nak thingie ?
<tp>
you dont need CTS on the target, all thats needed is RTS
<tabemann>
ack/nak works fine for me with e4thcom
<tp>
the target cant send faster than a PC can receive
<tp>
do you want RTS ?
<tp>
I'll get it going on the F407 if you want it
<tabemann>
the problem is that the USB-serial dongle I have doesn't support RTS anyways
<tp>
oh yeah
<crest>
tp: or just ignore the bug report
<tp>
I forgOt
<crest>
and close it years later as "overcome by events"
<tp>
crest, what are you on about ?
<tabemann>
<tp> tabemann, times have changed, once FLOSS developers would respond with thanks for a bug report and fix it right away
<tp>
well times have changed
<crest>
e.g. mozilla has bugs that are over a decade old and still not fixed
<tp>
people used to develop because they loved it, now many just want to be leet and cool programmers
* tabemann
programs for his own purposes because he likes creating stuff, while he programs at work because he needs a job
<tp>
crest, mozilla was always like that iirc, hardly a bastion of dedicated programmers, probably too commercial and always pushed to deliver with short timeframes ?
<tabemann>
my job is all about short timeframes
<tp>
tabemann, yeah your hobby work is awesome, youre easy to work with and consider all comments
<tp>
tabemann, sign of the times at work ?
<tp>
at least here on #forth people care about good programming, good code :)
<tabemann>
at work they have the philosophy that if they set an amount of time to be set in a period, it will get done regardless of how big or small that period is, so they might as well make it really small so they can get more stuff done
<crest>
FUZxxl reviewed my terminal.s and came up with a patch to decrease the code size even further
<tabemann>
right now I'm just going to stick with 1.6.0
<tabemann>
everything else seems more complicated and more difficult
<crest>
but it looks like this uses optional parts of the debug hardware
<crest>
and its unidirectional
<crest>
just target -> host
<tabemann>
yeah everything seems like either doesn't do everything we'd want, or is more elaborate, or requires purchasing more hardware and configuring it, or all of the above
<crest>
i'm not against purchasing hardware as long as it isn't to expensive or hard to get
<tabemann>
my problem is not the money but the wait
<tabemann>
and I don't want to spend even more money on amazon prime
<crest>
e.g. a ftid232h cable wouldn't be too hard to get (in germany)
<crest>
gn8
<tabemann>
unless it has a counterfeit chip in it, and ftdi's next windows update bricks it
<tabemann>
nacht
<tp>
yeah, counterfit is a real problem
<tabemann>
and ftdi's bricking of counterfeit chips is why I won't buy from them
<tp>
that was the stupidest move ever, it hurt them badly
<tp>
the BMP has all kinds of SWD tips, even a SWD reader
<tp>
I think it's worth a look
<tp>
and genuine STM32F103s can be bought via various reliable channels
<tp>
just not on ebay or aliexpress
<tp>
I have 20 brand new genuine STM32F103's
<tabemann>
i.e. one of STMicroelectronic's official dealers
<tp>
tabemann, right
<tp>
but mouser, avenet, arrow electronics are all reliable
<tabemann>
yes]
<tp>
just dont buy from asian companies if you dont want fakes
<tp>
my STM32F103's came from AVENET
<tp>
in texs
<tabemann>
buy from companies who source their components directly from STM
<tp>
Texas
<tp>
yes, as you say one of STMicroelectronic's official dealers
<tp>
ok rebuilding BMP with RTS enabled on the usart, will it work ?
<tabemann>
we shall see!
<tp>
it's abig build
<tp>
C stuff is MASSIVE
<tp>
the code is like a mad womans breakfast
<tp>
how doe people work with this stuff, it cant be any fun
<tp>
I feel tainted already
<tabemann>
how does it even fit on an f103?
<tp>
it needs 100KB of flash
<tp>
and they all have 128 even if they dont advertise it
<tabemann>
ah
<tp>
so plenty of space
<tabemann>
I was wondering, I thought the f103 had 64K of flash
<tp>
the R8 model has 128KB
<tabemann>
I see
<tp>
but so does the 64 KB model, it's the worst kept secret
<tp>
at some point STM used the die from the larger model in the smaller model and then set the flash size register to 64KB instead of 128KB
<tp>
thinking no one would notice
<tp>
and apps like stlink read that register so it think that only 64KB is available
<tabemann>
cheaper for them than actually having to maintain two sets of masks
<tp>
one just changes the stlink config
<tp>
exactly
<tp>
build hasnt bombed yet :)
<tabemann>
good luck...
<tp>
the debian machine is on a dual core amd slowpoke 'hp-miniserver'
<tp>
well I followed the API that it was built with
<tp>
honestly, it's so easy to configure RTS in assembler, I dont see the purpose for all this massive C palaver
<tp>
easier in Forth
<tabemann>
it's because stuff in C tends to be overengineered
<tp>
but Ive learnt a lesson, build Linux stuff on a Linux pc, it's infinitely easier
<tp>
forget trying to cross build, it's a frigging nightmare
<tp>
especiall where Linux is involved
<tabemann>
and I've learned from trying to build crest's code that trying to compile FreeBSD code on Linux is a nightmare
<tp>
Exactly
<tp>
it's a road to madness
<tabemann>
even though I don't get why he insists on some things like -std=c99 and all the warnigns
<tp>
thats why I recommend a BMP for his idea
<tp>
no OS involvement
<tp>
you just flash a binary to a blue pill (or equivalent, and there are plenty) and it's done
<tabemann>
his code works fine provided one set up the proper build settings (no -std=c99) and one uses 1.6.0 not 1.6.1
<tp>
thats why the BMP exists, people on windows, linux,mac,bsd all had trouble with openocd and gbd etc
<tp>
one BMP fixed all those problems
<tp>
hah it built!
<tp>
now to test!
<tabemann>
cool
<tp>
Im thinking of moving to openindiana ... because I like it so much, but no stlink or openocd. But with a bmp I dont need them
* tabemann
is sticking with Debian because there are certain programs he uses (e.g. Discord) that he isn't sure would be available on BSD or openindiana
<tp>
oh yeah, all good reasons
<tp>
I have a Linux box for Linux stuff now and Im keeping it as is
<tabemann>
I don't like change when it comes to computing environments
<tabemann>
okay, I'm falling asleep so I'm gonna hit the sack