X68000 Beta - Updates and Releases

[dentnz]

I had setup and was running the 20200513 build of the beta core and everything was working. I was able to load harddrive files from the second SD, browse for a game, and boot them. I was even able to boot .d88 disk images. Then all of a sudden, it stopped working. Perhaps I ran the update script, I can't remember.

Has anyone else experienced similar issues?

I've tried to delete the SRAM file and replace with a fresh one, remove .config files from the sdcard, replaced boot.rom. Nothing seems to work, I just get some white Japanese writing on the screen, which google translates says something about 'not being able to boot the system'. I haven't tried to reformat the SD card, and I was hoping I wouldn't have to.

I know this is a beta core, but it's just a bit weird how it was working quite well and then stopped.

[suverman]

There was a 20200522 release anyways, maybe you should try that one? Its definitely working for me.

[puu]

How to generate new SRAM file? Since the TG68 core cannot handle BUS ERROR, the SRAM initial value used when the SRAM file does not exist has been modified. It may be solved by starting up without SRAM file.
The SRAM file generated by the actual machine or other emulator does not have this work, so it may not start normally.

[puu]

During the boot sequence, the IPL ROM has access to the last address of main memory (which is supposed to be unimplemented normally) and expects a bus error. TG68 does not work as expected because there is no bus error. This problem is solved by setting the SRAM initial value to activate the built-in communication monitor before starting this process.

[dentnz]

OK, thanks puu, I will try removing the SRAM file entirely and setting it to none. Will report back if that solves the problem.

[Chris23235]

There was a 20200522 release anyways, maybe you should try that one? Its definitely working for me.

Does this version still require a secondary SD card? Where can we find these newer versions?

[puu]

Currently it is only on the blog of the author (me).
http://fpga8801.seesaa.net/

[puu]

The blog is written Japanese(I can speak C, VHDL, and Japanese only).
https://fpga8801.up.seesaa.net/rtl/rele ... 200522.qar

[Grabulosaure]

@puu
I've made a test version of your X68000 core which can use the primary SD card for the SASI disk :
http://temlib.org/pub/mister/release-F68kMiSTer.rbf
http://temlib.org/pub/mister/F68K.tar.gz

It is faster than using the secondary SD card, but it is still a partial solution as it doesn't support several units, there is no floppy emulation and no SRAM.
It would be better to have a version for MiSTer that do not need the secondary SD, though (porting your NIOS code into main MiSTer software and/or using additional blocks like my SASI disk emulation core).

I'm also curious about how large capacity SCSI disks can be implemented. It seems that some X68k computers had a proper SCSI controller (MB89352), but maybe it was possible to connect SCSI disks to the SASI connectors and support them with a driver, this would be the easiest solution.

Regards.

[puu]

SxSI:
https://www.tur-up.net/~ta/x68k/xm6soranofudosan.html

[dentnz]

Not sure exactly why it was working originally. But here are the steps to get it working again:

- Formatted my second sd card back to scratch
- Copied all the disks and hdf onto it
- Copied the 4mb, 6mb, 8mb SRAM onto it
- Copied latest working core 20200522 onto main SD card
- Started core, hit F11:

***Made sure that I marked FDD0 and FDD1 as 'Ejected'***

- Selected a HDF in HDD0
- Move to the bottom of the screen and select 'save'
- Reload the core.

This results in the HD loading. From there, select games, the game you want, and !start.bat

[dentnz]

To mount disks (d88), I simply load files into FDD0 and FDD1 - Additional disks (disk 3) may need to be loaded into FDD0 when prompted by the game. You can eject the HDD0 if you like, but I think I was able to load disks with it still attached.

[puu]

SRAM is not write to SD card automatically. When select "STORE" on SRAM line, store SRAM information to file in SD card. When change SRAM file (select "FILE" on SRAM line), SRAM file name will change, but SRAM content are not changed. If you want to change content of SRAM, select "LOAD" on SRAM line.
If X68k core work correctry, I recommend saving the current SRAM content to SD card, then store current setting to SD card(Select "STORE" on the line below the SRAM line). current setting will store to ".config.x68" in root dir in SD card, and will load srtting and SRAM content at next time core booting.

[gtv3000]

does anyone have a more updated core release than mine in 20200515? Thanks in advance!

[tontonkaloun]

@puu
I've made a test version of your X68000 core which can use the primary SD card for the SASI disk :
http://temlib.org/pub/mister/release-F68kMiSTer.rbf
http://temlib.org/pub/mister/F68K.tar.gz

It is faster than using the secondary SD card, but it is still a partial solution as it doesn't support several units, there is no floppy emulation and no SRAM.
It would be better to have a version for MiSTer that do not need the secondary SD, though (porting your NIOS code into main MiSTer software and/or using additional blocks like my SASI disk emulation core).

I'm also curious about how large capacity SCSI disks can be implemented. It seems that some X68k computers had a proper SCSI controller (MB89352), but maybe it was possible to connect SCSI disks to the SASI connectors and support them with a driver, this would be the easiest solution.

Regards.

I tried your version to load the main SD disk without success
How to setup?

[Grabulosaure]

