- September 1, 2017 at 1:58 pm #56522September 4, 2017 at 9:39 am #56528
Yes this is possible. I have a BusBlaster plugged into my computer an a colleague has been using it from his computer.
The same Codescape Console discoverprobes() command should find the probe if it is on the same subnet and may work over a LAN, depending on the LAN switches/routers in use.September 4, 2017 at 11:11 am #56531
I have downloaded Openocd 0.10.0.3 from Imagination website and have a license for Codescape Debugger GUI version 8.5.6. Can you please confirm if this is the correct way of setting up Openocd and Codescape?
1) Run Openocd on PC where the Busblaster is connect via USB
openocd -f mips_busblaster.cfg
2) Run DAConfig GUI on another PC and add DA-net target. Both PCs are on same subnet. DA-net fails to find Busblaster. It then asks for specific IP address. I added the IP address of PC on which Openocd is running but it still fails to find Busblaster.
Does it require a specific port number? I think Openocd open port 4444 by default.
KaushalSeptember 4, 2017 at 11:51 am #56532
Adding DA-net via DAConfig will not connect to the Busblaster; that will only work for connection to a DA-net probe.
There are instructions for using OpenOCD here
If you want to connect to your busblaster from Codescape Debugger, start CD, right-click on the ‘Targets’ pane and select the ‘Busblaster’ icon. Any busblasters on your LAN should be listed on a drop-down list.September 4, 2017 at 1:19 pm #56534
I have tried steps mentioned in the startup guide but Codescape and unable to detect BusBlaster. As I mentioned, Busblaster is on the same subnet as Codescape PC.
Is there a way I can manually give the IP address and port number in Codescape?
KaushalSeptember 4, 2017 at 1:28 pm #56535
Have you tried the ‘Add target’ option from Codescape debugger?September 4, 2017 at 2:06 pm #56537
I have tried Add target option. But BusBlaster does not show up over the network. Hence I was asking if there any way to manually set IP address and port. Or if you can tell me the default port it searches, I can start Openocd with that port.
KaushalSeptember 4, 2017 at 2:11 pm #56538
Are you running on Windows or Linux and are the drivers for the busblaster installed?September 5, 2017 at 11:33 am #56539
I am running Openocd on Linux. The drivers are installed and I can debug using Openocd commands in Linux. So I don’t see any issue with the hardware. I can even do telnet to Openocd from remote PC and debug.
Can you tell me how exactly Codescape discovers Busblaster over the network so that I can check if there are any network issues. As I said, I am able to connect to Openocd remotely over network.
KaushalSeptember 5, 2017 at 12:01 pm #56540
Sorry I was mistaken – the ‘busblaster’ icon in ‘Add Target’ will only list busblasters directly connected to your computer.
Try the ‘Nearby’ option on the Add target dialog. That option should list all probes (including busblasters) on your LAN. Select the busblaster from the list to connect.September 5, 2017 at 2:15 pm #56541
Can you please confirm Openocd configuration file(s) to be used for setting up Openocd + Codescape over network? Currently, I am invoking Openocd using
openocd -f mips_busblaster.cfg
Are there any extra configuration file(s) and command line options to be used?
KaushalSeptember 5, 2017 at 2:17 pm #56542
Further to my previous e-mail, using mips_busblaster.cfg file, I am able to detect the Busblaster probe and Openocd is able to get ID codes from the JTAG chain.
KaushalSeptember 5, 2017 at 4:34 pm #56544
I’ve reviewed this with my colleagues and I’m afraid I was wrong in stating that it was possible to connect to a busblaster over a LAN with Codescape Debugger.
Codescape Debugger can only connect to a busblaster if it is on the same computer, connected to the computer by USB cable.September 6, 2017 at 8:20 am #56551
Is this true for Codescape console as well? Because in the first reply you had mentioned Codescape console can discover Busblaster over network using discoverprobe() call.