The reason of bpmp_trywait happened?

Dear all

1: In JetPack4.6_R32.6.1, our customed board loss connect after several days when running our AI model.

2:  When found that  in syslog,  bpmp_trywait happened, then the device dead.

3: There are  part log of bpmp

4: this whole syslog file ,  I can not find  related reason in this log file. 

syslog.1 (57.0 MB)

5: bpmp is related to boot and power manager, so  may refer to hardware? 

What may caused bpmp_trywait failed ? Or which direction should we go to troubleshoot this problem?

Thank you very much!!! Best regards!!!

It seems like partitions are crashed. Could you re-flash and check if it can be revived?

After that, we reboot the device.
How to reflash it ? Like that : sudo ./ p3509-0000+p3668-0001-qspi-emmc external ?
And how to revived it ?

Is this still an issue to support? Any result can be shared? Thanks

Yes, it is still an issue.
And could you tell me how to reflash or how to revived it? I don’t quite understand about what reflash or revived refer.

Thank you very much.

For flashing Xavier NX developer kit, the command is:

~/nvidia/nvidia_sdk/JetPack_4.6.2_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra$ sudo ./ jetson-xavier-nx-devkit-emmc mmcblk0p1

The custom boards may have different design and the command can be different. If your rootfs is on external storage like NVMe SSD, you should use initrd.

Thank you , I know how to reflash device. So bpmp related problem can be resolved by reflash.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.