Started by Bryce, 17:21, 22 October 11
0 Members and 1 Guest are viewing this topic.
Quote from: Bryce on 17:21, 22 October 11Hi All, I'm just experimenting with some RAM expansions and was wondering whether there is a quick way to report how much RAM is connected to the CPC. It needs to be on a disk (ie: not a ROM routine) because there isn't / can't be any ROM expansion connected to the CPC while I am performing certain tests.Bryce.
Quote from: phi2x on 20:28, 24 October 11That's a very cool tool!It will be a nice addition to the stress tests I use: RAM: Expansion RAM CheckerCRTC & GA: Lots of demos CPU: Z80 Tests Suite, ZexallASIC: Arnold V test cartridgeVDU, Z80, CRTC & ASIC: Plus testAnd now, what about a FDC tests suite? Something that would check the different commands, examining the FDC flags state, the returned values and the timings.It would be tremendously useful for us emulator authors. The FDC is sadly the most neglected chip at the moment :/
Quote from: phi2x on 20:28, 24 October 11And now, what about a FDC tests suite? Something that would check the different commands, examining the FDC flags state, the returned values and the timings.It would be tremendously useful for us emulator authors. The FDC is sadly the most neglected chip at the moment :/
Quote from: phi2x on 21:42, 24 October 11Very interesting. I didn't know there was already a FDC test suite.And it looks nice too.Some remarks though:The test suite doesn't really indicate what each test is about.I see there are some brief explanations in the asm code, but it would be even better if there was a small txt file explaining each one of these tests and what are the correct values to satisfy it.
Quote from: phi2x on 21:42, 24 October 11I have bad news too. I have converted the dsk to an hfe file and ran it on my real CPC. The tests don't want to execute on it. Just after launching test.bas, the HxC goes crazy and then the Basic returns a "Drive A: read fail. Retry, Ignore or Cancel?".
Quote from: Bryce on 18:33, 31 October 11Hi SyX, I just did some intensive testing of your RAMTest dsk and there is still a minor error in the program. If I connect a 256K RAM expansion (tested on a 6128+), which is mapped to Banks 0 to 3, the test claims that I have 320K total and Banks 0 to 4 are populated. Which definitely isn't the case.
Quote from: Bryce on 20:02, 31 October 11I don't know which mode SyXs software uses, so I can't tell you how it's being banked. But no matter how it is banked, Bank 4 should be empty if only 256K external RAM is connected, shouldn't it?Bryce.
Bank 0 -> $C4 $C5 $C6 $C7 (internal expansion ram in 6128, if it's not disabled)Bank 1 -> $CC $CD $CE $CFBank 2 -> $D4 $D5 $D6 $D7Bank 3 -> $DC $DD $DE $DFBank 4 -> $E4 $E5 $E6 $E7Bank 5 -> $EC $ED $EE $EFBank 6 -> $F4 $F5 $F6 $F7Bank 7 -> $FC $FD $FE $FF
Page created in 0.116 seconds with 52 queries.