[casper] Python katcp cannot connect FPGA

[Haoxuan Zheng]

Hi CASPER,
Sorry for the spam, but since my original message was sent at the worst hour of 
the week (Friday evening), I would like to give it another try:

Our lab just got a new server which will be our data taking computer, and it 
has trouble connecting to our ROACH 2 through python katcp. Whenever I do fpga 
= corr.katcp_wrapper.FpgaClient('10.0.0.200', 7147, timeout = 60), 
fpga.is_connected() always say False. Here are some clues:

1) When I run the above command, I see the following on a separate telnet 7147 
connection on the ROACH2 (which runs fine), and the client-disconnected message 
comes right after the client-connected message:

#log info 946685931331 raw new\_client\_connection\_10.0.0.11:44001
#client-connected 10.0.0.11:44001
#client-disconnected 10.0.0.11:44001

2) The new computer connects to the ROACH1s fine with python katcp.

3) All other computers connect to the ROACH2s fine with python katcp.

I'm not sure if anyone else has experienced similar issues? Any help would be 
greatly appreciated!

Thanks a lot!
Jeff

Re: [casper] Python katcp cannot connect FPGA

[David MacMahon]

Hi, Jeff,

That sounds like a weird one!  Here are some ideas to try:

1) Check the output of "dmesg" on the roach2 after the problem occurs.

2) Watch the network traffic between the problematic machine and the roach2 
using tcpdump or wireshark.

3) Verify that the problematic computer is using the same python katcp version 
as the working computers.

Please send a message to the list once you figure it out.  You'll likely make 
some CASPER mailing list archive reader very happy in the future! :-)

Hope this helps,
Dave

On May 20, 2013, at 9:01 AM, Haoxuan Zheng wrote:

> Hi CASPER,
> Sorry for the spam, but since my original message was sent at the worst hour 
> of the week (Friday evening), I would like to give it another try:
> 
> Our lab just got a new server which will be our data taking computer, and it 
> has trouble connecting to our ROACH 2 through python katcp. Whenever I do 
> fpga = corr.katcp_wrapper.FpgaClient('10.0.0.200', 7147, timeout = 60), 
> fpga.is_connected() always say False. Here are some clues:
> 
> 1) When I run the above command, I see the following on a separate telnet 
> 7147 connection on the ROACH2 (which runs fine), and the client-disconnected 
> message comes right after the client-connected message:
> 
> #log info 946685931331 raw new\_client\_connection\_10.0.0.11:44001
> #client-connected 10.0.0.11:44001
> #client-disconnected 10.0.0.11:44001
> 
> 2) The new computer connects to the ROACH1s fine with python katcp.
> 
> 3) All other computers connect to the ROACH2s fine with python katcp.
> 
> I'm not sure if anyone else has experienced similar issues? Any help would be 
> greatly appreciated!
> 
> Thanks a lot!
> Jeff

Re: [casper] Fwd:connecting with .py this is register cnt_rst not found

[Laura Vertatschitsch]

Hey Katty,

This error is telling you that there is no register in your model with name
cnt_rst.  There still may be a register that serves the same purpose, but
simply goes by different spelling.

If you produced this bof file from a Simulink model, you can look in the
model to find the correct register.

