I also declare my BiG interest at one of this
great work!
Hallo Besucher, der Thread wurde 72k mal aufgerufen und enthält 317 Antworten
letzter Beitrag von Peto74 am
Unicart64 - The FPGA based cartridge for Commodore 64
- Peto74
- Erledigt
-
-
I also declare my BiG interest at one of this
great work!OK, thanks for your interest, reserved last one for you.
I have no other free boards. -
thank you very much
I'm looking forward to hear from you
-
2. Assy 250407, Vic ?
Same behaviour as before:
This one did not boot reliable with the cartridge, sometimes red screen, sometimes black screen, sometime normal prompt without run/stop.
2.1. If i get the normal prompt i can load the sdcmduc via disk, it shows the firmware number and ok.
2.2. Starting a kernal with tha starter program: ok.Thanks borstie also for negative answer !
Can you (or someone else ...) perform "RAM test" on ASSY 250407 ?
I give you patched version of EasyProg 1.7.0.
easyprog-1.7.0.zip
Menu --> Expert --> RAM test.
If borstie reported flashing problem, I would like to know, if SRAM writing cycle does the same.
My new theory is wrong/unstable writing cycle.
Thus, I expect problems there as well. Pls. test it also on 250469, just for the comparision.
Thanks. I'm looking forward.
-
-
I have an USB Blaster here.
OK, perfect, I hope I will be able to send you another experimental fw for testing.
Now, I need time to understand why writing (? ...theory) doesn't work. -
I have tested the cartridge with easyprog from post #84
1. Assy 250407, Vic ?
As soon i get a kernel prompt (sometimes red screen, sometimes black screen, sometimes ignores run/stop) i loaded the patched version of easyprog from disk and started it. First the splash screen, everything is normal. After pressing <cr> the c64 crashes completely with a garbled screen. Same with the unpatched version.If i start easyprog with no cartrdige it runs normally and says no proper hardware found. In this case no crash.
2. Assy 250469, Vic 8565R2
Everything is normal, starting easyprog and testing ram: okI tested it with the firmware from post #79 or should i flash the firmware from release pack into the fpga?
-
Many thanks, OK, let it be ... there is general timing problem on the PHI2 clock, my theory is during writing cycle (from symptoms)...
Now, It is up to me to analyse it and try to provide some experimental FW.
I need some time.Thank you for your BIG help!
-
Hi,
After analysis I have suspicion that main O2 (or PHI2) clock is not regenerated correctly.
This is fundamental signal and many other important signals are derived from this one.
For details, you can look at this thread.
Fragen zu PHI2 Edge RecoveryBut, I don't see original input O2 and/or FPGA interpretation of this signal from assy 250407.
I'm like a "blind" now. I just guess how it looks like. Normally, it is corrupted for every assy.
Here is example of this "corrupted" signal (FPGA interpretation) on assy 250469.
o2-clock-distortion.png
My regeneration logic tries to create nice jitter-free O2 signal for my FPGA.
And, I don't know if this job is done 100% for assy 250407.
Thus, I have prepared the experiments, I have just changed some parameters in regeneration logic.
Here are firmwares.
UC64_2019-02-11-clk-i44-111.zip
UC64_2019-02-11-clk-i45-11.zipBut still, we don't see the input, and we don't see the output.
It would be nice to have some logic analyzer (e.g. Saleae etc.), oscilloscope to check it. If you have it just let me know. -
Hi,
Here is another fw prepared for testing.
Original fw, I have moved only 1 sync point for SD card.
Here is precondition, regeneration is working 100%.Please, if you have time test it as a priority, assy 250407, only boot test/commander browsing.
Thanks.Peter
-
as soon as the USB Blaster arrives, I will test...
-
I have tested the firmware from post #84:
1. Assy 250407, Vic ?
Booting has nearly the same problems as before (sometimes red screen, sometimes black, sometimes prompt, sometimes the same screen as i get without sd-card). Browsing the sd-card with sdcmduc (starting from prompt) works with no problems.
If i try to flash kernals.crt it says cartridge hw error.
Easyprog works, no crashes (both versions), patched version says no cartridge ram at $DF00 found when i do the ram test, flash type was identified.2. Assy 250469, Vic 8565R2
Everything is okI haven't tested the other firmware versions from post #89 yet (short of time).
I have a logic analyzer and an older scope but i'm afraid i will damage the cartridge if i measure directly at the fpga pins or if i would solder some wires to the pins to do the measurements.
-
I cannot register at Intel to download Quartos SW. So i cannot flash / test firmware...
Has anybody the sw an could upload somwhere? -
I have a logic analyzer and an older scope but i'm afraid i will damage the cartridge if i measure directly at the fpga pins or if i would solder some wires to the pins to do the measurements.
No, no, no soldering ... first let's try my firmwares and later only in case of fail, we can go to show clock.
In such case I will guide you & produce special fw to redirect internal reg. clk to LED1 - connector "D1" in top of board.
It is possible to do without soldering. OK, later. -
Programmed and tested FW post #90 on my Assy. 250425 -> Red screen, sometimes yellow screen. More red screens.
-
Continue from post #90 ...
UC64_2019-02-15-sd-ramcode.zip
workaround just to test, original rom code was copied first to C64 ram, boot crt deactivated and boot started ... -
It's no longer possible to program FW, verify of all programing tries with all FWs fails:
-
It's no longer possible to program FW, verify of all programing tries with all FWs fails:
It seems to be missing power supply 5V from C64 side ... Did you turned on C64 ?
Follow my guide. Hopefully, nothing bad happened.
Unicart64 into C64 (without SD card is better).
Plug in programmer.
Turn on C64 (as power supply 5V) !
Start programming.
... -
I followed your guide exactly.
C64 power is on, C64 boots into normal blue screen.
Unicart without SD Card. -
In this moment no idea what to do.
Was there progress bar for programming and then failed to for verification ?
Or simply nothing and failed ?