I, too, and having similar problems with the Jetson TX2 Development Kit. When I first received it, applying 14.5Vdc to the barrel connector only lighted LED CR5 (VDD_IN), as expected, but the unit wouldn’t respond to the standard Force Recovery button turn-on sequence (off / push Force Recovery button / power on / with FR button pushed, momentarily press On button / release On button / release FR button). I mention the Force Recovery sequence in case someone spots a significant error.
Anyhow, after MANY MANY trials of doing this, and also trying other combinations (involving Reset button), one time the unit turned on! Namely, green LEDs CR1 (SOC Enabled) & CR2 (Power), and red LED CR6, all turned on. During this period I was able to flash the OS successfully (JetPack 4.4.1, I think) using SDKManager on my other Linux computer.
Subsequently, the unit turned on normally (i.e., with only a press of the Power On button) for several instances over the next few days, and I began to setup my Ubuntu desktop preferences. HOWEVER, yesterday the DevKit refused to turn on again , with behavior now having only CR5 lit when power is applied, with no other response (other than the PCIE/SATA red LED CR6 briefly flashing every time Power On button is pressed). The only thing I can imagine that happened is that perhaps there’s a problem with ESD protection as I plugged in the nominal 12V external power into the barrel connector (??). I have downloaded the DevKit schematics, but as of now have not figured out a possible culprit for why the unit ceased to turn on, especially since it worked flawlessly for several days.
I really don’t know what to do at this point. Please help! I invested a bit of $ into providing the DevKit with a mini-ITX case and a SATA SSD, and planned on making this my main Linux computer, so it would be great to find out how to fix this!!
Thanks very much for anyone’s insight.