search

OE4T / meta-tegra

BSP layer for NVIDIA Jetson platforms, based on L4T
MIT License
413 stars 228 forks source link

flash xavier problem #901

Closed vovachernin closed 2 years ago

vovachernin commented 2 years ago

hi! i compiled yocto image and when i flash it like ./deploy.sh core-image-sato-dev jetson-agx-xavier-devkit I get "ERR: could not retrieve chip ID" and flashing failed I checked at 2 different Jetson Xaviers the same result

To Reproduce Steps to reproduce the behavior:

  1. Build dunfell-l4t-r32.5.0q branch '...' wit
  2. h MACHINE based on 'jetson-agx-xavier-devkit'
  3. Build with bitbake argument ' bitbake core-image-sato-dev'
  4. Deploy to hardware recovery mode with './deploy.sh core-image-sato-dev jetson-agx-xavier-devkit' Using temp directory /tmp/tmp.NcFAhQuigN /tmp/tmp.NcFAhQuigN ~/work/yocto-tegra ./ nvflashxmlparse mkbootimg boot.img tegra194-a02-bpmp-p2888-a04.dtb mksparse preboot_c10_prod_cr.bin nvtboot_recovery_cpu_t194.bin tegrarcm_v2 tegra19x-mb1-prod-p2888-0004-e3900-0000.cfg mkgpt tegrabct_v2 cboot_t194.bin tegra194-mb1-bct-reset-p2888-0000-p2822-0000.cfg tegra194-a02-bpmp-p2888-a04-maxn.dtb tegra194-a01-bpmp-p2888-a01.dtb core-image-sato-dev.ext4 tegraparser_v2 tegra194-memcfg-sw-override.cfg tegra19x-mb1-pinmux-p2888-slvs-0000-a00-p2822-0000-a00.cfg tegra194-a02-bpmp-p2888-a01.dtb slot_metadata.bin camera-rtcpu-rce.img tegra194-a02-bpmp-p2888-a02.dtb preboot_d15_prod_cr.bin tegrahost_v2 tegra19x-mb1-pinmux-p2888-0000-a04-p2822-0000-b01.cfg tegra19x-mb1-pinmux-p2888-0000-p2822-0000.cfg tegra194-mb1-uphy-lane-p2888-0000-p2822-0000.cfg bpmp_t194.bin jetson-agx-xavier-devkit.cfg jetson-agx-xavier-devkit-override.cfg tegra19x-mb1-bct-device-qspi-p3668.cfg tegra194-a02-bpmp-p2888-as-galen-8gb.dtb tegra194-flash-helper.sh tegra194-mb1-bct-memcfg-8gb-p2888-128bit.cfg tegraflash_internal.py tegra194-mb1-bct-memcfg-p2888.cfg tegraflash.py tegra194-mb1-bct-pmic-p2888-0001-a02-p2822-0000.cfg tegra19x-mb1-padvoltage-p2888-0000-p2822-0000.cfg generate_bup_payload.sh tegra19x-mb1-pinmux-p2888-0000-a00-p2822-0000-a00.cfg tegra194-mb1-bct-gpioint-p2888-0000-p2822-0000.cfg doflash.sh tos-trusty_t194.img tegra19x-mb1-pinmux-p3668-a01.cfg tegra194-mb1-bct-ratchet-p2888-0000-p2822-0000.cfg tegradevflash_v2 tegra194-a02-bpmp-p2888-0004-a04-mccoy.dtb tegra19x-mb1-pinmux-p2888-0004-e3900-0000.cfg nvtboot_t194.bin odmsign.func tegra19x-mb1-prod-p2888-0000-p2822-0000.cfg tegra194-a02-bpmp-p3668-a00.dtb tegra194-br-bct-qspi.cfg tegrasign_v2 tegra194-mb1-bct-gpioint-p3668-0001-a00.cfg bmp.blob gen_tos_part_img.py tegra194-mb1-bct-misc-l4t-maxn.cfg tegra194-a02-bpmp-p2888-as-p3668.dtb tegra19x-mb1-padvoltage-p3668-a01.cfg tegra194-mb1-bct-reset-p3668-0001-a00.cfg nvtboot_applet_t194.bin spe_t194.bin sw_memcfg_overlay.pl flash.xml.in tegra194-mb1-bct-scr-cbb-mini-p3668.cfg tegra19x-mb1-padvoltage-p2888-0004-e3900-0000.cfg mb1_t194_prod.bin mts_c10_prod_cr.bin mce_c10_prod_cr.bin tegra194-mb1-bct-misc-l4t.cfg tegra194-mb1-bct-pmic-p2888-0001-a04-E-0-p2822-0000.cfg cbo.dtb tegra194-mb1-bct-pmic-p2888-0001-a04-p2822-0000.cfg l4t_sign_image.sh tegra186-flash-helper.sh tegra194-p2888-0001-p2822-0000.dtb tegra194-mb1-bct-pmic-p2888-0001-a01-p2822-0000.cfg tegra194-mb1-soft-fuses-l4t.cfg eks.img nv_smd_generator tegra19x-mb1-bct-device-sdmmc.cfg l4t_bup_gen.func tegra194-mb1-bct-pmic-p3668-0001-a00.cfg pkc/ pkc/nvsecuretool pkc/mkpkc xusb_sil_rel_fw tegra194-br-bct-sdmmc.cfg warmboot_t194_prod.bin tegra19x-mb1-padvoltage-p2888-0000-a00-p2822-0000-a00.cfg make-sdcard BUP_generator.py nvtboot_cpu_t194.bin adsp-fw.bin nvtboot_recovery_t194.bin tegra194-mb1-bct-misc-flash.cfg tegra194-mb1-bct-memcfg-derated-p2888.cfg rollback/ rollback/t19x/ rollback/t19x/rollback.cfg rollback/rollback_parser.py flashvars tegra194-mb1-bct-scr-cbb-mini.cfg BMP_generator_L4T.py chkbdinfo tegrakeyhash tegra194-mb1-bct-memcfg-p3668-0001-a00.cfg tegra194-a01-bpmp-p2888-a02.dtb bsp_version tegra19x-mb1-prod-p3668-0001-a00.cfg tegra194-a02-bpmp-p2888-0006-a04.dtb ERR: could not retrieve chip ID ----------------------------------------? why its fails here?
madisongh commented 2 years ago

Have you looked at this wiki page on the flashing process? When the script exits that early, it's usually a fairly basic setup problem.

Make sure you either use sudo or set up udev rules on your development host to allow for non-root access to the USB device.

Make sure you're using a good-quality USB cable connected directly to your development host.

Make sure the device is in recovery mode.

madisongh commented 2 years ago

This issue was resolved in the Slack channel, but for future reference the problem turned out to be a conflict between the NVIDIA flashing tools and another package on the development host. See this NVIDIA developer forum topic for more information.