Tx2i Power On issues

I am unable to power on the TX2i SOM by using the TX2 development kit. I have checked the development and its working satisfactorily. Kindly assist in trouble shooting the issue.



Do you mean there is no power on or you are saying that it is powered on but the system does not boot up?

Or you cannot tell the state?

The board is getting power, but the SOM isn’t booting. Is there a way to check if the SOM is powered on?


You could try to dump the log from uart console.


Can you tell me how to do that? Currently my PC doesn’t detect the board with the TX2i when connected via both ethernet and USB-UART at J28. The following is whats seen with the regular tx2 on the dev board…

4.5 LTS SID ttyGS0{0D}{0A}{0D}{0A}SID login: vte{0D}{0D}{0A}Password: {0D}{0A}Last login: Wed Nov 4 23:13:16 IST 2020 from on pts/0{0D}{0A}Welcome to Ubuntu 18.04.5 LTS (GNU/Linux 4.9.140-tegra aarch64){0D}{0A}{0D}{0A} * Documentation: https://help.ubuntu.com{0D}{0A} * Management: https://landscape.canonical.com{0D}{0A} * Support: https://ubuntu.com/advantage{0D}{0A}This system has been minimized by removing packages and content that are{0D}{0A}not required on a system that users do not log into.{0D}{0A}{0D}{0A}To restore this content, you can run the ‘unminimize’ command.{0D}{0A}{0D}{0A}51 packages can be updated.{0D}{0A}36 updates are security updates.{0D}{0A}{0D}{0A}vte@SID:~ {0D}{0A}vte@SID:~ sudo shutdown{0D}{0A}[sudo] password for vte: {0D}{0A}G&Sorry, try again.{0D}{0A}[sudo] password for vte: {0D}{0A}Shutdown scheduled for Thu 2020-11-05 01:50:34 IST, use ‘shutdown -c’ to cancel.{0D}{0A}vte@SID:~$

Read the page and it will teach you.


I’ve checked with the Tx2i SOM, nothing happened when powered On. I’m enclosing the dump from a working SOM to show that the board works…

