Hi Jason,
This is regarding the FTDI part. I am using RHEL 5.8. We could not identify
the right device/port in /dev/ directory. Do we need to install any
drivers?
I tried using the Linux driver they have here:
http://www.ftdichip.com/Drivers/VCP.htm However, I am not able to install
this driver.
Hi, Nimish,
I think you can find the information in the output of dmesg as (or after) you
connect the USB cable. It might also be in /var/log/messages.
Dave
On Dec 6, 2012, at 9:04 AM, Nimish Sane wrote:
> Hi Jason,
>
> This is regarding the FTDI part. I am using RHEL 5.8. We could not ident
Hi all:
We have Roach2 Rev2 boards and experienced similar behavior with the Fault
light. We have not used the FPGA at all yet, so cannot report on how it
affects programming the FPGA.
We are seeing Fault LED (Red) ON sometimes, and merely cycling power using
the "Power" switch on the board does
Hi, Andrew,
Thanks for looking into this.
On Dec 6, 2012, at 12:40 AM, Andrew Martens wrote:
> Just done some sims and can't replicate the behaviour.
Interesting. I just did some sims and also can't replicate this behavior in
simulation.
> Your problem is therefore interesting. Is this with
Hi Dave,
I can see it as a usb device /dev/usbdev* (8 devices actually) but not as
tty* that I can use. Does one need to install some drivers for this FTDI
component?
Thanks,
Nimish
On Thu, Dec 6, 2012 at 12:20 PM, David MacMahon
wrote:
> Hi, Nimish,
>
> I think you can find the information in
Hi, Nimish,
What does "dmesg | grep -i ftdi" show?
Does "lsmod | grep ftdi_sio" show anything? If not, try "modprobe ftdi_sio".
Dave
On Dec 6, 2012, at 10:53 AM, Nimish Sane wrote:
> Hi Dave,
>
> I can see it as a usb device /dev/usbdev* (8 devices actually) but not as
> tty* that I can use
Hi Dave,
All of these show nothing.
I just checked and see that there is an LED near the FTDI USB port (named
USB OK) that is ON (Red) on the board. Do you know what is that suppose to
indicate?
Thanks,
Nimish
On Thu, Dec 6, 2012 at 2:14 PM, David MacMahon wrote:
> Hi, Nimish,
>
> What does "
OK, the fact that the modprobe command showed nothing means that it succeeded,
so try running "dmesg | grep -i ftdi" again.
Dave
On Dec 6, 2012, at 11:20 AM, Nimish Sane wrote:
> Hi Dave,
>
> All of these show nothing.
>
> I just checked and see that there is an LED near the FTDI USB port (na
Ok. So now, dmesg | grep -i ftdi shows the following:
drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB
Serial Device
usbcore: registered new driver ftdi_sio
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
Nimish
On Thu, Dec 6, 2012 at 2:28 PM,
Now try disconnecting and reconnecting the USB cable. Now that the ftdi_sio
module is loaded, (re-)connecting the cable will hopefully prompt udev to
create the ttyUSB devices for you. After disconnecting, reconnecting, and
waiting for a couple of seconds, try "dmesg | grep -i ftdi" again.
Da
I tried this, but it did not create ttyUSB devices.
Nimish
On Thu, Dec 6, 2012 at 2:41 PM, David MacMahon wrote:
> Now try disconnecting and reconnecting the USB cable. Now that the
> ftdi_sio module is loaded, (re-)connecting the cable will hopefully prompt
> udev to create the ttyUSB devices
dmesg | grep -i ftdi still shows the same output.
On Thu, Dec 6, 2012 at 2:45 PM, Nimish Sane wrote:
> I tried this, but it did not create ttyUSB devices.
>
> Nimish
>
>
> On Thu, Dec 6, 2012 at 2:41 PM, David MacMahon
> wrote:
>
>> Now try disconnecting and reconnecting the USB cable. Now tha
I'm running out of ideas. Is the "usbserial" module loaded? Does "lsusb" show
the "Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO
IC" chip?
You could call RedHat support. That's one of the things you pay for when you
buy RHEL.
Dave
On Dec 6, 2012, at 11:46 AM, N
Yes, I can see that FTID message when I run lsusb.
I will check with RedHat support now.
Thanks for your help,
Nimish
On Thu, Dec 6, 2012 at 2:57 PM, David MacMahon wrote:
> I'm running out of ideas. Is the "usbserial" module loaded? Does "lsusb"
> show the "Future Technology Devices Interna
Hi Nimish,
> Yes, I can see that FTID message when I run lsusb.
And the output is what?
If the FTDI product ID is not recognized by ftdi_sio, then
you may have to create a udev rule
http://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_101_Customising_FTDI_VID_PID_In_Linux%28FT_81%29
Hi Dave H.,
lsusb returns this:
Bus 002 Device 021: ID 0403:6011 Future Technology Devices International,
Ltd FT4232H Quad HS USB-UART/FIFO IC
I had seen this note earlier, and thought I don't need to do anything since
product id was recognized fine. But, may be I need to something. Let me
check.
Hi Nimish,
lsusb returns this:
Bus 002 Device 021: ID 0403:6011 Future Technology Devices
International, Ltd FT4232H Quad HS USB-UART/FIFO IC
I had seen this note earlier, and thought I don't need to do anything
since product id was recognized fine. But, may be I need to something.
Let me check
Hi, Dave,
I think whether a udev rule needs to be created depends on whether the ftdi_sio
module knows about the vendor/product ID. If the module already has an alias
for the necessary vendor/product ID then the rule is already built-in.
Nimish, does "modinfo ftdi_sio | grep v0403p6011" output
Hi Dave,
I think whether a udev rule needs to be created depends on whether
the ftdi_sio module knows about the vendor/product ID. If the module
already has an alias for the necessary vendor/product ID then the
rule is already built-in.
I figured since I'd had similar trouble with a FT232H ca
On Dec 6, 2012, at 1:17 PM, David Hawkins wrote:
> Hi Dave,
>>
>> I think whether a udev rule needs to be created depends on whether
>> the ftdi_sio module knows about the vendor/product ID. If the module
>> already has an alias for the necessary vendor/product ID then the
>> rule is already bu
Hi Nimish,
Yes, I understand that now. lsusb just reads the info. I had to create a
rule and follow the TN-101 note that you mentioned. We had to reboot the
system apart from the steps mentioned in that application note from
FTDI. We can now see devices getting mounted as /dev/ttyUSB*
There is
Dave H.,
Yes, I understand that now. lsusb just reads the info. I had to create a
rule and follow the TN-101 note that you mentioned. We had to reboot the
system apart from the steps mentioned in that application note from FTDI.
We can now see devices getting mounted as /dev/ttyUSB*
There is noth
On Dec 6, 2012, at 1:29 PM, Nimish Sane wrote:
> Having done this, we can now use picocom to establish a communication over
> these ports. However, we do not see any roach login/prompt on any of the 4
> ports. So we are stuck at that point now. Any clue?
Make sure you're using the right baud r
Hi Dave,
I am using baud rate of 115200. I tried what you suggested and I still not
see anything on any of the 4 ports. I have tried with both the Roach2
boards that we have, and it is the same behavior.
I am going back to my another question, which I asked on a separate thread
(this may or may n
On Dec 6, 2012, at 2:31 PM, Nimish Sane wrote:
> I am using baud rate of 115200. I tried what you suggested and I still not
> see anything on any of the 4 ports. I have tried with both the Roach2 boards
> that we have, and it is the same behavior.
That's not good. Maybe try another comm progr
Nimish
On Dec 6, 2012, at 5:47 PM, David MacMahon wrote:
>
> On Dec 6, 2012, at 2:31 PM, Nimish Sane wrote:
>
>> I am using baud rate of 115200. I tried what you suggested and I still not
>> see anything on any of the 4 ports. I have tried with both the Roach2 boards
>> that we have, and it is
hi nimish,
are you using a null modem cable?
(this is needed for computer to computer).
what about stop bits, and parity bit settings?
what about the RS232 handshaking lines?
dan
On Thu, Dec 6, 2012 at 2:31 PM, Nimish Sane wrote:
> Hi Dave,
>
> I am using baud rate of 115200. I tried what yo
hi dale, nimish,
my mistake. i saw baud rate of 115200 and immediately
thought of RS232. for USB, there's no equivalent or need
for "null modem".
dan
On Thu, Dec 6, 2012 at 6:49 PM, Dale Gary wrote:
> Hi Dan and all,
>
> This is a USB cable. Is there anything analogous to null modem for su
> I am using baud rate of 115200. I tried what you suggested and I still not
> see anything on any of the 4 ports. I have tried with both the Roach2 boards
> that we have, and it is the same behavior.
We use minicom to good effect. Remember to disable all flow control, both HW
and SW (on my defa
Hi Dave
> I am working on ROACH2.
Jason also had a problem with snapshot blocks using ROACH2. His snap
block would not finish capturing, i.e write 7 into the control register,
busy bit goes high and byte count spins, but busy bit never goes low
again! Again, the logic to finish capturing is very
Hi Dave
I think Andrews point 3 is relevant.
We have picked up on transient on the register write with the latest memory
mapped TCPBORPH. It seems that sometimes, some of the bits goes high for a
short while and then settles at the required register value.
We need to figure out where the issue i
On Thu, Dec 6, 2012 at 10:31 PM, Nimish Sane wrote:
> I am using baud rate of 115200. I tried what you suggested and I still not
> see anything on any of the 4 ports. I have tried with both the Roach2 boards
> that we have, and it is the same behavior.
Note that on a serial port you will need to
32 matches
Mail list logo
