[Coco] NitrOS9 question

[David Ladd]

Dave,

>From looking into the headless version of the NitrOS-9 L2 bootfile there
isn't a VTIO in there.  So you should be good without VTIO.

I can help once I get my analog board back.


+-----------------------------------------------------------------------+
| David Ladd a.k.a. PacoOtaktay a.k.a. Drencor                          |
| YouTube: http://www.youtube.com/user/PacoOtaktay                      |
| YouTube Gaming Live: https://gaming.youtube.com/user/PacoOtaktay/live |
| Websites: http://dwladd.com     &     http://www.theterrorzone.com    |
| G+:  https://plus.google.com/113262444659438038657                    |
| G+:  https://plus.google.com/+DavidLaddPacoOtaktay                    |
|                                                                       |
| Do you have your CoCo 3 yet?                                          |
+-----------------------------------------------------------------------+


On Thu, Oct 5, 2017 at 4:59 PM, Dave Philipsen <dave at davebiz.com> wrote:

> Ok, so now I am delving in to vtio.asm and I've hit another brick wall.  I
> thought I had all of the files required to build NitrOS9 but I see a
> reference to a file called "systype" in the defsfile. My defsfile only
> references os9defs, rbfdefs, scfdefs, and cocodefs.  Where do I find the
> systype file?  Perhaps it contains the refrerence for SHFTCLR and ohers.
>
> Dave
>
>
>
> On 10/5/2017 4:12 PM, David Ladd wrote:
>
>> Dave,
>>
>> I have not tried NitrOS-9 L2 as a headless configuration yet.  Looking at
>> the headless section in the build process for the NitrOS-9 Project.  I
>> don't see the keyboard, joy, or snd driver in the headless area so that is
>> a good sign.  I do see a scdwv.dr and term_scdwv.dt which tells me that
>> you
>> probably can use the term_sc6551.dt and sc6551.dr.
>>
>> I myself can not verify this as my CoCo3FPGA is not in working condition
>> right now.  As soon as I get my Analog board back I will certainly try
>> some
>> of this out.
>>
>> +-----------------------------------------------------------------------+
>> | David Ladd a.k.a. PacoOtaktay a.k.a. Drencor                          |
>> | YouTube: http://www.youtube.com/user/PacoOtaktay                      |
>> | YouTube Gaming Live: https://gaming.youtube.com/user/PacoOtaktay/live |
>> | Websites: http://dwladd.com     &     http://www.theterrorzone.com    |
>> | G+:  https://plus.google.com/113262444659438038657                    |
>> | G+:  https://plus.google.com/+DavidLaddPacoOtaktay                    |
>> |                                                                       |
>> | Do you have your CoCo 3 yet?                                          |
>> +-----------------------------------------------------------------------+
>>
>>
>> On Thu, Oct 5, 2017 at 2:25 PM, Dave Philipsen <dave at davebiz.com> wrote:
>>
>> Ummm....I shouldn't need to.  I've defined T2 as the default console in
>>> Init.
>>>
>>> In fact, as I'm writing this I just tried adding Term back into the
>>> bootfile and I still have the same problem.  I get the Init and sysgo
>>> sign-on banners but the shell is not chained.
>>>
>>>
>>> Dave
>>>
>>>
>>>
>>> On 10/5/2017 2:04 PM, David Ladd wrote:
>>>
>>> Dave,
>>>>
>>>> I think you still need a TERM descriptor?  Though in this case you
>>>> probably
>>>> need a TERM descriptor based on T2?
>>>>
>>>> +-----------------------------------------------------------
>>>> ------------+
>>>> | David Ladd a.k.a. PacoOtaktay a.k.a. Drencor
>>>> |
>>>> | YouTube: http://www.youtube.com/user/PacoOtaktay
>>>>   |
>>>> | YouTube Gaming Live: https://gaming.youtube.com/user/PacoOtaktay/live
>>>> |
>>>> | Websites: http://dwladd.com     &     http://www.theterrorzone.com
>>>>   |
>>>> | G+:  https://plus.google.com/113262444659438038657
>>>>   |
>>>> | G+:  https://plus.google.com/+DavidLaddPacoOtaktay
>>>>   |
>>>> |
>>>>  |
>>>> | Do you have your CoCo 3 yet?
>>>> |
>>>> +-----------------------------------------------------------
>>>> ------------+
>>>>
>>>>
>>>> On Thu, Oct 5, 2017 at 1:16 PM, Dave Philipsen <dave at davebiz.com>
>>>> wrote:
>>>>
>>>> Ok, so I've successfully eliminated CoWin, KeyDrv, SndDrv, JoyDrv, RBDW,
>>>>
>>>>> DWIO, RAMD, R0, and Term from my bootfile and the CoCo3FPGA boots up
>>>>> with a
>>>>> shell on T2.  But, when I try to remove VTIO I get the signon message
>>>>> from
>>>>> Init on T2 but I don't get a shell.  To my knowledge VTIO is simply a
>>>>> device driver module for the SCF window devices.  If I have no window
>>>>> device descriptors in the bootfile, then, why is VTIO needed?  See
>>>>> output
>>>>> from 'mdir' below:
>>>>>
>>>>>
>>>>> KrnP2       Init        Clock       Clock2      IOMan       RBF
>>>>> SCF         PipeMan     RBSuper     LLCoCo3FPGA Piper SD1
>>>>> DD          SC6551      VTIO        T2          Pipe CCBKrn
>>>>> MDir        Shell       Date        DeIniz      Echo Iniz
>>>>> Link        Load        Save        Unlink
>>>>>
>>>>>
>>>>> Dave
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 10/3/2017 11:12 PM, Dave Philipsen wrote:
>>>>>
>>>>> Yep, it's an FPGA board so it's a synthesized 6809 running at 25 MHz.
>>>>>
>>>>>> Dave
>>>>>>
>>>>>> On 10/3/2017 9:23 PM, Brett Gordon wrote:
>>>>>>
>>>>>> I take it your platform is also 6809 based? Cool.. Sounds like a neat
>>>>>>
>>>>>>> idea.  Loads of fun.  kudos on the bootloader mod - submit patch!
>>>>>>>
>>>>>>> brett
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>
>>>>> Coco mailing list
>>>>> Coco at maltedmedia.com
>>>>> https://pairlist5.pair.net/mailman/listinfo/coco
>>>>>
>>>>>
>>>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> https://pairlist5.pair.net/mailman/listinfo/coco
>>>
>>>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>