kitune-san wrote: ↑Wed Aug 16, 2023 1:03 pmEDIT:
Apparently, at the highest speed setting, the write fails (destroys the disk).
Fixed.
https://github.com/kitune-san/PCXT_MiST ... /601-error
kitune-san wrote: ↑Wed Aug 16, 2023 1:03 pmEDIT:
Apparently, at the highest speed setting, the write fails (destroys the disk).
Fixed.
https://github.com/kitune-san/PCXT_MiST ... /601-error
The description of Quick Start is incorrect.
FreeDOS_HD.img does not work properly when using 8088bios.
If you are using 8088BIOS, please try using other bios.
Updated MMC drive options.
Perhaps it is an issue that occurs when booting with the setup disk and transitioning to the setup screen.
That's good
I found some bugs in KFMMC. I will fix it.
I use FDISK, which is certainly slow, but I don't feel it is unstable in my environment.
Anyway, I will buy some SD cards and try them out.
Fixed a bug in which the read/write command did not return an error status when an error occurred.
Not sure if this will solve the current problem, but I will upload it here.
When you have time, please try increasing the value of normal_spi_clock_cycle.
in my case...
In my environment I use 2GB and 32GB cards.
The 2GB card boots successfully.
The 32GB card can be formatted successfully and access FAT, but there is a problem with not being able to boot, which I am investigating.
It is strange.
Would the results be the same using this?
It may be due to the fact that I fixed the CHS of the drive to h=15 S=63 in this design.
Will reformatting it with a new drive make it usable?
By the way, are there any constraints for the direct(?) PS/2 port written in the SDC file?
If not, and if the input results are unstable, writing constraints may improve the issue.
keyboard repetition...
I do not remember what it was. Sorry.
I'm busy today and tomorrow, so I may not be able to reply.
The keyboard error in the diagnostic BIOS also occurred on my patched MiSTer. (https://github.com/kitune-san/PCXT_DeMi ... 9fa62f72d2)
I will take a look at the waveforms a bit and report back if I can find a countermeasure.
The reason for the error in diagnostic BIOS is not clear without seeing the waveform.
Also, if the transfer rate of the PS/2 keyboard is fast and stuck, it is still necessary to drop the clock to low after reception.
Or add a keycode FIFO.
kitune-san wrote: ↑Sun Mar 12, 2023 3:24 pmIn addition, adding the following commits will eliminate the 101 error.
However, keyboard input during diagnostics will cause the keyboard to get stuck.https://github.com/kitune-san/PCXT_MiST ... 00966f4b0f
Probably difficult to improve further.
Hmmm. Sometimes the keyboard stops working. (e.g. Area5150)
Even when 101 does not occur, I have experienced the 601 error or the keyboard not working.
These are resolved in the following branches.