BSP-Yocto-AM62x-PD23.1.1                        2023-07-21
==========================================================

- Linux TI vendor kernel v5.10.168 (based on TI tag 08.06.00.007)
- U-Boot v2021.01 (based on TI tag 08.06.00.007)
- Yocto 3.1.25 (dunfell)


Tested Yocto Images:
--------------------

- phytec-qt5demo-image:
  * phyboard-lyra-am62xx-1 (deprecated)
- phytec-qt5demo-image
  * phyboard-lyra-am62xx-2
- phytec-qt5demo-image
  * phyboard-lyra-am62xx-3


Build Environment:
------------------

- Ubuntu 20.04 64-bit


Features:
---------

- New machine phyboard-lyra-am62xx-3 for TI's
   High Security-Field Securable (HS-FS) SoCs.


Issues Fixed:
-------------

- BSP does not boot if the Hardware Introspection image is not
   flashed to the EEPROM


Known Issues:
-------------

See BSP-Yocto-AM62x-PD23.1.0


BSP-Yocto-AM62x-PD23.1.0                        2023-04-21
==========================================================

- Linux TI vendor kernel v5.10.158 (based on TI tag 08.06.00.002)
- U-Boot v2021.01 (based on TI tag 08.06.00.002)
- Yocto 3.1.23 (dunfell)


Tested Yocto Images:
--------------------

- phytec-qt5demo-image:
  * phyboard-lyra-am62xx-1 (deprecated)
- phytec-qt5demo-image
  * phyboard-lyra-am62xx-2


Build Environment:
------------------

- Ubuntu 20.04 64-bit


Features:
---------

- Switched to PHYTEC yogurt distro and phytec-qt5demo-image
- New machine phyboard-lyra-am62xx-2 (PBA-C-24.A1, PCM-071.A1)
- New device tree overlay for co-processors (RPMSG)
- New device tree overlay for GPIO fan
- New device tree overlays for SoM variant handling
- CAN support
- TPS65219 PMIC support
- u-boot updates
  * Storage device gets determined based on boot device
    For SDMMC and EMMC stored on the boot partition (ENV_IS_IN_FAT)
    For SPI stored on a fixed offset on the SPI NOR flash
  * SoM hardware detection code in u-boot (not active)
  * New DDR settings with extended temperature range + lower tREFI
  * Switched from partition UUIDs to fixed devices usage
    Booting from EMMC mounts rootfs via /dev/mmcblk0
    Booting from SDMMC mounts rootfs via /dev/mmcblk1
  * OSPI NOR flash boot


Issues Fixed:
-------------

- OSPI NOR flash boot
- CAN


Known Issues:
-------------

- If the EEPROM on the SoM is not programmed for hardware detection,
  you may see a message in u-boot that says
    phytec_eeprom_data_init: EEPROM data is all zero. Erased?
    phytec_eeprom_data_setup: EEPROM data init failed
- Bluetooth is non functional
- The flashcp command occasionally fails during the verification step
- The reboot command delays the reboot process by several seconds in 3% of all boots
- The kernel fails to allocate a USB device on usb1-port1 in 3% of all boots