Jump to content

Andrei Aldea

Members
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hey Sam, busy week so only getting around to replying - yes there are pre-built images for it but we took them down because I wasn't happy with the state it was in. We have a patch we're cleaning up that add the packages for GPU Acceleration and Wifi/BT that we're going to merge today/this weekend so I will re-enable the image generation and it will show up under Supported boards tomorrow/Sunday. If you do end up getting it and trying it out feel free to reach out here or on discord and let me know if you run into anything.
  2. Hey Tobias, Indeed there aren't many examples but to point you in the right direction: TI offers a web tool that you can also download called Sysconfig that lets you generate DTS files so you can find the right pin files (you'll need to match your config parameters with EVM schematic) https://www.ti.com/tool/SYSCONFIG You'll want to select Device (not Software Product) and click start.... Then you can add a SPI node and match your pins etc, and you'll see it generates a device tree.dtsi files with the right pins for you. Something like this - From there, to enable Spidev itself I would look at examples from BeagleBoard like this and adjust for your needs, this should give you the spidev node- https://openbeagle.org/beagleboard/BeagleBoard-DeviceTrees/-/blob/v6.12.x-Beagle/src/arm64/overlays/k3-am67a-beagley-ai-spidev0.dtso?ref_type=heads Note - you might notice some oddity with "compatible = "rohm,dh2228fv";" - That's one of those weird things about embedded Linux, my understanding is that the Spidev maintainers don't really want you to just attach "any" device, they want you to specify the exact device that SPI will be connected to but if you'r developing you can use some of those older drivers to kind of force it to be have generically. Let me know if that helps
  3. The main difference between the two is AM62B uses DDR4 and AM62-LP uses LPDDR4 - also AM62-LP uses the AMC package device. Anyway, I think because the board is so old it probably used GP vs HS-FS silicon like the modern boards so you need to adjust the config file to include something like this - TIBOOT3_FILE="tiboot3-am62x-gp-evm.bin" TISPL_FILE="tispl.bin_unsigned" UBOOT_FILE="u-boot.img_unsigned" So this config should work - it uses the GP silicon version of the images. BeaglePlay is the only current production AM62x board with GP silicon. BOARD_NAME="SK-AM62-LP" BOARDFAMILY="k3" BOARD_MAINTAINER="nobody" BOOTCONFIG="am62x_evm_a53_defconfig" BOOTFS_TYPE="fat" BOOT_FDT_FILE="ti/k3-am625-lp-sk.dts" TIBOOT3_BOOTCONFIG="am62x_lpsk_r5_defconfig" TIBOOT3_FILE="tiboot3-am62x-gp-evm.bin" TISPL_FILE="tispl.bin_unsigned" UBOOT_FILE="u-boot.img_unsigned" DEFAULT_CONSOLE="serial" HAS_VIDEO_OUTPUT="no" KERNEL_TARGET="edge" SERIALCON="ttyS2" ATF_BOARD="lite"
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines