Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

dcan0 alias fck already exist

Open
#63 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
linux

Research direction

Start by reviewing the changes in am335x-bone-common.dtsi and the added dcan0 pinmux under am33xx-pinmux, then reproduce the kernel message platform 481cc000.d_can: alias fck already exists. Determine whether enabling dcan0 alongside I2C2 causes the alias conflict and document the confirmed cause and required configuration.

Written by the indexing model from the issue text.

Description

I want to use dcan0 and followed this lead:
http://www.embedded-things.com/bbb/enable-canbus-on-the-beaglebone-black/#comment-152

To build the latest kernel I followed the instructions on this github page. Further I disabled my i2c2 pinmux by commenting out in am335x-bone-common.dtsi
//pinctrl-0 = <&i2c2_pins>;

And enabled dcan0
&dcan0 {
status = "okay"; // Switch on DCAN0
pinctrl-names = "default"; // Apply default pinmuxing
pinctrl-0 = <&dcan0_pins>;
};

And added pinmux to the am33xx-pinmux
dcan0_pins: pinmux_dcan0_pins {
pinctrl-single,pins = <
0x178 0x12 /* dcan0_tx, SLEWCTRL_FAST | PULLUP | MODE2 /
0x17C 0x32 /
dcan0_rx, SLEWCTRL_FAST | INPUT_PULLUP | MODE2 */
>;
};

Unfortunately I get the following message:
platform 481cc000.d_can: alias fck already exists

Is this due to having I2C2 and dcan0 enabled?

Dominant language
Shell
Stars
172
Forks
156
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from beagleboard/kernel

All issues in beagleboard/kernel

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.