Hi Peto,
I have a 250425 A and B and 250469 Rev.3 and 4
and can also test these ifyou want me to...
Du bist in Begriff, Forum64 zu verlassen, um auf die folgende Adresse weitergeleitet zu werden:
Bitte beachte, dass wir für den Inhalt der Zielseite nicht verantwortlich sind und unsere Datenschutzbestimmungen dort keine Anwendung finden.
letzter Beitrag von Peto74 am
Hi Peto,
I have a 250425 A and B and 250469 Rev.3 and 4
and can also test these ifyou want me to...
Thanks for your interests, I have contacted you into conversation ...
Many thanks borstie for your help .
You're welcome
Maybe I'll find some time in the future to repair my 250407-Assy...
I just did a review of all the boards I have and think i will be able to test all type boards (250407, KU-14194HB, 326298 Rev A, 250425) in all revisions and (250466, 250469) in all revisions.
Also have C128 and C128D.
Do not have a SX-64.
Uaaaw, great ... time to see true situation .
Regarding to C128/C128D ... I'm not sure, if this will work, it was not planned.
Hi
Did some testing. Looks good for most of the boards.
I think that reloaded could be make to work, while Ultimate64 should not be on top of the list.
Board 326298 and KU-14194HB could be make to work.
Can I do something to send you some debug information.
The unicart64 works great. I will keep it
Board | Revision | Boot | PRG | CRT | EF | No SD | SD | Switch 2 | comment |
Reloaded | MK1 | boots into yellow with no SD. Switch 2 starts dead test. Boot into red with SD. | |||||||
Reloaded | MK2 | boots into orange with no SD. Boot into orange with SD. Switch 2 start prompt | |||||||
U64 | std | boots into yellow with no SD. Boot into green with SD. Switch 2 start dead test. Switch 3 boot into prompt | |||||||
250407 | Rev B | yes | yes | yes | yes | yellow | SD commander | work | |
250407 | Rev C | yes | yes | yes | yes | yellow | SD commander | work | |
250407 | Rev A | yes | yes | yes | yes | yellow | SD commander | work | |
250466 | Rev A | yes | yes | yes | yes | yellow | SD commander | work | |
250425 | Rev A | yes | yes | yes | yes | yellow | SD commander | work | |
250425 | Rev B | yes | yes | yes | yes | yellow | SD commander | work | |
250469 | Rev A | yes | yes | yes | yes | yellow | SD commander | work | |
250469 | Rev B | yes | yes | yes | yes | yellow | SD commander | work | |
250469 | Rev 3 | yes | yes | yes | yes | yellow | SD commander | work | |
250469 | Rev 4 | yes | yes | yes | yes | yellow | SD commander | work | |
326298 | Rev A | black | |||||||
KU-14194HB | black | ||||||||
C128 | Yes | work | boots into yellow with no SD. Boot into black with SD. Switch 2 start dead test. C64 mode switch boots red. | ||||||
C128DCR | Yes | work | boots into Red with no SD. Boot into black with SD. Switch 2 start EF. C64 mode switch boots red. | ||||||
Hi FunFun,
THANK YOU VERY MUCH !
That's quite nice evening for me .
I see all boards are working except the older 326298, KU-14194HB.
The C128 was not planned to be supported, I didn't expect it.
The modern boards U64, MK1, MK2 were also not planned to be supported, but it should work, because I suppose (?) the bus timing is nice and precise comparing "standard" C64 boards, but I don't know very much about them. Hmm, interesting ...
In this moment I have to think about that.
Question: what is the "Switch 2" ?
Switch 2 is the middle button.
If i can provide any information to you or run some test programs please send them to me. I have an oscilloscope, if that can give any insights.
The Pi1541 II+ works on the reloaded boards.
one stupid question related to modern boards U64, MK1/2 ... I have looked to some videos and I see many settings e.g. Stereo SID and usage addresses DE00 - DFFF .. Is there everything turned off on these boards ?
just to be sure and to avoid possible misunderstanding / address conflicts
The MK1 http://wiki.icomp.de/wiki/C64_reloaded and https://www.c64-wiki.de/wiki/C64_Reloaded.
There is nothing that I can set jumpers for that will DE00 - DFFF beside jump J13. I removed the jumper, but it did not change anything. Still red screen.
I think it might have to do with the option of using the RESTORE key to change kernel upon boot.
The MK2. http://wiki.icomp.de/wiki/C64_reloaded_mk2 and https://www.c64-wiki.de/wiki/C64_Reloaded_MK2.
It is possible to set SID2 for DE00, but it is was not for my test.
In both cases it is possible to run EF using the <-- key while booting.
I am not quit sure i understand how the unicart64 works when booting from SD. Why does it work on some boards, but not others? You talk about bus timing.
The U64 will not be relevant to look into since it has USB storage.
In both cases it is possible to run EF using the <-- key while booting.
If this is working I suppose you are able to start SDCMDUC from EF image crt. Is it working ? Can you see the content of SD card in SDCMDUC afterwords ?
Red screen means that SD card is not bootable. But, it could be that data are not transferred correct from SD card to C64 memory due to any error, e.g. address conflict, bad timing, etc.etc.
This is a bit weird.
I managed to get the MK2 loads the SDCMDUC from SD. It is however not stable, since at other times it do not work.
I also managed to load SDCMDUC from EF using <-- on boot, but the are no files listed on the card or it "hangs" on "loading ... wait please !".
If a load SDCMDUC from EF with the SD i get error. "HW: ERROR" and "SD-CARD: ERROR". Inserting the card and you get "red screen".
Loading SDCMDUC from EF on a 250469 board works and so does loading from SD.
After having succesfully loaded SDCMDUC from SD on a 250469 board and then swap to MK2 it suddenly is possible to load from the SD.
What is stored in the "system volume information" ?
wpsettings.dat 12 bytes
indexervolumeguid 76 bytes
If i look at the "system volume information" after load from SD card on MK it contains garbage.
Pressing F1 to go to root bring garbage to the files shown on the screen and a reboot cause a "red screen".
It seems like the MK2 destroys the file system on the SD card.
Insert the card into a working board restores the SD card into working order.
I tried the same method on the MK1 board, but i cannot get it load from the EF.
What is stored in the "system volume information" ?
wpsettings.dat 12 bytes
indexervolumeguid 76 bytes
This is created by your Windows. Try to use google to find out how to disable this Windows feature. I did it somehow, I don't remember how yet ???
So, I don't have it anymore.
OK, for MK1,2 it is NOT working or it is unstable ... currently I don't know. Once you will have USB programmer, I will try to send you 3 experimental FWs just to check possible (?) timing issue.
We will see if it shows something, if this is right direction for source of problems.
Just let me know then ...
Meantime, for older boards 326298, KU-14194HB ... can you test the same ( <- key +EF + SDCMDUC, file browsing/loading) ?
I will try find out the schematics, because it is known as "prototype" boards.
Thanks.
Hi
I have received the USB blaster and installed the programmer software for the .pof files.
I just get black screen on 326298, KU-14194HB. I cannot use Button 2 or <-- to load EF.
EasyFlash card works and so does TFCIII+Pro.
You can send me some .pof files when you get the time.
Hi,
This is only experiment, not sure if this is good direction ... we will see.
UC64_2019-11-25-experimental.zip
You can try step by step all 3 FWs on older/modern boards.
Thanks.
I'm not sure, here are my starters for cartridge tests (already published on this thread) .
FYI: tests are ongoing for not working boards.