hi Matt,
2010/10/9 mattschinkel <[email protected]> > > Ah ah ah... These "garbage" chars (AT+GCAP...) are actually AT commands > :) > > Since CDC/ACM devices are supposed to be modem, this explains why I > receive > > this. I now need to figure out how to disable on my system... > > Please keep us informed if you find out how to fix this. Yet no fix, but... in usb_serial.jal, USB CONFIGURATION DESCRIPTOR says used protocol should be AT commands (USB_V25TER, Communication Interface Class Control Protocol Code). According to USB CDC specs, if setting this to 0 tells the host not to use any particular protocol. So I tried this, but then USB device isn't properly recognized, I don't have any /dev/ttyACM0 device anymore. It's because kernel module cdc_acm only "catches" those with AT commands. I found this interesting page, showing a patch to allow pseudo-modem to be added without AT commands (this is what we need). Interestingly this patch is aimed to "enable to drive electronic simple gadgets based on microcontrolers"... http://www.spinics.net/lists/stable-commits/msg08595.html But this requires kernel module compilation. According to the post, this has been added to Linux kernel 2.6.32 (this is a recent patch). I'm running 2.6.28 so I definitely need to test this. If,Matt, you have a windows box, can you test specifying Communication Interface Class Control Protocol Code as 0x00 instead of USB_V25TER (search in usb_serial.jal) and let us know how this is handle by windows ? What I still can't understand is when using usb serial echo sample, I never get any AT commands, but when using SLIP, I do. Could SLIP chars wake up AT ? (I'm definitely not an AT expert...) Cheers, Seb -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
