HDTenEightyP/NetNews huggingface dataset:
From: Roeber <fjr@ssd.ray.com>
Newsgroups: comp.os.vxworks
Subject: re:  Watch dog timer question
Date: Thu, 5 Nov 1992 08:05:19 -0500
Organization: Lawrence Berkeley Laboratory, Berkeley CA
NNTP-Posting-Host: 128.3.112.16
Originator: daemon@vxw.ee.lbl.gov

Brian Quigley writes:
>   
>  I've been helping a friend troubleshoot a problem which appears to stem from
>  a watchdog timer.  We have one task which is creating a watchdog timer 
>  (globally).  The timer is started and cancelled in this task.  We were
>  also hoping to be able cancel the timer from another task as well.
>  Unfortunately, cancelling the timer from another task doesn't seem to
>  work.  After closer re-reading, the wdLib documentation slightly 
>  implies that a task that creates a watchdog timer is the only one that
>  can access it.  

In VxWorks 5.0.2 there should be no reason why any task that knows a watch
dog ID shouldn't be able to cancel it by calling wdCancel.  There are no
task specific checks in the code.  If you are getting back bad status you
should check the error code.  Maybe you are trying to cancel it multiple
times or passing a bad ID value (or maybe the timer has already expired).  Fred

    _______________________________________________________
   |  Fred J Roeber,  Raytheon Submarine Signal Division   |
   |  1847 West Main Road,  Mail Stop 188                  |
   |  Portsmouth, RI  02871-1087  (401) 847-8000 (X4205)   |
   |                                                       |
   |                   fjr@ssd.ray.com                     |
   |_______________________________________________________|

Newsgroups: comp.os.vxworks
From: hmp@frc2.frc.ri.cmu.edu (Henning Pangels)
Subject: Re: Interesting ld68k behavior
Reply-To: hmp@frc2.frc.ri.cmu.edu (Henning Pangels)
Organization: Field Robotics Center, CMU
Date: Fri, 6 Nov 1992 19:58:27 GMT


In article <geoff.721065104@wrs.com> geoff@wrs.com (Geoff Espin) writes:


>The complaint that compiler flags "-Ttext" and "-e <entrypoint>" are
>independent, at first, seems valid.  But on further reflection,
>it would be very inconvenient if the linker always insisted that
>entry points be the first routines in a module, and that that module
>be the first module listed on the linker command line.  Not everybody
>writes system code.  :-)  What about the UNIX application developer?

I completely agree; from what (little) I know about the internal
structure of loadable module formats (like a.out), there's no reason
the entry point has to be at the beginning of the text segment. 

Perhaps, then, things should be changed in romStart() where, instead of
requiring the entry point ot be at the beginning of the text segment,
the actual address of the entry point specified with the -e flag is
looked up somehow. Is the "struct exec" header from the a.out file
no longer present after the compression/uncompression process?

-hp
--
Henning Pangels    |hmp@frc2.frc.ri.cmu.edu        |     Field Robotics Center
Research Programmer|(412) 268-7088                 |Carnegie-Mellon University
------------------------------------------------------------------------------
                  It can be difficult to wreck a nice beach.
From: Roeber <fjr@ssd.ray.com>
Newsgroups: comp.os.vxworks
Subject: re: MVME167 and RealTime Clock
Date: Thu, 12 Nov 1992 13:38:36 -0500
Organization: Lawrence Berkeley Laboratory, Berkeley CA
NNTP-Posting-Host: 128.3.112.16
Originator: daemon@vxw.ee.lbl.gov

I have some questions concerning setting up MV167 cards better.  First,
Paul Bade wrote:

