<remexre>
in the context of making an assembler, would it be reasonable to have e.g. R0 R1 R2 SUBr, where R0-Rn are just aliases for the literals 0-n and SUBr, figures out how to encode them?
<remexre>
or is there a better way that lets one continue to have prefix instructions, infer whether you need the register or immediate version of instructions, etc
<remexre>
I've seen the latter without an explanation, but idk if it was doing "real parsing" instead of just having a special dictionary
tabemann has joined #forth
<tpbsd>
remexre, mecrisp-across now uses under-bar before all assembler mnemonics such as:
<tpbsd>
_srli x15 x15 2
<tpbsd>
_bne x15 zero -
<tpbsd>
_mv x8 x14
<remexre>
How is it doing the parsing tho?
ryke has joined #forth
tpbsd has quit [Ping timeout: 248 seconds]
dave0 has quit [Read error: Connection reset by peer]
dave0 has joined #forth
tabemann has quit [Ping timeout: 256 seconds]
dddddd has quit [Read error: Connection reset by peer]
<tp>
rdrop-exit, 107 downloads of my Forth STM32F103C8-DIAGNOSTICS.bin now :)
<proteusguy>
That's a lot of forthing!
<tp>
proteusguy, and 99% are by windows using arduino types
<tp>
proteusguy, I doubt they even know it's a Forth system
<rdrop-exit>
kudos tp!
<tp>
proteusguy, it's a diagnostic program to identify fake STM32F103 mcu's
<tp>
rdrop-exit, I never thought it would get that high
<tp>
rdrop-exit, I figured it would top out at 42
<tp>
so rdrop-exit how is your flu, the volcano etc ?
<proteusguy>
there a lot of fakes going around or just rumours of fakes?
<rdrop-exit>
brb, have a call
<tp>
proteusguy, tons of fakes, it's not a rumour
<tp>
proteusguy, the one real fake is a chip marked "cks cs32f103C8", and not even the CKS factory lists it in their products, yet they're everywhere
<tp>
proteusguy, it's been decapped and is not a copy, it's a clone, the big problem is it identifies itself as a STM32F103 in all it's ID registers
<proteusguy>
wow that would be annoying. so how do you tell?
<tp>
proteusguy, another clone is the GD32F103, it's made by Giga Devices and marked accordingly, so it's a legit alternative implementation, but some unscrupulous sellers are sanding off the GD label and printing STM32F etc
<proteusguy>
so it's still identically functional just lying about the brand manufacturer?
<tp>
the 'clones' are "compatible" definitely not identical, and thats the problem
<tp>
one unexpected flag is that the original STM32F103 has a number of errata that were never fixed and never will be as that chip is long obsolete having been out since 2004
<tp>
one of the most serious errata is that the debug register cannot be read from a user program running on the chip *unless* the debug hardware is attached
<tp>
ironically the clones all seem to have fixed that issue!
<tp>
so my V2 of this diagnostic binary tries to read that register, and if it cant, then the chip is very likely a bonafide STM32f103
<proteusguy>
haha
<tp>
yeah, who'd have thunk it ?
<tp>
proteusguy, to get an idea of how endemic counterfeit chips are, take a long look at this site https://zeptobars.com/en/ it's russian, but the pics are just awesome, and they also compare the clones to the bonafides, note it takes a few hours
<tp>
but id very interesting if one is into clear chip die pics
<tp>
proteusguy, they must have some *very* serious gear to make those pics
<proteusguy>
universities have such stuff and they let kids play on them. ;-)
<proteusguy>
impressive images indeed
<tp>
I'm impressed, I have some good gear but my pics look lame in comparison
<tp>
good hobby gear
_whitelogger_ has joined #forth
mtsd has joined #forth
WickedShell has quit [Remote host closed the connection]
dys has joined #forth
xek has joined #forth
X-Scale` has joined #forth
X-Scale has quit [Ping timeout: 260 seconds]
X-Scale` is now known as X-Scale
mtsd has quit [Ping timeout: 272 seconds]
mtsd has joined #forth
WilhelmV1nWeiner has quit [Remote host closed the connection]