If I need to summarize the issue, we cannot “restore” the “backup” image of the Orin NX cards we previously purchased to the new cards. However, the old batches of these cards can do this among themselves. In the new Orins, according to version 5.1, we can neither flash (1) nor backup-restore, but in different versions, these can be done. We do not want to proceed with two different configurations.
Our suspicion about this issue is that we realized that the new Orin Nx’s cannot do it due to a problem caused by DRAM differentiation. Please confirm this from the log file we will provide below.
We are waiting for a solution from you about this.
I have already done this. There are two main issue for that. First, I have already configured all previous Orin Nx in field via JP 5.1. Secondly, I tried flash and later restore/backup process with JP 5.1.2 and we confirmed all new Orin Nx. But, we want to progress with old Orin Nx versions, and we don’t want to be two different configuration.
The main problem is that we cannot flash the new Orin Nx with JP 5.1 and restore/backup.
Not sure if this is still an issue, for new module with old SW flash issue, that seems to be impacted by the PCN, please check * Jetson PCN Summary to find the overlay patch to get it a try. Thanks
Unfortunately, I created new flash configuration due to new DRAM model. It is not a good thing to differentiate the production process with such changes in an industrial sense. While these systems, especially those operating on edge devices, should be stable, applying changes to each product differentiation also affects the process. I have already spent nearly 3 weeks to find the cause of this problem. We spent more time than we expected while reorganizing software tools etc. regarding this and it caused our production processes to be delayed. We expect more sensitivity in these matters. Instead of releasing a new product every year, it would be more industrial to release a product after sufficient R&D is done.
