summaryrefslogtreecommitdiff
path: root/include/env/phytec
AgeCommit message (Collapse)Author
2025-08-11include: env: phytec: k3: Add deprecation warning to legacy boot flowWadim Egorov
We switched towards standard boot with still keeping a fallback using legacy boot command alive. Add a deprecation warning to make it more clear that we will remove it in future versions. Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
2025-08-11board: phytec: phycore-am62x: Add watchdog start to bootcmdWadim Egorov
Allows run-time control over watchdog auto-start and the timeout via setting the environment variable watchdog_timeout_ms. A value of zero means "do not start". Use CONFIG_WATCHDOG_TIMEOUT_MSECS as initial value. Users can enable the watchdog to monitor the boot process until userspace or OS takes over to serve the watchdog. Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
2025-05-07include: env: phytec: k3_net: Use get_cmdDaniel Schultz
'net_fetch_cmd' is not defined by the K3 board files. They use the more common 'get_cmd' from NXP products. Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2025-05-07include: env: phytec: k3_net: Remove net_apply_extensionsDaniel Schultz
Extensions are now handled by the board-code. Remove this non-existing function to proper boot from network. Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2025-03-18board: phytec: phycore_am62x: Use custom k3_dfu.env fragmentWadim Egorov
TI's k3_dfu.env includes redundant dfu_alt_info_* data, some of which is incompatible with our board configuration. Replace it with a custom variant that better aligns with our setup, ensuring correct offsets and eliminating unnecessary entries. Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
2025-02-10include: env: phytec: Add optargs to K3 filesNathan Morrisson
Add the optargs variable so that we can set optional arguments while booting. Signed-off-by: Nathan Morrisson <nmorrisson@phytec.com> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2024-09-10include: env: phytec: Add K3 boot logic for OSPI/QSPI flashesDaniel Schultz
This boot logic allows to boot a Kernel image, Device-Tree blob and a initramfs from an external OSPI/QSPI NOR flash. Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2024-09-10include: net: phytec: Add K3 network boot logicDaniel Schultz
This boot logic allows to boot a Kernel image, Device-Tree blob and overlays via tftp/dhcp (configurable with 'net_fetch_cmd'). Additionally, it loads a rootfs via NFS. Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2024-09-10include: env: phytec: Add raucinit to k3_mmc environmentDaniel Schultz
Initialize the environment for booting an RAUC image when 'doraucboot' is set to 1. Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2024-09-10include: env: phytec: k3_mmc: Rename variablesDaniel Schultz
Add a mmc prefix to 'loadimage' and 'loadfdt' because we need similar variables for other boot sources. This will prevent name clashes and allows to implement similar boot logic. Also switch from loadaddr to kernel_addr_r. Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2024-07-22include: env: phytec: k3_mmc: Apply overlays during bootDaniel Schultz
Include the overlays.env file and run the apply routine before booting the Kernel. Signed-off-by: Daniel Schultz <d.schultz@phytec.de> Reviewed-by: Wadim Egorov <w.egorov@phytec.de>
2024-07-22include: env: phytec: Add common mmc boot for K3 SoMsDaniel Schultz
This environment include can be used to boot from a MMC device for PHYTEC's K3-based SoMs. Signed-off-by: Daniel Schultz <d.schultz@phytec.de> Reviewed-by: Wadim Egorov <w.egorov@phytec.de>
2024-07-22include: env: phytec: renaming of variables according to bootstd docBenjamin Hahn
Rename existing environment variables according to the bootstd doc. Renamed variables are fdto_addr, bootenv_addr, fdt_addr. Signed-off-by: Benjamin Hahn <B.Hahn@phytec.de> Signed-off-by: Daniel Schultz <d.schultz@phytec.de> Reviewed-by: Wadim Egorov <w.egorov@phytec.de>
2024-07-22include: env: phytec: Create env file for loading and applying overlaysBenjamin Hahn
The env scripts for loading and applying overlays are identical for many PHYTEC Boards. Create a common env that can be included. The env variables bootenv_addr and fdto_addr are board specific and need to be set in the board specific file. The env variable get_cmd also needs to be set in board specific files and can be set to tftp or dhcp. Signed-off-by: Benjamin Hahn <B.Hahn@phytec.de> Signed-off-by: Daniel Schultz <d.schultz@phytec.de> Reviewed-by: Teresa Remmet <t.remmet@phytec.de> Reviewed-by: Wadim Egorov <w.egorov@phytec.de>
2024-03-17include: env: Add phytec RAUC boot logicLeonard Anderweit
Add logic for booting systems with the RAUC update mechanism. This can be reused by other phytec boards. Signed-off-by: Leonard Anderweit <l.anderweit@phytec.de> Tested-by: Teresa Remmet <t.remmet@phytec.de>