|
Message
From: Luke Darnell<luke.darnell@g...>
Date: Tue Dec 21 05:23:09 CET 2004
Subject: [openrisc] JP2 seems to work fine; Still problem with GDB/Hello
World
Hi all,We now have a working gdb/jtag debugging system. The problem was that our or1200 implementation is different to the one in the CVS. We changed JP2 and were able to get it working. So if you change the or1200 to much, you might have to change JP2 to suit.
Thanks Igor and everyone else for the help.
regards, Luke
>Our system is working fine without any problems. It consists of two >CPUs (OR1200 and 8051) and debugger for both works excellent. No >problems at all. > >Perhaps you screwed up with the "hack". > >First you need to be sure that you can read out the ID. That means >that the JTAG connection is OK. >Then try to change value of some registers. All the data is protected >with the 32-bit CRC. If the CRC is OK, that means that the >communication is OK. This still has nothing to do with the CPU >debugging. Now if you have connected the CPU correctly, you should be >able to debug it. Perhaps you want to add some test register to the >CPU (to see if everything is OK on the CPU side). If your CPU is >running at low frequency, follow the "working with the slow CPU (or >something like this) in the documentation. > >And of course, take the latest version of the OR1200... > >I hope this is enough for a start. > >Regards, > Igor > > >On Tue, 14 Dec 2004 17:04:08 +1000, Luke Darnell ><luke.darnell@g...> wrote: > > >>Hi all, >> >>JP2 gave us similiar results to the ones you describe. >>We couldn't get JP2 going so we decided it might be easier to write our >>own interface, >>by altering JP2 to suit. >>Apparently JP2 already has some nice debug options (printing Jtag info >>with pretty colours etc) >>We are looking to get more info from our hardware so we can determine >>exactly what bits/bytes the jtag is spitting out, >>and hence where our problem is. >>More of a lower-level debugger. >>I will report back when we have something useful. >> >>I should mention that the or1200 we are using has been hacked up a bit. >> >>regards, >>Luke >> >> >> >> >>
|
 |