CDC ACM doesn't working in a custom linux kernel

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












1















I've a cubieboard2 running arch linux with a custom linux kernel.
In the cubieboard2 I plugged in my usb-serial device (like an arduino), the device is recognized as CDC ACM. My linux kernel has the CDC options enabled in the configuration, as I saw in this page, but, I can't use the serial port /dev/ttyACM0 using the applications minicom or pyserial.



Minicom just says that it can't open the serial port. Pyserial is able to open the port, but when I try reading it the result is:




SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)




Yet in pyserial if I try to write a byte the result is other:




SerialException: write failed: [Errno 5] Input/output error.




Other weird things happen when I close the serial port, it changes its name, in other words, when I close the /dev/ttyACM0 it changes to /dev/ttyACM1.



I've tried my device in my laptop and it works fine with both, pyserial and minicom.



cubieboard2 info:



$ uname -a
Linux alarm 3.4.61-rt77-ARCH+ #10 SMP PREEMPT RT Thu Apr 17 13:58:20 BRT 2014 armv7l GNU/Linux


my kernel config file: http://pastebin.com/raw.php?i=6LfsRyek



My guess is that it's missing having some kernel option enabled, but I don't know which.



Any idea?










share|improve this question




























    1















    I've a cubieboard2 running arch linux with a custom linux kernel.
    In the cubieboard2 I plugged in my usb-serial device (like an arduino), the device is recognized as CDC ACM. My linux kernel has the CDC options enabled in the configuration, as I saw in this page, but, I can't use the serial port /dev/ttyACM0 using the applications minicom or pyserial.



    Minicom just says that it can't open the serial port. Pyserial is able to open the port, but when I try reading it the result is:




    SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)




    Yet in pyserial if I try to write a byte the result is other:




    SerialException: write failed: [Errno 5] Input/output error.




    Other weird things happen when I close the serial port, it changes its name, in other words, when I close the /dev/ttyACM0 it changes to /dev/ttyACM1.



    I've tried my device in my laptop and it works fine with both, pyserial and minicom.



    cubieboard2 info:



    $ uname -a
    Linux alarm 3.4.61-rt77-ARCH+ #10 SMP PREEMPT RT Thu Apr 17 13:58:20 BRT 2014 armv7l GNU/Linux


    my kernel config file: http://pastebin.com/raw.php?i=6LfsRyek



    My guess is that it's missing having some kernel option enabled, but I don't know which.



    Any idea?










    share|improve this question


























      1












      1








      1








      I've a cubieboard2 running arch linux with a custom linux kernel.
      In the cubieboard2 I plugged in my usb-serial device (like an arduino), the device is recognized as CDC ACM. My linux kernel has the CDC options enabled in the configuration, as I saw in this page, but, I can't use the serial port /dev/ttyACM0 using the applications minicom or pyserial.



      Minicom just says that it can't open the serial port. Pyserial is able to open the port, but when I try reading it the result is:




      SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)




      Yet in pyserial if I try to write a byte the result is other:




      SerialException: write failed: [Errno 5] Input/output error.




      Other weird things happen when I close the serial port, it changes its name, in other words, when I close the /dev/ttyACM0 it changes to /dev/ttyACM1.



      I've tried my device in my laptop and it works fine with both, pyserial and minicom.



      cubieboard2 info:



      $ uname -a
      Linux alarm 3.4.61-rt77-ARCH+ #10 SMP PREEMPT RT Thu Apr 17 13:58:20 BRT 2014 armv7l GNU/Linux


      my kernel config file: http://pastebin.com/raw.php?i=6LfsRyek



      My guess is that it's missing having some kernel option enabled, but I don't know which.



      Any idea?










      share|improve this question
















      I've a cubieboard2 running arch linux with a custom linux kernel.
      In the cubieboard2 I plugged in my usb-serial device (like an arduino), the device is recognized as CDC ACM. My linux kernel has the CDC options enabled in the configuration, as I saw in this page, but, I can't use the serial port /dev/ttyACM0 using the applications minicom or pyserial.



      Minicom just says that it can't open the serial port. Pyserial is able to open the port, but when I try reading it the result is:




      SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)




      Yet in pyserial if I try to write a byte the result is other:




      SerialException: write failed: [Errno 5] Input/output error.




      Other weird things happen when I close the serial port, it changes its name, in other words, when I close the /dev/ttyACM0 it changes to /dev/ttyACM1.



      I've tried my device in my laptop and it works fine with both, pyserial and minicom.



      cubieboard2 info:



      $ uname -a
      Linux alarm 3.4.61-rt77-ARCH+ #10 SMP PREEMPT RT Thu Apr 17 13:58:20 BRT 2014 armv7l GNU/Linux


      my kernel config file: http://pastebin.com/raw.php?i=6LfsRyek



      My guess is that it's missing having some kernel option enabled, but I don't know which.



      Any idea?







      linux-kernel usb cubieboard






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 18 '14 at 3:16









      slm

      252k69530685




      252k69530685










      asked Apr 17 '14 at 20:25









      Ricardo CrudoRicardo Crudo

      18115




      18115




















          1 Answer
          1






          active

          oldest

          votes


















          0














          It seems to me that the problem is your device. It might enumerate OK, but behaves unexpectedly when further communications are performed. Try using Wireshark with usbmon (eventually tshark if you don't have an X session). The ttyACM1 name is usually due to re-enumeration after a faulty communication.






          share|improve this answer






















            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f125285%2fcdc-acm-doesnt-working-in-a-custom-linux-kernel%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            It seems to me that the problem is your device. It might enumerate OK, but behaves unexpectedly when further communications are performed. Try using Wireshark with usbmon (eventually tshark if you don't have an X session). The ttyACM1 name is usually due to re-enumeration after a faulty communication.






            share|improve this answer



























              0














              It seems to me that the problem is your device. It might enumerate OK, but behaves unexpectedly when further communications are performed. Try using Wireshark with usbmon (eventually tshark if you don't have an X session). The ttyACM1 name is usually due to re-enumeration after a faulty communication.






              share|improve this answer

























                0












                0








                0







                It seems to me that the problem is your device. It might enumerate OK, but behaves unexpectedly when further communications are performed. Try using Wireshark with usbmon (eventually tshark if you don't have an X session). The ttyACM1 name is usually due to re-enumeration after a faulty communication.






                share|improve this answer













                It seems to me that the problem is your device. It might enumerate OK, but behaves unexpectedly when further communications are performed. Try using Wireshark with usbmon (eventually tshark if you don't have an X session). The ttyACM1 name is usually due to re-enumeration after a faulty communication.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jul 25 '15 at 12:01









                CaerbannogCaerbannog

                1




                1



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f125285%2fcdc-acm-doesnt-working-in-a-custom-linux-kernel%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown






                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Bahrain

                    Postfix configuration issue with fips on centos 7; mailgun relay