Alternatively, you can log into your roach and run your .bof file as an
executable.  When you see the process id, you can actually navigate to a
folder that will list all the registers (
https://casper.berkeley.edu/wiki/Roach_Tutorial will show you).  Perhaps
the register name in the .bof file differs from the python code slightly.
 You may be able to infer the appropriate register from this list and
change the spelling in your python code.

Good luck!

--Laura



On Mon, May 20, 2013 at 9:47 AM, katherine viviana cortes urbina <
kattycort...@gmail.com> wrote:

> Hi all,
>
> I am sorry but still I can not solve the error
> -- Forwarded message --
> From: katherine viviana cortes urbina 
> Date: 2013/5/7
> Subject: Fwd: .py
> To: Casper Lists 
>
>
>
> Hi all,
>
> I synthesized a Design this is spectrometer with 2048 channel, 1 GHz in
> clock ADC, mode Interleaved. But if I connected to the ROACH by
> tut3_interleave_4096.py I have the error in the register cnt_rst this is
> not found.
>
> error :
> ./tut3_interleave_4096.py 192.168.100.2 -b s1_2013_May_02_1157.bof
>
> 
> Connecting to server 192.168.100.2 on port 7147...  ok
>
> 
> Programming FPGA with s1_2013_May_02_1157.bof... done
> Configuring accumulation period... done
> Resetting counters... FAILURE DETECTED. Log entries:
> 192.168.100.2: Starting thread Thread-1
> 192.168.100.2: #version poco-0.1
> 192.168.100.2: #build-state poco-0.2804
> 192.168.100.2: ?progdev s1_2013_May_02_1157.bof
>
> 192.168.100.2: !progdev ok 512
> 192.168.100.2: Programming FPGA with s1_2013_May_02_1157.bof... ok.
> 192.168.100.2: ?write acc_len 0 \0 \0\0
>
> 192.168.100.2: !write ok
> 192.168.100.2: ?read acc_len 0 4
>
> 192.168.100.2: !read ok \0 \0\0
> 192.168.100.2: Write4 to register acc_len at offset 0 ok.
> 192.168.100.2: ?write cnt_rst 0 \0\0\0
>
> 192.168.100.2: #log error 371725520384 poco register\_cnt_rst\_not\_found
> 192.168.100.2: 371725520384 poco: register cnt_rst not found
> 192.168.100.2: !write fail register
> 192.168.100.2: Request write failed.
>   Request: ?write cnt_rst 0 \0\0\0
>   Reply: !write fail register.
> None
> Traceback (most recent call last):
>   File "./tut3_interleave_4096.py", line 155, in 
> exit_fail()
>   File "./tut3_interleave_4096.py", line 132, in 
>
> fpga.write_int('cnt_rst',1)
>   File "/usr/local/lib/python2.6/site-packages/corr/katcp_wrapper.py",
> line 411, in write_int
> self.write(device_name, data, offset*4)
>   File "/usr/local/lib/python2.6/site-packages/corr/katcp_wrapper.py",
> line 351, in write
> self.blindwrite(device_name, data, offset)
>   File "/usr/local/lib/python2.6/site-packages/corr/katcp_wrapper.py",
> line 375, in blindwrite
> self._request("write", device_name, str(offset), data)
>   File "/usr/local/lib/python2.6/site-packages/corr/katcp_wrapper.py",
> line 67, in _request
> % (request.name, request, reply))
> RuntimeError: Request write failed.
>   Request: ?write cnt_rst 0 \0\0\0
>   Reply: !write fail register.
>
> any idea?
>
> Cheers katty
>
>

Re: [casper] Fwd:connecting with .py this is register cnt_rst not found

[Jack Hickish]

Hey Katty, Laura



> If you produced this bof file from a Simulink model, you can look in the
> model to find the correct register.
>
> Alternatively, you can log into your roach and run your .bof file as an
> executable.  When you see the process id, you can actually navigate to a
> folder that will list all the registers (
> https://casper.berkeley.edu/wiki/Roach_Tutorial will show you).  Perhaps
> the register name in the .bof file differs from the python code slightly.
>  You may be able to infer the appropriate register from this list and
> change the spelling in your python code.
>
>
As well as logging into the ROACH and looking at the register directory,
you can also use the listdev() katcp command, which will return a list of
all the software registers in your firmware. This is probably a few seconds
quicker and easier than the ssh-to-roach route.

Cheers,
Jack




>
> On Mon, May 20, 2013 at 9:47 AM, katherine viviana cortes urbina <
> kattycort...@gmail.com> wrote:
>
>> Hi all,
>>
>> I am sorry but still I can not solve the error
>> -- Forwarded message --
>> From: katherine viviana cortes urbina 
>> Date: 2013/5/7
>> Subject: Fwd: .py
>> To: Casper Lists 
>>
>>
>>
>> Hi all,
>>
>> I synthesized a Design this is spectrometer with 2048 channel, 1 GHz in
>> clock ADC, mode Interleaved. But if I connected to the ROACH by
>> tut3_interleave_4096.py I have the error in the register cnt_rst this is
>> not found.
>>
>> error :
>> ./tut3_interleave_4096.py 192.168.100.2 -b s1_2013_May_02_1157.bof
>>
>> 
>> Connecting to server 192.168.100.2 on port 7147...  ok
>>
>> 
>> Programming FPGA with s1_2013_May_02_1157.bof... done
>> Configuring accumulation period... done
>> Resetting counters... FAILURE DETECTED. Log entries:
>> 192.168.100.2: Starting thread Thread-1
>> 192.168.100.2: #version poco-0.1
>> 192.168.100.2: #build-state poco-0.2804
>> 192.168.100.2: ?progdev s1_2013_May_02_1157.bof
>>
>> 192.168.100.2: !progdev ok 512
>> 192.168.100.2: Programming FPGA with s1_2013_May_02_1157.bof... ok.
>> 192.168.100.2: ?write acc_len 0 \0 \0\0
>>
>> 192.168.100.2: !write ok
>> 192.168.100.2: ?read acc_len 0 4
>>
>> 192.168.100.2: !read ok \0 \0\0
>> 192.168.100.2: Write4 to register acc_len at offset 0 ok.
>> 192.168.100.2: ?write cnt_rst 0 \0\0\0
>>
>> 192.168.100.2: #log error 371725520384 poco register\_cnt_rst\_not\_found
>> 192.168.100.2: 371725520384 poco: register cnt_rst not found
>> 192.168.100.2: !write fail register
>> 192.168.100.2: Request write failed.
>>   Request: ?write cnt_rst 0 \0\0\0
>>   Reply: !write fail register.
>> None
>> Traceback (most recent call last):
>>   File "./tut3_interleave_4096.py", line 155, in 
>> exit_fail()
>>   File "./tut3_interleave_4096.py", line 132, in 
>>
>> fpga.write_int('cnt_rst',1)
>>   File "/usr/local/lib/python2.6/site-packages/corr/katcp_wrapper.py",
>> line 411, in write_int
>> self.write(device_name, data, offset*4)
>>   File "/usr/local/lib/python2.6/site-packages/corr/katcp_wrapper.py",
>> line 351, in write
>> self.blindwrite(device_name, data, offset)
>>   File "/usr/local/lib/python2.6/site-packages/corr/katcp_wrapper.py",
>> line 375, in blindwrite
>> self._request("write", device_name, str(offset), data)
>>   File "/usr/local/lib/python2.6/site-packages/corr/katcp_wrapper.py",
>> line 67, in _request
>> % (request.name, request, reply))
>> RuntimeError: Request write failed.
>>   Request: ?write cnt_rst 0 \0\0\0
>>   Reply: !write fail register.
>>
>> any idea?
>>
>> Cheers katty
>>
>>
>