>  Wind River was informed of this error quite sometime ago, so long ago
>  that I can't remember exactly when. The code I have used to correct the
>  situation is:
>  
>      strncpy ( oscFreq, (char*)0xfffc1f28, 4);  /* read clk speed from BBRAM */
>      oscFreq[4] = NULL; /* terminate string */
>   
>      printf("Board has a %2s.%s Mhz Oscillator\n", oscFreq, &oscFreq[2]);
>      if (!strncmp(oscFreq, "33", 2))
>      {
>        *PCC2_PRESCALE        = -33;
>        *PCC2_PRESCALE_CLK_ADJ  = -33;
>        if (strncmp(oscFreq, "3300", 4))
>        {
>          printf("sysLib.c: sysHwInit: \"Non-Integer clock frequency on Board will introduce error in system Clock ^G^G (see p 3-18 of MV167 manual)\n\"");
>        }
>      }
>         
>      else /* if (strncmp(oscFreq, "2500", 4))   */
>      {
>        *PCC2_PRESCALE        = -25;
>        *PCC2_PRESCALE_CLK_ADJ  = -25;
>      }

I agree that it would be nice to set up the board so it works at any frequency.
Paul is reading a value out of the battery backed RAM to do this.  I wonder
why we couldn't just use the value set in the memory bus clock register
(see MEMC_BCR register on pg 4-12 of the HW guide).  This register is set
up by diagnostics so that the board functions correctly.  It contains the
integer clock speed value.  By simply changing the definition of BCLK in
mv167.h  to be
   #define BCLK  (MEMC_BCR & 0xff)
This should give just what is needed; an integer value that changes to reflect
different clock speeds on modules.

Another issue is the setup of the MEMC_RCR register in the sysHwInit code.
The code for setting the register is set up as follows:

  #ifdef  INCLUDE_EX
    IMPORT int exBusAdrsSpace;
 
    /* For the peripherals to work correctly, the snoop wait bit must
     * be set in the MEMC040 chip.
     */
 
    *MEMC_RCR = MEMC_RCR_RAMEN | MEMC_RCR_SWAIT;
 
    exBusAdrsSpace = VME_AM_EXT_SUP_DATA;
  #endif  /* INCLUDE_EX */

I have no reason to want the Excelan driver support in my vxWorks version
so I want to undef INCLUDE_EX in my config.h file.  The problem is that the
MEMC_RCR doesn't get set up then.  I think the code to set that register
should be outside of the ifdef since the setting is needed for any of the
peripherals to work.  What do others think?    Fred

    _______________________________________________________
   |  Fred J Roeber,  Raytheon Submarine Signal Division   |
   |  1847 West Main Road,  Mail Stop 188                  |
   |  Portsmouth, RI  02871-1087  (401) 847-8000 (X4205)   |
   |                                                       |
   |                   fjr@ssd.ray.com                     |
   |_______________________________________________________|
From: hwajin@iphasew.com
Newsgroups: comp.os.vxworks
Subject: re: Help: task delete and memory cleanup
Date: Thu, 05 Nov 92 21:43:24 -0800
Organization: Lawrence Berkeley Laboratory, Berkeley CA
NNTP-Posting-Host: 128.3.112.16
Originator: daemon@vxw.ee.lbl.gov


sigRaise() checks the taskid to find out if the task is still a valid
task before sending the signal.  if you're already using
taskDeleteHook you should not have to call sigRaise to clean up.  just
perform the necessary cleanups inside taskDeleteHook routine.

	~hwajin
From: prb@aplexus.jhuapl.edu (Paul R. Bade)
Newsgroups: comp.os.vxworks
Subject: re: MVME167 timing
Date: Fri, 6 Nov 92 08:13:17 EST
Organization: Lawrence Berkeley Laboratory, Berkeley CA
NNTP-Posting-Host: 128.3.112.16
Originator: daemon@vxw.ee.lbl.gov


Yes, you all are correct that WRS forgot to initialize the prescaler.
But you may want to set the prescalers based on the 
board's clock frequency which can be read out of the BBRAM.
For example,


    strncpy ( oscFreq, (char*)0xfffc1f28, 4);  /* read clk speed from BBRAM */
    oscFreq[4] = NULL; /* terminate string */

    if (!strncmp(oscFreq, "33", 2))
    {
      *VMECHIP2_TIMEOUTCR       = (TIMEOUTCR_VGTO_64US  |
                                   TIMEOUTCR_VATO_1MS   |
                                   TIMEOUTCR_LBTO_64US  |
                                   TIMEOUTCR_WDTO_16MS  |
                                        0xdf /* prescaler adjust */);
    }

    else /* if (strncmp(oscFreq, "2500", 4))   */
    {
      *VMECHIP2_TIMEOUTCR       = (TIMEOUTCR_VGTO_64US  |
                                   TIMEOUTCR_VATO_1MS   |
                                   TIMEOUTCR_LBTO_64US  |
                                   TIMEOUTCR_WDTO_16MS  |
                                        0xe7 /* prescaler adjust */);
    }



