Microvision homebrew (part 10)
I downloaded the drivers and stuff and it came with some documentation. I was scanning it, and have realized that I'm in over my head here. I have worked with assembly before with Odyssey2 programming, but I have absolutely zero thoughts as to what this all means. One of the pdf documents I got is 399 pages long (!) and on page 32, there is a list of characters that I could use, like letters and numbers and stuff. I don't need that for the Microvision, all I need is to turn the pixels on and off. I wonder how I would tell the Propeller chip this, and also tell it the size of the screen (16x16). With assembly, I still can't memorize even the more simpler hexadecimal numbers, and turn to the windows calculator programming mode to convert decimal numbers to hexadecimal. So I guess the next step is to look at the sample code. That's how I learn, by tweaking sample code and learning the changes made. I think what I'll do is get familiar with the Propeller sample program, what it does and then try to make my own Propeller code. The problem is the box refers to lights, so the Propeller chip lights up. I don't really see anything on the chip that would light up. I think the greatest thing about this is that the Propeller chip can hold up to 32k, so maybe 10 years from now, I might be able to make a Tetris game for the Microvision. (My 2600tris game for the VCS was 32k and worked well.)
4 Comments
Recommended Comments