Hello,
I have several systems that are in deployment and are regularly reprogrammed with new firmware every few weeks.
Some of the systems implement SecureBoot and some do not,
So each time a system need to get updated the our custom update script first attempts to read the info like so:
./flash --read-info jetson-xavier-nx-devkit-emmc internal
In order to figure out if the systems Boot Authentication: is set to SBKPKC or NS.
After the script figures this out it will do flash accordingly.
If SBKPKC than flash command is:
sudo ./flash.sh -u ./rsa_keys/rsa3k.pem -v ./rsa_keys/sbk.key jetson-xavier-nx-devkit-emmc internal
Otherwise we use:
sudo ./flash.sh jetson-xavier-nx-devkit-emmc internal
The problem is that after the script runs the:
./flash --read-info jetson-xavier-nx-devkit-emmc internal
any other commands that follow either hangs forever or fails with a timeout error like so:
###############################################################################
# L4T BSP Information:
# R35 , REVISION: 5.0
# User release: 0.0
###############################################################################
ECID is
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.
Only if I do the reset to recovery manually between the read-info and full flash command it will start to communicate again and allow to program.
We have tried several commands with flash/tegraflash etc. they are an attempt to place the unit back in recovery mode but we could not find a command that does that, all hang or fail.
Is there a way using the flash.sh script of any other script or command that will allow us to place the target in recovery mode again without the need to power cycle it an manually and do a recovery reset manually again ?
Thanks
Amir