• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 252 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SK-AM62: Buiding hello-wold.dts

Nancy Wang
Expert 8210 points
Part Number: SK-AM62


HI,

Customers refer to the following link to compile  hello-wold.dts.

https://dev.ti.com/tirex/explore/node?node=A__AIq9NiwHIx.kmzGwE-te-g__linux_academy_am62x__XaWts8R__LATEST&search=am62x

how to solve Label or path rtc0 not found appears. ecap0, p1, p2 not found?

  • 0
    TI__Expert 8210 points

    Hi,

    Any update for this question?

  • 0 in reply to Nancy Wang
    TI__Guru 70007 points

    Hi Nancy,

    looks like the current documentation is not fully up-to-date with the ti-linux-5.10.y kernel tree (which is what is used in SDK v8.6). Usually you can resolve such "label not found" issues (and similar ones) by searching the Kernel dts sources using 'grep'. However since I can't download the linked dts example from the link you provided at the moment I can't debug this specifically, but the below should give you some ideas:

    a0797059@dasso:~/git/linux (ti-linux-5.10.y)
$ git grep rtc arch/arm64/boot/dts/ti/k3-am62*
arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi:     wkup_rtc0: rtc@2b1f0000 {
arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi:             compatible = "ti,am62-rtc";
arch/arm64/boot/dts/ti/k3-am625-skeleton.dts:&wkup_rtc0 {
arch/arm64/boot/dts/ti/k3-am62a-wakeup.dtsi:    wkup_rtc0: rtc@2b1f0000 {
arch/arm64/boot/dts/ti/k3-am62a-wakeup.dtsi:            compatible = "ti,am62-rtc";

    The above results suggests that you'll likely need to edit your dts file, and replace 'rtc0' with 'wkup_rtc0'.

    a0797059@dasso:~/git/linux (ti-linux-5.10.y)
$ git grep ecap arch/arm64/boot/dts/ti/k3-am62*
arch/arm64/boot/dts/ti/k3-am62-main.dtsi:       ecap0_pwm: pwm@23100000 {
arch/arm64/boot/dts/ti/k3-am62-main.dtsi:               compatible = "ti,am3352-ecap";
arch/arm64/boot/dts/ti/k3-am62-main.dtsi:       ecap0_capture: capture@23100000 {
arch/arm64/boot/dts/ti/k3-am62-main.dtsi:               compatible = "ti,am62-ecap-capture";
arch/arm64/boot/dts/ti/k3-am62-main.dtsi:       ecap1_pwm: pwm@23110000 {
arch/arm64/boot/dts/ti/k3-am62-main.dtsi:               compatible = "ti,am3352-ecap";
arch/arm64/boot/dts/ti/k3-am62-main.dtsi:       ecap1_capture: capture@23110000 {
arch/arm64/boot/dts/ti/k3-am62-main.dtsi:               compatible = "ti,am62-ecap-capture";
arch/arm64/boot/dts/ti/k3-am62-main.dtsi:       ecap2_pwm: pwm@23120000 {
arch/arm64/boot/dts/ti/k3-am62-main.dtsi:               compatible = "ti,am3352-ecap";
arch/arm64/boot/dts/ti/k3-am62-main.dtsi:       ecap2_capture: capture@23120000 {
arch/arm64/boot/dts/ti/k3-am62-main.dtsi:               compatible = "ti,am62-ecap-capture";
arch/arm64/boot/dts/ti/k3-am625-sk-ecap-capture.dts:    main_ecap2_capture_pins_default: main-ecap2-capture-pins-default {
arch/arm64/boot/dts/ti/k3-am625-sk-ecap-capture.dts:&ecap2_pwm {
arch/arm64/boot/dts/ti/k3-am625-sk-ecap-capture.dts:&ecap2_capture {
arch/arm64/boot/dts/ti/k3-am625-sk-ecap-capture.dts:    pinctrl-0 = <&main_ecap2_capture_pins_default>;
arch/arm64/boot/dts/ti/k3-am625-sk-rpi-hdr-pwm.dts:     main_ecap1_pins_default: main-ecap1-pins-default {
arch/arm64/boot/dts/ti/k3-am625-sk-rpi-hdr-pwm.dts:&ecap2_pwm {
arch/arm64/boot/dts/ti/k3-am625-sk-rpi-hdr-pwm.dts:     pinctrl-0 = <&main_ecap1_pins_default>;
arch/arm64/boot/dts/ti/k3-am625-skeleton.dts:&ecap0_pwm {
arch/arm64/boot/dts/ti/k3-am625-skeleton.dts:&ecap1_pwm {
arch/arm64/boot/dts/ti/k3-am625-skeleton.dts:&ecap2_pwm {
arch/arm64/boot/dts/ti/k3-am62a-main.dtsi:      ecap0: pwm@23100000 {
arch/arm64/boot/dts/ti/k3-am62a-main.dtsi:              compatible = "ti,am3352-ecap";
arch/arm64/boot/dts/ti/k3-am62a-main.dtsi:      ecap1: pwm@23110000 {
arch/arm64/boot/dts/ti/k3-am62a-main.dtsi:              compatible = "ti,am3352-ecap";
arch/arm64/boot/dts/ti/k3-am62a-main.dtsi:      ecap2: pwm@23120000 {
arch/arm64/boot/dts/ti/k3-am62a-main.dtsi:              compatible = "ti,am3352-ecap";
arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi:&ecap0_pwm {
arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi:&ecap1_pwm {
arch/arm64/boot/dts/ti/k3-am62x-sk-common.dtsi:&ecap2_pwm {

    Likewise, the above suggests that you'll need to replace 'ecap0' etc. with either 'ecap0_pwm' or 'ecap0_capture', depending on what the use case is. You can also simple remove the associated nodes from the k3-am625-hello-world.dts file if not needed for the custom boad.

    As for the inconsistencies, I'll file an internal ticket against the documentation project to have this improved.

    Regards, Andreas