CDC ACM doesn't working in a custom linux kernelcan't initialise/detect 16550A UART at unusual io port...

Why can my keyboard only digest 6 keypresses at a time?

Russian word for a male zebra

How to communicate to my GM that not being allowed to use stealth isn't fun for me?

How to ensure color fidelity of the same file on two computers?

Non-aqueous eyes?

Bb13b9 confusion

I have a problematic assistant manager, but I can't fire him

Cascading Switches. Will it affect performance?

Is it expected that a reader will skip parts of what you write?

Is it legal for a bar bouncer to confiscate a fake ID

Why does the Mishnah use the terms poor person and homeowner when discussing carrying on Shabbat?

How to trick the reader into thinking they're following a redshirt instead of the protagonist?

How is the excise border managed in Ireland?

How does the Around command at zero work?

Why {1,2} printed by a command in $() is not interpolated?

What is the color of artificial intelligence?

Does the Long March-11 increase its thrust after clearing the launch tower?

An easy proof that an isometry preserving the zero vector is linear

A map of non-pathological topology?

New pedal fell off maybe 50 miles after installation. Should I replace the entire crank, just the arm, or repair the thread?

Does the new finding on "reversing a quantum jump mid-flight" rule out any interpretations of QM?

Ability To Change Root User Password (Vulnerability?)

How can I get an unreasonable manager to approve time off?

How creative should the DM let an artificer be in terms of what they can build?



CDC ACM doesn't working in a custom linux kernel


can't initialise/detect 16550A UART at unusual io port addresscannot mount usbHow to get /dev/ttyUSB* to show up?Static CDC ACM device bindingConsole setting in initramfs (ARM)CDC-ACM driver returning garbage dataVirtualbox VMDK to bootable usb stick not workingusb 2-3: usb_reset_and_verify_device Failed to disable LTMPL2303/PL2303X USB-Serial driverrunning a terminal over PCMCIA serial port in unix






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







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
















bumped to the homepage by Community 41 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






















    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
















    bumped to the homepage by Community 41 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      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

      260k72559707




      260k72559707










      asked Apr 17 '14 at 20:25









      Ricardo CrudoRicardo Crudo

      18115




      18115





      bumped to the homepage by Community 41 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 41 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          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

                    Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

                    Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

                    Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...