Cp: cannot stat bug in flash.sh for AGX Xavier L4T 32.5.1

Hello all,

I’m trying to modify and reflash the initramfs on a Jetson AGX Xavier devkit running L4T 32.5.1.

I followed the instructions here How to modify L4T-INITRD for Xavier?
and here Custom initramfs on Jetpack 3.2 for TX1

got the jetpack BSP, untar, got the rootfs sample, untar, apply binaries, modify my l4t_initrd.img, repackage it and put it in bootloader folder.

launch the command

And I got this result

[   0.7185 ] tegrahost_v2 --chip 0x19 0 --updatesigheader 1_boot_sigheader.img.encrypt 1_boot_sigheader.img.hash zerosbk
[   1.0939 ] 
[   1.1231 ] Signed file: /home/perceval/workspace/FOTA_Xavier/Linux_for_Tegra/bootloader/temp_user_dir/boot_sigheader.img.encrypt
l4t_sign_image.sh: Generate header for boot_sigheader.img.encrypt
l4t_sign_image.sh: chip 0x19: add 0x27a8800 to offset  0x8 in sig file
l4t_sign_image.sh: Generate 16-byte-size-aligned base file for boot_sigheader.img.encrypt
l4t_sign_image.sh: the signed file is /home/perceval/workspace/FOTA_Xavier/Linux_for_Tegra/bootloader/temp_user_dir/boot_sigheader.img.encrypt
done.
Making recovery ramdisk for recovery image...
Re-generating recovery ramdisk for recovery image...
/home/perceval/workspace/FOTA_Xavier/Linux_for_Tegra/bootloader/ramdisk_tmp /home/perceval/workspace/FOTA_Xavier/Linux_for_Tegra/bootloader /home/perceval/workspace/FOTA_Xavier/Linux_for_Tegra
30402 blocks
_BASE_KERNEL_VERSION=4.9.201-tegra
cp: cannot stat '/home/perceval/workspace/FOTA_Xavier/Linux_for_Tegra/rootfs/usr/bin/w': No such file or directory
failed command: cp -fv /home/perceval/workspace/FOTA_Xavier/Linux_for_Tegra/rootfs/usr/bin/w /home/perceval/workspace/FOTA_Xavier/Linux_for_Tegra/bootloader/ramdisk_tmp//bin/w

/home/perceval/workspace/FOTA_Xavier/Linux_for_Tegra/rootfs/usr/bin/w is pointing to /etc/alternative/w which does not exist on my host.
I tried to add the -P option in the script ota_make_recovery_img_dtb.sh without any success.

Could you help me?
thank you

Perceval

So I manage to get it working with a simple sudo rm w && sudo ln -s w.proc w

Glad to know issue resolved!