We have the correct power up sequence with nvidia module but it is not booting up. In figure 1 blue is V_in power, yellow is power bad , green is module power, pink one is carrier power signal.
Even with power signal and reset signal is set , Xavier is not booting. We also tried the official development and the module is working there. We are using jetpack 5.1.3 .
Any suggestions or help will be appreciated .
Thanks,
Ozancan
Hi, if carrier_pwr_on is output from module correctly, then it means module has been powered correctly. So the issue might be that some shared interface pin status are not correct. You can check your IO design based on the checklist sheet attached in the Design Guide and also refer to the P2822 schematic. Especially pay attention to the UART ports which pin status might be affected by the level shift on carrier board.
Hi Trumany , thanks for the quick reply. We didn’t quite understand how the level shifters can affect the UART port pin status. Here some of the schematics of our carrier board design which include UART level shifter , ethernet, HDMI , serial communication , power rails.
If you use level shift to UART pins, then you should check the module UART pins status during power on to make sure it won’t be changed by the level shift. Otherwise the system might be affected and so boot fail.
We checked the UART pins during power on for checking any changes. There is no changing, while power on stage, the level of the pins turn high. The system draws 0.014A current.
Hi, we have some process about custom carrier board. We carefully probed uart signals and observed no change caused by level shifter ic. However, we have seen that when we probe sys_rst_n signal after power sequence is done with oscilloscope the system boots and operates normally. I’d like to point that sys_rst_n signal is correctly held low during booting process and goes high when power sequence is done. Also probing sys_rst_n does not help if we do it during power sequence.
We have successfully booted the device after toggling the sys_rst_in manually following the carrier_pwr_on signal. We did it by connecting sys_rst_in to MCU pin.
Do you think this is the proper way? We already check the signals towards to the Nvidia module. But, we could not catch any issue.
When we tried to connect USB-0 with our custom board, SDK does not detect any device, but USB1 and USB2 are functional. So, we cannot flash with our carrier board to the module. With other carrier boards we can use the USB0 port without a problem. We think that toggling the sys_rst pin did not solve the our main problem. So, the main problem still exists and prevents us from flashing the module too.
