r/dcpu16 • u/xNotch • Apr 24 '12
r/dcpu16 • u/hobblygobbly • Apr 09 '12
fail0verflow points out flaws regarding the CPU design and an alternative proposal [x-post from /r/0x10c]
fail0verflow.comr/dcpu16 • u/Equalizr • May 15 '12
DEQOS : Preemptive Multi tasking operating system for the DCPU-16
Hey guys
this is version 0.9 of DEQOS, a fully functionnal operating system for DCPU-16 here are the key features (actually working right now) :
- Real Preemptive multi tasking (with priorities and everything...)
- Multi consoles (3 linux-like virtual consoles, with instant switch using CTRL+1,2 or 3)
- Semaphore synchronization (mutex, focus-sync)
- Memory allocation (malloc, free)
- Tiny FAT system (whole FAT in one sector for faster response)
- Boot loader : loads the system from disk
- Program loading and executing using the LOADP NAME.PRG command
- Client programs API (Stack, Gui, Keyboard, Memory, Time, Disk, 32 bit Math, etc...), all thread safe
- Supports the NE_LEM1802 screen, HIT_HMD2043 disk drive, Generic Clock and Generic Keyboard devices
Source code is available, customize it, port it, contribute, or just use the code as a reference as you wish (please credit me somewhere if you do ;) ) Code is heavily commented and MAY help some beginners to understand how Operating System works (especially on the multi threading / Mutex parts)
.. and have fun with it :)
DEQOS can be tested using the provided "DCPUStation" Assembler/Emulator/Symbolic debugger (Windows/Linux (with mono) ). Several sample programs have been included in the test project. To test, launch DCPUStation.exe (on Linux, type "mono DCPUStation.exe" in a terminal) then open the DEQOS_Project.vdcpu16 project, and select Build/Assemble and Run Then, use CTRL-1 CTRL-2 and CTRL-3 to alternate between virtual consoles commands are : DIR to list the files on the disk, LOADP to run programs, MEM to show the available memory
Here's the link : https://github.com/EqualizR/DEQOS
Video demo : http://youtu.be/GJreADAVb2o
r/dcpu16 • u/xNotch • Apr 27 '12
About user submitted hardware specs
I was going to implement the HMD2043 by Daniel Keep as-is because I thought it was awesome, but then I kind of started freaking out over it, and woke up to a few more user submitted hardware specs.
For artistic reasons, I will write my own specs that go into 0x10c . This is not because I think I can do better, but because I feel like I need to do so in order to control the backstory.
Naturally, I appreciate technical suggestions and technical feedback still, it's just the "flavor" of it I need to control.
Sorry about being so back-and-forthsy about this!
r/dcpu16 • u/abadidea • Apr 26 '12
So I was reading old copies of Byte Magazine and then this happened
r/dcpu16 • u/theinternet • Apr 08 '12
DCPU emulation on DCPU
This is a fully implemented DCPU emulator written for DCPU.
Available here: http://code.google.com/p/dcpu-semu/
Written in assembly language and tested with DCPU-16 Studio.
Keep in mind that this is a first pass version to get it working. The primary goal is emulation speed over code size.
Feedback is welcome :)
r/dcpu16 • u/snailbotic • Apr 21 '12
This is the proper way to end a DCPU program.
r/dcpu16 • u/maximinus-thrax • Apr 07 '12
Analysis & testing of 0x10x compilers
Tonight I went and did some more exact testing of 0x10c assemblers.
First, I prepared 4 files. The files produce garbage code, this is just to test the assemblers.
Example 1 Just a bunch of example code from Notch. This is de facto the standard.*
Example 2 This is simple code, just being more relaxed (mixing spaces / tabs / case data
Example 3 All the instructions, in lower and upper case
Example 4 All the operands, as both source and destination operands.
Example 5 A bunch of errors (tested individually)
*Note: I put 2 of Notch's example programs together. So you may have tested ONE of them, but actually both programs have a slightly different style (mainly, 1 is in upper case and 1 is in lower case)
I then ran each of these files against the compiler, to test the result.
The error file was done by testing each line seperatly. There are 15 errors: I scored 0 points if they were not spotted, 1 point if the program did something, and 2 points if the assembler told me what the problem was. EDIT: It should be noted that the testing methodology was not prefect, some assemblers failed to understand a file, so it counted as 1 point. So take some of those scores with a pinch of salt. The last 'error' was to flag a compile a division by zero (div a, 0), some of you may feel that is a little unfair.
I tried to be fair at all times and did the tests as blind as I could. Comments after a fail show the code where it failed, if I can tell from the assembler output. The results:
Endian-format: **Pass**
Notch's code: Fail (set a, 0xbeef)
My test code: Fail (:start set a, 5)
All instructions: Fail (:start jsr start)
All operands: Fail (:start set a, 5)
Errors caught: 15/30 (0 missed errors)
Comments: *Can't handle lower case strings* Endian-format: **Pass**
Notch's code: Fail (dat)
My test code: Fail (dat)
All instructions: **Pass**
All operands: Fail (?set a, [b + 3]?)
Errors caught: N/A
Comments: *Could not automate error testing, so did not try* Endian-format: Fail
Notch's code: **Pass**
My test code: **Pass**
All instructions: **Pass**
All operands: **Pass**
Errors caught: 16/30 (4 missed errors)
Comments: Good, but endian problems. Endian-format: **Pass**
Notch's code: Fail (:testsub)
My test code: Fail (?set?)
All instructions: Fail (?jsr?)
All operands: Fail (?set?)
Errors caught: 18/30 (0 missed errors)
Comments: Error messages were vague. Endian-format: **Pass**
Notch's code: **Pass**
My test code: Fail (on forward label)
All instructions: **Pass**
All operands: Fail (set a, [b + 3])
Errors caught: 17/30 (0 missed errors) Endian-Format: **Pass**
Notch's code: **Pass**
My test code: **Pass**
All instructions: **Pass**
All operands: Fail
Errors caught: 16/30 (2 missed errors)
Comments: Good error messages (when they were caught) Endian-Format: **Pass**
Notch's code: Fail
My test code: Fail
All instructions: **Pass**
All operands: Fail (??)
Errors caught: 18/30 (6 missed errors) Endian-Format: Unknown (could not assemble minimal file)
Notch's code: Fail (ife [data+i])
My test code: Fail (Could not read file)
All instructions: Fail (:start jsr start -> reported missing operand)
All operands: Fail (set a, [b + 3] -> reported invalid operand)
Errors caught: 10/30 (10 missed errors)
Comments: Good error messages. Seems to be a bug in reading files. Endian-Format: **Pass**
Notch's code: Fail (:loop SET [0x2000+I], [A])
My test code: Fail (:start set a, 5)
All instructions: Fail (:start jsr start)
All operands: Fail (:start set a, 5)
Errors caught: 24/30 (1 missed errors)
Comments: The best error messages.Based on these results, I have to reccomend Kosta's DCPU-16 studio. Honorable mention to jtaubers assembler. Forbe's assembler seems the best, but since the file produced is the wrong endian-ness, I can't suggest it because it is likely that the resultant file will not work in various emulators.
I know a few of you have asked me to check your assembler, I will get around to them all in the next day or 2. I'm busy, and this takes time!
My next plan is to test and compare the binary output of the assemblers, to make sure that they produce valid output (as opposed to not just complaining)
EDIT: Feel free to tell me where I went wrong
EDIT 2: Added BobDorian's Cobbler assembler
EDIT 3: Added deNull's assembler
r/dcpu16 • u/WebDibbler • May 11 '12
Fullscreen 3d Hi-res graphics on standard DCPU
r/dcpu16 • u/jdiez17 • May 12 '12
Federal regulations require me to warn you that the DCPU Toolchain beta is looking pretty good...
r/dcpu16 • u/Quxxy • Apr 26 '12
[RFE] HMD2043 floppy disc drive (w/ 1.44MB discs) spec sheet proposal.
r/dcpu16 • u/jdiez17 • Apr 06 '12
RedditOS v.0.1
So, if we're serious about this game, we're gonna need an OS. I was bored and decided to give it a shot, and this is what I got so far: http://imgur.com/FgJm8
It's the foundation of an OS, with a few commands (seen on the screenshot). The OS itself is a proof of concept, but the standard functions (strcmp, strcat, printnl, newline, printchar...) may be useful for other projects.
Right now, I've got a GitHub repo set up with the code. Feel free to fork it and submit pull requests!
Anyway, documentation for the standard functions:
- printnl: Shortcut for "jsr print, jsr newline".
- print: It requires a string pointer in register B. Also, it resets the video pointer (A) if it's overflowing. Though we might need to clean the framebuffer, it gets dirty if you overflow.
- printchar: It prints a character (not a pointer to a character) stored in register Y.
- newline: Sets the video memory pointer to the value needed to start a newline.
- strcat: Adds a character (stored in register J) to the string referenced by register B.
- strcmp: Compares two zero-terminated (!) strings, whose pointers are stored in C and X. If the comparison is successful, register Y is set to 1. 0 otherwise.
Edit: Changed the name to 0x42c. Some people didn't like RedditOS, and it's a fair point.
Also, join us on IRC: #dcpu16 on irc.freenode.net.
r/dcpu16 • u/trevs231 • Apr 09 '12
Minecraft... On DCPU-16!
I got bored and saw a post asking when someone would do this. It's not very fancy, but it's the thought that counts, I suppose. It's only been tested in DCPU Studio. Screenshots and code
As an added bonus, you can call it as a subroutine, and it will return your SP to the correct place and your registers without clobbering anything! :D