CCS: No connection to bhs560v2u after installation

AJ,

Did you install CCS as a superuser or as a regular user?

Since you mentioned you ran the install_drivers.sh as sudo, sometimes the udev rules are not updated until the host is restarted. Can you do this and see if the pod is acknowledged?

If not, perhaps something went wrong with the install script. The udev rules directory should have a file named 71-bh-permissions.rules with the following contents

terminal said:

user@host:~$ ls /etc/udev/rules.d/
61-msp430uif.rules 71-bh-permissions.rules 71-ti-permissions.rules
70-mm-no-ti-emulators.rules 71-sd-permissions.rules 99-jlink.rules
user@host:~$ cat /etc/udev/rules.d/71-bh-permissions.rules
# Blackhawk Rules Definitions
# 23 MAY 2012
#

# Blackhawk XDS510 USB Devices
# Models:
# USB2000
# USB510L
# USB510W
#
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0b1e",ATTRS{idProduct}=="8008",MODE:="0666"

# Blackhawk XDS560v1 USB Devices
# Models:
# USB560
# USB560-M
# USB560-BP
#
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0b1e",ATTRS{idProduct}=="8007",MODE:="0666"

# Blackhawk XDS560v2 USB devices
# Models:
# USB560v2
# XDS560v2
# XDS560v2-BP
# XDS560v2 Mezzanine
#
SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0b1e",ATTRS{idProduct}=="0009",MODE:="0666"

If that file is not present, you can try to create it using the information above. However, keep in mind that something else may have happened during install as the file should be at that location.

With or without the file, you can try to run the utility as superuser and see if it works. That will be helpful to validate if the USB ports and the host are properly working with this pod. 

Hope this helps,

Rafael

desouza,

Thank you for responding.

This file was generated properly during the install and I cant detect the BlackHawk after restarting my computer...

In regards to installing the drivers as superuser, I just followed the readme instructions in the tarball.

Regards,
AJ

My blackhawk is also in normal mode (based on the LEDs) and I can see that

SUBSYSTEM=="usb",ENV{DEVTYPE}=="usb_device",ATTRS{idVendor}=="0b1e",ATTRS{idProduct}=="0009",MODE:="0666"

Matches:

Bus 001 Device 012: ID 0b1e:0009 Electronic Warfare Assoc., Inc. (EWA) from lsusb

Running "sudo ./Bh560v2Config_start.sh" vs "./Bh560v2Config_start.sh "doesnt make any difference. It still doesnt find the device.

Is there a procedure to using LAN? 

AJ,

It is certainly strange that your pod cannot be seen by the utility, especially because it works on the other host. I am starting to suspect of a cable fault (I have been bitten by that in the past) or something on the OS itself that is rendering the pod unusable - maybe some sort of incompatible component, but it is difficult to pinpoint.

For LAN you can scan your network by selecting "Search LAN" on the top of the Bh560v2Config utility. It should find the probe without problems.

If it doesn't, from a terminal simply issue an arp -a and look for a MAC address that starts with 00:0F:D2 (as shown in the screenshot above). After that, click on the "Add" button and simply input the corresponding IP address. 

Additional details about the utility are shown in its manual.

Hope this helps,

Rafael