[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [oc] UART16550 core



Hi Igor

I'm not too sure what you mean?
CYC_O from the master is not a very important signal, a slave can
ignore it if it wants. All I did was use it to qualify the Read/Write
enable signals . The wishbone speci is very vague when it
comes to the slaves handling of this signal.

regards
Carl

> You probably made a mistake here. Check pages 34 and 36 of the wishbone
> spec.
>
> Regards,
> Igor
>
> > -----Original Message-----
> > From: owner-cores@opencores.org [mailto:owner-cores@opencores.org]On
> > Behalf Of Carl van Schaik
> > Sent: 09. avgust 2001 10:50
> > To: cores@opencores.org
> > Subject: Re: [oc] UART16550 core
> >
> >
> > Hi Igor
> >
> > I can add the cycle signal if you like, the examples in the wishbone
spec
> > don't have that
> > signal, it is probably why I didn't include it.
> >
> > regards
> > Carl
> >
> > ----- Original Message -----
> > From: "Igor Mohor (uni-mb)" <igor.mohor@uni-mb.si>
> > To: <cores@opencores.org>
> > Sent: Wednesday, August 08, 2001 1:11 PM
> > Subject: RE: [oc] UART16550 core
> >
> >
> > > Hi, Carl,
> > >
> > > I noticed that CYCLE signal is missing in your WISHBONE interface.
> > >
> > > Regards,
> > > Igor
> > >
> > > > -----Original Message-----
> > > > From: owner-cores@opencores.org [mailto:owner-cores@opencores.org]On
> > > > Behalf Of Carl van Schaik
> > > > Sent: 07. avgust 2001 8:04
> > > > To: cores@opencores.org
> > > > Subject: Re: [oc] UART16550 core
> > > >
> > > >
> > > > Hi Igor,
> > > >
> > > > > so if I understand correctly, there are two versions, one in
> > > > Verilog that
> > > > > was downloaded
> > > > > from the opencores and one in VHDL that you wrote (perhaps
> > > > opencores files
> > > > > translated to
> > > > > VHDL and than changed).
> > > > This is correct except that the Verilog was not simply converted to
> > VHDL.
> > > > I have written UART's before and used the Verilog code mainly as
> > > > an example
> > > > for my own code for the 16550.
> > > >
> > > > > I don't know which ones to take for testing. I'm a verilog guy,
> > > > not VHDL,
> > > > > although I would
> > > > > take the VHDL files if they contain less bugs than the ones in
> > verilog.
> > > >
> > > > Well, from what I saw, the Verilog version has a few bugs.
> > The main ones
> > I
> > > > noticed are:
> > > >
> > > > FIFO - not cleared when data is popped out(empty). - Error bits
> > > > could remain
> > > > Break detection looked a bit weird (but I'm not a Verilog person)
> > > > Stop_bits signal in LCR(Line control register) is not used.
> > > > Only 16550 mode is supported, not 16540.
> > > > Break error is not passed through the FIFO!
> > > > Reciever will continue to recieve (0's) after a break is detected.
> > > >
> > > > > Can you tell me if I'm correct about the differences.
> > > > >
> > > > > In the meantime I'll start with the Verilog files.
> > > > >
> > > > > Regards,
> > > > > Igor
> > > >
> > > > regards
> > > > Carl
> > > >
> > > > --
> > > > To unsubscribe from cores mailing list please visit
> > > http://www.opencores.org/mailinglists.shtml
> > >
> > > --
> > > To unsubscribe from cores mailing list please visit
> > http://www.opencores.org/mailinglists.shtml
> > >
> >
> > --
> > To unsubscribe from cores mailing list please visit
> http://www.opencores.org/mailinglists.shtml
>
> --
> To unsubscribe from cores mailing list please visit
http://www.opencores.org/mailinglists.shtml
>

--
To unsubscribe from cores mailing list please visit http://www.opencores.org/mailinglists.shtml