Welcome to the Parallax Discussion Forums, sign-up to participate.
evanh wrote: »
Intriguing, since I don't have a FPGA I haven't tried to read any of sources previously. Mike, you say launch then copy ... this means that the SETQ + RDLONG pair somehow does a block copy, correct?
evanh wrote: »
Well, that's certainly effective, looking at SETQ2 also, but not something to be showing the average beginner. Just keeping a grasp of who is running what and where can become fragile me thinks.
I guess it can't really be much simpler while still allowing so many operating modes.
User Name wrote: »
Why lock it? They will probably be several more FPGA updates in the near future.
There is already a new thread to cover that.
Cluso99 wrote: »
I just updated the stickie (copied the above post).
But how do I get a link to the actual post so I can add a link in the first post???
Current files (bleeding edge) Dropbox files and binaries
The new Tachyon Forth Glossary of words (Kernel, Extend, Filesystem) --- Introduction to TACHYON Forth (+links to files)
Propeller Hardware Explorer and debugger (with VGA)
Watch Easynet in operation --- Build Tachyon V4 video
cgracey wrote: »
Updates images are now available from the top of this thread!
Rayman wrote: »
Do we really need to always populate the interrupt vectors?
Or, is this only required for debugging? (hope so)
include "nodebug.pasm" ' lives in Propeller Library folder, sets debug vectors to all be RETI0