But if before flash we disconnect board and reconnect it in force recovery mode and then flash it the device will boot without issue.
Now my question:
Is there a command that I can add to our script that reboot device to Force Recovery Mode? I triedtegrarcm_v2 with arguments --boot, --reboot and --oem without success.
may I know what’s the results after burn and flash since you’ve already in the forced-recovery mode?
anyways, please give it a try with… tegrarcm_v2 --reboot recovery
A random detail you might find of interest: You cannot run two flash commands or operations in a row without reentering recovery mode (a flash has a lot of commands in it, but I am speaking of one operation completes, and then the user starts another operation; cycle power while holding the recovery pins between operations).
Hello JerryChang,
after burn we are in Force Recovery Mode and after flash device boot successfully.
Maybe I am not clear enough. So I explain the situation again:
Steps that create error cbb@2300000:
0- connect jumper to device pins and turn on it in Force Recovery Mode
1- burn device
2- As current installed L4T keys are not same as those that we used in burn phase so system can not boot and is in Force Recovery Mode
3- flash device
4- after flash device will reboot automatically but we will see lots of cbb@2300000 that needs workaround about audio_adsp.
Steps that has not error cbb@2300000:
0- connect jumper to device pins and turn on it in Force Recovery Mode
1- burn device
2- As current installed L4T keys are not same as those that we used in burn phase so system can not boot and is in Force Recovery Mode 3- Turn off device and then turn on device so it goes again to Force Recovery Mode
4- flash device
5- after flash device will reboot automatically and without errorcbb@2300000
we usually press the hardware keys (forced-recovery+reboot) every time for image flashing.
hence, it’s suggested to follow Topic 315436, comment #24 to workaround by disabling asdp node.
Most flash commands are a “compound” set of commands. Obviously those don’t reboot in the middle of flash. However, many of the overall tasks you do cannot occur two in a row without restarting recovery mode. They will fail. Why not just test one of the failure cases? Is it not the case that the first operation works, and the second operation is the one that fails? If it suddenly works for the case of restarting between operations, then you have the answer.
Hi,
As you said I checked and both burn and flash process call reboot at the end of their procedure so it seems issue is not about reboot between flash and burn. I think maybe its because jumper between FC REC and GND is connected all the time.
The jumper is not needed, and should not remain connected, once in recovery mode. That jumper is like the shift key on a keyboard when trying to type a capital letter: Hold the button down, tap the button to be modified, and then let go. Recovery mode modifies either power on or power reset. If that pin is shorted to ground during any change in power state, then you are in recovery mode and the pin should then no longer be shorted.