[comp.sys.nsc.32k] 532 bug?

alvin@saturn.ucsc.edu (Alvin Jee) (05/02/91)

AHHHH!!!
   I've found somw interesting behaviour in my 532. It seems that the
   notb instruction is not doing it's thing. All I can get it to
   do is add one to my source operand. I've attached a copy of the
   output I get from the monitor.

   Oh, the first bsr gets a character from the serial port and puts it
   in r0. In this example, I've entered a space character.

   Any help and insight into this will be much appreciated!
	Alvin Jee
	alvin@spica.ucsc.edu

--------- This is the start of the whole thing -------

Command (? for help): dis 10000 8 
   10000        br      2
   10002        enter   [],0
   10005        bsr     48
   10008        notb    r0,r1
   1000b        bsr     130
   1000e        br      -12
   10010        exit    []
   10012        ret     0
Command (? for help): set bkpt0 10008
Command (? for help): run 10000
   10008        notb    r0,r1   (breakpoint)
Command (? for help): show
      r0=20             r1=0              r2=0              r3=0        
      r4=0              r5=0              r6=0              r7=0        
      f0=0              f1=0              f2=0              f3=0        
      f4=0              f5=0              f6=0              f7=0        
     l1l=0             l1h=0             l3l=0             l3h=0        
     l5l=0             l5h=0             l7l=0             l7h=0        
      pc=10008         usp=ffc           isp=bf8            fp=bf8      
      sb=0         intbase=40            mod=8             psr=ipsunzFvltc
     dcr=0             dsr=0             car=0             bpc=0        
     cfg=bf7          ptb0=0            ptb1=0            tear=0        
     mcr=0             msr=0             fsr=10000           .=10014    
      v1=0              v2=0           bkpt0=10008       bkpt1=0        
   bkpt2=0           bkpt3=0           bkpt4=0           bkpt5=0        
   bkpt6=0           bkpt7=0           radix=d'16        debug=d'0      
  scrlen=d'24     scsi_adr=1        scsi_lun=0        
Command (? for help): step
   1000b        bsr     130     (trace)
Command (? for help): show
      r0=20             r1=21             r2=0              r3=0        
      r4=0              r5=0              r6=0              r7=0        
      f0=0              f1=0              f2=0              f3=0        
      f4=0              f5=0              f6=0              f7=0        
     l1l=0             l1h=0             l3l=0             l3h=0        
     l5l=0             l5h=0             l7l=0             l7h=0        
      pc=1000b         usp=ffc           isp=bf8            fp=bf8      
      sb=0         intbase=40            mod=8             psr=ipsunzFvltc
     dcr=0             dsr=0             car=0             bpc=0        
     cfg=bf7          ptb0=0            ptb1=0            tear=0        
     mcr=0             msr=0             fsr=10000           .=10014    
      v1=0              v2=0           bkpt0=10008       bkpt1=0        
   bkpt2=0           bkpt3=0           bkpt4=0           bkpt5=0        
   bkpt6=0           bkpt7=0           radix=d'16        debug=d'0      
  scrlen=d'24     scsi_adr=1        scsi_lun=0        
Command (? for help): 
---------- Well, any ideas? ------------------------

dlr@daver.bungi.com (Dave Rand) (05/03/91)

[In the message entitled "532 bug?" on May  2,  0:48, Alvin Jee writes:]
> AHHHH!!!
>    I've found somw interesting behaviour in my 532. It seems that the
> [notb is broken] ...
> ---------- Well, any ideas? ------------------------

Yup. Chip is broken - get another one. But first, do check the power supply
using a good quality DVM. The +5 should be within 5%, close to the CPU (not
that it matters much with the good ground plane on the PC532). If it is
out of that range, anything could happen...



-- 
Dave Rand
{pyramid|mips|bct|vsi1}!daver!dlr	Internet: dlr@daver.bungi.com

alvin@saturn.ucsc.edu (Alvin Jee) (05/03/91)

Oh, boy.. do I feel stupid.
I was using the wrong opcode (imagine that). I think this
may be am argument for RISC-like machine--not getting the
names of the opcodes mixed. So, um, er, never mind.
	Alvin Jee