Re: MPC860: quicc_smc_serial_driver change

[nprasad3 at gmu dot edu]

Gary,

I am attaching the output from 3 different runs on my platform of the same tester. I had used the mbx port as a starting point but looks like the diag and interrupt driver do not like each other.

Thanks
Nirmal

----- Original Message -----
From: Gary Thomas <gary@mlbassoc.com>
Date: Thursday, January 8, 2004 8:14 am
Subject: Re: MPC860: quicc_smc_serial_driver change

> On Wed, 2004-01-07 at 16:26, nprasad3@gmu.edu wrote:
> > > Possibly (I wrote the driver), but probably long since discarded
> > > as a useful mode.
> > > 
> > This mode turns out to be very useful to me. I have only 1 port 
> > SCC1 that can be used by the diag interface as well as printf. I 
> > used the hal_diag.c from mbx port and it does not work with the 
> > interrupt driven driver so when I started with the interrupt 
> driven 
> > driver, it would go hang because of the diag_printf.
> > > > 
> > > > I started with the polling mode driver as I thought it would 
> be 
> > > > easy to get it going on my target first. 
> > > 
> > > What is there to get going?  This is all common 860/QUICC stuff,
> > > and there shouldn't need to be any platform specifics required.
> > > 
> > Anyways I do have the interrupt mode driver working now but only 
> by 
> > disabling diags. I have to see how to make the 2 co-exist on one 
> port 
> > (probably polling mode driver for debugging).
> 
> I don't understand - I've used SCC1 for both serial and diag at the
> same time.  I don't have an MBX860, but I do have other QUICC boards.
> 
> I just tried this on my Viper/860, using SCC1 as the serial console
> and it worked perfectly, mixing diagnostic I/O and large amounts of
> serial I/O via the serial driver.  The program and kernel setups
> are attached.
> 
> I think you must have some other problem, possibly dealing with
> interrupts.
> 
> -- 
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
>

Attachment: test_out.txt
Description: Text document