This is the code we have been using. Although we only have 25Mhz boards
right now, we plan to have a mix in the future.

		Paul Bade
		Johns Hopkins University / Applied Physics Lab


Newsgroups: comp.os.vxworks
From: geoff@wrs.com (Geoff Espin)
Subject: Re: Interesting ld68k behavior
Organization: Wind River Systems, Inc.
Date: Fri, 6 Nov 1992 15:51:44 GMT

hmp@frc2.frc.ri.cmu.edu (Henning Pangels) writes:

>I just thought I'd share an observation I've made recently while
>placing vxWorks and application code into ROM.
>...  [accurate description of linking and run-time events deleted]
>But imagine my surprise when I added some custom routines at the top
>of usrConfig.c (one might argue over the political correctness of
>doing so...), and usrInit no longer ended up at RAM_TEXT_HIGH_ADDRESS.
>Instead, whatever routine appeared first in usrConfig.c got that
>privilege and was subsequently called by romStart. 
>The obvious solution was to simply rearrange the order of the routines
>usrConfig.c so that usrInit() comes first.

WRS should explicitly document that the routines: usrConfig.c:usrInit(),
sysALib.s:sysInit() and romInit.s:romInit() must be the first routines
in the text segment, when used as system entry points.  usrInit() is only
the system entry point for the compressed image.  Usually it is called
by sysInit().

The complaint that compiler flags "-Ttext" and "-e <entrypoint>" are
independent, at first, seems valid.  But on further reflection,
it would be very inconvenient if the linker always insisted that
entry points be the first routines in a module, and that that module
be the first module listed on the linker command line.  Not everybody
writes system code.  :-)  What about the UNIX application developer?
Again, a few words of warning in the VxWorks Programmer's Guide wouldn't hurt.
A bug report will be submitted.

Geoff
-- 
Geoff Espin		geoff@wrs.com	(510)748-4100
Wind			River		Systems
1010 Atlantic Avenue	Alameda		CA 94501
From: idy@jet.uk (Ivan D Young)
Newsgroups: comp.os.vxworks
Subject: How to provide an application interface layer ?
Summary: How to provide a layer of s/w for applications to access VME modules ?
Keywords: VxWorks VME
Date: 5 Nov 92 11:40:11 GMT
Organization: Joint European Torus

We are about to deploy VME based systems here for the first time using
VxWorks.

We are considering how to provide an application interface layer for 
for access to VME hardware. The aim being to minimize the application
writer efforts by providing a consistent interface image.

We would be interested in how other people organize the access to VME
hardware. Any information or references to publications that may be 
relevant would be appreciated.

Brief description of environment:-
Hosts: Network of 40 Sun Sparc 2s running SUN/OS (Unix).
VME  : Crates distributed around the experiment and connected to hosts
       via ethernet.
VME Bus master : 68040 processor board with ethernet interface
		 providing the data path between the VME bus and
		 the hosts. Most application software is expect to run
		 in this processor under VxWorks.

VME slaves     : A mix of off the shelf and in-house designed modules.
		 Ranging from simple I/O boards,  in-house designs
		 for counters and ADCs with embedded 68030s
		 to commercial C40 based DSP boards. Also other
		 processor boards 030s or 040s running application code
		 as required, under VxWorks.


Please E-mail.
Thanks
Ivan...

