openrisc, jp1 jtag debug utility

i've worked thru all of the openrisc HW and SW steps. everything went well, or at leas seemed to. however, when i startup the jp1 utility, it connects to my board (xupv2) but the "Read" and "Expected" numbers to do match at all. the HW doc says if this happens to "check the onchip-ram module", but doesnt give any more details. i'm looking for some hints...

thanks

jeff

# ./jp1 xpc3 9999 Connected to parallel port at 378 Dropping root privileges. Read npc = 00000100 ppc = 00000104 r1 = 00000000 Expected npc = 4000000c ppc = 40000024 r1 = 00000005 Read npc = 00000100 ppc = 00000104 r1 = 00000000 Expected npc = 4000000c ppc = 40000024 r1 = 00000008 Read npc = 00000100 ppc = 00000104 r1 = 00000000 Expected npc = 40000024 ppc = 40000020 r1 = 0000000b Read npc = 00000100 ppc = 00000104 r1 = 00000000 Expected npc = 40000020 ppc = 4000001c r1 = 00000018 Read npc = 00000100 ppc = 00000104 r1 = 00000000 Expected npc = 4000001c ppc = 40000018 r1 = 00000031 Read npc = 00000100 ppc = 00000104 r1 = 00000000 Expected npc = 40000020 ppc = 4000001c r1 = 00000032 Read npc = 00000100 ppc = 00000104 r1 = 00000000 Expected npc = 40000010 ppc = 4000000c r1 = 00000063 Read npc = 00000100 ppc = 00000104 r1 = 00000000 Expected npc = 40000024 ppc = 40000020 r1 = 00000065 Read npc = 00000100 ppc = 00000104 r1 = 00000000 Expected npc = 4000000c ppc = 40000024 r1 = 000000c9 result = 5eadeccd Dropping root privileges. JTAG Proxy server started on port 9999 Press CTRL+c to exit.

Reply to
jeff murphy
Loading thread data ...

If you are using new debug interface you must use jp2 instead of jp1

Javier Castillo

formatting link

Reply to
Javier Castillo

i tried jp2. it doesnt connect at all. more hints welcome!

# ./jp2 xpc3 9999 Connected to parallel port at 378 Dropping root privileges. JTAG ID = f77db57b Stall 8051 RETRY RETRY RETRY RETRY JTAG ID = f77db57b RETRY JTAG ID = f77db57b RETRY JTAG ID = f77db57b RETRY JTAG ID = f77db57b

Reply to
jeff murphy

Edit jp2 file and inside the main() delete the call to dbg_test function

Regards

Javier Castillo

Reply to
Javier Castillo

still no joy.

gdb reports:

status -1 ffffffff An error was reported by the proxy server. The command was: "JTAG_COMMAND_READ",3220120016,0x00000004 The command returned -1.

since i'm working with a virtex2p, i didnt do the CLKDLL part of the instructions. the build tools report an expected clock speed of 75 Mhz. how critical is the CLKDLL step? at what clock speeds is it necessary to employ a clock divider?

i've followed all of the other steps, twice in fact from scratch, with the same results both times. i'd very much like to get openrisc running on this board...

Reply to
jeff murphy

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.