The VMware segment changed, so the VM moved from 192.168.223.128 to
192.168.154.128 and every hardcoded reference was stale. A freshly-installed
VM also has neither sshd nor the toolchain, which previously only surfaced
half-way through a modify_imx6 iteration.
- fpga-imx6-flow: new "VM prerequisite check" section -- how to detect a
missing sshd (Connection refused) and reach the guest over vmrun/VMware
Tools when SSH is impossible, plus the Yocto SDK install + ARM-ELF
verification step. Records the real gotchas hit during install:
unattended-upgrades holding the dpkg lock, EOL xenial repos, and CRLF
breaking scripts pushed into the guest.
- smod_atsc_dev SKILL/imx6.md: refer to CROSS_VM_HOST/USER/PASS, no literal IP.
- imx6_app.py: drop the stale 192.168.223.128 default so a missing
CROSS_VM_HOST fails loudly instead of dialing the wrong host.
Machine-local values (IP, credentials, vmx/vmrun paths, toolchain prefix)
live in ~/skills_env.md, which stays out of git.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The Vivado install root differs per machine (C:\Xilinx here, D:\Xilinx on the
box these skills were written on), so every hardcoded path was already wrong
on this machine.
- new fpga_flash/scripts/vivado_env.py: resolves --vivado-dir > env var >
VIVADO_ROOT (falling back to VIVADO_PATH) from ~/skills_env.md
- gen_mcs / program_flash / check_flash_csv: --vivado-dir now optional
- fpga_update/gen_update_mcs.py: same precedence for --vivado
- fpga_flash / smod_atsc_dev / vivado-prj-create SKILL.md: document the
lookup instead of naming a drive letter
- skills_env template: VIVADO_ROOT/VIVADO_PATH are now blanks to fill in,
so a new machine can't inherit a wrong default
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
bowei