[Coco] NitrOS9 question
Neal Crook
foofoobedoo at gmail.com
Fri Oct 6 07:55:15 EDT 2017
In my mc09 l2 development I found a bug where a too - small bootfile would
hang. Padding it fixed the problem. I will look out the details over the
weekend and let you know, so we can see if our experiences tally. It would
be good to know that it was a generic problem and not specific to my target
hardware. I spent quite a lot of time in emulation trying to track it down
without success
Neal
On 6 Oct 2017 12:40, "Dave Philipsen" <dave at davebiz.com> wrote:
Haha! That doesn't work either. But as soon as I re-assemble Term with
265 extra bytes in it, it boots just fine. So it really does appear to be
an issue with size and not order.
That being said, I'm gonna hit the sack because it's almost midnight here.
Will attack this thing more tomorrow. Thanks to everyone for all of your
suggestions and help!
Dave
On 10/5/2017 11:49 PM, David Ladd wrote:
> Dave,
>
> Try this boot order.
>
> KrnP2 IOMan Init RBF RBSuper LLCoCo3FPGA DD SD1 SCF SC6551 Term PipeMan
> Piper Pipe Clock Clock2
>
>
>
> +-----------------------------------------------------------------------+
> | 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://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 11:46 PM, Dave Philipsen <dave at davebiz.com <mailto:
> dave at davebiz.com>> wrote:
>
> Ok, this is my module order right now:
>
>
> KrnP2 Init Clock Clock2 IOMan RBF SCF PipeMan RBSuper LLCoCo3FPGA
> Piper SD1 DD SC6551 Term Pipe
>
> But I don't think it has to do with the order. I just took VTIO
> out completely and then added 265 bytes to the Term descriptor.
> And now it works without VTIO! So it appears there is an issue
> with size.
>
>
>
>
> Dave
>
>
>
>
>
>
> On 10/5/2017 11:39 PM, David Ladd wrote:
>
> Dave,
>
> Hmmmm the BLOB....That is not a good thing. Damn I wish I had
> a way to
> test it lol. What is your module order in your OS9Boot file
> right now?
>
>
> +-----------------------------------------------------------
> ------------+
> | David Ladd a.k.a. PacoOtaktay a.k.a. Drencor |
> | YouTube: http://www.youtube.com/user/PacoOtaktay
> <http://www.youtube.com/user/PacoOtaktay> |
> | YouTube Gaming Live:
> https://gaming.youtube.com/user/PacoOtaktay/live
> <https://gaming.youtube.com/user/PacoOtaktay/live> |
> | Websites: http://dwladd.com & http://www.theterrorzone.com |
> | G+: https://plus.google.com/113262444659438038657
> <https://plus.google.com/113262444659438038657>
> |
> | G+: https://plus.google.com/+DavidLaddPacoOtaktay
> <https://plus.google.com/+DavidLaddPacoOtaktay>
> |
> | |
> | Do you have your CoCo 3 yet? |
> +-----------------------------------------------------------
> ------------+
>
>
> On Thu, Oct 5, 2017 at 11:14 PM, Dave Philipsen
> <dave at davebiz.com <mailto:dave at davebiz.com>> wrote:
>
> Ok, I just found out something very interesting. I
> decided to assemble a
> dummy VTIO with entry points for Init, Read, Write,
> GetStat, SetStat, and
> Term. There is no code in the module except for a single
> rts that all six
> routines point to. When I include this version of VTIO in
> the bootfile it
> still fails in headless mode. The VTIO module is only
> about 140 bytes
> long. Now, when I simply add a few lines with:
>
> fcc /0000000000000000000000000000
> 0000000000000000000000/
>
> This makes the VTIO module a little bigger. It is now 497
> bytes long.
> And, it works! Don't ask me why but I have a feeling it
> has nothing to do
> with what's in VTIO. But it could possibly have something
> to do with where
> other modules end up in memory. I'm wondering now if it's
> something
> strange going on with CCBKrn...
>
> Dave
>
>
>
>
> On 10/5/2017 10:58 PM, David Ladd wrote:
>
> Dave,
>
> That is interesting. Since in the headless options in
> the repo I don't
> see
> the VTIO listed in the modules. I know as I used the
> Toolshed's OS9
> utility to ident one of the bootfile's and I didn't
> see VTIO in there
> anywhere.
>
> Though there is a disk image for becker_headless.
>
> +-----------------------------
> ------------------------------------------+
> | David Ladd a.k.a. PacoOtaktay a.k.a. Drencor
> |
> | YouTube: http://www.youtube.com/user/PacoOtaktay
> <http://www.youtube.com/user/PacoOtaktay>
> |
> | YouTube Gaming Live:
> https://gaming.youtube.com/user/PacoOtaktay/live
> <https://gaming.youtube.com/user/PacoOtaktay/live> |
> | Websites: http://dwladd.com &
> http://www.theterrorzone.com |
> | G+: https://plus.google.com/113262444659438038657
> <https://plus.google.com/113262444659438038657>
> |
> | G+: https://plus.google.com/+DavidLaddPacoOtaktay
> <https://plus.google.com/+DavidLaddPacoOtaktay>
> |
> | |
> | Do you have your CoCo 3 yet? |
> +-----------------------------
> ------------------------------------------+
>
>
> On Thu, Oct 5, 2017 at 10:46 PM, Dave Philipsen
> <dave at davebiz.com <mailto:dave at davebiz.com>> wrote:
>
> Ok, well here's something somewhat interesting. I
> don't have the VTIO
>
> source file setup yet where I can assemble it on
> my CoCo3FPGA. But, I
> made
> a copy of the VTIO module and I patched it by
> putting 'RTS' in place of
> the
> long branches to init, read, write, getstat,
> settat, and the first byte
> of
> the term routines. So, effectively, there is no
> access to the module.
> When I include it in the bootfile for the headless
> boot the shell still
> works!
>
> So could it be just the mere existence of the VTIO
> module makes the shell
> work for some oddball reason?
>
> The next thing I'm going to try is to assemble a
> 100% bogus VTIO module
> with only code in it to return (rts) from the six
> entry points and see
> what
> happens.
>
>
> Dave
>
>
>
> On 10/5/2017 10:05 PM, Bill Pierce via Coco wrote:
>
> There's 2 shells built in NitrOS9... try the other
> one. The one used in
>
> L2 is ShellPlus. The L1 shell (will work in
> L2) is shell_21.
> Shell plus monitors for keystrokes for the
> arrow keys for the cmd line
> so
> that may be what you're running into. I don't
> think shell_21 does this
> (not
> sure).
>
>
>
> Bill Pierce
> "Charlie stole the handle, and the train it
> won't stop going, no way to
> slow down!" - Ian Anderson - Jethro Tull
>
> My Music from the Tandy/Radio Shack Color
> Computer 2 & 3
> https://sites.google.com/site/dabarnstudio/
> <https://sites.google.com/site/dabarnstudio/>
> Co-Contributor, Co-Editor for CocoPedia
> http://www.cocopedia.com/wiki/index.php/Main_Page
> <http://www.cocopedia.com/wiki/index.php/Main_Page
> >
>
> E-Mail: ooogalapasooo at aol.com
> <mailto:ooogalapasooo at aol.com>
>
>
>
>
> -----Original Message-----
> From: Dave Philipsen <dave at davebiz.com
> <mailto:dave at davebiz.com>>
> To: CoCoList for Color Computer Enthusiasts
> <coco at maltedmedia.com
> <mailto:coco at maltedmedia.com>>
> Sent: Thu, Oct 5, 2017 10:18 pm
> Subject: Re: [Coco] NitrOS9 question
>
> Look in nitros9-v3.3.0/level2/defs/DefsfileSee
> if it's listed there.
> It
> may be of no consequence though. Interesting
> thing is that I can tell
> sysgo
> to run another program on startup instead of
> shell and it will run. The
> only way I can get shell to run is if I
> include VTIO in the
> bootfile.DaveOn
> 10/5/2017 9:00 PM, Bill Pierce via Coco
> wrote:> Dave, where did you get
> your sources? I have searched the entire
> repository for "systype" and
> found
> nothing. I remember systype from vanilla OS9,
> but I don't think it's
> used
> anymore.> The current VTIO source does
> reference "cocovtio.d" though.>>
> >> >> Bill Pierce> "Charlie stole the
> handle, and the train it won't
> stop going, no way to slow down!" - Ian
> Anderson - Jethro Tull>> My
> Music
> from the Tandy/Radio Shack Color Computer 2 & 3>
> https://sites.google.com/site/dabarnstudio/
> <https://sites.google.com/site/dabarnstudio/>>
> Co-Contributor, Co-Editor
> for CocoPedia>
> http://www.cocopedia.com/wiki/index.php/Main_Page
> <http://www.cocopedia.com/wiki/index.php/Main_Page
> >>>
> E-Mail: ooogalapasooo at aol.com
> <mailto:ooogalapasooo at aol.com>>> >> >>
>
> -----Original Message----->
> From: Dave Philipsen <dave at davebiz.com
> <mailto:dave at davebiz.com>>> To: coco
> <coco at maltedmedia.com
> <mailto:coco at maltedmedia.com>
> Sent: Thu, Oct 5, 2017 6:00 pm> Subject: Re:
> [Coco] NitrOS9 question>>
> 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.DaveOn 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
> <http://www.youtube.com/user/PacoOtaktay>
> |> |
> YouTube Gaming Live:
> https://gaming.youtube.com/user/PacoOtaktay/live
> <https://gaming.youtube.com/user/PacoOtaktay/live>
> |>
> | Websites: http://dwladd.com &
> http://www.theterrorzone.com
> |> | G+:
> https://plus.google.com/113262444659438038657
> <https://plus.google.com/113262444659438038657>
> |> | G+:
> https://plus.google.com/+DavidLaddPacoOtaktay
> <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
> <mailto: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
> <http://www.youtube.com/user/PacoOtaktay>
> |>>> |
> YouTube Gaming Live:
> https://gaming.youtube.com/user/PacoOtaktay/live
> <https://gaming.youtube.com/user/PacoOtaktay/live>
> |>>> | Websites: http://dwladd.com &
> http://www.theterrorzone.com
> |>>> | G+:
> https://plus.google.com/113262444659438038657
> <https://plus.google.com/113262444659438038657>
> |>>> | G+:
> https://plus.google.com/+DavidLaddPacoOtaktay
> <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
> <mailto: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
> <mailto:Coco at maltedmedia.com>>>>>
>
> https://pairlist5.pair.net/mai
> lman/listinfo/coco>>>>>>>>>>
> -->> Coco mailing list>>
> Coco at maltedmedia.com
> <mailto:Coco at maltedmedia.com>>>
>
> https://pairlist5.pair.net/mai
> lman/listinfo/coco>>-- Coco
> mailing
> listCoco at maltedmedia.comhttps:
> //
> pairlist5.pair.net/mailman/lis
> tinfo/coco
> <http://pairlist5.pair.net/mai
> lman/listinfo/coco>>--
> Coco mailing
> listCoco at maltedmedia.comhttps://
> pairlist5.pair.net/mailman/l
> <http://pairlist5.pair.net/mai
> lman/l>
>
> istinfo/coco
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com <mailto:Coco at maltedmedia.com>
> https://pairlist5.pair.net/mailman/listinfo/coco
>
> <https://pairlist5.pair.net/mailman/listinfo/coco>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com <mailto:Coco at maltedmedia.com>
> https://pairlist5.pair.net/mailman/listinfo/coco
> <https://pairlist5.pair.net/mailman/listinfo/coco>
>
>
>
>
--
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco
More information about the Coco
mailing list