What I want to check

Today's Goal : Clarify the goal again and reconfirm the specific tasks to complete the project..

About my goal

• For non-Robotics Capes, implement a device tree overlay for kernel 5.10, referring to the existing device tree overlay in kernel 4.19.

  • What is the target board? (Black, AI, AI64[not owned])

    • <write here>
    • wiki . AI. 5.18, 5.19 debian.

  • Ask again where the relevant files are located

    • Device Tree Overlay development locations in kernel 4.19
      • https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v4.19.x-ti-overlays/src/arm/overlays
    • Repositories and branches to which pull requests should be submitted
      • https://github.com/beagleboard/BeagleBoard-DeviceTrees/
    • Links to other files that may be helpful
      • <write here>

    Reference for old overlays, https://github.com/beagleboard/bb.org-overlays

  • Organize the arrangements for proceeding with the development

    • Instead of specifying the from U-Boot, as this blog says, I should just specify it in uEnv.txt and develop it?
      • This page uses changing U-Boot options for applying custom device tree overlay. https://beagleboard.org/blog/2022-02-15-using-device-tree-overlays-example-on-beaglebone-cape-add-on-boards
        • I don't know how the functionality is implemented to automatically select and load the best device tree when the Cape is connected yet.
      • <write here (yes or no)>

  • What is the development flow [Relay Cape as an example]

    My Assumptions

    1. See https://github.com/beagleboard/BeagleBoard-DeviceTrees/blob/v4.19.x-ti-overlays/src/arm/overlays/BBORG_RELAY-00A2.dts and copy for the kernel 5.10
    2. Overwrite the overlays on the existing build and check the function works correctly
    3. If I found any trouble, using kernel message, specifying issues and fix them
    4. If the Cape function works correctly, send a pull request to <write here>

    <wirte here if my assumptions are wrong>

• For Robotics Capes, create the appropriate device trees for both 4.19 and 5.10 from scratch.

  • What is the target board? (Black, AI, AI64[not owned])
    • <write here>
  • What is the development flow?
    • <write here>

Questions

• There are multiple repositories, I want to understand these relationships (projects and branches). Where should I proceed with basic development?

  • Device Tree repository? What is the difference?

    • https://github.com/beagleboard/BeagleBoard-DeviceTrees

    • https://github.com/beagleboard/bb.org-overlays

    • bone number mapping

    • pin control file (k3.h)

    

    • make this pin2pad macro

    

    

• in 5.18, 5.19 , pin definition is diffalent.

• main line no patch for AI-64

  

charactor devices is difficult “gpio-d”

overlay,

multiplexing driver

pinmux helper driver