<![CDATA[FPGA Arcade]]> http://www.fpgaarcade.com/punbb/index.php Tue, 08 Aug 2017 23:25:06 +0000 PunBB <![CDATA[Electron Data I/O]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=1309&action=new I think there was cartridge slot on expansion module with joystick port

Tue, 08 Aug 2017 23:25:06 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=1309&action=new
<![CDATA[unable to read ADF files with the latest Amiga release]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=1304&action=new JimDrew wrote:

Just moving the files from the sub-directory to the root directory makes everything work perfectly.

IMHO it's most probably not at all about moving anything to a sub-directory or to the root.
It's about loading the loader core (with that .ini) before loading the amiga core .ini.

AFAICT Kremlar should be able to repro the same DF0:???? problem by having everything in the root, but renaming the .ini to "replay_amiga.ini" and let the regular loader replay.ini be (if that "config" line is still in there).
Let the Replay load the loader replay.ini first and then the replay_amiga.ini (from the OSD) - should be enough to trigger the problem.

In any case - I think this is just the static/dynamic bits are not reset between loading new .ini's.

Fri, 28 Jul 2017 21:40:51 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=1304&action=new
<![CDATA[Optimal monitor choice (50 Hz etc.)]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=130&action=new cj wrote:

I'm thinking of getting a DVI-I to DVI-D and VGA adapter like this. Does this make sense at all?

I use that kind of adapter to have analog and digital side-by-side - one monitor with VGA and another with DVI input.
While I haven't tried myself I think you should be able to connect a VGA->SCART on the VGA out and drive a TV instead.

Mon, 09 Sep 2013 08:34:43 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=130&action=new
<![CDATA[We need help with the new WIKI]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=1308&action=new http://www.fpgaarcade.com has been redesigned as some of you might have noticed.
We also added a new wiki: http://www.fpgaarcade.com/knowledge-base/

We need help from the community writing articles for it. Here's a list of topics we need to be written. Help us!

Complete hardware setup instructions with pictures, including how to set it up for dev'ing (rs232 + null modem changer + usb-serial) and xilinx USB cable

Complete software setup instructions for building / creating new cores and update the arm fw (edited)

Howtos for the different cores, what they are capable of at the moment and where to find them (and the usual disclaimer about not being able to provide roms)

Links to decent vhdl tutorials wouldn’t be bad either (like the one @gouky sent to me

“how to ‘box’ the replay board - picospu, atx adapter, suggestions on boxes”

Mon, 07 Aug 2017 16:05:42 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=1308&action=new
<![CDATA[Floppy board extension]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=1141&action=new Will you be making a floppy adapter available then?

Thu, 14 Jul 2016 20:29:42 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=1141&action=new
<![CDATA[Hardware availibility]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=1096&action=new Any new updates to share this week smile

Fri, 11 Mar 2016 07:30:26 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=1096&action=new
<![CDATA[Forum]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=1307&action=new IP board all the way.. cost is small, and it's great to use. Not free, but close.

Sat, 05 Aug 2017 10:00:30 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=1307&action=new
<![CDATA[About adding XDRAM to the system]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=1306&action=new Anyway it is not necessary to write the file with the modified kickstart, just add a few DATA lines in the Replay.Ini for example:

DATA = 0x01,0x00F83962,1

For Kickstart 3.1 (40.069) (A1200)

The first DATA modifies the address where it looks for RAM and the second corrects the checksum.

Tue, 01 Aug 2017 20:26:20 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=1306&action=new
<![CDATA[RTG]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=277&action=new Lots more to come smile

Thu, 27 Mar 2014 09:08:17 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=277&action=new
<![CDATA[Upgraded to latest ARM firmware now C64 doesn't work]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=1305&action=new Thanks Mike. I can wait for the release.

Sun, 30 Jul 2017 19:34:56 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=1305&action=new
<![CDATA[Latest firmware for the FPGA arcade board 1.0B]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=1044&action=new erique wrote:
mmartinka wrote:

I do not really understand how exactly the "Mount SDCard" entry works in the ARM menu.

It mounts the SDCARD over USB to your host PC (as a MassStorageDevice), so that you can read/write the files on the Replay SDCARD without having to physically remove the SDCARD from your Replay and insert it in your PC/SDCARD reader.

I think I outlined it in detail in the previous post but maybe I missed something?

Thanks for description...

Wed, 30 Dec 2015 23:15:33 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=1044&action=new
<![CDATA[C64 core talk]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=236&action=new Just the default.  I'll feel pretty stupid if there's something I should be changing:

# Replay INI file


#    "123456789012345678901234567890"
info = "  Replay/C64 (c) 2015 W.S."
info = ">>> http://www.pin4.at/  <<<"
info = "--- Joystick in Port A/B ---"
info = "-Keyboard in lower PS/2 prt-"

bin = c64_1541_1761.rpl

# sets initial clocking (PLL)
# M1, N1, M2, N2, M3, N3, ps0, ps1, ps2, ps3, ps4, ps5, pd0, pd1, pd2, pd3, pd4, pd5, ys0, ys1, ys2, ys3, ys4, ys5
CLOCK = 245, 1144, 343, 1375, 46, 423, 1, 4, 4, 0, 2, 0, 1, 14, 5, 1, 4, 1, 1, 1, 1, 0, 1, 0

# sets composite/svhs coder, if fitted

# sets video filter for all 3 channels
# dc=250mv, 9MHZ
VFILTER = 0, 0, 3

# tells the firmware what will be available after FPGA got configured
#         vid
en_twi =   1
#         cfg osd
en_spi =   1,  1

# replay button configuration
#        off / menu / reset
button = menu


# VGA/DVI settings, "EN_TWI" must be set to one !
#           0x1c 0x1d 0x1e 0x1f 0x20 0x21 0x23 0x31 0x33 0x34 0x35 0x36 0x37 0x48 0x49 0x56
video =     0x00,0x48,0xC0,0x80,0x00,0x01,0x00,0x80,0x08,0x16,0x30,0x60,0x00,0x18,0xC0,0x00

# 2x32bit static+dynamic configuration bits, "CFG" in EN_SPI must be set to one!
# It is only required if no menu setup is given (which manipulates the settings as well)
#         31                             0,  31                             0
config = *11111111111111111111111111111111, *11111111111111111111111111111111


# enables verification feature, checks back any ROM/DATA upload

# C64 ROMs
ROM = basic.901226-01.bin,     0x02000,0x0001A000
ROM = characters.901225-01.bin,0x01000,0x0001D000
ROM = kernal.901227-03.bin,    0x02000,0x0001E000

# C64 monitor (last operand states it is a PRG file type
# with the start address in the first two bytes)
#ROM = mon/atmon-c000h, 0, 0, 1

# 1541 ROMs
ROM = 1541-c000.325302-01.bin, 0x02000,0x0004C000
ROM = 1541-e000.901229-03.bin, 0x02000,0x0004E000


title = "C64 Loader"

# loader menu, filters for "PRG" extension
# (requires ARM FW from 1mar2014 or newer)
item = "Load PRG to RAM" , loadselect, 0x00000000
#                           FFFFFFFFHRV
option = "*.PRG"         , *00000001000, flags

title = "1541 Disk Select"

# IEC bus address of 1541
item = "1541 IEC adr.",  0x00000300,static
option = "@8",           0x00000000,default
option = "@9",           0x00000100
option = "@10",          0x00000200
option = "@11",          0x00000300

# write protection override
item = "D64 WR protect", 0x00008000,dynamic
option = "ENABLED",      0x00008000,default
option = "DISABLED",     0x00000000

# loader menu, filters for D64 extension
item = "Set D64 Disk",cha_select, 0

title = "C64 SETTINGS"

item = "JOY swap/merge",  0x000000C0,dynamic
option = "default setup", 0x00000000,default
option = "both on low",   0x00000040
option = "both on up",    0x00000080
option = "swap low/up",   0x000000C0

item = "GEORAM module",   0x00000004,static
option = "enable",        0x00000004,default
option = "disable",       0x00000000

item = "GEORAM size",     0x00000018,static
option = "512 kB",        0x00000000,default
option = "1 MB",          0x00000008
option = "2 MB",          0x00000010
option = "4 MB",          0x00000018

item = "512k GEORAM img.", loadselect, 0x00780000
option = "*.IMG"         , 0,flags

title = "C64 DEBUG SETTINGS"

# module setting
item = "EXROM pin",        0x00000001,static
option = "/EXROM=1 (off)", 0x00000001,default
option = "/EXROM=0 (on)" , 0x00000000

item = "GAME pin",         0x00000002,static
option = "/GAME=1 (off)" , 0x00000002,default
option = "/GAME=0 (on)"  , 0x00000000

item = "VIC registers",  0x00000002,dynamic
option = "Show all",     0x00000002
option = "Hide all",     0x00000000,default

item = "VIC reg.pos.",   0x00000700,dynamic
option = "0 (top)",      0x00000000,default
option = "1",            0x00000100
option = "2 (middle)",   0x00000200
option = "3",            0x00000300
option = "4 (bottom)",   0x00000400

item = "Sprites",        0x00000001,dynamic
option = "enabled",      0x00000001,default
option = "disabled",     0x00000000

item = "Freeze core",    0x00000004,dynamic
option = "enabled",      0x00000004
option = "disabled",     0x00000000,default

title = "Audio/Video Setup"

item = "Video Mode",       0x00000020,dynamic
option = " HD 720x576p50", 0x00000020,default
option = " SD 720x576i50", 0x00000000

item = "Scanlines",        0x00000018,dynamic
option = "3...MAX",        0x00000018
option = "2...MED",        0x00000010
option = "1...MIN",        0x00000008,default
option = "0...OFF",        0x00000000

# HDs / Carts / Floppys etc
cha_cfg = "removable", D64

Mon, 17 Feb 2014 21:35:58 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=236&action=new
<![CDATA[Dual-booting the Replay and the Amiga with a single SDCARD partition]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=1303&action=new With the most recent ARM firmware (July 24, 2017) we added support to connect the entire SDCARD as a block device to the Amiga IDE bus. This means that, using common tools and drivers, you can now read/write to the SDCARD FAT32 partition and even boot the Amiga directly from it.

Assuming you already have an SDCARD setup with the appropriate Replay related files (replay.ini, replay_amiga.bin, kick31.rom, system.hdf, ...) you will also need GiggleDisk and FAT95, both available from Aminet.

Before trying this I recommend that you back up your SDCARD, and ideally also zero out the first 16 sectors/blocks as any old data might interfere with the dual MBR + RDB setup.

The key to this is to edit the replay.ini file and add/change the chb_mount command to

chb_mount = "?mmc",0


chb_mount = "?mmc",1

depending on if you want to attach it as master or slave.

By attaching the SDCARD as slave, and your usual "system.hdf" as master, you should be able to query and mount the SDCARD like this


chb_mount = "System.hdf",0
chb_mount = "?mmc",1


3.System:> GiggleDisk scsi.device 1 prefix FAT mountdos
GiggleDisk (c)2005 Guido Mersmann

 0, DosType: 46415401, LowCyl:       2048 HighCyl:   15521792, Size:    7 GB, FileSystem: L:fat95 

Mounting 'FAT0:'

(provided you've installed GiggleDisk and FAT95 ofc. Actual cyl/size values will most likely differ wink.
N.B. Make sure you have enough stack to run GiggleDisk - otherwise it will crash/guru!

If everything looks fine you can tell FAT95 to write back a matching RDB starting from the second block of the SDCARD, leaving the MBR (at block 0) intact.

3.System:> boot95 FAT0:

You can confirm that the RDB was written correctly by rebooting into the Amiga Early Startup Control, and inspect the Boot Options. It should now list the FAT0: as a bootable partition.
Attempting to boot from FAT0: will get you nowhere at this point - you'll need to reinstall Workbench (or copy an existing installation) to FAT0:

And when that is done you can swap the master/slave (or simply remove the previous .hdf completely)

chb_mount = "?mmc",0
#chb_mount = "System.hdf",0

and boot directly from the SDCARD.

Fri, 28 Jul 2017 17:47:21 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=1303&action=new
<![CDATA[cdrom os 3.9 install]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=1302&action=new @uigiflip

If you mean "attaching raw partitions" (i.e. partitions lacking an RDB) then yes - we added this in the latest firmware.
The RDB is just fake tho - and you cannot change any of its settings (doing so will throw an error in HDToolBox).

This also allow people to use the ClassicWB images as-is with the Replay.

Mon, 24 Jul 2017 18:46:40 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=1302&action=new
<![CDATA[ao486 - i486SX core + SoC]]> http://www.fpgaarcade.com/punbb/viewtopic.php?id=326&action=new phluxx wrote:

Hopefully I do not start an emotional discussion  here wink

You do not. :-)

phluxx wrote:

What I mean is: Amiga, C64, vintage consoles, arcade hw etc. are programmed tightly around the HW timing. Programmers synchronized the execution time of commands with the speed of the video signal.

You normally do not have that in the PC world. PCs always had different speeds (there was the one first IBM PC, but it wasn't so dominant).

Also, there were only very few smooth 2D scrollers with exactly 50/60 fps on the PC.

I understand what you mean. In fact, I agree with you. It's just beside the point. :-)

Whether on Amiga or on DOS-era PC, there are only two real options for running your software: keeping old hardware around or using some kind of virtual machine/emulator. In this respect, the two platforms are very much alike. I'd like the Arcade board to provide a third option.

phluxx wrote:

There is not *the* single PC timing which is important to have an authentic experience of a game. Start Up a VM, or even an emulator, and the game will feel as original as in the past. At least for my personal perception.

The difference emulation/FPGA was striking for me on the Amiga. I would not expect this for pc games.

Running vintage software in complex virtual machine or emulator software on top of an already extremely complex stack of hardware and software is a different experience from running it directly on the relatively simple, original hardware. In my opinion, the Arcade board is a good compromise between the two.

Tue, 10 Jun 2014 19:30:56 +0000 http://www.fpgaarcade.com/punbb/viewtopic.php?id=326&action=new