Re: [casper] Fwd:connecting with .py this is register cnt_rst not found

[David MacMahon]

Hi, Katty,

As you discovered the hard way, the python script and bof file that you 
attached are not compatible with each other.  Where did you get this tutorial?

Thanks,
Dave

On May 20, 2013, at 9:47 AM, katherine viviana cortes urbina wrote:

> Hi all,
>  
> I am sorry but still I can not solve the error 
> -- Forwarded message --
> From: katherine viviana cortes urbina 
> Date: 2013/5/7
> Subject: Fwd: .py
> To: Casper Lists 
> 
> 
> 
> Hi all,
> 
> I synthesized a Design this is spectrometer with 2048 channel, 1 GHz in clock 
> ADC, mode Interleaved. But if I connected to the ROACH by 
> tut3_interleave_4096.py I have the error in the register cnt_rst this is not 
> found.
> 
> error : 
> ./tut3_interleave_4096.py 192.168.100.2 -b s1_2013_May_02_1157.bof
> Connecting to server 192.168.100.2 on port 7147...  ok
> 
> 
> Programming FPGA with s1_2013_May_02_1157.bof... done
> Configuring accumulation period... done
> Resetting counters... FAILURE DETECTED. Log entries:
> 192.168.100.2: Starting thread Thread-1
> 192.168.100.2: #version poco-0.1
> 192.168.100.2: #build-state poco-0.2804
> 192.168.100.2: ?progdev s1_2013_May_02_1157.bof
> 
> 192.168.100.2: !progdev ok 512
> 192.168.100.2: Programming FPGA with s1_2013_May_02_1157.bof... ok.
> 192.168.100.2: ?write acc_len 0 \0 \0\0
> 
> 192.168.100.2: !write ok
> 192.168.100.2: ?read acc_len 0 4
> 
> 192.168.100.2: !read ok \0 \0\0
> 192.168.100.2: Write4 to register acc_len at offset 0 ok.
> 192.168.100.2: ?write cnt_rst 0 \0\0\0 
> 
> 192.168.100.2: #log error 371725520384 poco register\_cnt_rst\_not\_found
> 192.168.100.2: 371725520384 poco: register cnt_rst not found
> 192.168.100.2: !write fail register
> 192.168.100.2: Request write failed.
>   Request: ?write cnt_rst 0 \0\0\0 
>   Reply: !write fail register.
> None
> Traceback (most recent call last):
>   File "./tut3_interleave_4096.py", line 155, in 
> exit_fail()
>   File "./tut3_interleave_4096.py", line 132, in 
> 
> fpga.write_int('cnt_rst',1) 
>   File "/usr/local/lib/python2.6/site-packages/corr/katcp_wrapper.py", line 
> 411, in write_int
> self.write(device_name, data, offset*4)
>   File "/usr/local/lib/python2.6/site-packages/corr/katcp_wrapper.py", line 
> 351, in write
> self.blindwrite(device_name, data, offset)
>   File "/usr/local/lib/python2.6/site-packages/corr/katcp_wrapper.py", line 
> 375, in blindwrite
> self._request("write", device_name, str(offset), data)
>   File "/usr/local/lib/python2.6/site-packages/corr/katcp_wrapper.py", line 
> 67, in _request
> % (request.name, request, reply))
> RuntimeError: Request write failed.
>   Request: ?write cnt_rst 0 \0\0\0 
>   Reply: !write fail register.
> 
> any idea?
> 
> Cheers katty
> 
> 

