Liste des Groupes |
In article <vetqgo$1k6sl$1@paganini.bofh.team>,
Waldek Hebisch <antispam@fricas.org> wrote:albert@spenarnc.xs4all.nl wrote:In article <vesgmb$1i2rq$1@paganini.bofh.team>,>
>
For what it is worth.
I have ported the ciforth model (only 64 bits,the 5.4.0 level) onto
linux running on a riscv, taking advantage from earlier Dutch
implementation of noforth for triecky code words (UMD/MOD).
http://home.hccnet.nl/a.w.m.van.der.horst/lina.html
As usual, all words are extensively tested, all words are documented.
Thanks, works on Milkv.
>Once you have mapped the io space in virtual space and access it>
via VMA-IO, you can apply all knowledge gained from the documentation
of the underlying System On a Chip.
For this particular board the printed circuit layout, the schematics
(9 pages) and a full 1000+ page documentation of the SoC (Allwinner
D1) is available. That is why I bought it.
For Milkv there are schematics and chipset documentation (I did not
check how complete it is).
Could you try if the mapping succeeds?
Start up as root.
Now do
MMAP-IO
and check VMA-IO
It contains the virtual memory address, or possible an error code
-13. The SoC descriptions maps from VMA-IO.
You can also check DEV-MEM that should be 4, normally.
In forth.lab you can see the use of MMAP-IO in relation to
a number of SoC's.
I strive to have working: set-function gpio-on gpio-off gpio-on.
The io-nummers are system dependant.
Les messages affichés proviennent d'usenet.