Programming Computer for processor

  • massey101
    3rd Nov 2010 Member 0 Permalink
    Jason, I have managed to replicate your error and am very confused
    This error does not occur when reading from any other ram slot. Until then try not writing to ram slot 0

    EDIT: The problem is that every time a ram slot is read ram slot 0 is autocleared! I would deffinately avoid using ram slot 0 for programs (maybe use it for a display that does not have to read from)
  • JasonTroll
    3rd Nov 2010 Member 0 Permalink
    >:U
    Stupid RAM lol.

    Anyway, thanks for the help.

    Also, epic creation, I love it <3
    If only it didn't take 15 minutes to run the entire stack ;-;
  • massey101
    3rd Nov 2010 Member 0 Permalink
    Yer I know speed is definitely the drawback!
    I was thinking of using the ram off jacksonmj's "8x6 Line text display" to stack commands into a waiting line to wait to be written to the stack.
  • Simon
    3rd Nov 2010 Administrator 0 Permalink
    massey101
    I don't know if it will help, but I made a stack, I suppose you could either use it as a pointer for a static "data block" or use it as some sort of memory
    LoadSaveBlock(48909);
    And a slightly improved version
    LoadSaveBlock(49259);
  • massey101
    3rd Nov 2010 Member 0 Permalink
    Simon thats Great, its even in the correct orientation! I will just connect it up with a modified clock and see how it goes
  • Simon
    3rd Nov 2010 Administrator 0 Permalink
    I've tested it a bit, and it should run at "maximum speed" (i.e. Pure spark from battery), so you should not have any problems with the clock.
  • massey101
    3rd Nov 2010 Member 0 Permalink
    Na with the clock, Its just cause I only want it to write at particular times. You'll see when I finnish it
  • massey101
    3rd Nov 2010 Member 0 Permalink
    There we go Simon, I have completed the new processor with your stack to save the data before it is compiled and then built. (See first Post)

    EDIT: OK I can't edit the first post

    The new one is PCL Computer V1.3

    It now has two new buttons Compile and Build.
    To use write your program using the main buttons, a spark will be sent down and multiple sparks will be sent back, wait for these to complete before clicking the next one.
    (make sure you do not double click it will ruin the whole program) (Also make sure you do not go past the end otherwise the beginning of the program will be deleted).

    When done click Compile, this will start going and make the program ready to be built. When this has finished and no more sparks are going, click Build. This will then proceed to place the program in the stack and move it down to the bottom.

    If you are lame you can still use the original. Finally make sure to vote it up.

    LoadSaveBlock(49983);

    EDIT: Also sometimes rarely a dot of CNCT will not fall correctly. Just delete it if this happens.
  • JasonTroll
    3rd Nov 2010 Member 0 Permalink
    When I activate the 'BUILD' button, nothing happens, only when I apply a spark near where the sparks from the BUILD button cease, do I get any thing to actually happen.

    Is it supposed to be this way ?
  • massey101
    3rd Nov 2010 Member 0 Permalink
    I do not understand what you mean, the build button is activated with NUET after you have made and compiled a program.

    EDIT: Oh crap it doesn't save whether a switch is on or not...

    When you start it up there will be a void arrow near the centre spark the PSCN that it points at to get it started

    EDIT: I will start working on an alternative

    EDIT: I think I've fixed it using some of devast8a's flip flops