[Coco] SDC and T2 conflict? RESOLVED

K. Pruitt pruittk at roadrunner.com
Mon Jun 29 22:19:01 EDT 2015


----- Original Message ----- 
From: "K. Pruitt"
Sent: Monday, June 29, 2015 5:02 PM
Subject: Re: [Coco] SDC and T2 conflict? RESOLVED


>
> ----- Original Message ----- 
> From: "Darren A" Sent: Monday, June 29, 2015 4:41 PM
> Subject: Re: [Coco] SDC and T2 conflict? RESOLVED
>
>
>> On Mon, Jun 29, 2015 at 5:02 PM, K. Pruitt wrote:
>>
>>> Conflict resolved.
>>>
>>> If /T2 is being used, the SDC appears to be required to be in slot 4. 
>>> No
>>> other slot worked for me. With the SDC in slot 4 and my disto controller 
>>> in
>>> slot 3 I can access /T2 without issue.
>>>
>>> In any other slot, any command sent to /SD0 or /SD1 will generate 
>>> nothing
>>> but an error 244 if I've sent anything to /T2.
>>>
>>>
>>
>> What is the build date of the NitrOS-9 release you are running?
>>
>> The SDC driver was updated in December 2014. The updated driver activates
>> the MPI slot containing the SDC controller every time it is called, so
>> unless your using an old version, I don't know why you would be having 
>> that
>> problem.
>>
>> - Darren
>>
>> -- 
>
> I think the original build date of the copy I am using was April 14, 2014. 
> I'll update my system.
>
> Thanks Darren.
>
>
> -- 

Using the latest build solved the problem of the SDC drives vanishing, but 
accessing the RS232 Pak still causes some system instability for me. Without 
the SC6551 driver present there is no problem. As I can access the RS232 pak 
without using the /T2 driver, I will go that route. Problem solved for my 
purposes.

Thanks again.




More information about the Coco mailing list