There's a new version of the high score list hack that has been tested on real hardware
Go there
torsdag 15 december 2011
måndag 3 oktober 2011
Mamepanel with Linux
The Mamepanel is great when building an usb arcade controller. It's a customizable (at build time) joystick/keyboard/volume control in one AVR uC. One drawback is that my two joystick setup wasn't recognized as two 8 button joysticks but rather as one joystick with 18 buttons. This is a known problem with using AVRUSB with a Linux-machine.
The only solution i found to the problem was to recompile the Linux usbhid module and mark the Mamepanel as quirky.
This is how I did it on Debian Lenny:
as root:
Get the source
The only solution i found to the problem was to recompile the Linux usbhid module and mark the Mamepanel as quirky.
This is how I did it on Debian Lenny:
as root:
Get the source
aptitude update aptitude install linux-source tar jxvf /usr/src/linux-source-2.6.26.tar.bz2 linux-source-2.6.26/drivers/hid cd linux-source-2.6.26/drivers/hidAdd these lines where they fit in /usr/src/linux-source-2.6.26/drivers/hid/usbhid/hid-quirks.c. The USB_DEVICE_ID_WIKIDOT_MAMEPANEL32 device id should probably be changed to something else if an ATMEGA8 is used (can be checked with lsusb).
#define USB_VENDOR_ID_VOTI 0x16c0
#define USB_DEVICE_ID_VOTI_MAMEPANEL32 0x05df
{ USB_VENDOR_ID_VOTI, USB_DEVICE_ID_VOTI_MAMEPANEL32, HID_QUIRK_MULTI_INPUT },
Build and load the new module (It's probably a good idea to check that usbhid.ko exists before rmmodding the old one)make -C /usr/src/linux-headers-$(uname -r) M=$(pwd) modules cd usbhid/ rmmod usbhid && insmod usbhid.kohope for the best.
onsdag 7 september 2011
Space Invaders high score list hack
(edit) Added a new version to the bottom of the post (/edit)
The space invaders high score hack adds a high score list to Space Invaders, the arcade version, when inserted in the original game code.
Two high score list screens are added. One before a demo game begins and one after a player is game over. If the players score is high enough when game over occurs an enter initials screen is shown.
The hack has been developed using a game version using four 2Kbyte roms.
The time and effort put into this was greatly reduced by using the thorough disassembly comments by Chris Cantrell at http://computerarcheology.com
Screens
 |
| Game over screen |
 |
| High scores shown before demo screen |
 |
| Enter initials screen |
Download
spacehigh000.zip source and patch in hex format. Does NOT contain any roms.
I have only tried this in MAME so there are NO guarantees that it will work on the real hardware.
spacehigh001.zip source and patch in hex format. Does NOT contain any roms.
This version has been successfully tested on real Midway L-shaped hardware strapped for 9316 EPROMs. The f chip was replaced with a ST M2732A.
söndag 9 januari 2011
MobileLCD
Description
MobileLCD is a J2ME (MIDP2.0) implementation of just enough of the commands in the Goldelox MD1 graphical display module command set to make the GOLDELOX driver in serdisplib work. It can be seen as an J2ME serial LCD Emulator.
The application uses the StreamConnection class and has been tested using, but should not be limited to:
Specs
Usage
Specify serial port
At startup LCDEmu enumerates the serial ports available on the device (not including Bluetooth ports).
Set resolution
The resolution can be selected using a list of valid values.
Run
When the set up is done press Run.
Using with Linux
USB cable
When connecting a phone to my Debian box using an USB cable three serial ports show up under /dev/ and it's only a matter of pointing serdisplib to the right one
The display can be tested with serdisplibs testserdisp command (make sure you have the correct permissions to use the port:
testserdisp -n GOLDELOX -p "RS232:/dev/ttyACM2" -d 2
Bluetooth
To connect a phone to my Debian box using Bluetooth I use rfcomm (in bluez-utils package?):
# You probably have to pair your phone with the computer before trying this.
# Add a Serial Port Profile to our computer
sdptool add SP
# Wait for phone to connect to channel 1, create /dev/rfcomm2
rfcomm listen 2 1
# Test display
testserdisp -n GOLDELOX -p "RS232:/dev/rfcomm2" -d 2
Lcd4linux talking to MobileLCD running on a Nokia 2760 over Bluetooth:
Lcd4linux talking to MobileLCD running on a SE P990 over USB:
Download
MobileLCD_0.02.jad
MobileLCD_0.02.jar
MobileLCD is a J2ME (MIDP2.0) implementation of just enough of the commands in the Goldelox MD1 graphical display module command set to make the GOLDELOX driver in serdisplib work. It can be seen as an J2ME serial LCD Emulator.
The application uses the StreamConnection class and has been tested using, but should not be limited to:
- Serial port
- Serial port over Bluetooth
Specs
- Resolutions: 320, 220, 176, 160, 128, 96, 64
- Implemented commands: 0x42, 0x45, 0x49, 0x55, 0x56, (0x59 returns ACK but doesn't do much)
- Goldelox MD1 mode
- Experimental PICASO SGC rev 5 mode
- No backlight or screensaver control
Usage
Specify serial port
At startup LCDEmu enumerates the serial ports available on the device (not including Bluetooth ports).
- To open one of the enumerated serial ports use comm:
. Example: comm:USB2 - To make a serial port connection over Bluetooth use btspp://<remote device address> <channel> Example: btspp://001122334455:1
The resolution can be selected using a list of valid values.
Run
When the set up is done press Run.
Using with Linux
USB cable
When connecting a phone to my Debian box using an USB cable three serial ports show up under /dev/ and it's only a matter of pointing serdisplib to the right one
The display can be tested with serdisplibs testserdisp command (make sure you have the correct permissions to use the port:
testserdisp -n GOLDELOX -p "RS232:/dev/ttyACM2" -d 2
Bluetooth
To connect a phone to my Debian box using Bluetooth I use rfcomm (in bluez-utils package?):
# You probably have to pair your phone with the computer before trying this.
# Add a Serial Port Profile to our computer
sdptool add SP
# Wait for phone to connect to channel 1, create /dev/rfcomm2
rfcomm listen 2 1
# Test display
testserdisp -n GOLDELOX -p "RS232:/dev/rfcomm2" -d 2
Lcd4linux talking to MobileLCD running on a Nokia 2760 over Bluetooth:
Download
MobileLCD_0.02.jad
MobileLCD_0.02.jar
söndag 26 december 2010
Open source LPC17xx development
This summer I wanted to try something new in the microcontroller area and decided to advance from 8-bit AVR and PIC to 32-bit ARM. There is a jungle of ARM-based microcontrollers out there and deciding on which one is "the best" isn't very easy. I ended up choosing an NXP LPC17xx Cortex-M3 based micro controller since the price was fairly good and I found MicropendousX, an open hardware dev-board project with free open source schematics and pcb-layout in KiCad (free open source EDA-tool) format.
I used the 1758 version (Seems abandoned in favour for the 1768) but removed ethernet and redrew the layout using more hole-mounted components to make it easier to mount, probe and re-wire.
I will add the schematic and board files someday, hopefully soon...
The result:
Features:
The GNU toolchain I use is the arm-none-eabi lite edition of G++ from Codesourcery.
As an IDE I use Eclipse. Stepping through C and assembler code works like a charm. I think I used these instructions to get it working.
I used the 1758 version (Seems abandoned in favour for the 1768) but removed ethernet and redrew the layout using more hole-mounted components to make it easier to mount, probe and re-wire.
I will add the schematic and board files someday, hopefully soon...
The result:
- LPC1758 clocked at 12.5MHz internally "PLLed" to up to 100MHz
- JTAG-connector, can be used for programming and debugging
- SD-card slot (verified working using M. Thomas Chan's FatFs port)
- USB-port (verified working using CMSIS USB mass storage device example)
- Access to all pins of the chip
The GNU toolchain I use is the arm-none-eabi lite edition of G++ from Codesourcery.
As an IDE I use Eclipse. Stepping through C and assembler code works like a charm. I think I used these instructions to get it working.
lördag 25 december 2010
Calling Cortex-M3 assembler function in RAM from gcc C
I needed a fast function written in assembler and run from RAM. I thought the most simple way to do this without adding stuff to the linker script was to change the .text directive to .data (same as initialised variables). But the result of the change was a hard fault when the function got called.
The solution was to tell gcc it is a function with .type logic_sample_fast, %function
So the whole function looks like this:
The solution was to tell gcc it is a function with .type logic_sample_fast, %function
So the whole function looks like this:
.syntax unified .cpu cortex-m3 .thumb .data .align 4 #define FIO0PIN (0x2009c014) #define FIO1PIN (0x2009c034) #define LOGIC_IN_FIOPIN_REG FIO1PIN .global logic_sample_fast .type logic_sample_fast, %function .thumb_func logic_sample_fast: movw r1, :lower16:LOGIC_IN_FIOPIN_REG movt r1, :upper16:LOGIC_IN_FIOPIN_REG cpsid i trig0: ldrb r2, [r1] ands r3, r2, #1 bne trig0 trig1: ldrb r2, [r1] ands r3, r2, #1 beq trig1 .rept (40*8) ldrb r2, [r1] strb r2, [r0], #1 .endr cpsie i bx lrAnd the definition in C like this:
void logic_sample_fast(uint8_t *buffer);
fredag 30 juli 2010
ZRip - extract the Z code text adventure part of a zblorb file
The Z machine is a virtual machine used by Infocom in the 80's-90's so that they more easily could port their different text adventure games to the many different platforms of the time. The Z machine has its own instruction set called Z code. Some versions of the Z machine support images and sound.
IF-Archive contains many Z-code games playable on a Z machine.
The blorb-format is a format developed to collect the Z code, images and sound that were previously in separate files into one single file. (Btw, blorbs can contain code for other interpreters as well, not just Z code)
This is were ZRip comes in.
Blorbs can contain high resolution sound and images and become quite big and not suitable for machines with limited memory capacity. ZRip reads a blorb-file and tries to extract just the Z code.
Here's the source
IF-Archive contains many Z-code games playable on a Z machine.
The blorb-format is a format developed to collect the Z code, images and sound that were previously in separate files into one single file. (Btw, blorbs can contain code for other interpreters as well, not just Z code)
This is were ZRip comes in.
Blorbs can contain high resolution sound and images and become quite big and not suitable for machines with limited memory capacity. ZRip reads a blorb-file and tries to extract just the Z code.
Here's the source
Prenumerera på:
Inlägg (Atom)