-- 
+-------------------------------------------------------+----------------+
| Ivan D Young          | Voice : 0235 528822 ext 4591  |  ++===||===++  |
| CODAS Division        |       : 0235 464591           |  || /-||-\ ||  |
| JET Joint Undertaking | FAX   : 0235 464404           |  ||| O||O |||  |
| Abingdon              | E-mail: idy@jet.uk            |  || \_||_ /||  |
| Oxfordshire  OX14 3EA |                               |  ++===||===++  |
| United Kingdom        |                               |     J E T      |
+-----------------------+-------------------------------+----------------+
| "If it's a good idea, go ahead and do it. Its easier to apologise,     |
| than to get permission."    Grace Hopper.                              |
+------------------------------------------------------------------------+


- Disclaimer: Please note that the above is a personal view and should not 
  be construed as an official comment from the JET project.
Newsgroups: comp.os.cpm
From: fmouse@wixer.cactus.org (Lindsay Haisley)
Subject: Re: PD C Compiler?
Organization: Real/Time Communications
Date: Thu, 5 Nov 92 22:18:06 GMT


In article <1992Nov2.165922.29374@afc.com> andy@afc.com (Andy Hunt) writes:
>Hi, I'm looking for a reasonable C compiler for my old MAX-80.
>Either a native compiler, or a cross compiler that I can
>run under Unix.  Is there anything available?

BDS C, one of the best CP/M C compilers is still on the market, and is
quite reasonably priced, I believe.  It's currently marketed and
supported by Jay Sage of Sage Microsystems East.  You can reach him on
his BBS at 617-965-7259 (password "DDT") or by voice at 617-569-3552,
call about 10 Eastern time.  BDS C is a nearly complete K&R
implementation which makes fairly tight code and was the leader of the
pack at one point in speed benchmarks.


-- 
"Everything works if you let it"    |            Lindsay Haisley
-- The Roadie                       |            fmouse@wixer.cactus.org
                                    |            ***    formerly    ****
                                    |            roadhog@wixer.cactus.org
Newsgroups: comp.os.cpm
From: syswtr@iowasp.physics.uiowa.edu
Subject: Re: 22DISK problem with trs-80 4pex
Organization: Department of Physics and Astronomy, University of Iowa
Distribution: usa
Date: Wed, 11 Nov 1992 14:15:41 GMT

In article <10NOV199219471721@zeus.tamu.edu>, jle9162@zeus.tamu.edu (ECKHARDT, JASON LEE) writes:
> I have a trs-80 model 4p and and 486/clone. I have been getting software
> of the net for the 4p but its all on my pc. So i got 22disk to hopefully
> write all this good stuff to my model 4's cpm disks.
> Unforunately, 22disk doesn't (seem) to support my version of cpm.
> I think its cpm plus 3.0 : according to anadisk it has a 2:1 interleave
> and sector ids 0-17 and 256 byte sectors.
> 
> Can anyone tell me how to get this format working with 22disk?
> 
> thanks, jason.
> 
 The 4P will also read an Osborne format (185K capacity).  There is also
a Zenith format (152K or 156K) that should work..

Willy
From: donm@crash.cts.com (Don Maslin)
Newsgroups: comp.os.cpm
Subject: Re: msdos to cpm
Date: 9 Nov 92 15:12:20 GMT
Article-I.D.: crash.1992Nov09.071221.564
Distribution: usa
Organization: CTS Network Services (crash, ctsnet), El Cajon, CA

Either 22DISK by Sydex (shareware) or UniForm by MicroSolutions (commercial)
is what you seek.

 
              Sydex
              P.O. Box 5700
              Eugene, OR  97405
              Voice:  (503)  683-6033
              FAX:    (503)  683-1622
              Data:   (503)  683-1385
 
                Micro Solutions, Inc.
                132 West Lincoln Hwy.
                DeKalb IL 60115
                (815) 756-3411
 
Newsgroups: comp.os.cpm
From: wieland@ea.ecn.purdue.edu (Jeffrey J Wieland)
Subject: Re: I just got a Z80 CP/M
Organization: Purdue University Engineering Computer Network
Date: Fri, 6 Nov 1992 17:16:43 GMT

