PCIE link resets, which fails flashes

I get this persistent error while flashing …This makes flashing fail. I just got one success till now

[ 70.731541] pcieport 0004:00:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 70.731543] pcieport 0004:00:00.0: device [10de:229c] error status/mask=00000001/0000e000
[ 70.731546] pcieport 0004:00:00.0: [ 0] RxErr
[ 70.731554] pcieport 0004:00:00.0: AER: Uncorrected (Fatal) error received: 0004:00:00.0
[ 70.731562] pcieport 0004:00:00.0: PCIe Bus Error: severity=Uncorrected (Fatal), type=Transaction Layer, (Receiver ID)
[ 70.731563] pcieport 0004:00:00.0: device [10de:229c] error status/mask=00000020/00400000
[ 70.731565] pcieport 0004:00:00.0: [ 5] SDES (First)
[ 70.731571] pci 0004:01:00.0: AER: can’t recover (no error_detected callback)
[ 70.939077] pcieport 0004:00:00.0: AER: Root Port link has been reset (0)
[ 70.939089] pcieport 0004:00:00.0: AER: device recovery failed

Is this on custom board or NV devkit?

custom board

Please review hardware design. Previous cases with such error are all coming from hardware.

OK let me review the hardware

the error seems to be software not hardware. Flash fails every time on jetpack 6.1 while gets once flashed on jetpack 5.1.2. sharing the logs in a while

I already explained this multiple times in your previous topic.

If same NVMe could be flashed on PCIe C4 of NV devkit but failed on your board, then this is probably an issue from your hardware.

I really don’t know what is your exact request that you want us to do here. There is not much thing to configure in software. Software is not something magical that you could configure everything there.

Are you able to capture PCIe LA trace by using PCIe analyzer? I guess you already told us not possible. If so, then I can only ask you to review you hardware.

1 Like

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