[Coco] So is this a G board?

Fri Jun 28 09:44:59 EDT 2013

Luis,

Cleaning of the CoCo1 cart fingers is done by inserting the carts only, DO NOT try to do it any other way.

Not an issue ATM.

Suggestion....

Replace uP, if you have a Pro-Tector+ use that as well.

Something sounds very borderline/defective in this machine.

Regards,

Mark

________________________________
 From: Luis Antoniosi (CoCoDemus) <retrocanada76 at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com> 
Sent: Friday, June 28, 2013 8:38 AM
Subject: Re: [Coco] So is this a G board?

I don't have a scope but I friend of mine does. So if I need I can use it.

The behaviour of the sIDE is erratic, sometimes is hangs right after
displaying HDBDOS 1.1D... with some garbage, other times it will pass the
boot (showing the HDBDOS 1.1 LBDA MODE) and a Ok but accessing the CF will
give me I/O error. Sometimes i will get the boot and a ?FN ERROR (trying to
load AUTOEXEC.BAS ?).

If I boot without a CF card instead of showing LBA HARD DRIVE NOT FOUND it
will display garbage after the HDBDOS 1.1 logo.

I compiled a HDBLBA13.ROM (from toolshed) and flashed on sIDE and it works
on coco3 but again no sucess on coco1. Same erratic behaviour.

Then I flashed ADOS2 and HDBDOSCC1.ROM on bank (0 and 1). ADOS works fine
except that: POKE &H77F5,51 will hang. So to access the floppy I need to
switch the multipak button. DW3 boots fine from bank 1 but when acessing
the DW3 server i get i/o error.

I played several carts on it and all seemed to work. The fdcs FD500 and
FD502 work fine too.

Today I found a game that works on coco2/3 to not work on cococ1: The Keys
of the Wizard.

I have cleand the sIDE contacts, I will try to clean the coco1 contacts but
they seemed pretty clean to me.

On Fri, Jun 28, 2013 at 9:14 AM, Mark Marlette <mmarlette at frontiernet.net>wrote:

> Luis,
>
> This is strange for sure. Boisy might want to add something here..... ??
>
> It
>  sounds like to me the sIDE is not getting addressed or selected. That
> is strange since it is IOmapped. Proper address appears on address bus and
> the
> device is selected. The default proper address in the default condition is
> $FF50-$FF59.
>
> If you have a scope, let me know then we can go to the next level. Address
> appears on ADR bus and a signal is then presented from the CPLD called
> SEL_OUT~. This signal is then presented back in to the CPLD to be gated
> with some more logic inside the CPLD to produce SLENB~, a critical signal
> in the sIDE. I will send you the schematic of the sIDE in PM.
>
> As you have mentioned other devices work in
> the slot...just try pulling the sIDE in and out of the slot six times or
>  so to clean the card edge of the CoCo. With power off of course. sIDE is
> fully decoded so you are just making sure the connector is clean. Also
> check the sIDE's gold contacts clean with soft white eraser to remove
> tarnish. Lightly a few times top/bottom should do it. But since the sIDE
> works in other CoCos, not likely the issue.
>
> What
>  does this program produce on the screen? It should read the switch
> settings for banks 0-3. The 1st switch will cause the program to crash,
> that is normal.  So if SW 1 is up and 2&3 are down, program should
> display a 0. If 2&3 are down and up respectively, should read 1.
> You get the idea....
>
> If these numbers are not produced the the
> most basic card select is not occurring and of course the CF card will
> not be detected.
>
> 10 POKE &HFF40,0
> 20 POKE &HFF7F,0
> 30 PRINTHEX$(PEEK(&HFF59)):GOTO 30
>
> Also looking back at some information when we designed this might help you
> on the boot process.......Jeeeez a 2004 dated email from Boisy when were
> developing this device.....
>
>
> >Here's
> what HDB-DOS does at startup to the IDE:
> >
> >(1)
> Checks for the existence of a master drive on the IDE bus.  It does
> >this
> by writing $55 to the IDE Sector Register and reading the register
> >back.  If what it read back is $55, then HDB-DOS
> assumes that a drive is
> >present.    This is because if a drive is not present,
> we are writing to a
> >"dead
> register" that won't hold the contents of what we wrote.  When we
> >read
> back what we wrote, we assume the drive is powered up and ready to roll.
> >
> >(2)
> Assuming the drive checks out fine, it sends a $70 command to the
> >drive
> and sits in a loop until the seek returns no error.
> >
> >(3)
> Once the loop in #2 is exited, the $EC (Read Capacity) command is sent
> >to
> the controller and the size information is gathered about the drive.
> >
> >(4)
> AUTOEXEC.BAS is then read, etc...
> >
> >So
> to summarize, #1 verifies a drive is on the interface, #2 just does a
> >seek
> (probably useless) and #3 queries the drive to determine how many >Disk
> BASIC
> "drives" it can hold.
>
> Regards,
>
> Mark
> http://www.cloud9tech.com
>
>
>
> ________________________________
>  From: Retro Canada <retrocanada76 at gmail.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Cc: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Friday, June 28, 2013 6:09 AM
> Subject: Re: [Coco] So is this a G board?
>
>
> but why the superide hangs here?
>
> Sent from my iPhone
>
> On 2013-06-28, at 1:05 AM, Arthur Flexser <flexser at fiu.edu> wrote:
>
> > If you're asking about that wire running to one of the PIAs, I'm pretty
> > sure that's part of RS's official 64K upgrade used by the repair centers.
> > Notice that it has two warranty stickers on the bottom, presumably the
> > second one applied after someone brought it into RS to have it
> "officially"
> > upgraded to 64K.
> >
> > I suppose RS wanted to make it possible to check for 64K by looking at
> the
> > status of one of the PIA lines, but since I don't think other people with
> > 64K upgrades followed that convention, this unreliable method of checking
> > for 64K was pretty much ignored in favor of more straightforward software
> > methods.
> >
> > Art
> >
> >
> > On Fri, Jun 28, 2013 at 12:49 AM, Retro Canada <retrocanada76 at gmail.com
> >wrote:
> >
> >> another thing this board has 2 mc1372. why? there is only one video
> output!
> >>
> >> Sent from my iPhone
> >>
> >> On 2013-06-28, at 12:14 AM, Retro Canada <retrocanada76 at gmail.com>
> wrote:
> >>
> >>> Hi i got this beautiful great white coco
> >>>
> >>> http://twitter.com/RetroCanada76/status/350422134088167424/photo/1
> >>>
> >>> its was sealed, never opened. once opened i found this
> >>>
> >>> http://twitter.com/RetroCanada76/status/350465048709320704/photo/1
> >>>
> >>> which is exactly this guy here posted
> >>>
> >>>
> http://www.doki-doki.net/~lamune/computers/coco/26-3003b/P2223732-r.html
> >>>
> >>> This machine doesn't run DWCC1 gives i/o error and my superide hangs
> >> when looking for the Cf. everything else seems to work except the
> artifact
> >> colors:
> >>>
> >>> http://twitter.com/RetroCanada76/status/350464227212922880/photo/1
> >>>
> >>> http://twitter.com/RetroCanada76/status/350464318850088962/photo/1
> >>>
> >>> green and pink?
> >>>
> >>> tried to regulate the trimmers but no success...
> >>>
> >>>
> >>> Sent from my iPhone
> >>
> >> --
> >> Coco mailing list
> >> Coco at maltedmedia.com
> >> http://five.pairlist.net/mailman/listinfo/coco
> >
> > --
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>

-- 
Long live the CoCo

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco