CDC ACM doesn't work in a custom linux kernelcan't initialise/detect 16550A UART at unusual io port...
Why increase or decrease rudder when using elevator in turns?
Can I get bubble tea at Taiyuan airport?
Can you set fire to beer barrels?
"A tin of biscuits" vs "A biscuit tin"
counter in hexadecimal base
Extra battery in the gap of an HDD
Why did Crew Dragon switch to burst disks instead of multiple check valves?
"Table" method for expanding brackets vs "each term in the first bracket gets multiplied by each term in the second bracket"
Variable fixing based on a good feasible solution
Can digital computers understand infinity?
Are Snap and Flatpack apps safe to install? Are they "official", approved or tested for a particular distro version?
What is the name for a fluid transition between two tones? When did it first appear?
Why exactly is the answer 50 ohms?
Pass a bash variable to python script
"inuendo" in a piano score
Incorrect mmap behavior when assembly files in included in the project
3-prong to 4-prong conversion - EXTRA MISLABELLED WIRES - Dryer cable upgrade and installation
7 mentions of night in Gospel of John
Skewer removal without quick release
Open Loop gain of an Op-Amp
Boot directly into another kernel from running Linux without bootloader
How can demon technology be prevented from surpassing humans?
Some interesting and elementary topics with connections to the representation theory?
What is this white sheet behind the insulation?
CDC ACM doesn't work in a custom linux kernel
can't initialise/detect 16550A UART at unusual io port addressGSM modem does not create /dev/ttyUSB filecannot mount usbHow to get /dev/ttyUSB* to show up?Console setting in initramfs (ARM)CDC-ACM driver returning garbage dataCustom Kernel for VMWarePL2303/PL2303X USB-Serial driver
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{
margin-bottom:0;
}
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
add a comment
|
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
add a comment
|
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
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
linux-kernel usb cubieboard
edited 55 mins ago
mosvy
17.8k2 gold badges24 silver badges55 bronze badges
17.8k2 gold badges24 silver badges55 bronze badges
asked Apr 17 '14 at 20:25
Ricardo CrudoRicardo Crudo
231 gold badge1 silver badge5 bronze badges
231 gold badge1 silver badge5 bronze badges
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
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.
add a comment
|
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/4.0/"u003ecc by-sa 4.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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f125285%2fcdc-acm-doesnt-work-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
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.
add a comment
|
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.
add a comment
|
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.
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.
answered Jul 25 '15 at 12:01
CaerbannogCaerbannog
1
1
add a comment
|
add a comment
|
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f125285%2fcdc-acm-doesnt-work-in-a-custom-linux-kernel%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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