Forum Discussion
Altera_Forum
Honored Contributor
19 years agoFirstly, thanks for the help.
(I swear I replied to this posting this morning, but my posting seems to have gone missing.) --- Quote Start --- originally posted by slacker@Oct 29 2006, 01:48 AM running '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 --- Quote End --- When I run jtagconfig connected to the Cyclone-II board: # ./jtagconfig
1) USB-Blaster
020B40DDAnd when I run gdb-server: # ./nios2-gdb-server --tcpport 4321
There are no Nios II CPUs with debug modules available which match the values
specified. Please check that your PLD is correctly configured, downloading a
new SOF file if necessary. When connected to my real target board: # ./jtagconfig
1) USB-Blaster
020B30DD !
020A10DD !
Captured DR after reset = (020B30DD020A10DD)
Captured IR after reset = (55555) I expect two nodes, since that board has both the NIOS2 debug unit and the jtag uart. When I run the gdb-server connected to my ral target, I get the same result as with the Cyclone-II. <div class='quotetop'>QUOTE </div> --- Quote Start --- 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.[/b] --- Quote End --- Doh. I should have known that. <div class='quotetop'>QUOTE </div> --- Quote Start --- 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.[/b] --- Quote End --- Yup, that's all I want is a working gdb-server. I can handle it from there.