Re: [casper] ROACH2: Cannot communicate over USB

[David MacMahon]

Hi, Ryan,

Everything seems OK.  Were you root or a member of the dialout group when you 
tried connecting?  I use screen instead of minicom, so I can't offer any extra 
ideas regarding minicom itself.

FWIW, /dev/ttyUSB2 is the one that usually works for me.

Dave

On May 20, 2013, at 11:34 AM, Ryan Monroe wrote:

> Hey all, sorry for the spam :-(
> 
> I'm trying to communicate with my ROACH2 for initial configuration.  My 
> understanding is that we should set up a machine per this .  Then use 
> the USB port the same way we used serial for ROACH1... just over either 
> ttyUSB2 or ttyUSB3.
> 
> My problem is that I receive no communications from the ROACH through USB.  
> After configuring the settings in minicom (filename, flow control, init/reset 
> string), I can connect to the four USB virtual serial ports on the ROACH2, 
> but I receive no data upon starting it up.  Here's the test I ran:
> 
> 
> 
> 
> Start up computer.  Connect ROACH2 to power.  Do not start up ROACH2.
> 
> 
> Upon logging in, run "dmesg > tc_dmesg_preUSB.txt" (see file)
> run "ls /dev/ttyUSB*" (see results in "tc_lsOnUSB.txt")
> 
> Plug in the USB cable to both ends
> run "dmesg > tc_dmesg_postUSB.txt" (see file)
> run "ls /dev/ttyUSB*" (see results in "tc_lsOnUSB.txt")
> 
> 
> Run "sudo minicom -s TTYUSB2" and "sudo minicom -s TTYUSB3".  Take a 
> screenshot to display the state of the configurations 
> (tc_minicom_settings.jpg)
> 
> Run:
> "sudo minicom TTYUSB0"
> "sudo minicom TTYUSB1"
> "sudo minicom TTYUSB2"
> "sudo minicom TTYUSB3"
> 
> Take a screenshot (tc_before_powering_roach.jpg)
> Press the ROACH2 power button
> Wait several minutes
> Take a screenshot to show that we received nothing from the ROACH. 
> (tc_before_powering_roach.jpg ... it was the same result)
> 
> Unplug the USB cable
> Watch as the four minicom terminals fill with error messages 
> (tc_usb_removed.png)
> =
> 
> 
> So ladies and gents, any ideas?  Thanks in advance!
> -- 
> --Ryan Monroe
> 626.773.0805
> 
> 

Re: [casper] ROACH2: Cannot communicate over USB

[Ryan Monroe]

Hey David,

We noticed the dialout group thing, and have tested it with me being 
both root (via sudo minicom USBTTY2) and dialout.  Thanks!


--Ryan Monroe
626.773.0805

On 05/20/2013 11:46 AM, David MacMahon wrote:

Hi, Ryan,

Everything seems OK.  Were you root or a member of the dialout group when you 
tried connecting?  I use screen instead of minicom, so I can't offer any extra 
ideas regarding minicom itself.

FWIW, /dev/ttyUSB2 is the one that usually works for me.

Dave

On May 20, 2013, at 11:34 AM, Ryan Monroe wrote:


Hey all, sorry for the spam :-(

I'm trying to communicate with my ROACH2 for initial configuration.  My understanding 
is that we should set up a machine per this .  Then use the USB port the 
same way we used serial for ROACH1... just over either ttyUSB2 or ttyUSB3.

My problem is that I receive no communications from the ROACH through USB.  
After configuring the settings in minicom (filename, flow control, init/reset 
string), I can connect to the four USB virtual serial ports on the ROACH2, but 
I receive no data upon starting it up.  Here's the test I ran:




Start up computer.  Connect ROACH2 to power.  Do not start up ROACH2.


Upon logging in, run "dmesg > tc_dmesg_preUSB.txt" (see file)
run "ls /dev/ttyUSB*" (see results in "tc_lsOnUSB.txt")

Plug in the USB cable to both ends
run "dmesg > tc_dmesg_postUSB.txt" (see file)
run "ls /dev/ttyUSB*" (see results in "tc_lsOnUSB.txt")


Run "sudo minicom -s TTYUSB2" and "sudo minicom -s TTYUSB3".  Take a screenshot 
to display the state of the configurations (tc_minicom_settings.jpg)

Run:
"sudo minicom TTYUSB0"
"sudo minicom TTYUSB1"
"sudo minicom TTYUSB2"
"sudo minicom TTYUSB3"

Take a screenshot (tc_before_powering_roach.jpg)
Press the ROACH2 power button
Wait several minutes
Take a screenshot to show that we received nothing from the ROACH. 
(tc_before_powering_roach.jpg ... it was the same result)

Unplug the USB cable
Watch as the four minicom terminals fill with error messages 
(tc_usb_removed.png)
=


So ladies and gents, any ideas?  Thanks in advance!
--
--Ryan Monroe
626.773.0805

Re: [casper] ROACH2: Cannot communicate over USB

[David MacMahon]

Hi, Ryan,

Just for something else to try, this is the exact command that I use:

screen /dev/ttyUSB2 115200

When finished, I use "k" to close the screen session ( is the screen 
command character, which defaults to CTRL-A but I remap to CTRL-Z in my 
.screenrc file).

Have you tried a "known good" ROACH2 with this computer?

Dave

On May 20, 2013, at 11:48 AM, Ryan Monroe wrote:

> Hey David,
> 
> We noticed the dialout group thing, and have tested it with me being both 
> root (via sudo minicom USBTTY2) and dialout.  Thanks!
> 
> --Ryan Monroe
> 626.773.0805
> 
> On 05/20/2013 11:46 AM, David MacMahon wrote:
>> Hi, Ryan,
>> 
>> Everything seems OK.  Were you root or a member of the dialout group when 
>> you tried connecting?  I use screen instead of minicom, so I can't offer any 
>> extra ideas regarding minicom itself.
>> 
>> FWIW, /dev/ttyUSB2 is the one that usually works for me.
>> 
>> Dave
>> 
>> On May 20, 2013, at 11:34 AM, Ryan Monroe wrote:
>> 
>>> Hey all, sorry for the spam :-(
>>> 
>>> I'm trying to communicate with my ROACH2 for initial configuration.  My 
>>> understanding is that we should set up a machine per this .  Then use 
>>> the USB port the same way we used serial for ROACH1... just over either 
>>> ttyUSB2 or ttyUSB3.
>>> 
>>> My problem is that I receive no communications from the ROACH through USB.  
>>> After configuring the settings in minicom (filename, flow control, 
>>> init/reset string), I can connect to the four USB virtual serial ports on 
>>> the ROACH2, but I receive no data upon starting it up.  Here's the test I 
>>> ran:
>>> 
>>> 
>>> 
>>> 
>>> Start up computer.  Connect ROACH2 to power.  Do not start up ROACH2.
>>> 
>>> 
>>> Upon logging in, run "dmesg > tc_dmesg_preUSB.txt" (see file)
>>> run "ls /dev/ttyUSB*" (see results in "tc_lsOnUSB.txt")
>>> 
>>> Plug in the USB cable to both ends
>>> run "dmesg > tc_dmesg_postUSB.txt" (see file)
>>> run "ls /dev/ttyUSB*" (see results in "tc_lsOnUSB.txt")
>>> 
>>> 
>>> Run "sudo minicom -s TTYUSB2" and "sudo minicom -s TTYUSB3".  Take a 
>>> screenshot to display the state of the configurations 
>>> (tc_minicom_settings.jpg)
>>> 
>>> Run:
>>> "sudo minicom TTYUSB0"
>>> "sudo minicom TTYUSB1"
>>> "sudo minicom TTYUSB2"
>>> "sudo minicom TTYUSB3"
>>> 
>>> Take a screenshot (tc_before_powering_roach.jpg)
>>> Press the ROACH2 power button
>>> Wait several minutes
>>> Take a screenshot to show that we received nothing from the ROACH. 
>>> (tc_before_powering_roach.jpg ... it was the same result)
>>> 
>>> Unplug the USB cable
>>> Watch as the four minicom terminals fill with error messages 
>>> (tc_usb_removed.png)
>>> =
>>> 
>>> 
>>> So ladies and gents, any ideas?  Thanks in advance!
>>> -- 
>>> --Ryan Monroe
>>> 626.773.0805
>>> 
>>> 
> 

Re: [casper] ROACH2: Cannot communicate over USB

[Nimish Sane]

Hi Ryan,

What machine you are using? FWIW, we had hard time time connecting from
RedHat, it just worked smoothly with Windows and Ubuntu.

Thanks,

Nimish

On Mon, May 20, 2013 at 2:56 PM, David MacMahon
wrote:

> Hi, Ryan,
>
> Just for something else to try, this is the exact command that I use:
>
> screen /dev/ttyUSB2 115200
>
> When finished, I use "k" to close the screen session ( is the
> screen command character, which defaults to CTRL-A but I remap to CTRL-Z in
> my .screenrc file).
>
> Have you tried a "known good" ROACH2 with this computer?
>
> Dave
>
> On May 20, 2013, at 11:48 AM, Ryan Monroe wrote:
>
> > Hey David,
> >
> > We noticed the dialout group thing, and have tested it with me being
> both root (via sudo minicom USBTTY2) and dialout.  Thanks!
> >
> > --Ryan Monroe
> > 626.773.0805
> >
> > On 05/20/2013 11:46 AM, David MacMahon wrote:
> >> Hi, Ryan,
> >>
> >> Everything seems OK.  Were you root or a member of the dialout group
> when you tried connecting?  I use screen instead of minicom, so I can't
> offer any extra ideas regarding minicom itself.
> >>
> >> FWIW, /dev/ttyUSB2 is the one that usually works for me.
> >>
> >> Dave
> >>
> >> On May 20, 2013, at 11:34 AM, Ryan Monroe wrote:
> >>
> >>> Hey all, sorry for the spam :-(
> >>>
> >>> I'm trying to communicate with my ROACH2 for initial configuration.
>  My understanding is that we should set up a machine per this .  Then
> use the USB port the same way we used serial for ROACH1... just over either
> ttyUSB2 or ttyUSB3.
> >>>
> >>> My problem is that I receive no communications from the ROACH through
> USB.  After configuring the settings in minicom (filename, flow control,
> init/reset string), I can connect to the four USB virtual serial ports on
> the ROACH2, but I receive no data upon starting it up.  Here's the test I
> ran:
> >>>
> >>>
> >>> 
> >>> 
> >>> Start up computer.  Connect ROACH2 to power.  Do not start up ROACH2.
> >>> 
> >>>
> >>> Upon logging in, run "dmesg > tc_dmesg_preUSB.txt" (see file)
> >>> run "ls /dev/ttyUSB*" (see results in "tc_lsOnUSB.txt")
> >>>
> >>> Plug in the USB cable to both ends
> >>> run "dmesg > tc_dmesg_postUSB.txt" (see file)
> >>> run "ls /dev/ttyUSB*" (see results in "tc_lsOnUSB.txt")
> >>> 
> >>>
> >>> Run "sudo minicom -s TTYUSB2" and "sudo minicom -s TTYUSB3".  Take a
> screenshot to display the state of the configurations
> (tc_minicom_settings.jpg)
> >>>
> >>> Run:
> >>> "sudo minicom TTYUSB0"
> >>> "sudo minicom TTYUSB1"
> >>> "sudo minicom TTYUSB2"
> >>> "sudo minicom TTYUSB3"
> >>>
> >>> Take a screenshot (tc_before_powering_roach.jpg)
> >>> Press the ROACH2 power button
> >>> Wait several minutes
> >>> Take a screenshot to show that we received nothing from the ROACH.
> (tc_before_powering_roach.jpg ... it was the same result)
> >>>
> >>> Unplug the USB cable
> >>> Watch as the four minicom terminals fill with error messages
> (tc_usb_removed.png)
> >>> =
> >>>
> >>>
> >>> So ladies and gents, any ideas?  Thanks in advance!
> >>> --
> >>> --Ryan Monroe
> >>> 626.773.0805
> >>>
> >>>
> 
> >
>
>
>

Re: [casper] ROACH2: Cannot communicate over USB

[John Ford]

> Hi Ryan,
>
> What machine you are using? FWIW, we had hard time time connecting from
> RedHat, it just worked smoothly with Windows and Ubuntu.

This reminded me that I that our sysadmin installed a udev rule for this
in my redhat 6 laptop:

Yes, Master<1000> more /etc/udev/rules.d/99-ftdi.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6011",
MODE="666",
 OPTIONS="last_rule"

John


>
> Thanks,
>
> Nimish
>
> On Mon, May 20, 2013 at 2:56 PM, David MacMahon
> wrote:
>
>> Hi, Ryan,
>>
>> Just for something else to try, this is the exact command that I use:
>>
>> screen /dev/ttyUSB2 115200
>>
>> When finished, I use "k" to close the screen session ( is the
>> screen command character, which defaults to CTRL-A but I remap to CTRL-Z
>> in
>> my .screenrc file).
>>
>> Have you tried a "known good" ROACH2 with this computer?
>>
>> Dave
>>
>> On May 20, 2013, at 11:48 AM, Ryan Monroe wrote:
>>
>> > Hey David,
>> >
>> > We noticed the dialout group thing, and have tested it with me being
>> both root (via sudo minicom USBTTY2) and dialout.  Thanks!
>> >
>> > --Ryan Monroe
>> > 626.773.0805
>> >
>> > On 05/20/2013 11:46 AM, David MacMahon wrote:
>> >> Hi, Ryan,
>> >>
>> >> Everything seems OK.  Were you root or a member of the dialout group
>> when you tried connecting?  I use screen instead of minicom, so I can't
>> offer any extra ideas regarding minicom itself.
>> >>
>> >> FWIW, /dev/ttyUSB2 is the one that usually works for me.
>> >>
>> >> Dave
>> >>
>> >> On May 20, 2013, at 11:34 AM, Ryan Monroe wrote:
>> >>
>> >>> Hey all, sorry for the spam :-(
>> >>>
>> >>> I'm trying to communicate with my ROACH2 for initial configuration.
>>  My understanding is that we should set up a machine per this .
>> Then
>> use the USB port the same way we used serial for ROACH1... just over
>> either
>> ttyUSB2 or ttyUSB3.
>> >>>
>> >>> My problem is that I receive no communications from the ROACH
>> through
>> USB.  After configuring the settings in minicom (filename, flow control,
>> init/reset string), I can connect to the four USB virtual serial ports
>> on
>> the ROACH2, but I receive no data upon starting it up.  Here's the test
>> I
>> ran:
>> >>>
>> >>>
>> >>> 
>> >>> > disconnected>
>> >>> Start up computer.  Connect ROACH2 to power.  Do not start up
>> ROACH2.
>> >>> 
>> >>>
>> >>> Upon logging in, run "dmesg > tc_dmesg_preUSB.txt" (see file)
>> >>> run "ls /dev/ttyUSB*" (see results in "tc_lsOnUSB.txt")
>> >>>
>> >>> Plug in the USB cable to both ends
>> >>> run "dmesg > tc_dmesg_postUSB.txt" (see file)
>> >>> run "ls /dev/ttyUSB*" (see results in "tc_lsOnUSB.txt")
>> >>> 
>> >>>
>> >>> Run "sudo minicom -s TTYUSB2" and "sudo minicom -s TTYUSB3".  Take a
>> screenshot to display the state of the configurations
>> (tc_minicom_settings.jpg)
>> >>>
>> >>> Run:
>> >>> "sudo minicom TTYUSB0"
>> >>> "sudo minicom TTYUSB1"
>> >>> "sudo minicom TTYUSB2"
>> >>> "sudo minicom TTYUSB3"
>> >>>
>> >>> Take a screenshot (tc_before_powering_roach.jpg)
>> >>> Press the ROACH2 power button
>> >>> Wait several minutes
>> >>> Take a screenshot to show that we received nothing from the ROACH.
>> (tc_before_powering_roach.jpg ... it was the same result)
>> >>>
>> >>> Unplug the USB cable
>> >>> Watch as the four minicom terminals fill with error messages
>> (tc_usb_removed.png)
>> >>> =
>> >>>
>> >>>
>> >>> So ladies and gents, any ideas?  Thanks in advance!
>> >>> --
>> >>> --Ryan Monroe
>> >>> 626.773.0805
>> >>>
>> >>>
>> 
>> >
>>
>>
>>
>

Re: [casper] ROACH2: Cannot communicate over USB

[Nimish Sane]

We had problems even after installing the rule and still continue to have,
though we do not need to use RedHat to talk to Roaches now.

On Mon, May 20, 2013 at 3:29 PM, John Ford  wrote:

> > Hi Ryan,
> >
> > What machine you are using? FWIW, we had hard time time connecting from
> > RedHat, it just worked smoothly with Windows and Ubuntu.
>
> This reminded me that I that our sysadmin installed a udev rule for this
> in my redhat 6 laptop:
>
> Yes, Master<1000> more /etc/udev/rules.d/99-ftdi.rules
> SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6011",
> MODE="666",
>  OPTIONS="last_rule"
>
> John
>
>
> >
> > Thanks,
> >
> > Nimish
> >
> > On Mon, May 20, 2013 at 2:56 PM, David MacMahon
> > wrote:
> >
> >> Hi, Ryan,
> >>
> >> Just for something else to try, this is the exact command that I use:
> >>
> >> screen /dev/ttyUSB2 115200
> >>
> >> When finished, I use "k" to close the screen session ( is the
> >> screen command character, which defaults to CTRL-A but I remap to CTRL-Z
> >> in
> >> my .screenrc file).
> >>
> >> Have you tried a "known good" ROACH2 with this computer?
> >>
> >> Dave
> >>
> >> On May 20, 2013, at 11:48 AM, Ryan Monroe wrote:
> >>
> >> > Hey David,
> >> >
> >> > We noticed the dialout group thing, and have tested it with me being
> >> both root (via sudo minicom USBTTY2) and dialout.  Thanks!
> >> >
> >> > --Ryan Monroe
> >> > 626.773.0805
> >> >
> >> > On 05/20/2013 11:46 AM, David MacMahon wrote:
> >> >> Hi, Ryan,
> >> >>
> >> >> Everything seems OK.  Were you root or a member of the dialout group
> >> when you tried connecting?  I use screen instead of minicom, so I can't
> >> offer any extra ideas regarding minicom itself.
> >> >>
> >> >> FWIW, /dev/ttyUSB2 is the one that usually works for me.
> >> >>
> >> >> Dave
> >> >>
> >> >> On May 20, 2013, at 11:34 AM, Ryan Monroe wrote:
> >> >>
> >> >>> Hey all, sorry for the spam :-(
> >> >>>
> >> >>> I'm trying to communicate with my ROACH2 for initial configuration.
> >>  My understanding is that we should set up a machine per this .
> >> Then
> >> use the USB port the same way we used serial for ROACH1... just over
> >> either
> >> ttyUSB2 or ttyUSB3.
> >> >>>
> >> >>> My problem is that I receive no communications from the ROACH
> >> through
> >> USB.  After configuring the settings in minicom (filename, flow control,
> >> init/reset string), I can connect to the four USB virtual serial ports
> >> on
> >> the ROACH2, but I receive no data upon starting it up.  Here's the test
> >> I
> >> ran:
> >> >>>
> >> >>>
> >> >>> 
> >> >>>  >> disconnected>
> >> >>> Start up computer.  Connect ROACH2 to power.  Do not start up
> >> ROACH2.
> >> >>> 
> >> >>>
> >> >>> Upon logging in, run "dmesg > tc_dmesg_preUSB.txt" (see file)
> >> >>> run "ls /dev/ttyUSB*" (see results in "tc_lsOnUSB.txt")
> >> >>>
> >> >>> Plug in the USB cable to both ends
> >> >>> run "dmesg > tc_dmesg_postUSB.txt" (see file)
> >> >>> run "ls /dev/ttyUSB*" (see results in "tc_lsOnUSB.txt")
> >> >>> 
> >> >>>
> >> >>> Run "sudo minicom -s TTYUSB2" and "sudo minicom -s TTYUSB3".  Take a
> >> screenshot to display the state of the configurations
> >> (tc_minicom_settings.jpg)
> >> >>>
> >> >>> Run:
> >> >>> "sudo minicom TTYUSB0"
> >> >>> "sudo minicom TTYUSB1"
> >> >>> "sudo minicom TTYUSB2"
> >> >>> "sudo minicom TTYUSB3"
> >> >>>
> >> >>> Take a screenshot (tc_before_powering_roach.jpg)
> >> >>> Press the ROACH2 power button
> >> >>> Wait several minutes
> >> >>> Take a screenshot to show that we received nothing from the ROACH.
> >> (tc_before_powering_roach.jpg ... it was the same result)
> >> >>>
> >> >>> Unplug the USB cable
> >> >>> Watch as the four minicom terminals fill with error messages
> >> (tc_usb_removed.png)
> >> >>> =
> >> >>>
> >> >>>
> >> >>> So ladies and gents, any ideas?  Thanks in advance!
> >> >>> --
> >> >>> --Ryan Monroe
> >> >>> 626.773.0805
> >> >>>
> >> >>>
> >>
> 
> >> >
> >>
> >>
> >>
> >
>
>
>