Now it does not turn on due to, I suppose, problems with the kernel (after installing SDK components via SDK manager, they accidentally installed linux4t or another kernel along with the header). After rebooting, it immediately enters force recovery mode
Any action, even an attempt to completely overwrite the image, does not help. We would be able to fully format because the device itself is important. There are no and never will be access keys( because we by accident deleted them ), so, unfortunately, we won’t be able to specify the key as a parameter when using the flash.sh script
your platform did not fused while you assign --no-burn options to the fuse script,
i.e. $ sudo ./odmfuse.sh --noburn -i 0x19 -c PKC -p -k rsa.pem jetson-xavier.
Yes, the device was flashed twice and worked at all times. Then we flashed one of our scripts, which worked on a non-secure boot rootfs system, system install something related with Linux-4t-headers and other kernels’ components. After this, we can not do something with the device.
BTW,
since there’s error reported about reading board information,
you may also look into flash configuration file, i.e. p2771-0000.conf.common,
there’s process_board_version() function to parse board information. you may add those board version to your flash commands.
thanks
I have tried solutions from Topic 123506 and some addition from there like these. Also I tried the version from 32.3.1. A mistake is the same.
Here some new issue then I tried to do these steps on 32.4.3:
cd rootfs && sudo tar xvf ../../SamplerootFileSystem...
cd .. && sudo ./apply_binaries.sh
sudo BOARDID=2888 FAB=400 BOARDSKU=0004 BOARDREV=K.0 ./odomfuse-chaned.sh --noburn -i 0x19 -c PKC -p -k ./rsa.pem jetson-xavier
Here screenshot of this fail. jetson was in recovery mode