The oldest data was removed. Continue…
gement-pmon-p3310-1000-300 matches{0D}{0A}[0003.837] I> node /plugin-manager/fragement-pmon-p3310-1000-800 matches{0D}{0A}[0003.845] I> node /plugin-manager/fragment-devslp@0 matches{0D}{0A}[0003.858] I> node /plugin-manager/fragment-500-pcie-config matches{0D}{0A}[0003.872] I> node /plugin-manager/fragment-500-xusb-config matches{0D}{0A}[0003.895] I> node /plugin-manager/fragment-p3310-c00-comm matches{0D}{0A}[0003.909] I> node /plugin-manager/fragment-p3310-c00-pmic matches{0D}{0A}[0003.919] I> node /plugin-manager/fragment-p3310-c01 matches{0D}{0A}[0003.932] I> node /plugin-manager/fragment-p3310-c03 matches{0D}{0A}[0003.967] I> node /plugin-manager/fragment-e3326@0 matches{0D}{0A}[0004.048] I> node /plugin-manager/fragment-p3310-c00-camera matches{0D}{0A}[0004.075] I> Disable plugin-manager status in FDT{0D}{0A}[0004.079] I> Plugin-manager override finished successfully{0D}{0A}[0004.084] I> tegrabl_load_kernel_and_dtb: Done{0D}{0A}[0004.089] E> tegrabl_display_clear: display is not initialized{0D}{0A}[0004.094] W> Boot logo display failed…{0D}{0A}[0004.098] I> Kernel EP: 0x80600000, DTB: 0x80000000{0D}{0A}{0D}{0A}{0D}{0A}U-Boot 2016.07-g7a7e3f476e (Oct 16 2020 - 12:15:13 -0700){0D}{0A}{0D}{0A}TEGRA186{0D}{0A}Model: NVIDIA P2771-0000-500{0D}{0A}DRAM: 7.8 GiB{0D}{0A}MC: Tegra SD/MMC: 0, Tegra SD/MMC: 1{0D}{0A}*** Warning - bad CRC, using default environment{0D}{0A}{0D}{0A}In: serial{0D}{0A}Out: serial{0D}{0A}Err: serial{0D}{0A}Net: eth0: ethernet@2490000{0D}{0A}Hit any key to stop autoboot: 2 {08}{08}{08} 1 {08}{08}{08} 0 {0D}{0A}MMC: no card present{0D}{0A}switch to partitions #0, OK{0D}{0A}mmc0(part 0) is current device{0D}{0A}Scanning mmc 0:1…{0D}{0A}Found /boot/extlinux/extlinux.conf{0D}{0A}Retrieving file: /boot/extlinux/extlinux.conf{0D}{0A}857 bytes read in 125 ms (5.9 KiB/s){0D}{0A}1:{09}primary kernel{0D}{0A}Retrieving file: /boot/initrd{0D}{0A}5565270 bytes read in 221 ms (24 MiB/s){0D}{0A}Retrieving file: /boot/Image{0D}{0A}34332680 bytes read in 857 ms (38.2 MiB/s){0D}{0A}append: console=ttyS0,115200 androidboot.presilicon=true firmware_class.path=/etc/firmware root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2 video=tegrafb no_console_suspend=1 earlycon=uart8250,mmio32,0x3100000 nvdumper_reserved=0x2772e0000 gpt usbcore.old_scheme_first=1 tegraid= maxcpus=6 boot.slot_suffix= boot.ratchetvalues=0.2031647.1 bl_prof_dataptr=0x10000@0x275840000 sdhci_tegra.en_boot_part_access=1 quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 isolcpus=1-2 {0D}{0A}## Flattened Device Tree blob at 80000000{0D}{0A} Booting using the fdt blob at 0x80000000{0D}{0A} reserving fdt memory region: addr=80000000 size=10000{0D}{0A} Using Device Tree in place at 0000000080000000, end 000000008005fa73{0D}{0A}{0D}{0A}Starting kernel …{0D}{0A}{0D}{0A}[ 0.000000] Booting Linux on physical CPU 0x100{0D}{0A}[ 0.000000] Linux version 4.9.140-tegra (buildbrain@mobile-u64-4255) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05) ) #1 SMP PREEMPT Fri Oct 16 12:25:00 PDT 2020{0D}{0A}[ 0.000000] Boot CPU: AArch64 Processor [411fd073]{0D}{0A}[ 0.000000] OF: fdt:memory scan node memory@80000000, reg size 16416,{0D}{0A}[ 0.000000] OF: fdt: - 80000000 , 70000000{0D}{0A}[ 0.000000] OF: fdt: - f0200000 , 185600000{0D}{0A}[ 0.000000] OF: fdt: - 275e00000 , 200000{0D}{0A}[ 0.000000] OF: fdt: - 276600000 , 200000{0D}{0A}[ 0.000000] OF: fdt: - 277000000 , 200000{0D}{0A}[ 0.000000] earlycon: uart8250 at MMIO32 0x0000000003100000 (options ‘’){0D}{0A}[ 0.000000] bootconsole [uart8250] enabled{0D}{0A}[ 1.625001] cgroup: cgroup2: unknown option “nsdelegate”{0D}{0A}[ 2.688541] using random self ethernet address{0D}{0A}[ 2.701322] using random host ethernet address{0D}{0A}[ 2.956031] random: crng init done{0D}{0A}[ 2.959440] random: 7 urandom warning(s) missed due to ratelimiting{0D}{0A}[ 3.420099] using random self ethernet address{0D}{0A}[ 3.457328] using random host ethernet address{0D}{0A}[ 3.659497] CPU1: shutdown{0D}{0A}[ 3.732465] CPU2: shutdown{0D}{0A}{0D}{0D}{0A}Ubuntu 18.04.5 LTS SID ttyS0{0D}{0A}{0D}{0A}SID login:


Then I guess maybe this board has defect. Do you have only one TX2i module to test?

BTW, can you try to give the log in a format that is better to read? You can refer to how other users log look like.


I had bought 10 Nos. of TX2i SOMs and all of them are exhibiting the same behavior. I have a couple of older Tx2i SOMs that were purchased earlier. These are working fine with the development board…

Ok. Then that sounds not a hardware defect.

Are you able to flash those modules with this carrier board?

Yes, I was able to flash the older TX2i’s to the latest Jetpack version using the board…


And what happened to the new boards?

I have been able to successfully flash 3/10 SOMs using the SDK manager. Will complete and check the remaining 7 shortly.

Thanks for the help.

Please check the devkit user guide. If your dev kit is B02 or B04 revision carrier board, it can not support TX2i module.

I have both the B & C series boards. Current issue was observed on the C series board, but funny enough I am able to use my older TX2i SOMs on the B series boards as well.

Can you share the part number of new/old TX2i module and carrier board?

I see a lot of serial nos. on the board. The Tx2i SOM bears the the model no.: P3489 and SN:0420418026387

There are some sample part numbers in this site:https://developer.nvidia.com/embedded/faq#jetson-part-numbers, you can refer to that to list the SKU and SN of new & old TX2i module and your B an C carrier board.

old SKU kit: 945-82771-0000-000 Y
new SKU kit: 945-82771-0000-000 AY

Hi, I am a little confused…

Do you have two kinds of TX2i module (SoM), new and old, right? If so, please list the SKU and SN of them.

Also please list the SKU and SN of the “development board” that old SoM can work on.