@Komas, Ich habe 417/650 das läuft bei mir meist ganz gut.
Mfg Jood
You are about to leave Forum64 to get redirected to the following address:
Please note, that the target website is not operated by us. We are not responsible for it's content nor does our privacy policy apply there.
last post from Vegatronic at the
@Komas, Ich habe 417/650 das läuft bei mir meist ganz gut.
Mfg Jood
Super, das probiere ich am WE aus, danke!
Gibt es das Modul auch fertig zu kaufen bzw. könnte mir jemand hier aus dem Forum eines fertig aufbauen?
Danke.
@Komas, Ich habe 417/650 das läuft bei mir meist ganz gut.
Mfg Jood
Klappt leider nicht (immer); die Streifen oben und unten wie im #91 gezeigt sind auf jeden Fall da, und einmal ist ein Nuvie auch abgestürzt. Muss mal die neue FW testen.
Klappt leider nicht (immer);
Ich habe auch einen C64 (250425) da läuft das RAD quasi gar nicht drauf, Doomrad läuft, aber mit Glitches!
Leider mein neues Board das ich zum Haupt-C64 erklären wollte, Real REU, U2+ REU, und U1 REU Laufen.
Achja, weil ich den Fehler auf gerne, und immer wieder mache...
Es darf nur ein DMA Gerät angeschlossen sein, das RAD verträgt sich nicht mit REU, U2+, was auch immer.
Mfg Jood
How about opening a thread where we can only post the values of WAIT_ENABLE_RW_ADDRLATCH and WAIT_ENABLE_DATA_WRITING, on which model of C64 (assy, PLA, ect etc), and rapsberry used?
Possibly in English.
I'm spending a lot of time trying to get Sonic working in my C64C.
I just managed to get all the tests for the REU to work
Jood was so kind and sent me his board where he couldn't find good settings. I could get it run, but for absolutely correct behavior I'll expose one more parameter to resolve this (the only one in the orchestration which has a fixed value... to my relief: this is something which I did not find documented anywhere...). My "theory" is that it's related to the RAM on the board (my guess is that this parameter mostly remains untouched).
Long story short: I suggested to collect values before, the influence of components varies. PLAs do not make a difference, the VICs (and assy) maybe, cartridge port expanders make larger a difference. If the RPi makes a difference then you should check its exact model and your power supply. In any case this does not make sense before the firmware update, and secondly I think a thread where people will just paste values will be frustrating for those who diagnose problems. The only reasonable way is some sort of aggregated data.
Could the RAD cart somehow emulate a SuperCPU expanion?
Could the RAD cart somehow emulate a SuperCPU expanion?
in principle, supposedly yes. But at the same time it seems to be a lot of work for few software titles, and given my scarce free time...
hello, sorry for the inconvenience I wanted to know if in the next firmware, you can insert the turbo option of the 6510? as mentioned in the super Mario Bros forum it slows me down with the normal RAD equipment, thank you very much a warm greeting
Jood was so kind and sent me his board where he couldn't find good settings. I could get it run, but for absolutely correct behavior I'll expose one more parameter to resolve this (the only one in the orchestration which has a fixed value... to my relief: this is something which I did not find documented anywhere...). My "theory" is that it's related to the RAM on the board (my guess is that this parameter mostly remains untouched).
Long story short: I suggested to collect values before, the influence of components varies. PLAs do not make a difference, the VICs (and assy) maybe, cartridge port expanders make larger a difference. If the RPi makes a difference then you should check its exact model and your power supply. In any case this does not make sense before the firmware update, and secondly I think a thread where people will just paste values will be frustrating for those who diagnose problems. The only reasonable way is some sort of aggregated data.
Hi,
with
WAIT_ENABLE_RW_ADDRLATCH 427
WAIT_ENABLE_DATA_WRITING 635
I got Sonic running (played to level 4) on my 250425 C64. With higher values it crashed after a few seconds (<30s).
hope this helps, pottendo
Display MoreHi,
with
WAIT_ENABLE_RW_ADDRLATCH 427
WAIT_ENABLE_DATA_WRITING 635
I got Sonic running (played to level 4) on my 250425 C64. With higher values it crashed after a few seconds (<30s).
hope this helps, pottendo
What type of rapsberry in your case?
Display MoreDisplay MoreHi,
with
WAIT_ENABLE_RW_ADDRLATCH 427
WAIT_ENABLE_DATA_WRITING 635
I got Sonic running (played to level 4) on my 250425 C64. With higher values it crashed after a few seconds (<30s).
hope this helps, pottendo
What type of rapsberry in your case?
hi,
I have a Raspberry Model 3+ (1.4GHz max-frequency).
bye, pottendo
Hi all -- here's a strange one for you. I'd like to know if anyoneelse has experienced this:
On a C128 DCR (NTSC) with X-Pander 3, when I have the RAD plugged in my internal floppy drive will make noises like the rotation is laboured / erratic, and disks won't load. The weird drive noise starts when I'm in the RAD menu, and ends shortly after the menu is exited, but once the drive spins up to load a file the drive noise returns and the disk won't load.
This is irrespective of whether the RAD is the only cartridge on the X-Pander, and -- surprisingly to me -- whether it's bus or external powered! I originally thought it was a power draw issue that was impacting the power supply which feeds the 1571, but for it to happen when the pi is externally powered makes no sense to me. If I take the X-Pander 3 out of the equation, the drive works fine when the RAD is plugged directly into the Commodore. And if I put an authentic REU in its place on the X-Pander 3 everything is likewise fine. I haven't found specific RAD config settings under the £ menu that fix it.
I'm stumped! Any ideas?
Hi all -- here's a strange one for you. I'd like to know if anyoneelse has experienced this:
You are a big step ahead of me (Pal 128 DCR).
If I plug my RAD Expansion in, I don't even get a
correct power-on message from my C128.
Where the type of connection doesn't matter
(directly, with/without extender).
Works flawless with my C64, I really love it.
Have to try it with a wedge shaped C128.
Maybe to much mods inside my DCR ?
Stefan
Does it behave differently if you set STARTUP to REUx or GEOx?
Does it behave differently if you set STARTUP to REUx or GEOx?
Good idea, will try it.
Stefan
Hi all - here is a video that demonstrates the sound I was talking about. In making this I determined that if I leave it for several seconds it appears to "settle down" and behave normally, and that it may or may not return after reentering the menu but definitely does after a physical power off/on.
Again none of this happens with the RAD not plugged in, or plugged in without the X-Pander 3. It doesn't matter how the RAD is powered. Add it doesn't happen with a real REU.
I'd leave it be but am a little worried I may be risking damaging something...
I've had a quick look at the video. You sound as if the behavior is not really deterministic. And the drive sound -- is that different from the normal boot attempts (which might just be interrupted by the RAD). To me it sound like the spinning drive motor... (after the seeking)
Maybe I missed the point?