I have a bunch of jetson TK1s that I’d like to flash and use, but I’m not able to get access to recovery mode. They all behave the same.
My monitors never detect a signal.
I’ve got a null modem attached and can see it cycle trying to boot from pxe (previous owners) and drop into local mode, but it doesn’t appear to be a full OS.
Tegra124 (Jetson TK1) # version U-Boot 2014.10-rc2-g3127911 (Jun 07 2016 - 21:00:01) arm-cortex_a9-linux-gnueabi-gcc (crosstool-NG email@example.com) 4.5.3 GNU ld (crosstool-NG firstname.lastname@example.org) 126.96.36.19900303
It seems like there is a ubuntu OS installed, I can poke around in ls, but not quite sure how to make it boot out of this barebones env otherwise.
Tegra124 (Jetson TK1) # ls mmc 0:1 <DIR> 4096 . <DIR> 4096 .. <DIR> 16384 lost+found <DIR> 4096 boot <DIR> 4096 bin <DIR> 4096 dev <DIR> 12288 etc <DIR> 4096 home <DIR> 4096 lib <DIR> 4096 media <DIR> 4096 mnt <DIR> 4096 opt <DIR> 4096 proc 62 README.txt <DIR> 4096 root <DIR> 4096 run <DIR> 12288 sbin <DIR> 4096 srv <DIR> 4096 sys <DIR> 4096 tmp <DIR> 4096 usr <DIR> 4096 var
Whenever I use the physical keys or use 'enterrcm` to go into recovery mode, I no longer get feedback from the null modem cable nor do I ever see the 0955:7410 usb device show up in my ubuntu 20.04 host.
It’s possible that they are all defunct boards, but I have a mess of them and I would have expected that at some of them were still functional.
Is it expected that the data on null modem cable will go blank when in recovery?
Is it possible that there is some sort of “touch key to continue” button not displaying because my HDMI is not showing anything?
Are there any methods of getting around recovery mode being unavailable? Perhaps in this barebones OS?
Here is the help menu from the OS for helping me identify what it is? (what’s it called?)
Tegra124 (Jetson TK1) # ? ? - alias for 'help' base - print or set address offset bdinfo - print Board Info structure boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootelf - Boot from an ELF image in memory bootm - boot application image from memory bootp - boot image via network using BOOTP/TFTP protocol bootvx - Boot vxWorks from an ELF image bootz - boot Linux zImage image from memory cmp - memory compare coninfo - print console devices and information cp - memory copy crc32 - checksum calculation dfu - Device Firmware Upgrade dhcp - boot image via network using DHCP/TFTP protocol dm - Driver model low level access echo - echo args to console editenv - edit environment variable enterrcm- reset Tegra and enter USB Recovery Mode env - environment handling commands exit - exit script ext2load- load binary file from a Ext2 filesystem ext2ls - list files in a directory (default /) ext4load- load binary file from a Ext4 filesystem ext4ls - list files in a directory (default /) ext4size- determine a file's size false - do nothing, unsuccessfully fatinfo - print information about filesystem fatload - load binary file from a dos filesystem fatls - list files in a directory (default /) fatsize - determine a file's size fdt - flattened device tree utility commands go - start application at address 'addr' gpio - query and control gpio pins help - print command description/usage i2c - I2C sub-system imxtract- extract a part of a multi-image itest - return true/false on integer compare load - load binary file from a filesystem loadb - load binary file over serial line (kermit mode) loads - load S-Record file over serial line loadx - load binary file over serial line (xmodem mode) loady - load binary file over serial line (ymodem mode) loop - infinite loop on address range ls - list files in a directory (default /) md - memory display mii - MII utility commands mm - memory modify (auto-incrementing address) mmc - MMC sub system mmcinfo - display MMC info mw - memory write (fill) nm - memory modify (constant address) part - disk partition related commands pci - list and access PCI Configuration Space ping - send ICMP ECHO_REQUEST to network host printenv- print environment variables pxe - commands to get and boot from pxe files reset - Perform RESET of the CPU run - run commands in an environment variable saveenv - save environment variables to persistent storage setenv - set environment variables sf - SPI flash sub-system showvar - print local hushshell variables size - determine a file's size sleep - delay execution for some time source - run script from memory sspi - SPI utility command sysboot - command to get and boot from syslinux files test - minimal test like /bin/sh tftpboot- boot image via network using TFTP protocol true - do nothing, successfully ums - Use the UMS [User Mass Storage] usb - USB sub-system usbboot - boot from USB device version - print monitor, compiler and linker version