Previous | Next
| From: MagerValp (all posts)
Date: 2002-02-28
Subject: Re: Serial Slave for the Plus/4
|
>>>>> "MM" == Marko Mäkelä <marko.makela@HUT.FI> writes:
MV> Is it possible to print various shades of grey by just calling MV> $ffd2? For various reasons I'd rather not sta directly to the MV> attribute map.
MM> Can you sta to the zero-page or $200 page location that holds the MM> current colour?
I'd like to use the exact same code on all platforms (VIC-II, VDC,
TED) to draw the screen, so that's what I'm trying to avoid. Of course, it's just a matter of a simple #ifdef, but it's kinda fun to try to write platform independent code on the commodores :)
MV> Is there anything special about the 6551 in the Plus/4?
MM> I had no trouble with porting the null-modem version of cbmlink to MM> the plus/4. But my code doesn't use 6551 interrupts, if that makes MM> a difference.
It turns out it didn't like having hardware handshake turned on. After disabling it I get tons of transmission errors, but at least it works.
Just tested copying a couple of files back and forth, and copying from the Plus/4 to the PC appears to work without any problems. Copying to the Plus/4 produces corrupted files (about 1-2 bytes in every K has a bit wrong) or drops characters (which makes the program hang as it doesn't handle it gracefully). I use the exact same cable with the Turbo232 at 115200, so I don't think it's that. The Plus/4 shouldn't have any problems at all at 19200, should it? I have a feeling my RS-232 interface is acting up.
I finally got around to testing cbmlink, and it has pretty much the same problem: lots of timeouts and corrupted data. -ds worked after the fourth try or so. Oh, and did you say that the 6551 server for the C64 and C128 was untested? I couldn't get it to work, not with -c serial COM1 nor 38400,COM1.
--
___ . . . . . + . . o
_|___|_ + . + . + . Per Olofsson, arkadspelare
o-o . . . o + MagerValp@cling.gu.se
- + + . http://www.cling.gu.se/~cl3polof/
|
| |
Copyright © Plus/4 World Team, 2001-2024 |
