|
Message
From: Xiang Li<olivercamel@g...>
Date: Sun Mar 30 21:43:33 CEST 2008
Subject: [openrisc] How do you debug or1200?
Hi all,I am a beginner of the or1200 processor, very glad to join the openrisc
world.
I've made an or1200 cpu running on altera's FPGA successfully by using a
prebuild toolchain in cygwin (altera's tools work better in windows
environment). Since I converted the binary file into altera's mif formate
and initialized on-chip ram with it directly, there was no debugging at all.
Now I am trying to find a solution of debugging to make code developing
easier. But unfortunately with my little knowledge of Linux and Xilinx, I
don't know what do I need to do to introduce the debugging utility (it seems
i need to study lots of new things ...). So can someone give me a hand
to show me a "block diagram" of how to debug or1200? so that I can
start studying on a correct way.
According to my understanding, the diagram should be:
source code -> GCC/binutiles -> GDB with JP1 protocol -> a xilinx parallel
cable -> a JTAG TAP core and a debug interface core by Igor -> or1200 cpu.
But I am not sure if i understood correctly? and is this the most popular
way of debugging that everybody is using?
Besides, I have several more questions:
1. Is there anyone successfully debugging their program in windows
environment (i.e. cygwin)?
2. Is there any other cable can be used except for Xilinx's Parallel Cable
III? such as xilinx usb cable? since most PCs have no parallel port now. Or,
3. Is there anybody debugging or1200 via a UART connection?
4. As far as I know, there should be a piece of code called "stub" that
combined with the software to response the GDB's commands. Is this
automatically generated by GCC?
Thanks for the help.
Best regards,
Li Xiang
3.30
-------------- next part --------------
An HTML attachment was scrubbed...
URL: attachment-0001.html
|
 |
Browse
