I’ve generated the massflash package with the l4t_initrd_flash.sh script.
It created a folder starting with “mfi_” inside the root directory of the l4t bsp.
My board config has been copied, but the files it references are not inside that folder.
Despite the mfi folder containing a tools/kernel_flash directory I can not run the l4t_initrd_flash.sh file from there. Files are missing.
The documentation tells me to still use the massflash command with the script from the normal tools folder.
Does the MFI folder contain all data required to flash the board standalone if I just tar them?
How can I flash with it then?
I’d like to move the package to a production pc.
Well, the conf file which is used in the target conf is not copied, so it complains that it doesn’t exist.
If I add the file it says:
Log will be saved to Linux_for_Tegra/initrdlog/flash_1-1_0_20230508-060545.log
Ongoing processes: 4263
In fact I found the file here instead: mfi_p3509-0000+p3668-nvme/initrdlog/flash_1-1_0_20230508-060545.log
I can copy the mfi folder somewhere else and it will work.
As soon as I move the Linux_for_Tegra folder somewhere else it fails to flash since the flash command references files which are not in the mfi folder:
I was hoping that the package geneterated for massflash would be standalone.
Otherwise there is not really a use of placing it in a separate folder and making copies of files which are in the L4T directory anyway.
We can of course use a copy of the L4T folder, but it is 53GB in my case and that will cause some issues. Please add a way of creating a tar file which can be copied to a production machine for flashing which is much smaller.
Maybe there is a misunderstanding due to an undocumented feature. I did not see a tarball, just a folder. Where will the tarball be located? I used the same command as you just with 10 instances instead of 5.
Yeah you were right. There is a tar.gz file.
It has the same content as the folder which I was using.
So it is missing referenced conf files and does not work anymore as soon as I rename my original BSP folder as the flash command referenced the xml partition file for the NVMe directly by its absolute path. So that will not work :(