JOURNAL: Infinity Squared (Mark )

previous page next page
  • Crazy drunk pedestrian... 2006-06-09 10:41:03 Bah... so much fog... I had my hopes up for crashing into a ghost along the way... but it was uneventful by the end of it... just meant I was leaning across the steering wheel all the way home...

    Something's stirring... 
  • YAAAAAAAAAAARRRRRRRRRRRRR!!!! 2006-06-08 10:00:20 Damn it... I had a long post written up T_T


    Now I gotta settle for saying that Rina is up in the air... probably... maybe... I dunno...


    GAhhhh, why did I have to click on that link T_T 
  • Nostalgia 2006-06-01 11:26:34 Wow... tomorrow is the final day of my university school days (not counting exams)...

    Been taking heaps of pictures and planning to see how long before the battery in my DV cam holds up tomorrow too...

    I'll post more about how it is to be near 4 and half years of labour tomorrow when it's actually over ^_^ 
  • Happy Birthday Kadaj! 2006-05-31 09:19:39 Yeah... happy... birthday... and all that... XD 
  • I'm developing an ulcer... 2006-05-27 12:06:17 ... I'm betting...

    This program is freaking pissing me off.

    I'm writing the VHDL code for this Xilinx FPGA (Spartan 3 developer board). It's essentially a single instruction micro computer (in case I haven't already said that in a journal post somewhere). Basically it'll take from a memory location (a RAM for all intents and purposes) the 8 bit binary instruction (as woud have been interpreted from the assembly language conversion which is luckily none of my concern) and run with it. Pipelining and such are not employed. It's a straight off, fetch the instruction, decode the instruction, run the instruction, get results for the instruction... hence "single instruction" architecture.

    Anyway, the coding itself isn't difficult, but more like tedious. Mind numblingly tedious. I don't even want to imagine how multi-instruction architectures are done, combined with pipelining and multi-threading. Yeah, it's probably done with these FPGAs... The real difficulty really is in the development software, the Xilinx code generator and simulator.

    What's wrong with it? It's a bitch, that's what. It not only ruins the code you write, but tricks you as well into thinking something's happening before it eats it, and then re-writes all the codes stored in your harddrive locally (hence why I have to continually make back ups in USB drives), and then gives out errors which don't really have any sort of hint why they are happening...

    T_T

    I've got 2 time states running at the moment... But it ends when it tries to access the program itself from memory... Yeah, I'm screwed... because when the program to run is not in the memory then you're running garbage...

    I only ever need to access that memory and then everything will be as right as rain T_T

    x_x 
previous page next page
Current server time: Sep 16, 2025 17:24:23