Merge pull request #39 from WallaceIT/am62p-support

Add TI AM62Px to supported SOCs

docs/board_setup.md

@@ -49,7 +49,7 @@ booting from FEL mode. On some models, this will happen automatically. On
 others, further setup is required. We recommend that you check your board
 vendor's user guide.
 
-## TI AM62x / TI AM62Ax
+## TI AM62x / TI AM62Ax / TI AM62Px
 
 Connect the USB device port to your host PC. Power your board, making sure that
 the SoC is configured to boot from DFU. The SoC can also fall back to DFU if all

docs/fw_binaries.md

@@ -229,7 +229,7 @@ SPL part, you can typically use u-boot.img for this
 configuration:
  * path
 
-## For TI AM62x/AM62Ax devices
+## For TI AM62x/AM62Ax/AM62Px devices
 
 [example](../src/snagrecover/templates/am625-beagle-play.yaml)
 
@@ -245,8 +245,13 @@ for building the required images. The instructions for building the binaries are
 board-specific. When building the images please make sure to use the USB DFU defconfig for
 Snagrecover and SD Boot defconfig for Snagflash.
 
+**AM62Px:** Please refer to
+[this documentation](https://software-dl.ti.com/processor-sdk-linux/esd/AM62PX/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html#build-u-boot)
+for building the required images. The instructions for building the binaries are
+board-specific. When building the images please make sure to use the USB DFU defconfig for
+Snagrecover and SD Boot defconfig for Snagflash.
 
-AM62x/AM62Ax SoCs require multiple complex firmware images to boot.
+AM62x/AM62Ax/AM62Px SoCs require multiple complex firmware images to boot.
 
 **tiboot3:** X.509 certificate container with U-Boot SPL for R5, TIFS, and a FIT
 container with device tree blobs. If you change U-Boot's USB VID/PID, you should

src/snagrecover/supported_socs.yaml

@@ -11,6 +11,8 @@ tested:
         family: am62x
   am62a7:
         family: am62x
+  am62p:
+        family: am62x
   h3:
         family: sunxi
   imx28: