Hello,

I am trying to run minsoc on the S3e starter board. I get the following errors when I am trying to upload the software.

Not able to connect to gdb.

On the window where I start the adv debug bridge:

Devices on JTAG chain:
Index Name ID Code IR Length
----------------------------------------------------------------
0: (unknown) 0x06E5E093 -1
1: (unknown) 0xF5046093 -1
2: XC3S500E_FG320 0x41C22093 6

Target device 2, JTAG ID = 0x41c22093
Warning: overriding autoprobe debug command (0x2) with command line value (0x2)
IDCODE sanity test passed, chain OK!
No watchpoint hardware found, HWP server not starting
HWP server listening on host pganti-VirtualBox (0.0.0.0), port 9928, address family IPv4
JTAG bridge ready!
HWP server thread running!
Warning: Unknown HWP request qSupported:qRelocInsn+
Warning: Unknown HWP request Hg0
Warning: Unknown HWP request Hc-1
Warning: Unknown HWP request qC
Warning: Unknown HWP request qAttached
Warning: Unknown HWP request qOffsets


On the window where I start gdb:

pganti@pganti-VirtualBox:~/minsoc/sw/uart$ or32-elf-gdb uart-nocache.or32Building automata... done, num uncovered: 0/216.
Parsing operands data... done.
GNU gdb (OpenRISC 32-bit toolchain for or32-elf (built 20110410)) 7.2-or32-1.0rc3
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later " target="_blank">http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=or32-elf".
For bug reporting instructions, please see:
..." target="_blank">http://www.opencores.org/>...
Reading symbols from /home/pganti/minsoc/sw/uart/uart-nocache.or32...done.
(gdb) target remote:9928
:9928: Connection timed out.
(gdb) set remotetimeout 10
(gdb) target remote:9928
:9928: Connection timed out.
(gdb) target remote:9928
:9928: Connection timed out.
(gdb) target remote:9928
Remote debugging using :9928
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Malformed response to offset query, timeout
(gdb)

Can you please help me with this?

9928 is the wrong port for GDB. Use 9999 instead, that's the RSP server for GDB. Port 9928 is the HWP server that the AdvancedWatchpointControl program to attach to.

I have used port 9999 instead of 9928 , I get the same errors.

Found Xilinx Platform Cable USB (DLC9)
Found Xilinx Platform Cable USB (DLC9)
firmware version = 0x0405 (1029)
cable CPLD version = 0x0012 (18)
Enumerating JTAG chain...

Devices on JTAG chain:
Index Name ID Code IR Length
----------------------------------------------------------------
0: (unknown) 0x06E5E093 -1
1: (unknown) 0xF5046093 -1
2: XC3S500E_FG320 0x41C22093 6

Target device 2, JTAG ID = 0x41c22093
Warning: overriding autoprobe debug command (0x2) with command line value (0x2)
IDCODE sanity test passed, chain OK!
No watchpoint hardware found, HWP server not starting
HWP server listening on host pganti-VirtualBox (0.0.0.0), port 9928, address family IPv4
JTAG bridge ready!
HWP server thread running!


pganti@pganti-VirtualBox:~$ cd minsoc/sw/uartpganti@pganti-VirtualBox:~/minsoc/sw/uart$ or32-elf-gdb uart-nocache.or32Building automata... done, num uncovered: 0/216.
Parsing operands data... done.
GNU gdb (OpenRISC 32-bit toolchain for or32-elf (built 20110410)) 7.2-or32-1.0rc3
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later " target="_blank">http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=or32-elf".
For bug reporting instructions, please see:
..." target="_blank">http://www.opencores.org/>...
Reading symbols from /home/pganti/minsoc/sw/uart/uart-nocache.or32...done.
(gdb) target remote : 9999
Remote debugging using : 9999
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Malformed response to offset query, timeout
(gdb) load
You can't do that when your target is `exec'
(gdb) load
You can't do that when your target is `exec'
(gdb)

