Forum Discussion
Altera_Forum
Honored Contributor
19 years agoRunning 'jtagconfig', from an EDS command shell should provide you with the necessary information. You should see output similar to the following:
1) USB-Blaster
020010DD EP1S10
Node 11104600
Node 0C006E00 The two "nodes" are (in my case) the jtag_uart in my design and the jtag debug core, which is used to communicate with the gdb server.... Here are a couple of pointers: 1. jtagd doesn't need to be started as a separate process. The act of starting any of the "clients" that use jtagd (i.e.: jtagconfig or gdb_server) should be enough. 2. Don't call the gdb-server-wrapped command, directly. - Though I don't think you're doing this, I wanted to be sure. Here's the sort of command sequence, that I've used successfully: 1. Start the gdb server: nios2-gdb-server --tcpport=2342 --tcppersist
2. Start the client: nios2-elf-gdb <your_program>.elf
3. From within the client's GDB console:
(gdb) target remote localhost:2342
Remote debugging using localhost:2342
(gdb) load
Loading section .exceptions, size 0x13c lma 0x4000020
Loading section .text, size 0x277bc lma 0x1000000
Loading section .rodata, size 0x39b8 lma 0x10277bc
Loading section .rwdata, size 0x1f50 lma 0x102b174
Start address 0x1000000, load size 184832
Transfer rate: 739328 bits/sec, 510 bytes/write. From this point, you should be able to start, step and debug your code. In other words, it's standard GDB stuff....once you have the conduit setup. Cheers, - slacker