ERROR: might be timeout in USB write - JP 5.1.1

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
,
1

Hi,
We had received a bunch of AGX Orin 32GB SOMs. We could not able to flash our build from source BSP onto one of the SOMs. We had successfully flashed the all other SOMs.

We are getting USB timeout error(log attached). We had tried disabling the USB autosuspend and tried with other Ubuntu 20.04 host PC too. But unfortunately we could not resolve it.
Expecting some guidelines regarding this issue.

FlashFailedLog.txt (70.9 KB)

Thanks.

3

We had tried flashing JP 5.1.1 using sdkmanager where could able to flash the default BSP. But we could not flash the build from source BSP.
We seen this behaviour in only one SOM, all other SOMs successfully got flashed.
Commad for flash: sudo ./flash.sh jetson-agx-orin-xxx-xxx mmcblk0p1

4

What does that mean build from source BSP? What source did you modify?

Does default BSP able to flash that only one problematic module?

5

What does that mean build from source BSP? What source did you modify?

I mean to say that we had downloaded the JP 5.1.1 source code and applied kernel customization (our peripheral driver, device tree changes and kernel changes) and built the source.

Does default BSP able to flash that only one problematic module?

Sorry, I didn’t get you exactly. The default BSP flashed successfully using sdkmanager.

6

Let me change my question

  1. You told us only one module has flash problem. Correct?

  2. If you don’t build anything from source code, but just use default BSP, will it be able to flash this one module mentioned in (1)?

7
  1. You told us only one module has flash problem. Correct?
    – Yes, only one module has the flash problem.
  2. If you don’t build anything from source code, but just use default BSP, will it be able to flash this one module mentioned in (1)?
    – Yes, we can able to flash the default BSP without building anything using the same command.

Moreover, I tried building the default source without any customizations(without applying our kernel changes and our driver) and tried flashing, but end up with the same error(Timeout in USB Write).

Conclusion: Default BSP without building is flashing well, but building the default BSP is not getting flashed.

Help is most appreciated.
Thanks.

8

Please dump the UART serial console log during flash failure.

9

Please find the UART serial console log during flash failure.
Flash_console_log.zip (3.1 KB)

10

Hi,

Could you also share one UART log based on that “working BSP” situation on this module?

11

Here you go,
Flash_working_console_log.zip (5.6 KB)

12

Do you have NV devkit to test jp5.1.3 on this module and dump log? This error log is related to DRAM enable.

The working log has

[0117.341] I> Non-ECC region[0]: Start:0x80000000, End:0x880000000

The non working log is

[0120.197] I> Non-ECC region[0]: Start:0x80000000, End:0x80000000

In NG case, start and end address are same so memory allocation is totally failure.

If this is only one module that has issue, I wonder if this is related to PCN modules.

13

Unfortunately we couldn’t test it with devkit.
Can we initiate the RMA for this Module?

14

RMA may not help. If this is PCN related modules, then you would hit issue again and again with new modules in future.

Are you able to test latest BSP?

15

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