Some Jetson NANO Modules are booting fail on the custom board

Hello,

There is ‘Power ON’ issue with latest manufactured Jetson NANO Modules on the custom board.

We are testing 3 Case of custom board.

1 - Developer Kit (A02)
2 - Custom board with Power Logic (Power Logic is simmilar to Dev Kit)
3 - Custom board with MCU (MCU makes POWER_EN signal, It can control delay time)

And We are testing 3 case of modules.

A - Latest manufactured Modules
B - Old manufactured Modules
(* P/N are same between A and B modules : 900-13448-0020-000 )

Power On Results

Boot Sucess : 1A, 1B, 2B, 3B
Boot Fail : 2A, 3A

There is something change in booting sequence guide about Powen_EN delay time.
I think it related to our result.
Firstl, I wanna know 400ms delay of Powen_EN signal is critical or not.
Becasue, Dev Kit power logic makes delay time around 280ms.
And Dev Kit works with latest manufactured module.
So, I wanna make it clear.

Our power logic board result as below :
20220628_power_logic_custom_board.pptx (327.9 KB)

And Our mcu board result as below :
20220628_mcu_board.pptx (472.1 KB)

We can make delay time more than 400ms and It doesn’t works as same.
But there is something different thing in mcu case, there is noise at the begining of power input.
I wonder this short noise can make fail to power on or not?

Hi, please refer to this topic (New power sequencing requirements) for 400ms sequence change. It might cause issue sometimes.

If issue is still with correct sequence, there might be some other difference between your design and devkit. You can compare your schematic to that of P3449.

BTW, is it real Developer Kit (A02) ? A02 is an early version number which is not compatible to B01 board. Can you share the carrier board number?

I don’t test SD card Module. We are just using carrier board of dev kit.
And now we are testing Power ON. So, I think it doesn’t matter.

We want to check Power LED is ON or Not.
Booting fail means Power LED is not going to be ON.

A01 carrier board is different to B01 board. Better to compare to B01 board to have a check.

The power sequence topic is for B01 board design.

Ok, I see I would consider it.
But A02 has no issue with Power ON any modules.
Do you think What data do we need to compare with B01 Dev Kit??

And this result after nosie is removed at the begining.
20220628_mcu_board_noise_remover.pptx (534.9 KB)

Anyway, It follows booting sequence. But it doesn’t work, also.
Do you think what can I do to solve?

USE: A02 jetson nano carrier board

It is A02 board per the photo. A02 board should not be used with B01 devkit module. I have no idea about your board. But since it only happens on your board, you may need to compare your board schematic to P3449 B01 carrier board in DLC, especially on power part, to find out difference first.

1 Like

Our Custom Board Schematics pdf file
20220629_Schematics_jetsonNano_Custom_Board.pdf (112.8 KB)
. Upload

Schemaitcs Difference, 6Page U1101, U1102, U1100, U1103 Part

A - Latest manufactured Modules
B - Old manufactured Modules
(* P/N are same between A and B modules : 900-13448-0020-000 )

A & B jetson Nano Module is very well working in the “A02 Dev Kit Board”(945-13450-0000-000).

Have you tried the rework like that of “R377 = 400k ohm 1% resistor, C280 = 2.2uF 10V 0603” on P3449?

In addition, why do you use two separated 5V (VDD_5V and VDD_5V_IN) for module and carrier board? It should be same 5V for both per P3449 design.

OK, possible.
I should unify “VDD_5V + VDD_5V_IN” Power line to One Power line (VDD_5V_IN).

Result: Not Boot

20220630_R377_C280_signal1.pptx (258.1 KB)

  1. Part Change
    R377(=R1103): 390K ohm
    C280(=C1101): 2.2uF
    VDD_5V_IN - POWER_EN Delay time: 522ms
    -. Result: Not Boot

  2. Part Change
    R377(=R1103): 470K ohm
    C280(=C1101): 1uF + “100nF + 100nF”, (ADD MLCC parallel)
    VDD_5V_IN - POWER_EN Delay time: 438ms
    -. Result: Not Boot

