AW: [microblaze-uclinux] Xmdstub connect on serial port

["Schunke Jan-Hendrik" <Schunke@shf-communication.de>]

Hi John,

Your bitstream does not work either :-(

I have a revision 1 board. What board do you have? I know that the added quite a lot decoupling capacitors to rev 3.

When I run loopback I get

Com1:
Hello from debug UART
Hello again from debug UART
^w~~

Com2
Hello from console UART
Hello again from console UART
^w~~

Having typed Hello on the Terminals so there might be a problem. 

Also when I use dip sw 1 to reset the messages should be reprinted on the terminal, right?
That does not seems to work well. Only once in 10 tries, I would say. 

Why do not you use a pushbutton, for example the reset button. That is connected to an external reset generator that makes sure that you do not get any debounce problems. 

Also I would suggest that we put the reset signals of the dcm's onto an external pushbotton and the locked signal to a user led. That makes debugging hardware a little bit easier. I will do this for my design and send you the chandes as soon as I have time.

Thanks for your reply

Jan


> -----Ursprüngliche Nachricht-----
> Von: John Williams [mailto:jwilliams@itee.uq.edu.au] 
> Gesendet: Donnerstag, 24. Juli 2003 11:00
> An: microblaze-uclinux@itee.uq.edu.au
> Betreff: Re: [microblaze-uclinux] Xmdstub connect on serial port
> 
> 
> Hi Jan,
> 
> Schunke Jan-Hendrik wrote:
> > I am using the latest mb_vanilla_ddr on Insight V2MB1000 with P160 
> > Communication (This should be Johns setup). Two things:
> > 
> > 1) Some of the Gpio signals and the sram_addr signals are 
> not locked 
> > down. This should be changed because there is the possibility to 
> > damage your hardware. My suggestion is to put them on the LVDS 
> > transmit ports.
> 
> I agree - I periodically remember and then forget this fact.  I wish 
> there was a synthesis option to remove un-constrained signals, but 
> anyway.  Apparently there's an EDK component somewhere called 
> bus_splitter or similar, that can be used for this purpose, but I 
> haven't looked into it.
> 
> In the meantime if you have an safer UCF file please send it 
> to me and 
> I'll update the download.
> 
> > 2) I am having a hard time to get the connection to the 
> xmdstub. When 
> > compiling in xmdstub mode I cannot connect to the xmdstub after 
> > downloading the bitstream (I did update the bistream).
> 
> A common cause of this is to have the reset held high - in 
> mbvanilla_ddr 
> it's routed to DIP switch 1, which should be in the "up" 
> position. But 
> since you got the loopback running that's probably not the cause.
> 
> Can you try this bitstream and let me know if it works?  I've 
> been using 
> it on my board with no problems.   Also what rev of the insight board 
> are you using, 1 or 3 (no revision 2 as far as I know)?
> 
http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux/Downloads/_files/download.bit

> When I run in executable mode and use the loopback.c source then I can 
> see the messages printed to teminals on COM1 and COM2 (I use Tera 
> Term).

In loopback if you type characters on either terminal do they get echoed 
back to the screen?

Regards,

John

___________________________
microblaze-uclinux mailing list microblaze-uclinux@itee.uq.edu.au Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/



___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/