@tontonkaloun
In the menu, select "Hard Disk" "MiSTer" instead of "NIOS".
Select an HDF disk image with "HDS *.HDF" (which is a terrible name, sorry)
Only the first hard disk is implemented.
For the floppy and RAM, use PUU's menu (F11), for example set "FDD 0...3 = EJECTED".
When "Hard Disk" is set to "MiSTer" in the menu, HDD 0 to HDD F in PUU's menu are ignored. Else, everything should work as before.

[tontonkaloun]

@tontonkaloun
In the menu, select "Hard Disk" "MiSTer" instead of "NIOS".
Select an HDF disk image with "HDS *.HDF" (which is a terrible name, sorry)
Only the first hard disk is implemented.
For the floppy and RAM, use PUU's menu (F11), for example set "FDD 0...3 = EJECTED".
When "Hard Disk" is set to "MiSTer" in the menu, HDD 0 to HDD F in PUU's menu are ignored. Else, everything should work as before.

that's what i did, but it doesn't work

disk error

[Grabulosaure]

@tontonkaloun
Can you test it on the secondary SD card? Didi you test several files?

[puu]

@Grabulosaure
Thanks for changing the HDD emulation to the primary SD card.
I have not manipulated the files on the SD card with MiSTer, so I will refer to your RTL.
By the way, it seems that the I / F on the MiSTer side has two addresses, LBA and ADRS, but is it necessary to handle the files in the SD card as 512B / sector in sector units? In the version without disk emulation of X68k (for DE0-CV), the SD card was handled in sector units (without using file system), but the SD card is 512B / sector and the SASI of X68k is 256B / sector, so the same data I adjusted the sector size by writing 2 bytes ("ABC" → "AABBCC"). Is it possible to read / update it only every 512B?

[Grabulosaure]

@puu
There are two ways to handle disks (HDD, floppy) in MIST/MISTER :
- Use simple interface where raw files can be accessed sector by sector.
- Adapt MiSTer software to handle disk formats and transfers as suitable for the core. (this is the case for Amiga/Minimig, PCE CD, ...)
I am not sure that what I have done is the correct solution, if it will be suitable for floppy and SRAM.

LBA is the "Logical Block Address" = sector number as 512 bytes.
ADRS is the position within the sector. A dual port memory is used to store copied data.

SASI uses 256 bytes sectors, the MISTER interface uses 512 bytes, so it is a bit complex. For example to write only one 256B SASI sector, my HDD emulation code needs to read first a 512 bytes sector, then modify half of it, then write back 512 bytes.

[puu]

@Grabulosaure
OK, I understand. SRAM will easy to change to primary SD. FDD is a little bit hard.

[tontonkaloun]

@tontonkaloun
Can you test it on the secondary SD card? Didi you test several files?

using the second sd card, it works very well
Yes, I have tried several files

[jawler]

any news about x68000 core? i love this system

[puu]

Mouse controller was changed.
http://fpga8801.seesaa.net/archives/20200602-1.html

[dfilskov]

Mouse controller was changed.
http://fpga8801.seesaa.net/archives/20200602-1.html

Great! Thank you

Please compile RBF files ... if you need us to test each version. I'm sure there are many people who would really like to try the newest RBF!

I personally really look forward to trying this core ... I hope you can make it work using only the MAIN SD card - I don't have an IO board with the second SD card slot.

[dentnz]

I’d be keen to help get fdd working off the main sd card if you want, @puu @grabulosaur?

[puu]

Although the operation has not been confirmed at all yet, the RTL of expanding the D88 file into the FDD track image is almost finished. The circuit for writing back from the track image to D88 is also quite complicated.

[dfilskov]

For people with no IO board here's how to make Grabulosaure's old version work

I used the mod'ed version her: https://temlib.org/pub/mister/release-F68kMiSTer.rbf - thanks a LOT, Grabulosaure

• Place boot.rom into /Games/X68000/ or name it X68000.rom and place it in /bootrom/ (and perhaps SRAM.DAT in /Games/X68000/ - but I'm not sure if it's needed)
• Place e.g. TETRIS.HDF into /Games/X68000/
• In OSD: Start the mod'ed core (X68000 20.05.10)
• In OSD: Set 'Hard Disk' to MiSTer
• In OSD: Go right (arrow key) and select 'Save settings'
• In OSD: Select 'HDS *.HDF' and select the HDF-game you want
• In core: Tap F11 - if cursor gets stuck open the OSD (F12) and select 'Reset')
• In core: Set all FDDs to EJECT (to load from HDF)
• In core: Tap F11
• In OSD: Select 'Reset' - close the OSD
• Wait 3-4 seconds (reboot)

[dfilskov]

I’d be keen to help get fdd working off the main sd card if you want, @puu @grabulosaur?

Wow - that would be great!

[dentnz]

@grabulosaur

In the user_io file, there is a sd handling loop. This loop is used to stream data across. For snes msu1, I hijacked the loop, making it call a separate function in support/snes... this allowed me to do specific sector sizes - either smaller or larger than 512 bytes.

Do you have your source code available for the main sd card HD stuff?