Following Getting Started with reComputer Industrial | Seeed Studio Wiki we’ve been able to properly setup our reComputer devices (Industrial J4012). We repeatedly need to change settings for each new device and thought it would be faster to create an image. However, using
sudo ./l4t_create_images_for_kernel_flash.sh
we’re not managing to create an image. We’ve noticed that certain files are missing. At some point the file references flash.sh which is not present in the tar file linked on the wiki. We’ve copied it from the nvidia sdk, but then we run into issues with the chipid.
Does someone know what steps need to be taken to create an image of your reComputer, and how to flash this to another device of the same kind (Industrial J4012)?
In theory, you should be able to successfully flash the image for the reComputer Industrial by following the steps without needing to recreate the image file. Regarding your issue, I would like to clarify a few points:
What version of JetPack are you flashing?
What do you mean by “non-existent file”? Could you please provide a screenshot of that part?
Please send us your flash log for us to review.
Thank you in advance for your cooperation, as this will help us assist you better!
We are able to flash our devices according to your manual [wiki.seeedstudio]/reComputer_Industrial_Getting_Started/#flash-jetpack (can’t include links), no issues there. However, after this, we change additional settings, install software, set IPs for the ethernet ports, etc. We would like to create something like an image of this prepped device, such that we can flash a new device with this new image, and we don’t have to do all the extra steps again.
We use jetpack 6.0. I can’t reproduce the steps for point 2 as fast as it has been a while since I’ve tried, but I’ll try if it seems necessary. As for point 3, there are no issues with flashing whilst following your manual. I hope the above explanation helps clear up what we’re trying to achieve, and you already have some good pointers.
/home/bpa/Desktop/flash_jetson/j4012/mfi_recomputer-industrial-orin-j201/recomputer-industrial-orin-j201.conf: line 29: /home/bpa/Desktop/flash_jetson/j4012/mfi_recomputer-industrial-orin-j201/p3768-0000-p3767-0000-a0.conf: No such file or directory
/home/bpa/Desktop/flash_jetson/j4012/mfi_recomputer-industrial-orin-j201/recomputer-industrial-orin-j201.conf: line 29: /home/bpa/Desktop/flash_jetson/j4012/mfi_recomputer-industrial-orin-j201/p3768-0000-p3767-0000-a0.conf: No such file or directory
Error: /home/bpa/Desktop/flash_jetson/j4012/mfi_recomputer-industrial-orin-j201/flash.sh is not found
This l4t_create_images_for_kernel_flash.sh generally doesn’t apply to custom carrier boards. We actually host our source, check Linux_for_Tegra. We understand that you want to made some modifications to the jetpack we made, please check the repo see if you can find something useful.
General idea is, you need to chroot to the rootfs folder (after setting up qemu-aarch64-static) and you may operate inside, installing the software you want, change the configurations and leave this chroot environment.
If you have special flash requirements, you may contact our techsupport for image customization.