| Author |
Message |
Forum: Projects Topic: Introducing the 65m32 |
| robfinch |
|
Posted: Sun Aug 07, 2016 4:30 am
|
|
Replies: 48
Views: 100857
|
| Thanks for the post Mike. I've been looking forward to learning more about 65m32. As Dr. Jeff and Mike already mentioned I have to third the motion for 8/16 bit data support. Maybe leave some room open for 64 bit operands as well. In my one core I had just 32 ... |
|
 |
Forum: Projects Topic: Introducing the 65m32 |
| Dr Jefyll |
|
Posted: Sun Aug 07, 2016 4:27 pm
|
|
Replies: 48
Views: 100857
|
| ... me alright, because my #1 project would be to write a Forth kernal. And, Mike, I know you've coded Forth primitives as a means to road-test the 65m32 instruction set. I'm sure those test cases worked out fine . But other folks have different goals, and that's where the extra registers become ... |
|
|
Forum: Projects Topic: Introducing the 65m32 |
| barrym95838 |
|
Posted: Mon Aug 08, 2016 6:31 am
|
|
Replies: 48
Views: 100857
|
| ... haven't stumbled into any rude ones yet, at least not in standard English. As I told Garth, I'm quite fond of uniform-length mnemonics, and the 65m32 is no exception. This fondness is not without its awkward moments, though. "cdc" is "complement and add with carry", "cdd" ... |
|
|
Forum: Projects Topic: Introducing the 65m32 |
| barrym95838 |
|
Posted: Thu Aug 11, 2016 7:02 am
|
|
Replies: 48
Views: 100857
|
| ... instruction do with a literal value such as this? In most microprocessors, this mode of addressing is undocumented or forbidden, but the 65m32 makes use of it, by simply modifying the behavior of such instructions: :a0100003 sta #3,x \ This is equivalent to ldx #3,a but \ with no flag ... |
|
|
Forum: Projects Topic: Introducing the 65m32 |
| barrym95838 |
|
Posted: Sat Aug 13, 2016 2:19 am
|
|
Replies: 48
Views: 100857
|
| ... any) DEC TO+1 DEX BNE MU1 RTS ... and here's the same thing (actually better, because it chooses the correct direction by itself) ... \----------- 65m32: 11 words ----------- \ Move memory up/down (1 W to 4 GW) \ x = source start address \ y = destination start address \ b = number of words to ... |
|
|
Forum: Projects Topic: Introducing the 65m32 |
| MichaelM |
|
Posted: Sat Aug 13, 2016 7:58 pm
|
|
Replies: 48
Views: 100857
|
| Mike: Great set of demo programs. Clearly shows the expressive power of the architecture. I'd like to suggest that you provide a comment regarding the example source code you included with your assembler code for common FORTH words; it appears to me to be 80x86 assembler, but I don't see where you'v... |
|
|
Forum: Projects Topic: Introducing the 65m32 |
| barrym95838 |
|
Posted: Sun Aug 14, 2016 5:44 am
|
|
Replies: 48
Views: 100857
|
| ... instructions, and could be considered needlessly tricky, but I believe that it's the shortest and most efficient way to do the task (for the 65m32, not necessarily for the human composing, debugging, and/or maintaining this little gem). :) Mike B. |
|
|
Forum: Projects Topic: Introducing the 65m32 |
| BigEd |
|
Posted: Sun Aug 14, 2016 7:40 am
|
|
Replies: 48
Views: 100857
|
| Thanks for the code examples - it's a crucial part of a new architecture, to see what the software would look like, and not always made explicit. As I've said elsewhere, I'm fully in favour of a word-based architecture. Bear in mind that the people who will speak up (on anything) are the people who ... |
|
|
Forum: Projects Topic: Introducing the 65m32 |
| BigEd |
|
Posted: Mon Aug 15, 2016 6:13 am
|
|
Replies: 48
Views: 100857
|
| ... - he won't necessarily have time to follow the discussion here, but this gives us all a chance to see and respond to his thoughts: Nice to see the 65m32 project back to life again. Meanwhile, I took a look at your 65m32 text at anycpu.org. Literals now seem to be 16 Bit instead of 17. I remember, ... |
|
|
Forum: Projects Topic: Introducing the 65m32 |
| barrym95838 |
|
Posted: Sun Aug 21, 2016 6:34 am
|
|
Replies: 48
Views: 100857
|
| ... I wanted to let you know that I'll try to take some time to prepare my next post soon. In it, I will be examining the under-explored territory of 65m32 interrupt and exception management, and I will need some help from you guys in hammering out some of the low-level details. Thanks for watching, ... |
|
|
Forum: Projects Topic: Introducing the 65m32 |
| barrym95838 |
|
Posted: Thu Sep 01, 2016 7:52 am
|
|
Replies: 48
Views: 100857
|
| ... have a lot of experience with these, so I'm just going to throw out some ideas and let you guys evaluate them. The initial incarnation of the 65m32 will not have a separate supervisor mode, but I don't want to cripple a future version by doing something stupid early on. Please tell me if you ... |
|
|
Forum: Projects Topic: Introducing the 65m32 |
| BigEd |
|
Posted: Thu Sep 01, 2016 8:28 am
|
|
Replies: 48
Views: 100857
|
| About long-running instructions: ARM provides two modes, a conventional mode where instructions will finish before the interrupt, and a fast-interrupt mode where instructions are abandoned and will be restarted after the RTI. (It does not offer what the later 68000 did, which is to save internal mac... |
|
|
Forum: Projects Topic: Introducing the 65m32 |
| robfinch |
|
Posted: Fri Sep 02, 2016 5:32 am
|
|
Replies: 48
Views: 100857
|
| 2) 65m32 instructions can be one or two words long. This could cause future memory management issues if, for example, an instruction straddles a paging boundary. Is it too soon to think about stuff like this? One means of avoiding ... |
|
|
Forum: Projects Topic: Introducing the 65m32 |
| barrym95838 |
|
Posted: Thu Sep 29, 2016 5:08 am
|
|
Replies: 48
Views: 100857
|
| ... 5) Install eForth. 6) Optimize eForth for size (first) and speed (second). 7) Learn enough Verilog to configure an inexpensive FPGA board as a 65m32 emulator. 8) Learn how to use eForth to do pretty much anything else, including porting other interpreters and/or compilers. I will post my simulator ... |
|
|
Forum: Projects Topic: Introducing the 65m32 |
| BigEd |
|
Posted: Thu Sep 29, 2016 8:35 am
|
|
Replies: 48
Views: 100857
|
| Just thinking aloud: I suppose vectored interrupts are useful when - peripherals are plugged in with an accompanying ROM with the drivers on - there are more sources of interrupt than interrupt lines and you need to handle more than one of them in a very time-critical fashion Of course, I'm used to ... |
|
|
| Sort by: |
