The Powder Toy

BIOS Concept for R16K1S60 CPU by Cool4Cool

Cool4Cool
Cool4Cool
177 / 11
27th Dec 2016
23rd Sep 2017
This is a BIOS for the R16K1S60 CPU by lbphacker. This is just an idea, and is probably not the best it could be (e.g. it runs slowly, I'm still a noob). Feel free to improve upon the concept w/ credit. Specification/source: http://pastebin.com/JR5jTHra
computer electronics processor bios goodstuff r16k1s60 iherelikespie rterm 60hz subframe

Comments

  • QuanTech
    QuanTech     31st Dec 2016
    make a c compiler with opengl :PPP
  • QuanTech
    QuanTech     31st Dec 2016
    WAT? LBPHacker, what is this 'C Compiler' thing I hear going around???
  • Cool4Cool
    Cool4Cool     31st Dec 2016
    @Aavak, as was already discussed, the keyboard is not used for the demo. You need to write a program to be able to use it.
  • Aavak
    Aavak     31st Dec 2016
    the keyborad dose not work
  • unknownkarma
    unknownkarma     31st Dec 2016
    Oh, I didn't notice that was there, but even if I did I don't think I would have known how to use it. Thanks.
  • LBPHacker
    LBPHacker     30th Dec 2016
    You *can* do that with rasm. Is it not in the manual? @org 0x20 // db 120 (where // is a newline)
  • unknownkarma
    unknownkarma     30th Dec 2016
    That comment shifted a bit :c
  • unknownkarma
    unknownkarma     30th Dec 2016
    Neither, I suppose more of a memory editor added to the compiler. Currently when you use the compiler it clears all the memory except for the code.. I was hoping you could directly store data. So instead of something like mov ax, 120 mov [0x20], ax you could instead tell the compiler to directly insert 120 to 0x20, not including it in your code. But prehaps the C assembler will already cover that with variables.
  • Weretyu777
    Weretyu777     30th Dec 2016
    I know a bit about math and programming and I am kinda clueless as to what's being talked about here.
  • LBPHacker
    LBPHacker     30th Dec 2016
    That depends on what you mean by storing values at addresses. If you mean storing immediate x at address immediate y (mov [imm], imm), well, that's something even i7 processors can't do. If you mean storing immediate x at address indirect y (mov [reg], imm), sure, that's gonna work! Although it's a feature of the architecture, not of the compiler/assembler.