Jetson Nano_P3449_B01_POWER_LOGIC1.pdf (64.1 KB)

20220630_PARTChange_PowerLOgic_schematic1…xlsx (147.4 KB)

Dear !!!

we change part to same bland item.

See attached Excel file list " 20220630_PARTChange_PowerLogic_schematic1…xlsx "

It is weird. 1. you have unified two 5V, right? 2. Tried rework; 3. Used same components. All not boot?

Are you using same SW? Or did you flash same SW version to new and old modules? Do you have log? It looks that you have not route out the debug UART lines.

jetson_nano_debug_uart2.pdf (67.1 KB)

A. Custom Board UART Port Schematic. pdf

Our Custom Board DEbug UART is UART2TX/UART2RX.
(P3449-B01) 236 port Number: UART2TX
(P3449-B01) 238 port Number: UART2RX

--------------- TEST MODULE------------
A - Latest manufactured Modules (5221 05-02)
B - Old manufactured Modules (5020 30-01)
(* P/N are same between A and B modules : 900-13448-0020-000 )

-------------- TEST BOARD -------------
Custom Board (P3449-B01 schematic COPY)

  1. you have unified two 5V, right?

--------------------> Answer

attached file is “20220630_UNIFY_POWER_LINE_VDD_5V_IN.pptx” .
20220630_UNIFY_POWER_LINE_VDD_5V_IN.pptx (40.1 KB)
Only USE One Power Line: VDD_5V_IN Power (+5V/ max 5A, DC-DC convertor).
-. Result: Not BOOT

--------------------> Answer
I used POWER SUPPLY Eqipment(Power Source +5V).
I tried to change Adaptor Power(+12V/2A) to POWER SUPPLY EQ (+5V).
-. Result: Not BOOT
attached file is " 20220630_Power_Supply_VDD_5V_IN.pptx ".
20220630_Power_Supply_VDD_5V_IN.pptx (39.0 KB)

  1. Tried rework;

--------------------> Answer

-. Result: Not BOOT

  1. Used same components.
    --------------------> Answer
    Different components: U55, U50, U51, U59
    I will get Original component and try test.
    -. Result: try, Not yet

  2. Are you using same SW? Or did you flash same SW version to new and old modules?

----------------------> Answer
A - Latest manufactured Modules (5221 05-02) —> New Module
B - Old manufactured Modules (5020 30-01) —> Old Module

A, B Also working Boot in the “A02 Dev KIT”
A module: Not BOOT (Custom Board, P3449-B01 schematic COPY)
B module: OK BOOT (Custom Board, P3449-B01 schematic COPY)

  1. Do you have log?

--------------------> Answer
--------------- TEST MODULE------------
A - Latest manufactured Modules (5221 05-02)
( P/N are same between A and B modules : 900-13448-0020-000 )*

-------------- TEST BOARD -------------
A02 DEV KIT

attached file is “20220630_A02DevKit_Latest manufactured Modules (5221 05-02).log”
20220630_A02DevKit_Latest manufactured Modules (5221 05-02).log (39.0 KB)

  1. It looks that you have not route out the debug UART

--------------------> Answer
A. Custom Board UART Port Schematic. pdf

Our Custom Board DEbug UART is UART2TX/UART2RX.
(P3449-B01) 236 port Number: UART2TX
(P3449-B01) 238 port Number: UART2RX

No clue.

How many new/old modules have you tested? What’s the fail rate?

--------------- TEST MODULE------------
A - Latest manufactured Modules (5221 05-02)
B - Old manufactured Modules (5020 30-01)
( P/N are same between A and B modules : 900-13448-0020-000 )*

-------------- TEST BOARD -------------
Custom Board (P3449-B01 schematic COPY)

How many new/old modules have you tested?

-----------------------> Answer

New Module: 4EA
OLD Module: 1EA

What’s the fail rate

---------------------> Answer
100%