-
Notifications
You must be signed in to change notification settings - Fork 779
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A strange issue happens on FT232B #509
Comments
Can you get to me the USB trace from your analyzer? |
Considering the software is windows only, that's a no-go. |
The FT232Bx and FT232Rx are basically identical from a software point of view. |
Below is the device information I get from UsbView: [Port1] : USB Serial Converter Is Port User Connectable: yes Device Power State: PowerDeviceD0
English product name: "M 504 G" ConnectionStatus:
bLength: 0x12
bLength: 0x07
bLength: 0x07
bLength: 0x09
bLength: 0x09
bLength: 0x07
bLength: 0x07 =================================================== |
Yeah, sounds like it is correct. |
I can't get the two status bytes. Even it's shown as ACK in protocol analyser. |
I'll try your code as above on a FT232RL and get back to you. I think it may be something else going on here. I'll check it in a day or so. |
Below is my code, it's modified from example code. I run it from Arduino Uno. I will try to increase the buffer size and have a try. And what does UHS3 means? #include <cdcftdi.h> #include <SPI.h> class FTDIAsync : public FTDIAsyncOper uint8_t FTDIAsync::OnInit(FTDI *pftdi)
} USB Usb; void setup() if (Usb.Init() == -1) delay( 200 ); void loop()
} |
UHS3 is here --> https://github.com/felis/UHS30 |
Thanks a lot. I will try it two days later. As the device is used by someone else. And I will feedback the result after testing. |
FYI I was having the same issue with a different use of the FT232B chip and after lots of trial and error I found this PR fixes the issue #174. Not looked at why it fixes it, just happy its working :) |
It's not a bug. The UNO simply doesn't have enough RAM. Warning is in the readme... |
I'm using the library on Particle B524 module and encountered the same issues described. Send and receive on FT232R works fine but receive on FT232B was returning NAK, Send was working correctly though. PR #174 fixed the issue for me. |
It's a great new for me. Thanks a lot.
|
Hi All,
I'm working on a project which need to get data from a USB device(MAVO-MONITOR USB). This device works well under windows. There is an FT232B chip in it to convert Uart to USB. And I use USB Host Shield with Arduino Uno to read the data from it. It works well with FT232R, I have tried FT232R board with loopback mode and communicate with another USB2Uart board. All the data can be send an received normally. But after I connect it with MAVO-MONITOR USB device. It can just send(I have confirmed this by sending Reset Command for this device and it will reset after received it). Arduino can't get data from this device.
From the above experiment I'm sure this is not a HW related issue. As FT232R works well and I can send command to the device.
And I have used a USB analyer for debugging (Teledyne LeCroy USB Protocol Analyser, T3). My code is like below:
There is no output from this code. I have tried, the value of rcvd is always 0. This should be at least 2 event there is valid data on the serial port.
From protocol analyser I can see the package comes from device send to EP1 and the HOST Shield has ACK to it. But I don't know why I can't get any data in my code. And I have checked the return value 'rcode', it's always 4 when means hrNAK. So this really puzzled me: the HOST have ACK to the device, but I can see nothing.
I have tried to compare the USB packages with Windows communication. But there are too many packages.
Does anyone know what's the different between FT232R and FT232B(this version is too old to buy, I can just find FT232BM in the market, and I'm not sure if I can see same issue with BM version)? And is there any directions for me to debug?
Thanks a lot.
Ziv
The text was updated successfully, but these errors were encountered: