Add support for Freescale mcf5206e peripherals for Pluto 6 emulation #13261
Conversation
|
Just to make a note regarding the m68000 core changes, I only added these lines, but it seems running m68kmake.py and m68000gen.py rewrote the files and probably changed all the white spacing or something to cause those 12k changes. //m68k_in.lst
4ac8 ffff halt . . c:0p
m68ki_trace_t0(); /* auto-disable (see m68kcpu.h) */
m_icount = 0;
m_stopped = STOP_LEVEL_HALT;
//m68000.lst
4ac8 ffff halt - - |
|
a few basic things. Hashes should be in lowercase, not CAPS also you've added a set of all NO_DUMP ROMs, we don't do that, this represents no data at all. ROM_START( pl6_atw ) |
Ah thank you for reminding me, will add the dump details now. I need to submit those, actually. |
|
the CAPS thing in general applies elsewhere too btw, you've got uppercase in many other places too, MAME tends to prefer lowercase to pick a few random ones out m_vfd[m_cursor-1] = (m_buff[m_cursor-1] | vfd_charMap[m_cmd & 0x3F]); (but there are many more) |
|
all in all I'm just happy somebody is giving these attention though, many of these fruit machine boards use very specific CPU variants where internal peripherals need doing. When everything was added it was added with the hope that they'd eventually be picked up and fleshed out, and sorted out properly. |
| U56: MC68682 DUART | ||
| B1: Varta NiCd 3v SRAM battery, which is likely leaking if not already replaced. | ||
| EXP 0+1: Fujitsu Cremson MB86290A/Expansion ports. |
There was a problem hiding this comment.
There was a problem hiding this comment.
i.e. I don't remember big differences between Cremson and Orchid really ...
There was a problem hiding this comment.
It is, but I was getting errors about not having a screen attached despite not installing the device, so I commented it out for now.
There was a problem hiding this comment.
It needs a configured screen_device and a ram_device as absolute bare minimum (needs the host for gathering data).
MB86292(config, m_gpu, 0);
m_gpu->set_screen(m_screen);
m_gpu->set_vram(m_vram);
// m_gpu->set_xint_cb().set(FUNC(alien_state::gpu_irq_w<0>));There was a problem hiding this comment.
Or, in case of Pluto 5, SDRAM is on Calypso 16 card, I went the ram_device approach because this is a 200x card, and eventually it's gonna give back a penalty depending on what type is mounted.
PS: left is FPGA.
There was a problem hiding this comment.
It needs a configured
screen_deviceand aram_deviceas absolute bare minimum (needs the host for gathering data).MB86292(config, m_gpu, 0); m_gpu->set_screen(m_screen); m_gpu->set_vram(m_vram); // m_gpu->set_xint_cb().set(FUNC(alien_state::gpu_irq_w<0>));
Yeah but I needed to think about it as the video device isn't always installed (actually quite a lot), so was going to only have those included when needed, not always in the class definition
There was a problem hiding this comment.
Yep, because that is isolated from the rest of the system, needs a bus slot mechanism instead ...
There was a problem hiding this comment.
Will do that when I get chance.
|
Will sort that 'statement has no effect' error when I'm back and free |
| * Game Notes * | ||
| pl6_cm: Hybrid Pluto 6 + PC setup. They are connected over RS232. Pluto 6 is probably handling IO and security here. | ||
| Uses a Intel Celeron (2.1Ghz) PC with a Protech PROX3770 motherboard. Game runs on Windows XP. | ||
| pl6_dev: Heber's official development kit for the Pluto 6. Only ships with a development BIOS and an SDK. | ||
| This "game" requires a bootable (FAT32 with Active partition) CHD, else it does nothing visually. | ||
| The CHD in this driver is an image of the CF card that was supplied by Heber in the SDK for demo purposes. | ||
| Security and FPGA encryption is disabled on this model. | ||
There was a problem hiding this comment.
Can't find anything about the Protech PROX3770 beyond some bare listing. The earlier PROX3680 seems to be running on Intel chipset (ICH2 + Socket 370), still no BIOS tho as canon for industrial boards.
If pl6_demo (sic?) is supposed to be the x86 BIOS then it should go as a separate driver regardless because it's very out of scope to what's here (and, eventually, connect thru serial as two MAME instances).
There was a problem hiding this comment.
pl6_demo is a demo program that uses a debug version of the bootloader to load the game program from a FAT32 partition on CF/IDE and then run on board.
The Protech PROX3770 was for pl6_cm, and yes I agree it should be a separate instance, will make a note.
|
Is someone else able to confirm if when doing a memdump that coldfire_mbus_device::mbdr_r is being unmapped somewhere? I cannot see why but memdump is listing 0xF00001F0-0xFFFFFFFF as being unmapped and I cannot tell why when the prior registers are loading |
Ignore this - was getting confused and not thinking |
|
I am at the point where the pluto 6 demo will now go into the demo screen to show the outputs. In theory the ColdFire UART should work enough that the serial menu would work, but further work on the FPGA HLE will be needed. The demo freezes when trying to send out other data on the other UARTs, but this will require more work to figure out which interrupts are needed. macOS full build works on my side, Windows should too but my mingw setup isn't working right, so hopefully should be good |
|
Any sign of life from the Fujitsu GPU? |
|
The video demo tries to initialise it but the emulation is skeleton and Im not the best person to implement it. There’s two demos from Heber that do make good use of the cremson and Ill try to link it up again when I know more about the implementation. It wasnt used that much in games but Heber did have a prototype dual video game. I know the owner and he said he had preserved the software from it, so Ill ask him if he would contribute when possible. |
Hi all,
I have been trying to emulate the Pluto 6 system from Heber and get it to a more useable state. My main intention was for homebrew projects but I also wanted to get Heber's demo programs to run.
A list of changes:
-- ColdFire SIM Module - Preliminary but handles the timer IRQs
-- ColdFire UART Modules - Based on the existing mc68681.cpp driver
-- ColdFire Mbus Module - Preliminary, Motorola/Freescale/NXP's I2C driver
-- Serial VFD - Better name/base device designation needed, essentially a serialised VFD 1x16 character display. Was used in a lot of fruit machines in the late 90s going on 2000s.
My intention is to at least get the demo program to load up and run in MAME, and currently only the SIM module needs updating to do this to correctly run the appropriate interrupt vector, followed by FPGA emulation for sound and UART support which is currently lacking. I've tried to follow best practices where possible but if there's anything I have missed or should be added, please let me know!