RSS Bot Posted February 13 Posted February 13 Description This PR adds support for the Texas Instruments SK-AM68 and SK-AM69 boards. Notable features of SK-AM68 board: 16GB LPDDR4‐4266 with support for inline error correction code (ECC) DisplayPort 4K resolution with MST support and HDMI Two CSI-2 ports compatible with Raspberry Pi 8 TOPS deep-learning performance and hardware-accelerated edge AI Three USB 3.0 Type A ports, one USB 3.0 Type C port Gigabit Ethernet and 4x CAN-FD Headers One M.2 key M connector Notable features of SK-AM69 board: 32GB LPDDR4‐4266 with support for inline error correction code (ECC) DisplayPort 4K resolution with MST support and HDMI Three CSI-2 ports compatible with Raspberry Pi 32 TOPS deep-learning performance and hardware-accelerated edge AI Three USB 3.0 Type A ports, one USB 3.0 Type C port Gigabit Ethernet and 4x CAN-FD Headers One M.2 key E connector and one M.2 key M connector Further details like features, schematics and purchase links can be found on the board page: SK-AM68 SK-AM69 Note: To support SK-AM69 board, we had to switch U-Boot source for K3 family devices to ti-u-boot:2023.04 (commit 1), since boot configs for SK-AM69 board has not been upstreamed yet. How Has This Been Tested? First, we verified that the changes introduced do not deprecate any existing board support by: [ ] Build and boot SK-AM62B Jammy CLI/Standard on Edge(v6.6) kernel [ ] Build and boot SK-AM64B Jammy CLI/Standard on Current(v6.1) and Edge(v6.6) kernels [ ] Build and boot SK-TDA4VM Jammy CLI/Standard on Current(v6.1) and Edge(v6.6) kernels Further, the functionalities of new boards were tested by: [ ] Build and boot SK-AM68 Jammy CLI/Standard on Current(v6.1) and Edge(v6.6) kernels [ ] Build and boot SK-AM69 Jammy CLI/Standard on Current(v6.1) and Edge(v6.6) kernels [ ] Gbit Ethernet works [ ] USB 3.0 ports work Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
Recommended Posts