In article <1992Nov6.004618.26117@Princeton.EDU> mneufeld@phoenix.Princeton.EDU (Michael John Neufeld) writes:
>In article <1992Nov5.093010.60418@cc.usu.edu> ivie@cc.usu.edu (CP/M lives!) writes:
>>In article <1992Nov4.224605.4967@midway.uchicago.edu>, silveanu@uhuru.uchicago.edu (Adrian Silveanu) writes:
>>> Where there ever any CP/M computers with a moniter other than mono?
>>

There was a color graphics board for CP/M Kaypros -- I know -- I have
one that I bought from one of the engineers that designed it.  It was
made by MicroSphere.  It uses the Texas Instruments TI-9918A chip,
which gives 256x192 resolution, 16 colors and 32 sprites.  This is the
same chip that a lot of game machines and early micro computers used,
like the Texas Instruments TI99.

I had started writing a set of procedures for it with Turbo Modula 2,
but I have not found the time to finish it.

I also remember reading about a color graphics board that plugged into
a standard Centronics parallel port, so you drive it from virtually any
computer.  I think I saw this back in '86 or '87.  I don't remember
what company made it.
--
			    Jeffrey J. Wieland
		      Communication Systems Programmer
		        Agricultural Computer Network

    INTERNET: wieland@acn.purdue.edu		ENTM 216
    BITNET:   WIELAND@PURCCVM			Purdue University
    UUCP:     ...!ecn-ee!wieland		West Lafayette, IN 47907
    FAX:      (317)494-8342			(317)494-8333
Newsgroups: comp.os.cpm
From: shad04@ccu.umanitoba.ca (Dan Fandrich)
Subject: Re: Undocumented Z80 opcodes
Organization: University of Manitoba, Winnipeg, Manitoba, Canada
Date: Fri, 13 Nov 1992 12:12:32 GMT

In article <19896.2affc496@ul.ie> 9113797@ul.ie writes:
>
>Does anyone have a List
>of the UNdocumented op-codes
>For the Zilog Z80 Mirco processor
>
>If so would you send me a copy
>
>
>Garret Flynn,
>Information Technology,
>University of Limerick,
>Ireland,

Not bad, but the second line is harsh and the rhyme scheme is weak.  
How about:

      Does anyone have a tabulation,
      Of all of the undoc'mented instructions,
         For the Zilog Z80
         Micro-heavyweighty;
      If so, would you send me a reproduction?

But who am I to critique someone from the University of Limerick?

>>> Dan
-- 
Internet: shad04@ccu.umanitoba.ca               Compu$erve: 72365,306
From: c.currie@CLUS1.ULCC.AC.UK (Christopher Currie)
Newsgroups: comp.os.cpm
Subject: TRS80 and MS-DOS
Date: 4 Nov 92 11:11:30 GMT
Organization: The Internet

>>
>Date: Mon, 2 Nov 92 19:47:41 EST
>From: eudoh@st6000.sct.edu (Etop Udoh)
>Subject: TRS-80 to MSDOS....
>Message-ID: <9211030047.AA19081@st6000.sct.edu>
>
>hi,
>
>   As far as I know, the Model 4/4D/4P will run CP/M without any other
>modifications,

Yes, it will.

> as opposed to at least the Model III which I'm aware of
>which requires a hardware board....forgot who makes it....

There were boards made by Memory Merchant (Shuffleboard), Holmes, 
and Omikron (the Mapper).
>
>   Anyway, theres a program/utility called supercross XT or something
>of that nature which allows you to read and write other operating systems
>including MSDOS but this runs under the MOdel III operating system and
>Model 4 Trsdos.....
>
>
There is also PC-CRoss-Zap, which runs under MS-DOS on the PC, and 
is supplied by Hypersoft at:

    PO Box 51155, Raleigh, NC 27609 USA

They also make Hypercross which runs on the Model III and allows
you to read-write, under TRS-80 operating systems, PC and CP/M 
disks.

>   For CP/M, there's a customized CP/M called Montezuma Micro 
CP/M

>   By the way, this is CP/M 2.2 which is far superior to Radio Shack's
> CP/M 3.0......and also available (don't know where you can find it these
>days ) for this CP/M is "Monte's Toolkit" which includes disk formating
>and reading utilities, including a virtual file utility for moving files
>between CP/M, TRSDOS, or MSDOS.....
>
They also did Monte's Window, a TSR with notepad, calculator, 
calendar, etc.

