<tp>
youll have to take it apart and look at the pcb
<tp>
see what is actually in it
<tp>
?
<tabemann>
I'll trust what that page says
<tabemann>
as there's no visible screws on the calculator
<tp>
so what do you think is in it ?
<tabemann>
probably a STM32F730V8T6 because I just bought this calculator
* tabemann
is reading Epsilon source code to get a picture of how they interface with flash
<tp>
hmm
<tp>
did they change the mcu after Mecrisp-Stellaris made their version for it ?
<tabemann>
that's my guess
<tabemann>
this Epsilon code uses the MPU for memory regions
<tp>
all stm32 mcus have a chip type ID in rom
reepca has quit [Ping timeout: 260 seconds]
<tp>
Mecrisp-Stellaris does support the STM F746 Discovery chip = STM32F746NG
dave0 has quit [Quit: dave's not here]
reepca has joined #forth
reepca has joined #forth
<tp>
address space and is seen by the system as if it was an internal memory
<tp>
· memory-mapped mode: the external Flash memory is mapped to the microcontroller
<tp>
The QUADSPI is a specialized communication interface targeting single, dual or quad SPI
<tp>
Flash memories.
<tp>
problem solved :)
<tp>
the mcu does all the work
<tabemann>
yes, that's what I gathered
<tabemann>
what I'm wondering is what do I have to do to configure it so it works properly
<tp>
thats from the STM32F777 manual
<tp>
the first thing I do is generate a svd2forth from the chip cmsis-svd and have a look
<tabemann>
this damn Epsilon code hides everything behind data structures...
<tabemann>
like Arduino
reepca has quit [Ping timeout: 258 seconds]
<tp>
it's got 6 SPI peripherals
<tp>
C loves structures
<tabemann>
this is C++
<tabemann>
so they're not like C structs
<tabemann>
but rather classes with methods
<tp>
recently a very experienced engineer on a forum I read claimed that cmsis-svd included "structures of registers"
<tp>
C thinking is so pervasive
<tabemann>
I've programmed over the years in C or C++, like at my last job, yet for something like this I want to see registers and bitfields
<tp>
for embedded you mean ?
<tp>
embedded is different to systems programming, C tries to make them the same imho
<tabemann>
yeah
<tabemann>
what I did was applications programming mostly
<tp>
thats the mainstream I think
<tp>
you now have a feel for that embedded difference I imagine
<tabemann>
stuff for MRI machines, stuff for printing presses, stuff for simulators for spacecraft instruments - I was for a short bit doing some embedded though, all in C though
<tp>
looks like one must configure for the SPI memory chip
<tabemann>
the thing is I have to figure out how to configure the SPI interface
<tp>
so your Forth would need a word to configure for the spi at init I guess
<tp>
thats not going to be too hard once you study the spi chip data
<tp>
and the mcu config
<tp>
I find SPI really easy
<tp>
what you CAN do is load a Forth into the on MCU flash and experiment
<tp>
thats the whole point of Forth afterall
<tp>
bbl, off shopping
reepca has joined #forth
reepca has quit [Ping timeout: 256 seconds]
jsoft has joined #forth
jsoft has quit [Ping timeout: 258 seconds]
reepca has joined #forth
gravicappa has joined #forth
dys has joined #forth
mtsd has joined #forth
xek has joined #forth
dddddd has quit [Ping timeout: 260 seconds]
WickedShell has quit [Remote host closed the connection]
xek has quit [Read error: Connection reset by peer]