This is quite interesting.

-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0\|734\|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Off Topic -> This is quite interesting.
Sun, 18 Nov 2007, 09:27
power mousey	The Mach64 Programmable Logic Kit www.xgamestation.com/phpbb/viewtopic.php?t=6382 I also found out about CPLD. en.wikipedia.org/wiki/CPLD \|edit\| I would probably get this but my hardware heart and my wallet is saved up towards the XGS 6502. \|edit\|
Sun, 18 Nov 2007, 10:52
Phoenix	What is the Mach64 programmable logic kit?
Sun, 18 Nov 2007, 10:58
Dabz	What is the Mach64 programmable logic kit? Its a kit that can program logic for a Mac64!?! Whatever that means.. hehehe Dabz -=-=- Intel Core i5 6400 2.7GHz, NVIDIA GeForce GTX 1070 (8GB), 8Gig DDR4 RAM, 256GB SSD, 1TB HDD, Windows 10 64bit
Sun, 18 Nov 2007, 11:13
power mousey	hehe seriously, in all probablity....a hobbyist kit from Andre Lamothe for learning and experimenting with Field Gate Arrays and thousands and tens of thousands of logic gates for both hardware hacking and software programming. if anyone is interested just contact him to sign up as a beta tester. You'll have to sign a NDA(Non-Disclosure Agreement). \|edit\| I'm still set on the XGS 6502. come on Andre, get it out \|edit\|
Tue, 20 Nov 2007, 03:15
power mousey	here are some screenshots of the Mach64 programmable logic kit also the book is included too. a hardware project with it
Tue, 20 Nov 2007, 13:39
dna	Looks like you can make the cartridges for different gaming modules with this. I've never seen it before. -=-=- DNA
Tue, 20 Nov 2007, 15:32
power mousey	well hey dna you aint seen nothing yet! especially with the up n coming XGS 6502. unlike the original XGS and even the Hydra... this XGS 6502 will be some hardware oriented. but more towards software and game programming with 6502 assembly language, an advanced built-in Basic and perhaps a tool chain system later with perhaps both a C and Forth-like language as well. I wish Andre would put up some screenshots and/or some code demos from the XGS 6502. Yet, its top secret hush hush and with beta testers and demo coders writing demos,games and other apps on the various prototypes. Its very tight lid and sealed. Yet, here is some code from using the original XGS emulator/editor and assembler...and no doubt will be used in one form or another for use in XGS 6502 assemly language programming. ; *********************************** ; Demo by kent williams ; ; CONSTANTS ****************** API_Hook: .EQ $FFFF ; General API Functions API_Exit: .EQ $01 API_Get_Rand: .EQ $02 API_Get_Key_State: .EQ $03 ; GPU Functions GPU_Load_Sprites: .EQ $0F GPU_Set_Color: .EQ $04 GPU_Draw_Point: .EQ $05 GPU_Draw_Line: .EQ $06 GPU_Draw_String: .EQ $07 GPU_Draw_Sprite: .EQ $08 GPU_Draw_Sprite_16x16: .EQ $09 GPU_Draw_Screen: .EQ $0A GPU_Lock_Video: .EQ $0B GPU_Unlock_Video: .EQ $0C GPU_Clear_Screen: .EQ $0D GPU_Flip: .EQ $0E ; Directions UP: .EQ 0 DOWN: .EQ 1 LEFT: .EQ 2 RIGHT: .EQ 3 ; Directions KEY_UP: .EQ $C8 KEY_DOWN: .EQ $D0 KEY_LEFT: .EQ $CB KEY_RIGHT: .EQ $CD KEY_SPACE: .EQ $39 ; ZERO PAGE DATA ************* .ORG $0 key_map: .DB $FF, $00 ; Long Pointer long_ptr: long_ptr_h: .DB 0 long_ptr_l: .DB 0 ; DATA *********************** .ORG $600 ; Global parameter passing area api_func: .DB 0 p_0: .DB 0 p_1: .DB 0 p_2: .DB 0 p_3: .DB 0 p_x_0: .DB 0 p_y_0: .DB 0 p_x_1: .DB 0 p_y_1: .DB 0 p_r_0: .DB 0 p_g_0: .DB 0 p_b_0: .DB 0 ; Global return value passing area r_0: .DB 0 r_1: .DB 0 r_2: .DB 0 r_3: .DB 0 ; Temporary registers tr_0: .DB 0 tr_1: .DB 0 tr_2: .DB 0 tr_3: .DB 0 ; Misc. flags key_press: .DB 0 ; DEMO VARS counter: .DB $00 point_x: .DB $0F point_y: .DB $14 ; CODE *********************** .ORG $A00 main_loop: clear_screen: LDA #$00 STA p_0 LDA #$1F STA p_1 LDA #GPU_Clear_Screen STA api_func JSR API_Hook ; Lock the video buffer LDA #GPU_Lock_Video STA api_func JSR API_Hook set_color: ;set drawing color ;Red-like color LDA #$F1 STA p_0 LDA #$00 STA p_1 LDA #GPU_Set_Color STA api_func JSR API_HOOK set_point: LDA point_x STA p_x_0 LDA point_y STA p_y_0 LDA #GPU_Draw_Point STA api_func JSR API_HOOK unlock_video: ; Unlock the video buffer LDA #GPU_Unlock_Video STA api_func JSR API_Hook ; Blit the frame buffer ; to the screen LDA #GPU_Flip STA api_func JSR API_Hook ;time delay JSR time_frame key_pressed: ; Grab the keyboard status LDA #API_Get_Key_State STA api_func JSR API_Hook LDA #0 STA key_press ;keyboard wait...key wait. JSR time_frame ; Check for the exit key ; (escape) LDY #$01 LDA ( key_map ), Y BNE exit_routine ;check for the Right arrow key ;205-->scan code LDY #205 LDA (key_map ), Y BNE right_arrow ;check for the Left arrow key ;203-->scan code LDY #203 LDA (key_map ), Y BNE left_arrow ;no keys pressed..or none ;of the specific keys pressed ;go back to main_loop...the start. JMP main_loop ;* exit routine * exit_routine: LDA #API_Exit STA api_func JSR API_Hook ;* right arrow routine * right_arrow: LDX point_x INX CPX #80 BNE store_px1 DEX store_px1: STX point_x JMP main_loop ;* left arrow routine * left_arrow: LDX point_x DEX STX point_x JMP main_loop ;* time frame function * time_frame: ;time frame to slow down drawing ;and for input...general time delay LDX #50 load_y: LDY #250 time_nop: NOP NOP NOP NOP NOP NOP NOP DEY BNE time_nop DEX BNE load_y RTS ; ; ASSETS ********************* .ORG $8000 string: .DB 66,76,0 ; SYSTEM VECTORS *************** .ORG $FFFA .DB $0A, $00 ; /NMI - Non-Maskable Int .DB $0A, $00 ; /RES - System reset .DB $0A, $00 ; /IRQ - Interrupt Request .END --v I could continue just using this. But its just an alpha version and incomplete. Also, I don't want to miss out on the XGS 6502 when it comes out.
Wed, 21 Nov 2007, 10:11
power mousey	um if anybody is curious or even interested.... under zero page data, the memory addresses of 0 to 255 are allocated and used for the keyboard scan codes. now and under this section of code: key_pressed: ; ** Grab the keyboard status LDA #API_Get_Key_State STA api_func JSR API_Hook LDA #0 STA key_press ;keyboard wait...key wait. JSR time_frame ; Check for the exit key ; ** (escape) LDY #$01 LDA ( key_map ), Y BNE exit_routine ;check for the Right arrow key ;205-->scan code LDY #205 LDA (key_map ), Y BNE right_arrow ;check for the Left arrow key ;203-->scan code LDY #203 LDA (key_map ), Y BNE left_arrow ;no keys pressed..or none ;of the specific keys pressed ;go back to main_loop...the start. JMP main_loop --v initially, when the key poll routine is called the memory map of zero page data is reset. Since this is an alpha version and the docs for the various GPU and API functions is brief: I don't know if the memory map is zeroed out and if a particular key is pressed that corresponds to one of the memory map keys is set to a one. While the other keys remain in a state of 0. There could be a different function or method for this API function of polling for a key input. But the one I assume will suffice, is simple and works. And highly probable is the method used. so if a Escape key is pressed and its scan code is 1. So the contents of register Y is loaded with 1 to test for a Escape key. the accumulator or register A is loaded with the contents of the first memory address of key_map...and which is $00. And the contents of $00 contain 0. Add the 1 in the reister Y to key map memory adress and the memory address is $01...zero page memory address. Finally, register A is loaded with the contents of memory addrss $01. The contents of both contain 1. Since the whole key map is zeroed out in all of its zero page memory addresses of key map...except for key_map memory address $01 which contains a 1. The Escape key with a scan code of 1 was pressed and acquired too. And....and, since a 1 from memory address is loaded into the accumulator this affects the flag status bit. Since a zero is not contained in the zero flag..it sets/resets to a 0 for FALSE. The BNE exit_routine is true and will perform its entire intstruction. The program will exit. Since, we are testing for a Escape key and with the scan code of 1. The keys are all memory mapped. Actually its all quite simple too.