I think it's a problem with the inputs to GDB, since it thinks the target is 'exec,' it should be 'remote' (I think, I'm not a GDB guru). Don't put a space between the colon and the port number in

"target remote :9999"

I get the same error if I don't include the space.
Actually I get the same errors even when I try simulating the design.

Remote debugging using :9999
Malformed packet(a) (missing colon): t=0;Data=0;Bss=0
Packet: 'Text=0;Data=0;Bss=0'

Can you help me with this?

So, first great job raul and all team of minsoc for this new script and install makefile

i just download again minsoc and try to compile for spartan-3E500, and i have the same problem and others problem (that raul has fixed now) and like you can see i use also xilinx cable DLC10

to start, to fix this new problem please flow this steps:

1- download minsoc svn co http;//opencores.org/ocsvn/minsoc/minsoc/trunk minsoc

2- you can see in rtl/verilog there all IP you need to build SOC (or1200, uart.....)

3- delete or1200 IP from orsoc project and download again or1200 alone (in the same place minsoc/rtl/verlog/) svn co http;//opencores.org/ocsvn/openrisc/openrisc/trunk/orpsocv2/rtl/verilog/or1200 or1200

4-you can see in or1200 there is no or1200_define.v, so downlod him also from orpsoc project svn co http;//opencores.org/openrisc/openrisc/trunk/orsocv2/boards/xilinx/ml501/rtl/verilog/include include

5- copy or1200_define.v from include to backend/spartan3e_starter_kit/

6- configure adv_define.v also (disable jsp)

7- go to backen/spartan3e_starter_kit

8- configure or1200_define.v for s3esk (you can found instruction in howto form minsoc stable version in tag branch)

9- do "./configure"

10- go to syn/ and do make all

11-compile adv software

12-after downloading bitstrem => ./adv_jtag_bridge -x2 xpc_usb

13-i have use gdb7.2 to uplaod uart.or32

14-felicitation you can see "hello world" in mincom

finally like you can see minsoc project is now work with or1200v3 without problem (except CPU test)

i will try to put all this instruction in a nice doc and update for ethrernet and SPI.

hope that will work with you also

i forget if if if that also not working, you can build project using ISE graphics wiyhout using makefiles but flowing the same steps from 1 to 8 (i did and it work also)

Thinking back, I'm not sure I ever got GDB 7.2 to work, actually...have you tried GDB 6.8? That's what I use.

Also, I don't think that you can use the OR1200v3 without any problems...the bug that stops the CPU test is still there, and you can trigger it during the normal course of debugging. I always do, which is why I still use the OR1200v1.

for GDB7.2 it work fine, i have tested yesterday

for gdb6.8 and or1200v1 this is the stable version for minsoc, and when you want to pass to or1200v3 you must have problem with adv_debug_system and that adv need update

i mention also that you can upload you application from gdb7.2 to or1200v3 now without problem but not debugging this is still problem ans test CPU still failed.

now there is new minsoc structure for compilation and many bug has been fixed but i haven't tested yet (i don't think makefiles is the problem but or1200 version and the most updated)

there is another thing, i specified about or1200v3 that is from orpsocv2 project and not form or1200v3 trunk branch that still have problem with s3esk (ORSOC has been ported in Spartan-3E500 using or1200v3 and working)

For the record, all changes to or1200 made in the orpsoc version have now been
fed back into the trunk version of or1200.
So those should be in harmony and equivalent.

I am a little confused here. So should I use the trunk version of Minsoc without replacing the or1200 and is working fine???

Or should I use the or1200 from orpsocv2??? I am having problems synthesizing the code when I use or1200 from orpsocv2.

And which version of gdb should I use??? I am currently using gdb 7.2.

Pganti,

you should use the minsoc's stable version and follow the wiki.

Minsoc uses a patched gdb-6.8 for now:
- http://minsoc.wikaba.com/gdb_install

Regards,
Raul