There are memory-mapped versions of some software, e.g. Wordstar 
3.3, around for the Model 4.

>   current updated stuff available for this defunct line of computers are:
>
... goodies deleted...

>  external drive modification using the 50 pin rear connector

You shouldn't need a mod for the Model III, which is built to take 
two internal and two external drives. It's the Model 4P that has 
to be modified to take more than two drives.

Christopher Currie

c.currie@clus1.ulcc.ac.uk
From: kerwin@acsu.buffalo.edu (John J. Kerwin)
Newsgroups: comp.os.cpm
Subject: TURBO DOS *********
Date: 9 Nov 92 05:10:51 GMT
Organization: UB



Has anyone heard of turbo dos for the CPM if you have please e-mail me
i have a couple of question i would like to ask you 


                                                 jk
Newsgroups: comp.os.cpm
From: jle9162@zeus.tamu.edu (ECKHARDT, JASON LEE)
Subject: 22DISK problem with trs-80 4p
News-Software: VAX/VMS VNEWS 1.41    
Organization: Texas A&M University, Academic Computing Services
Distribution: usa
Date: Wed, 11 Nov 1992 01:47:00 GMT

I have a trs-80 model 4p and and 486/clone. I have been getting software
of the net for the 4p but its all on my pc. So i got 22disk to hopefully
write all this good stuff to my model 4's cpm disks.
Unforunately, 22disk doesn't (seem) to support my version of cpm.
I think its cpm plus 3.0 : according to anadisk it has a 2:1 interleave
and sector ids 0-17 and 256 byte sectors.

Can anyone tell me how to get this format working with 22disk?

thanks, jason.

Newsgroups: comp.os.cpm
From: jle9162@zeus.tamu.edu (ECKHARDT, JASON LEE)
Subject: small c problem
News-Software: VAX/VMS VNEWS 1.41    
Organization: Texas A&M University, Academic Computing Services
Distribution: usa
Date: Sun, 8 Nov 1992 06:47:00 GMT

I just got smallc21 and it seems that I can't use the "%f" conversion
specifier with this compiler?!  Is this not built in this version or am
I supposed to include something? If this is a deficiency, is there another
pd compiler available with a full 'c' implementation? (ansi would be great).

jason.
From: "richard wyble" <richard.wyble@channel1.com>
Newsgroups: comp.os.cpm
Subject: pascal mt/+ for sale
Date: 11 Nov 92 23:48:58 EST
Reply-To: "richard wyble" <richard.wyble@channel1.com>
Distribution: comp
Organization: Channel 1 Communications

Pascal MT/+ for sale, original packaging, documentation, and discs. Disc
format is 8" cpm generic, and I include copies in 5.25" Kaypro DSDD. Make an
offer.
---
  EZ 1.39  richard.wyble@channel1.com (Richard J. Wyble)
--
Channel 1 (R)   Cambridge, MA

Newsgroups: comp.os.cpm
From: wolff@inf.fu-berlin.de (Thomas Wolff)
Subject: Re: msdos to cpm
Organization: Free University of Berlin, Germany
Distribution: usa
Date: Tue, 10 Nov 1992 10:51:08 GMT

donm@crash.cts.com (Don Maslin) writes:

>Either 22DISK by Sydex (shareware) or UniForm by MicroSolutions (commercial)
>is what you seek.

UniForm does not seem to run anymore on recent MSDOS versions. It was of 
questionable use anyway, at least not generally usable, since it was not 
configurable to arbitrary formats. This is both unfortunate because its 
concept of installing virtual drives instead of implementing copy commands 
was certainly the nicer one.
Dan Fandrich recently announced a new program to install virtual drives 
handling CP/M disks (if I understood him right), but - again unfortunately - 
it doesn't seem to have been released yet.
 
Thomas
wolff@inf.fu-berlin.de
Newsgroups: comp.os.cpm
From: sjh@skewsby.demon.co.uk (Simon J Hopkins)