gdb: wishbone-tool default port is 1234

[pdp7]

wishbone-tool server defaults to 1234:
https://github.com/litex-hub/wishbone-utils/blob/master/wishbone-tool/src/main.rs#L232

pdp7@x1:~/dev/fpga/fomu-workshop/riscv-blink$ wishbone-tool -s gdb
INFO [wishbone_tool::bridge::usb] opened USB device device 044 on bus 001
INFO [wishbone_tool::server] accepting connections on 127.0.0.1:1234

pdp7@x1:~/dev/fpga/fomu-workshop/riscv-blink$ which wishbone-tool
/home/pdp7/dev/fpga/ecp5-toolchain/ecp5-toolchain-linux_x86_64-v1.6.9/bin//wishbone-tool
pdp7@x1:~/dev/fpga/fomu-workshop/riscv-blink$ wishbone-tool --help
Wishbone Tool 0.4.7
Sean Cross <[email protected]>

[xobs]

The gdb server used to default to port 1234. Actually, all ports were 1234. However, as it is now possible to run both a gdb server and a wishbone server, gdb now defaults to the more common 3333:

https://github.com/litex-hub/wishbone-utils/blob/master/wishbone-tool/src/main.rs#L171-L179

https://github.com/litex-hub/wishbone-utils/blob/master/wishbone-tool/src/main.rs#L253-L259

As of about ten days ago, the newer wishbone-tool is now included in the latest fomu-toolchain.

Incidentally, to get both a gdb and a wishbone server running, run wishbone-tool -s gdb -s wishbone.

[shenki]

The gdb server used to default to port 1234. Actually, all ports were 1234. However, as it is now possible to run both a gdb server and a wishbone server, gdb now defaults to the more common 3333:

I was surprised when it ran at 3333. My shell history has 1234 from Qemu's gdb server. 3333 is familiar for openocd users I guess?

[xobs]

Interesting. This might be a better question for the wishbone-tool repository, but what port would you expect it to run on? Keeping in mind that 1234 is what litex already uses as the Etherbone port and so is no longer available.

[shenki]

Yeah if etherbone uses that then we do need to pick something else. 3333 is easy to remember.

I don't think it's a big deal - as long as our documentation matches the defaults, then we're set.