[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

2349.0. "Amiga Diagostic Program Specifications" by ANT::JANZEN (Mr. MSI ECL Test) Fri Mar 10 1989 19:07

    Diagnostic Plan for Amiga
    There are apparently no diagnostic programs for the Amiga for the
    general public.  How should such diags work?  What should they do?
    
    1.  Is it OK for diags to directly access h/w resources, since diags
    must assume enough is broken that only a minimum machine remains?
    2.  Should it begin in Intuition with a menu of 
    	a. tests to run, hardware to test
    	b. depth of test (long memory test (ca. 1 hour), short memory
         test, etc.)
    3. Should it test external hardware?
    
    here are some tests:
    1. memory test; short, long .  rotating ones, zeros, full ones,zeros,
    	alternating ones.  Report on memory size, gaps.
    2. CPU test: full instruction set, addressing modes, traps, exceptions,
    floating point.
    3. Hardware registers: UART registers read/write bits; blitter
    registers	read/write data bits; etc.
    4. Blitter DMA drill.
    5. D/A convertors (external scope or speaker needed).
    6. Parallel port (how do we verify this with cheapest possible h/w)
    7. video interface: ntsc, have to connect it to tv and do raster
    	patterns.
    8. rgb interface: hue alignment, hue granularity, grays, (you have
    to prompt the user to say, "I've seen it, it's ok, go to next test')
    
    
    The diags should have an overall repeat or just memory test repeat
    option.  Short looping for scoping should be avaialbe..
    Reports should identify failing chips by name: paula, agnus, 8520.
    68000.
    
    External peripherals:
    external and internal drive tests, using scratch diskette.  read/write
    patterns.  choosable patterns.
    printer check.  serial device terminal mode check.
    probably have to use a loop-back cable on serial device.  Does the
    parallel deivce have an input?
    Have to check the mouses.  How do you check mouses?  have to have
    user interaction?  Try to avoid this.
    What are your thoughts?
    Tom
T.RTitleUserPersonal
Name
DateLines
2349.1Yes there are.WJG::GUINEAUFri Mar 10 1989 19:288
I believe there are diagnostic programs available for the Amiga.

Look in WJG::AMIGA:DIAGV5.ARC;1        DIAG_COLORS.TXT;1
          
I've never tried them so I can;t say how good they are.

John
2349.2GOOD one neededMQOFS::DESROSIERSLets procrastinate....tomorrowSun Mar 12 1989 04:0616
    Well, I have, my 2052 developped some problems and these did not
    show any errors.  I tried them on a freind's 2000 with the basic
    1 meg and no memory problems were detected even though we are quite
    sure there are.
    
    My memory problems became visible when I added an 2090A + HD, it
    seems that the HD driver changed the memory map enough so that programs
    like DPaint and Pixmate would guru.  My freind's problem was different,
    transformer would guru on his machine, but ran when HE added an
    HD controller, altough DPaint would now guru once in a while.
    
    Better diags are needed soon for the Amiga.  I think that even
    Commodore does not have proper diags!
    
    Still on western standard time   Jean
    
2349.3ODT for the AMIGA ?KLO::ALVAREZMiguel, from beautiful ClonmelMon Mar 13 1989 08:5813
    	I'm sure the AMIGA must have diagnostics in firmware, where
    many of the functions mentioned in .0 must be tested. 
    	However, what's missing is an interface to these routines by
    which you could run them at will, loop or single step, and have
    access to memory/registers. Also to provide more specific failure
    codes than the color of the screen.
    	Maybe Commodore could publish a "self-test" guide and somebody
    could then build a simple interface which requires the least possible
    amount of resources to be functional. Ideally blasted into ROM,
    so that disk I/O is not required. For those familiar with DECservers,
    something like ODT.
    
    Miguel A. Alvarez 
2349.4DIAGV5TDCIS3::POUTHIERTue Mar 14 1989 09:415
    We need to run DIAGV5 a program called CPRI (priority selection
    to CPU) which one is not in the kit DIAGV5.ARC ???
    Where is CPRI ??.
    
    Michel