(4) UARTS: UART0 (debug/console), UART1, 2 and 4 connected to MAX232 transceivers
(1) SD card
(1) USB (host)
(1) USB (peripheral)
(2) ethernet PHY LAN8710 on i2c bus RMII
No onboard LEDs
I have followed https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black (June 05 2020) instructions. I am able to boot to linux and login.
I am using dtb-rebuilder. I copied/renamed am335x-boneblack.dts, am33xx.dtsi, am335x-bone-common.dtsi and am335x-boneblack-common.dtsi. I have changed/added uart1,2 and 4, commented out the leds/user_leds, added pinmux for the second RMII and other changes to the am335x-zzz-common.dtsi. I have commented out the tda19988 and sound section of amm335x-boneblack-common.dtsi. After doing all that, I found a post on this forum that mentioned to start with am335x-bonegreen.dts because it is same as boneblack except it doesn’t have HDMI. Thenk got me thinking if there is a existing device tree that I should start with instead of the boneblack.
Which device tree is closest match to my custom board?
Also, my custom board hardware is not going to change. I don’t think I need helper or cape manager. However I don’t understand the purpose the helper or cape manager. Ultimately I don’t think I need .dtsi (include) or overlay files. I would like to end up with a single .dts file that matches my board.
Comments about pros/cons of putting device tree in one .dts file are welcome.