BeagleBone Slackware UART issue
Clash Royale CLAN TAG#URR8PPP
I'm working with a custom made image of Slackware ARM 14.1 with kernel 3.8.X since about 3 years and now needed to upgrade kernel for cdc-acm driver and watchdog.
I've tried different kernels from distro supplied with BeagleBone (Debian 7.11 to 9.5, kernel 4.1.X to 4.14.X). Each time I replace files in /boot/ and /lib/modules and /lib/firmware, they are all booting properly but never been able to make UART working again.
With kernel 3.8.X, I was using /boot/uEnv.txt line :
optargs=capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART4
I know there was changes between 4.1.X and 4.4.X and 4.14.X but tried each configurations with no success. Is it possible the issue is because I have a FAT partition for /boot/ and EXT4 partition for / ? Because I'll have to remote update systems so will not be able to change partitions.
Also could it be possible that the issue is the U-Boot version? From the debug serial :
U-Boot 2014.04-rc2-00015-g99288ca (Mar 12 2014 - 09:49:41)
EDIT :
Updated the U-Boot, still the same issue
U-Boot 2018.09-00002-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500), Build: jenkins-github_Bootloader-Builder-65
slackware beagleboneblack uart
add a comment |
I'm working with a custom made image of Slackware ARM 14.1 with kernel 3.8.X since about 3 years and now needed to upgrade kernel for cdc-acm driver and watchdog.
I've tried different kernels from distro supplied with BeagleBone (Debian 7.11 to 9.5, kernel 4.1.X to 4.14.X). Each time I replace files in /boot/ and /lib/modules and /lib/firmware, they are all booting properly but never been able to make UART working again.
With kernel 3.8.X, I was using /boot/uEnv.txt line :
optargs=capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART4
I know there was changes between 4.1.X and 4.4.X and 4.14.X but tried each configurations with no success. Is it possible the issue is because I have a FAT partition for /boot/ and EXT4 partition for / ? Because I'll have to remote update systems so will not be able to change partitions.
Also could it be possible that the issue is the U-Boot version? From the debug serial :
U-Boot 2014.04-rc2-00015-g99288ca (Mar 12 2014 - 09:49:41)
EDIT :
Updated the U-Boot, still the same issue
U-Boot 2018.09-00002-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500), Build: jenkins-github_Bootloader-Builder-65
slackware beagleboneblack uart
add a comment |
I'm working with a custom made image of Slackware ARM 14.1 with kernel 3.8.X since about 3 years and now needed to upgrade kernel for cdc-acm driver and watchdog.
I've tried different kernels from distro supplied with BeagleBone (Debian 7.11 to 9.5, kernel 4.1.X to 4.14.X). Each time I replace files in /boot/ and /lib/modules and /lib/firmware, they are all booting properly but never been able to make UART working again.
With kernel 3.8.X, I was using /boot/uEnv.txt line :
optargs=capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART4
I know there was changes between 4.1.X and 4.4.X and 4.14.X but tried each configurations with no success. Is it possible the issue is because I have a FAT partition for /boot/ and EXT4 partition for / ? Because I'll have to remote update systems so will not be able to change partitions.
Also could it be possible that the issue is the U-Boot version? From the debug serial :
U-Boot 2014.04-rc2-00015-g99288ca (Mar 12 2014 - 09:49:41)
EDIT :
Updated the U-Boot, still the same issue
U-Boot 2018.09-00002-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500), Build: jenkins-github_Bootloader-Builder-65
slackware beagleboneblack uart
I'm working with a custom made image of Slackware ARM 14.1 with kernel 3.8.X since about 3 years and now needed to upgrade kernel for cdc-acm driver and watchdog.
I've tried different kernels from distro supplied with BeagleBone (Debian 7.11 to 9.5, kernel 4.1.X to 4.14.X). Each time I replace files in /boot/ and /lib/modules and /lib/firmware, they are all booting properly but never been able to make UART working again.
With kernel 3.8.X, I was using /boot/uEnv.txt line :
optargs=capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART4
I know there was changes between 4.1.X and 4.4.X and 4.14.X but tried each configurations with no success. Is it possible the issue is because I have a FAT partition for /boot/ and EXT4 partition for / ? Because I'll have to remote update systems so will not be able to change partitions.
Also could it be possible that the issue is the U-Boot version? From the debug serial :
U-Boot 2014.04-rc2-00015-g99288ca (Mar 12 2014 - 09:49:41)
EDIT :
Updated the U-Boot, still the same issue
U-Boot 2018.09-00002-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500), Build: jenkins-github_Bootloader-Builder-65
slackware beagleboneblack uart
slackware beagleboneblack uart
edited Jan 17 at 6:01
Alexandre Lavoie
asked Jan 16 at 19:12
Alexandre LavoieAlexandre Lavoie
1255
1255
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Finally I used the kernel 4.4.54 from image bone-debian-9.5-iot-armhf-2018-10-07-4gb.img which serial ports work as ttyS? instead of ttyO?.
Something probably wrong with 4.14.X configuration (uEnv.txt or other), but I'm satisfied with 4.4.X for now.
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/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
);
);
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%2f494906%2fbeaglebone-slackware-uart-issue%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
Finally I used the kernel 4.4.54 from image bone-debian-9.5-iot-armhf-2018-10-07-4gb.img which serial ports work as ttyS? instead of ttyO?.
Something probably wrong with 4.14.X configuration (uEnv.txt or other), but I'm satisfied with 4.4.X for now.
add a comment |
Finally I used the kernel 4.4.54 from image bone-debian-9.5-iot-armhf-2018-10-07-4gb.img which serial ports work as ttyS? instead of ttyO?.
Something probably wrong with 4.14.X configuration (uEnv.txt or other), but I'm satisfied with 4.4.X for now.
add a comment |
Finally I used the kernel 4.4.54 from image bone-debian-9.5-iot-armhf-2018-10-07-4gb.img which serial ports work as ttyS? instead of ttyO?.
Something probably wrong with 4.14.X configuration (uEnv.txt or other), but I'm satisfied with 4.4.X for now.
Finally I used the kernel 4.4.54 from image bone-debian-9.5-iot-armhf-2018-10-07-4gb.img which serial ports work as ttyS? instead of ttyO?.
Something probably wrong with 4.14.X configuration (uEnv.txt or other), but I'm satisfied with 4.4.X for now.
answered Jan 17 at 19:54
Alexandre LavoieAlexandre Lavoie
1255
1255
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%2f494906%2fbeaglebone-slackware-uart-issue%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