XDIMAX Products Forum

Hi again, I did find this documentation. I guess the real question is, sometime ago I had asked if it would be possible to manually drive the CS bits that are not being used by the SPI as extra GPIO bits. This feature existed in the USB12, and I discovered that it was not available in the SUB20. So ...

Where can I find the documentation on how this works.
Thanks!
John

Hello again, I have placed a short program below that will duplicate the problem. I have placed a define statement that can be used to easily switch the program between use of the real time and virtual timers. When using the real time timer, the segmentation violation occurs. When using the virtual ...

Hello and thank you for your comments, I believe you are right on track. I spent several hours debugging with gdb and it appears that there is some interaction with the ITIMER_REAL and the USB libusb functions. I can run the operation with ITIMER_VIRTUAL just fine with only a slight cost in timing a...

I have done the export SUB_20=10, and I get the following: BULK_OUT 11 bytes: 0a 62 08 00 20 00 00 00 20 00 00 Transfer completed, transferred=11 BULK_IN 7 bytes: 06 62 04 00 20 00 00 BULK_OUT 11 bytes: 0a 62 08 00 20 00 00 00 00 00 00 Transfer completed, transferred=11 BULK_IN 7 bytes: 06 62 04 00 ...

PS.
I just realized what you were saying about the export statement.
I will try that as soon as I get back tot he board.
Thanks allot,
John

1. So does it work on Jaunty with libusb-1.0.6 ? It does NOT work with libusb1.0.6 or 1.0.5, or 1.0.7. Do you have specific API call it fails on? Can you send us a peace of code around it? First of all, it happens when I am doing a tight loop of repetition. I have seen it occur on 3 API calls: 1: if...

I am using a SUB-20 board SPI interface as a demo controller for an evaluation board for our company product. I developed the application (a GUI) in C using GTK and used the libusb-1.0.6. The same GUI works under Linux and Windows. When I upgraded my Linux system from Hardy (8.04) to Jaunty (9.04), ...

Hi Joe, The problem does related to USB communication. Your assumption was correct. USB Host (PC in your case) has 1ms USB frame. It means any new USB transfer can be started only with new 1ms frame. That's why back to back spi_transfer calls have 1ms gap between. The most simple way to eliminate i...