I recently updated my Jetson Xaiver NX and it booted into a black screen with a blinking cursor every time I tried to reboot. I have to hold ctrl+alt+F1 to recover but it doesn’t solve the issue if I reboot again. It looks like the update is not completed since there is a message telling me to reboot after the update every time I recovered from the black screen. I didn’t have the issue before the update.
Hi,
Do you use apt-get upgrade and hit this issue? If so, please refer to this post to resolve it.
I am having the same problem after the most recent update. Rebooting 7 times does indeed lead to a successful boot, but editing extlinux.conf, reconfiguring, and rebooting as above does not solve the problem. The original extlinux.conf file includes both quiet and root, as below:
APPEND ${cbootargs} quiet root= …
After editing, should it read
APPEND ${cbootargs} root=
?
After editing, should it read
What are you trying to say here? Not very sure about it. You cannot just leave the root as a blank.
The root needs to include the information of your rootfs. If you mount the rootfs on emmc, it should be default value as /dev/mmcblk0p1. However, if you mount it to something else, then it is probably not mmcblk0p1.
1 Like
There should be an ellipsis after root–I know the equal sign is still followed by all the rootfs arguments. Was just confirming that it should only read “root” and not “quiet root”. I think my confusion arises from the fact that the image had already been updated to include the hackaround in the extlinux.conf file by the time I re-flashed the SD card. So I am probably following ‘old’ instructions. I’m following that other thread with great enthusiasm. The real problem now is that I have re-flashed the SD card with the latest 4.4 image and it still does not boot properly. I have used SDK manager and have written the image directly using Etcher. I’ve tried two different SD cards (one brand new for the purpose) and have repeated this several times. It gets this far in the process and the screen randomly blinks:
And here is the output from the serial console:
Welcome to minicom 2.7.1
OPTIONS: I18n
Compiled on Aug 13 2017, 15:25:34.
Port /dev/ttyUSB0, 07:10:46
Press CTRL-A Z for help on special keys
��
[0000.024] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet lev.
[0000.033] I> MB1 (prd-version: 1.5.1.3-t194-41334769-d2a21c57)
[0000.038] I> Boot-mode: Coldboot
[0000.041] I> Chip revision : A02
[0000.044] I> Bootrom patch version : 15 (correctly patched)
[0000.049] I> ATE fuse revision : 0x200
[0000.053] I> Ram repair fuse : 0x0
[0000.056] I> Ram Code : 0x0
[0000.059] I> rst_source : 0x0
[0000.061] I> rst_level : 0x0
[0000.065] I> Boot-device: QSPI
[0000.067] I> Qspi flash params source = brbct
[0000.072] I> Qspi using bpmp-dma
[0000.074] I> Qspi clock source : pllp
[0000.078] I> QSPI Flash Size = 32 MB
[0000.081] I> Qspi initialized successfully
[0000.085] W> No valid slot number is found in scratch register
[0000.091] W> Return default slot: _a
[0000.094] I> Active Boot chain : 0
[0000.097] I> Boot-device: QSPI
[0000.100] I> Qspi flash params source = brbct
[0000.106] W> MB1_PLATFORM_CONFIG: device prod data is empty in MB1 BCT.
[0000.113] I> Temperature = 23000
[0000.117] W> Skipping boost for clk: BPMP_CPU_NIC
[0000.121] W> Skipping boost for clk: BPMP_APB
[0000.125] W> Skipping boost for clk: AXI_CBB
[0000.129] W> Skipping boost for clk: AON_CPU_NIC
[0000.133] W> Skipping boost for clk: CAN1
[0000.137] W> Skipping boost for clk: CAN2
[0000.141] I> Boot-device: QSPI
[0000.144] I> Boot-device: QSPI
[0000.147] I> Qspi flash params source = mb1bct
[0000.151] I> Qspi using bpmp-dma
[0000.154] I> Qspi clock source : pllc_out0
[0000.158] I> Qspi reinitialized
[0000.160] I> Qspi flash params source = mb1bct
[0000.166] I> ECC region[0]: Start:0x0, End:0x0
[0000.170] I> ECC region[1]: Start:0x0, End:0x0
[0000.174] I> ECC region[2]: Start:0x0, End:0x0
[0000.178] I> ECC region[3]: Start:0x0, End:0x0
[0000.182] I> ECC region[4]: Start:0x0, End:0x0
[0000.187] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0000.192] I> Non-ECC region[1]: Start:0x0, End:0x0
[0000.197] I> Non-ECC region[2]: Start:0x0, End:0x0
[0000.201] I> Non-ECC region[3]: Start:0x0, End:0x0
[0000.206] I> Non-ECC region[4]: Start:0x0, End:0x0
[0000.211] E> FAILED: Thermal config
[0000.218] E> FAILED: MEMIO rail config
[0000.229] I> Boot-device: QSPI
[0000.232] I> Qspi flash params source = mb1bct
[0000.241] I> Qspi flash params source = mb1bct
[0000.252] I> Qspi flash params source = mb1bct
[0000.319] I> Qspi flash params source = mb1bct
[0000.328] I> Qspi flash params source = mb1bct
[0000.355] I> Qspi flash params source = mb1bct
[0000.366] I> MB1 done
����main enter
SPE VERSION #: R01.00.14 Created: Sep 19 2018 @ 11:03:21
HW Function test
Start Scheduler.
in late init
��
[0000.375] I> Welcome to MB2(TBoot-BPMP) (version: 00.00.2018.32-mobile-aa987)
[0000.376] I> DMA Heap @ [0x526fa000 - 0x52ffa000]
[0000.376] I> Default Heap @ [0xd486400 - 0xd48a400]
[0000.377] E> DEVICE_PROD: Invalid value data = 70020000, size = 0.
[0000.383] W> device prod register failed
[0000.387] I> Boot-device: QSPI
[0000.390] I> Boot_device: QSPI_FLASH instance: 0
[0000.395] I> QSPI Flash Size = 32 MB
[0000.398] I> Qspi initialized successfully
[0000.401] I> qspi flash-0 params source = boot args
[0000.406] E> Failed: Unknown device 6
[0000.413] I> Found 47 partitions in QSPI_FLASH (instance 0)
[0000.416] W> No valid slot number is found in scratch register
[0000.421] W> Return default slot: _a
[0000.424] I> Active Boot chain : 0
[0000.428] I> parsing oem signed section of bpmp-fw header done
[0000.433] I> bpmp-fw binary init read from storage
[0000.438] I> oem authentication of bpmp-fw header done
[0000.452] I> bpmp-fw binary done read from storage
[0000.453] I> bpmp-fw: Authentication init Done
[0000.454] I> parsing oem signed section of cpubl header done
[0000.457] I> cpubl binary init read from storage
[0000.462] I> bpmp-fw: Authentication Finalize Done
[0000.467] I> oem authentication of cpubl header done
[0000.474] I> cpubl binary done read from storage
[0000.476] I> cpubl: Authentication init Done
[0000.480] I> parsing oem signed section of rce header done
[0000.485] I> rce binary init read from storage
[0000.490] I> Relocating BR-BCT
[0000.492] I> cpubl: Authentication Finalize Done
[0000.497] I> oem authentication of rce header done
[0000.502] I> rce binary done read from storage
[0000.506] I> rce: Authentication init Done
[0000.510] I> parsing oem signed section of ape header done
[0000.515] I> ape binary init read from storage
[0000.519] I> rce: Authentication Finalize Done
[0000.524] I> oem authentication of ape header done
[0000.528] I> ape binary done read from storage
[0000.532] I> ape: Authentication init Done
[0000.537] I> parsing oem signed section of tos header done
[0000.542] I> tos binary init read from storage
[0000.546] I> ape: Authentication Finalize Done
[0000.551] I> oem authentication of tos header done
[0000.557] I> tos binary done read from storage
[0000.559] I> tos: Authentication init Done
[0000.564] I> parsing oem signed section of bpmp-fw-dtb header done
[0000.569] I> bpmp-fw-dtb binary init read from storage
[0000.574] I> tos: Authentication Finalize Done
[0000.580] I> oem authentication of bpmp-fw-dtb header done
[0000.584] I> bpmp-fw-dtb binary done read from storage
[0000.589] I> bpmp-fw-dtb: Authentication init Done
[0000.594] I> parsing oem signed section of cpubl-dtb header done
[0000.599] I> cpubl-dtb binary init read from storage
[0000.604] I> bpmp-fw-dtb: Authentication Finalize Done
[0000.650] I> oem authentication of cpubl-dtb header done
[0000.651] I> cpubl-dtb binary done read from storage
[0000.652] I> cpubl-dtb: Authentication init Done
[0000.653] I> parsing oem signed section of eks header done
[0000.653] I> eks binary init read from storage
[0000.654] I> cpubl-dtb: Authentication Finalize Done
[0000.655] I> oem authentication of eks header done
[0000.659] I> eks binary done read from storage
[0000.663] I> eks: Authentication init Done
[0000.667] I> eks: Authentication Finalize Done
[0000.671] I> EKB detected (length: 0x410) @ VA:0x52705400
��NOTICE: BL31: v1.3(release):fe06da916
NOTICE: BL31: Built : 18:06:49, Apr 8 2020
ipc-unittest-main: 1519: Welcome to IPC unittest!!!
ipc-unittest-main: 1531: waiting forever
ipc-unittest-srv: 329: Init unittest services!!!
hwkey-agent: 40: hwkey-agent is running!!
hwkey-agent: 182: key_mgnt_processing …
hwkey-agent: 157: Init hweky-agent services!!
platform_bootstrap_epilog: trusty bootstrap complete
��
welcome to lk
calling constructors
initializing heap
creating bootstrap completion thread
top of bootstrap2()
initializing platform
bpmp: platform_init
tag is 57f8a77779f848bf2ecf21dabee5645f
tag_show initialized
dt initialized
mail initialized
chipid initialized
fuse initialized
sku initialized
speedo initialized
ec_get_ec_list: found 45 ecs
ec initialized
ec_mrq initialized
vmon_populate_monitors: found 3 monitors
vmon initialized
adc initialized
fmon_populate_monitors: found 73 monitors
fmon initialized
fmon_mrq initialized
reset initialized
nvhs initialized
391 clocks registered
clk_mrq_init: mrq handler registered
clk initialized
nvlink initialized
io_dpd initialized
io_dpd initialized
thermal initialized
i2c5 controller initialized
initialized i2c mrq handling
i2c initialized
regulator initialized
avfs_clk_platform_init: bad clk id in clock@cluster2_avfs
avfs_clk_platform initialized
soctherm initialized
aotag initialized
powergate initialized
dvs initialized
pm initialized
pg_late initialized
strap initialized
tag initialized
emc initialized
clk_dt initialized
avfs_ccplex_platform initialized
tj_max: dt node not found
tj_init initialized
uphy_mrq_init: mrq handler registered
uphy_dt initialized
uphy initialized
safereg_init: period 80 ms
ec_late initialized
��
[0001.013] I> Welcome to Cboot
��mrq initialized
WARNING: no registered clock for FMON_NAFLL_CLUSTER2 (id 282)
fmon_post initialized
��[0001.013] I> Cboot Version: t194-d00c695c
[0001.015] I> CPU-BL Params @ 0xf2820000
[0001.019] I> 0) Base:0x00000000 Size:0x00000000
[0001.023] I> 1) Base:0xf1100000 Size:0x00100000
[0001.028] I> 2) Base:0xf2000000 Size:0x00200000
[0001.032] I> 3) Base:0xf1200000 Size:0x00200000
[0001.037] I> 4) Base:0xf1000000 Size:0x00100000
��clk_dt_late initialized
machine_check initialized
pm_post initialized
dbells initialized
avfs_clk_platform_post initialized
dmce initialized
cvc initialized
ccplex_avfs_hw_init: nafll_cluster0: not monitored
ccplex_avfs_hw_init: nafll_cluster1: not monitored
ccplex_avfs_hw_init: nafll_cluster3: not monitored
avfs_clk_mach_post initialized
regulator_post initialized
rm initialized
sc7_diag initialized
thermal_test initialized
serial_late initialized
clk_post initialized
clk_dt_post initialized
mc_reg initialized
pg_post initialized
dyn_modules initialized
sku_debugfs initialized
speedo_debugfs initialized
adc_debugfs initialized
Failed to register PTO counter for id 282
Failed to register PTO counter for id 282
Failed to register PTO counter for id 282
Failed to register PTO counter for id 282
clk_debugfs initialized
emc_debugfs initialized
dvs_debugfs initialized
fmon_debugfs_init_one: no clock debugfs node to attach FMON_NAFLL_CLUSTER2
fmon_debugfs initialized
vmon_debugfs initialized
pg_debugfs initialized
profile_fs initialized
debugfs_cons initialized
mail_fs initialized
profile initialized
cvc_debugfs initialized
dmce_debugfs initialized
ec_debugfs initialized
rm_rail_debugfs_init: /rm/vdd_cpu: failed
rm_rail_debugfs_init: /rm/vdd_cpu: failed
rm_debugfs initialized
soctherm_debug initialized
gr_reader initialized
mods initialized
dt_fs initialized
debugfs_mrq initialized
debug_mrq initialized
debug_safereg initialized
initializing target
calling apps_init()
starting app shell
entering main console loop
] ��[0001.041] I> 5) Base:0xf0f00000 Size:0x00100000
[0001.185] I> 6) Base:0xf3800000 Size:0x00400000
[0001.190] I> 7) Base:0xf1c00000 Size:0x00400000
[0001.194] I> 8) Base:0xf0e00000 Size:0x00100000
[0001.198] I> 9) Base:0xf0d00000 Size:0x00100000
[0001.203] I> 10) Base:0xf3000000 Size:0x00800000
[0001.207] I> 11) Base:0x40000000 Size:0x00040000
[0001.212] I> 12) Base:0xf0c00000 Size:0x00100000
[0001.216] I> 13) Base:0x40046000 Size:0x00002000
[0001.221] I> 14) Base:0x40048000 Size:0x00002000
[0001.225] I> 15) Base:0xac000000 Size:0x00004000
[0001.230] I> 16) Base:0x4004a000 Size:0x00002000
[0001.234] I> 17) Base:0xf0b00000 Size:0x00100000
[0001.239] I> 18) Base:0x4004c000 Size:0x00002000
[0001.243] I> 19) Base:0xf2200000 Size:0x00600000
[0001.248] I> 20) Base:0x4004e000 Size:0x00002000
[0001.252] I> 21) Base:0xf09d0000 Size:0x0000c000
[0001.257] I> 22) Base:0x00000000 Size:0x00000000
[0001.261] I> 23) Base:0xf09e0000 Size:0x00020000
[0001.265] I> 24) Base:0xf6000000 Size:0x02000000
[0001.270] I> 25) Base:0x40050000 Size:0x00002000
[0001.274] I> 26) Base:0x40040000 Size:0x00006000
[0001.279] I> 27) Base:0xf1800000 Size:0x00400000
[0001.283] I> 28) Base:0xf4c00000 Size:0x01400000
[0001.288] I> 29) Base:0xf1400000 Size:0x00400000
[0001.292] I> 30) Base:0xf0a00000 Size:0x00100000
[0001.297] I> 31) Base:0x00000000 Size:0x00000000
[0001.301] I> 32) Base:0xf8000000 Size:0x08000000
[0001.306] I> 33) Base:0x00000000 Size:0x00000000
[0001.310] I> 34) Base:0xf3c00000 Size:0x01000000
[0001.315] I> 35) Base:0xab000000 Size:0x01000000
[0001.319] I> 36) Base:0xa0000000 Size:0x0b000000
[0001.323] I> 37) Base:0xf2800000 Size:0x00800000
[0001.328] I> 38) Base:0x80000000 Size:0x20000000
[0001.332] I> 39) Base:0xb0000000 Size:0x08000000
[0001.337] I> 40) Base:0x00000000 Size:0x00000000
[0001.341] I> 41) Base:0x00000000 Size:0x00000000
[0001.346] I> 42) Base:0x00000000 Size:0x00000000
[0001.350] I> 43) Base:0x00000000 Size:0x00000000
[0001.355] I> 44) Base:0x00000000 Size:0x00000000
[0001.359] I> 45) Base:0x00000000 Size:0x00000000
[0001.364] GIC-SPI Target CPU: 0
[0001.367] Interrupts Init done
[0001.369] calling constructors
[0001.372] initializing heap
[0001.375] I> Heap: [0xa06905a8 … 0xab000000]
[0001.379] initializing threads
[0001.382] initializing timers
[0001.385] creating bootstrap completion thread
[0001.389] top of bootstrap2()
[0001.392] CPU: MIDR: 0x4E0F0040, MPIDR: 0x80000000
[0001.397] initializing platform
[0001.400] E> DEVICE_PROD: Invalid value data = 0, size = 0.
[0001.405] W> device prod register failed
[0001.409] I> Bl_dtb @0xaaf00000
[0001.414] E> “plugin-manager” doesn’t exist, creating
[0001.417] E> “ids” doesn’t exist, creating
[0001.421] E> “connection” doesn’t exist, creating
[0001.425] E> “configs” doesn’t exist, creating
[0001.433] I> Find /i2c@3160000’s alias i2c0
[0001.434] I> Reading eeprom i2c=0 address=0x50
[0001.463] I> Device at /i2c@3160000:0x50
[0001.463] I> Reading eeprom i2c=0 address=0x57
[0001.488] I> Device at /i2c@3160000:0x57
[0001.490] I> Find /i2c@c240000’s alias i2c1
[0001.490] I> Reading eeprom i2c=1 address=0x50
[0001.492] E> I2C: slave not found in slaves.
[0001.492] E> I2C: Could not write 0 bytes to slave: 0x00a0 with repeat start t.
[0001.493] E> I2C_DEV: Failed to send register address 0x00000000.
[0001.494] E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xa0 a.
[0001.502] E> eeprom: Retry to read I2C slave device.
[0001.507] E> I2C: slave not found in slaves.
[0001.511] E> I2C: Could not write 0 bytes to slave: 0x00a0 with repeat start t.
[0001.519] E> I2C_DEV: Failed to send register address 0x00000000.
[0001.524] E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xa0 a.
[0001.534] E> eeprom: Failed to read I2C slave device
[0001.539] I> Eeprom read failed 0x3526070d
[0001.543] I> create_pm_ids: id: 3668-0000-200-G, len: 15
[0001.548] I> config: mem-type:00,power-config:00,misc-config:00,modem-config:03
[0001.559] I> create_pm_ids: id: 3509-0000-100-F, len: 15
[0001.564] I> config: mem-type:00,power-config:00,misc-config:00,modem-config:03
[0001.575] I> Adding plugin-manager/ids/3668-0000-200=/i2c@3160000:module@0x50
[0001.582] E> “i2c@3160000” doesn’t exist, creating
[0001.587] E> “module@0x50” doesn’t exist, creating
[0001.591] I> Adding plugin-manager/ids/3509-0000-100=/i2c@3160000:module@0x57
[0001.598] E> “module@0x57” doesn’t exist, creating
[0001.604] I> Adding plugin-manager/cvm
[0001.607] E> “chip-id” doesn’t exist, creating
[0001.611] I> Adding plugin-manager/chip-id/A02
[0001.615] I> Plugin-manager override starting
[0001.620] I> node /plugin-manager/fragment-pcie-c5-rp matches
[0001.628] I> node /plugin-manager/fragement-tegra-wdt-en matches
[0001.634] I> node /plugin-manager/fragement-tegra-sdhci-emmc-dis matches
[0001.641] I> Disable plugin-manager status in FDT
[0001.642] I> Plugin-manager override finished successfully
[0001.647] I> gpio framework initialized
[0001.652] I> tegrabl_gpio_driver_register: register ‘nvidia,tegra194-gpio’ drir
[0001.659] I> tegrabl_gpio_driver_register: register 'nvidia,tegra194-gpio-aon’r
[0001.666] I> tegrabl_tca9539_init: i2c bus: 1, slave addr: 0x46
[0001.673] E> fetch_driver_phandle_from_dt: failed to get node with compatible 9
[0001.680] E> fetch_driver_phandle_from_dt: failed to get node with compatible 9
[0001.688] W> tegrabl_tca9539_init: failed to fetch phandle from dt
[0001.694] I> tegrabl_tca9539_init: i2c bus: 1, slave addr: 0x44
[0001.700] E> fetch_driver_phandle_from_dt: failed to get node with compatible 9
[0001.708] E> fetch_driver_phandle_from_dt: failed to get node with compatible 9
[0001.715] W> tegrabl_tca9539_init: failed to fetch phandle from dt
[0001.722] I> fixed regulator driver initialized
[0001.731] I> register ‘maxim’ power off handle
[0001.731] I> virtual i2c enabled
[0001.733] I> registered ‘maxim,max20024’ pmic
[0001.738] I> tegrabl_gpio_driver_register: register ‘max20024-gpio’ driver
[0001.744] I> Boot-device: QSPI
[0001.747] I> Boot_device: QSPI_FLASH instance: 0
[0001.752] I> QSPI source rate = 204000 Khz
[0001.755] I> Requested rate for QSPI clock = 34000 Khz
[0001.761] I> BPMP-set rate for QSPI clk = 34000 Khz
[0001.765] I> QSPI Flash Size = 32 MB
[0001.769] I> Qspi initialized successfully
[0001.772] I> qspi flash-0 params source = boot args
[0001.777] I> create_pm_ids: id: 3668-0000-200-G, len: 15
[0001.782] I> config: mem-type:00,power-config:00,misc-config:00,modem-config:03
[0001.793] I> create_pm_ids: id: 3509-0000-100-F, len: 15
[0001.799] I> config: mem-type:00,power-config:00,misc-config:00,modem-config:03
[0001.810] I> Found sdcard
[0001.814] I> enabling ‘vdd-sdmmc1-sw’ regulator
[0001.820] I> regulator ‘vdd-sdmmc1-sw’ already enabled
[0002.069] I> sdmmc SDR mode
[0002.084] I> -0 params source =
[0002.085] I> Found 47 partitions in QSPI_FLASH (instance 0)
[0002.093] I> Found 11 partitions in SDCARD (instance 0)
[0002.099] I> regulator ‘vdd-hdmi-5v0’ already enabled
[0002.102] I> regulator ‘vdd-hdmi-5v0’ already enabled
[0002.103] I> hdmi cable connected
[0002.104] E> set volts not configured for ‘vdd-1v0’
[0002.105] E> set volts not configured for ‘vdd-1v8-hs’
[0002.107] E> invalid display type
[0002.108] E> cannot find any other nvdisp nodes
[0002.123] I> edid read success
[0002.135] I> edid read success
[0002.136] I> width = 640, height = 480, frequency = 25174825
[0002.136] I> width = 640, height = 480, frequency = 25174825
[0002.137] I> width = 640, height = 480, frequency = 25174825
[0002.137] I> width = 1366, height = 768, frequency = 85500000
[0002.137] I> width = 1280, height = 720, frequency = 74250000
[0002.141] I> width = 1920, height = 1080, frequency = 74175824
[0002.147] I> width = 1280, height = 720, frequency = 74175824
[0002.152] I> width = 640, height = 480, frequency = 25174825
[0002.158] I> width = 720, height = 480, frequency = 26973026
[0002.163] I> width = 1280, height = 720, frequency = 74175824
[0002.169] I> width = 720, height = 576, frequency = 26973026
[0002.174] I> Best mode Width = 1280, Height = 720, freq = 74175824
[0002.184] I> hdmi_enable, starting HDMI initialisation
[0002.190] I> hdmi_enable, HDMI initialisation complete
[0002.196] I> Load in CBoot Boot Options partition and parse it
[0002.197] E> Error -9 when finding node with path /boot-configuration
[0002.202] E> tegrabl_cbo_parse_info: “boot-configuration” not found in CBO fil.
[0002.210] I> Hit any key to stop autoboot: 4 3 2 1
[0004.218] initializing target
[0004.218] calling apps_init()
[0004.219] starting app kernel_boot_app
[0004.225] I> found decompressor handler: lz4-legacy
[0004.225] I> decompressing BMP blob …
[0004.229] I> Kernel type = Normal
[0004.229] I> Loading kernel-bootctrl from partition
[0004.229] I> Loading partition kernel-bootctrl at 0xa4660000 from device(0x6)
[0004.254] W> tegrabl_get_kernel_bootctrl: magic number(0x00000000) is invalid
[0004.254] W> tegrabl_get_kernel_bootctrl: use default dummy boot control data
[0004.255] I> ########## SD boot ##########
[0004.255] I> Found sdcard
[0004.256] I> regulator ‘vdd-sdmmc1-sw’ already enabled
[0004.259] I> regulator ‘vdd-sdmmc1-sw’ already enabled
[0004.294] I> sdmmc SDR mode
[0004.309] I> -0 params source =
[0004.309] I> Already published: 00060000
[0004.309] I> Look for boot partition
[0004.310] I> Fallback: assuming 0th partition is boot partition
[0004.310] I> Detect filesystem
[0004.326] I> Loading extlinux.conf …
[0004.327] I> rootfs path: /sd/boot/extlinux/extlinux.conf
[0004.351] I> L4T boot options
[0004.352] I> [1]: “primary kernel”
[0004.352] I> Enter choice:
[0007.353] I> Continuing with default option: 1
[0007.353] I> Loading kernel sig file from rootfs …
[0007.353] I> rootfs path: /sd/boot/Image.sig
[0007.366] I> Loading kernel binary from rootfs …
[0007.366] I> rootfs path: /sd/boot/Image
[0010.186] I> Validate kernel …
[0010.186] I> T19x: Authenticate kernel (bin_type: 37), max size 0x5000000
[0010.517] I> No kernel-dtb binary path
[0010.518] W> No valid slot number is found in scratch register
[0010.518] W> Return default slot: _a
[0010.518] I> A/B: bin_type (38) slot 0
[0010.519] I> Loading kernel-dtb from partition
[0010.519] I> Loading partition kernel-dtb at 0x91000000 from device(0x6)
[0010.560] I> Validate kernel-dtb …
[0010.561] I> T19x: Authenticate kernel-dtb (bin_type: 38), max size 0x400000
[0010.564] I> Loading ramdisk from rootfs …
[0010.564] I> rootfs path: /sd/boot/initrd
[0011.025] I> Kernel hdr @0xa4660000
[0011.026] I> Kernel dtb @0x90000000
[0011.026] I> decompressor handler not found
[0011.026] I> Copying kernel image (34265104 bytes) from 0xa4660000 to 0x800800e
[0011.037] I> Updated bpmp info to DTB
[0011.038] I> Ramdisk: Base: 0x92000000; Size: 0x54ec8f
[0011.039] I> Updated initrd info to DTB
[0011.039] W> WARN: Fail to override “console=none” in commandline
[0011.039] E> tegrabl_linuxboot_add_disp_param, du 1 failed to get display paras
[0011.046] E> tegrabl_linuxboot_add_disp_param, du 1 failed to get display paras
[0011.053] W> No valid slot number is found in scratch register
[0011.059] W> Return default slot: _a
[0011.062] I> Active slot suffix:
[0011.065] I> add_boot_slot_suffix: slot_suffix =
[0011.070] I> Linux Cmdline: root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 co
[0011.107] I> Updated bootarg info to DTB
[0011.111] W> MAC addr invalid!
[0011.114] E> Failed to get WIFI MAC address
[0011.118] W> MAC addr invalid!
[0011.121] E> Failed to get Bluetooth MAC address
[0011.125] I> eeprom_get_mac_addr: MAC (type: 2): 48:b0:2d:05:9e:ca
[0011.132] E> “plugin-manager” doesn’t exist, creating
[0011.136] I> Adding /chosen/plugin-manager/cvm
[0011.140] E> “chip-id” doesn’t exist, creating
[0011.145] I> Adding /chosen/plugin-manager/chip-id
[0011.149] E> “configs” doesn’t exist, creating
[0011.154] I> Adding /chosen/plugin-manager/configs
[0011.158] E> “ids” doesn’t exist, creating
[0011.162] I> Adding /chosen/plugin-manager/ids
[0011.167] E> “odm-data” doesn’t exist, creating
[0011.171] I> Adding /chosen/plugin-manager/odm-data
[0011.178] E> “memory” doesn’t exist, creating
[0011.180] I> [0] START: 0x80000000, END: 0xac000000
[0011.184] I> [1] START: 0xac004000, END: 0xf09d0000
[0011.189] I> [2] START: 0xf09dc000, END: 0xf09e0000
[0011.194] I> dram_block larger than 80000000
[0011.198] I> [3] START: 0x100000000, END: 0x280000000
[0011.203] I> added [base:0x80000000, size:0x2c000000] to /memory
[0011.209] I> added [base:0xac200000, size:0x44600000] to /memory
[0011.215] I> added [base:0x100000000, size:0x180000000] to /memory
[0011.221] I> Updated memory info to DTB
[0011.225] E> add_disp_param: failed to get display params for du=1
[0011.231] E> “reset” doesn’t exist, creating
[0011.235] I> NVG: Logical CPU: 0; MPIDR: 0x80000000
[0011.239] I> NVG: Logical CPU: 1; MPIDR: 0x80000001
[0011.244] I> NVG: Logical CPU: 2; MPIDR: 0x80000100
[0011.249] I> NVG: Logical CPU: 3; MPIDR: 0x80000101
[0011.253] I> NVG: Logical CPU: 4; MPIDR: 0x80000200
[0011.258] I> NVG: Logical CPU: 5; MPIDR: 0x80000201
[0011.263] I> Deleted cpu@6 node in DT
[0011.266] I> Deleted cpu@7 node in DT
[0011.270] I> Deleted cluster3 node in FDT
[0011.274] I> Update arm-pmu in FDT
[0011.277] I> - update property: interrupts
[0011.281] I> - update property: interrupt-affinity
[0011.286] E> “misc-data” doesn’t exist, creating
[0011.290] I> Boot-device: QSPI
[0011.293] W> Unknown boot device
[0011.296] I> Add storage-qspi to plugin-manager/misc-data
[0011.301] W> Unknown storage device
[0011.305] I> Add serial number:1421020009762 as DT property
[0011.311] I> Plugin-manager override starting
[0011.315] I> node /plugin-manager/fragment-pcie-c5-rp matches
[0011.321] I> node /plugin-manager/fragement-tegra-wdt-en matches
[0011.327] I> node /plugin-manager/fragement-tegra-sdhci-emmc-dis matches
[0011.334] I> Disable plugin-manager status in FDT
[0011.337] I> Plugin-manager override finished successfully
[0011.342] I> tegrabl_load_kernel_and_dtb: Done
[0011.360] I> Kernel EP: 0x80080000, DTB: 0x90000000
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.140-tegra (buildbrain@mobile-u64-3193) (gcc ve0
[ 0.000000] Boot CPU: AArch64 Processor [4e0f0040]
[ 0.000000] OF: fdt:memory scan node memory, reg size 48,
[ 0.000000] OF: fdt: - 80000000 , 2c000000
[ 0.000000] OF: fdt: - ac200000 , 44600000
[ 0.000000] OF: fdt: - 100000000 , 180000000
[ 0.000000] earlycon: tegra_comb_uart0 at MMIO32 0x000000000c168000 (options)
[ 0.000000] bootconsole [tegra_comb_uart0] enabled
[ 0.000000] Found tegra_fbmem: 003a0000@a069c000
[ 0.000000] Found lut_mem: 00002008@a0696000
��WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: pll_d2 has no dyn ramp
WARNING: at platform/drivers/pg/pg-gpu-t194.c:185
WARNING: at platform/drivers/pg/pg-gpu-t194.c:185
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
��[ 2.002183] imx219 9-0010: imx219_board_setup: error during i2c read probe)
[ 2.002227] imx219 9-0010: board setup failed
[ 2.026194] imx219 10-0010: imx219_board_setup: error during i2c read probe )
[ 2.026232] imx219 10-0010: board setup failed
[ 4.909622] cgroup: cgroup2: unknown option “nsdelegate”
��WARNING: at platform/drivers/pg/pg-gpu-t194.c:185
WARNING: at platform/drivers/pg/pg-gpu-t194.c:185
��[ 6.520033] random: crng init done
[ 6.520180] random: 7 urandom warning(s) missed due to ratelimiting
[ 6.838447] rtk_btusb: btusb_open hdev->promisc ==0
[ 6.861511] rtk_btusb: fw name is rtl8822cu_fw
[ 6.868673] rtk_btusb: This is not 8723a, use new patch style!
[ 7.238995] using random self ethernet address
[ 7.239184] using random host ethernet address
[ 8.277447] using random self ethernet address
[ 8.277451] using random host ethernet address
��WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
WARNING: at platform/drivers/pg/pg-cv-t194.c:73
��[ 9.915157] CPU2: shutdown
[ 10.015122] CPU3: shutdown
[ 10.107168] CPU4: shutdown
[ 10.171359] CPU5: shutdown
Ubuntu 18.04.4 LTS localhost ttyTCU0
localhost login:
You are correct. There is a “quiet” word/token which is space delimited from other content. Wherever “quiet” shows it should be removed, and all other content left in place. A space separating content before the old quiet and after the old quiet would be all that is needed. You can verify this succeeded after a boot via whether or not “quiet” exists in the output of “cat /proc/cmdline”.
Got it. Thank you, @linuxdev. Now my problem is that I have yet to recover from the OTA update bug discussed previously. My NX is stuck in the state described above by the screenshot and serial console output. Any advice on that?
Is this a dev kit NX using a microSD card? If so, then you can use a host PC to directly work on that (I don’t know if you will find a way to repair, but you could find a way to recover important content ). If this is a production unit, then eMMC can be cloned instead of using the microSD on the host PC.
Someone else may know of a way to use the image from the failed unit with QEMU and make repairs, but I do not have enough experience with QEMU on a PC to say how to run the “apt” tool for fixes.
Yes it is a dev kit with an SD card.
Just so you know ahead of time, you can save a copy of the SD card rootfs partition prior to working on the card itself, or you can copy the partition to your host PC via dd and work on the copy. Either of those mean you can afford to make mistakes.
If you monitor “dmesg --follow” on your host PC, and then see what shows up as you connect the microSD card, it should tell you the device name. I’m going to make up the name “/dev/mmcblk2”, and use that for examples, but you would have to use the actual device name showing up on your PC.
The first partition will likely be the rootfs. With the card connected to the PC you can list partitions and their filesystem types:
lsblk -f /dev/mmcblk2
The partition which is “ext4” is the one you are interested in. I’ll pretend yours is “/dev/mmcblk2p1”.
Before you copy anything to your PC make sure your PC has a lot of spare disk space. “df -H -T -t ext4” will provide the amount of space on any partition running ext4 (you could leave out the “-t ext4” and see all partitions, even ones which are not actual storage).
To see the size of the actual partition (again pretending it is mmcblk2) size:
sudo gdisk -l /dev/mmcblk2 | grep APP
To copy this to your host PC, and assuming you have a lot of disk space…at least as large as the APP partition size…and better yet 50GB more than that:
sudo dd if=/dev/mmcblk2p1 of=backup.img bs=1M
You can then either mount the microSD card partition, or loopback mount the backup.img:
# I use "`/mnt`" out of tradition, but it could be any temporary location.
sudo mount /dev/mmcblk2p1 /mnt
ls /mnt/*
sudo umount /mnt
# Or, loopback mount of the backup.img:
sudo mount -o loop /where/ever/it/is/backup.img /mnt
ls /mnt/*
sudo umount /mnt
Once you have this it means anyone who can offer a means of using QEMU from the host PC to run apt operations can fix this directly on the host PC. I’d suggest saving the backup image and working directly on the microSD since it also implies you can test after any change. If it fails, then you can overwrite the modified APP partition with the backup.img and start clean again. If you can’t repair this way, then you can flash to the microSD again and then copy your backup.img home or other directories back in and save most of your work.
Thanks for the excellent advice. Unfortunately I’m stuck in the situation now where I have a brand new image written to my SD card, but I cannot boot the device. It is in a state described by the screen output and serial log shown above. Any ideas from these outputs what my current problem could be? Perhaps I should start a whole new thread?
I just had duplicated issue reported by other vendors.
Actually, I think that error indicates the display manager not working. Other functions should be fine.
But I would like to know did you already configure the user account? I mean… have you ever see ubuntu desktop showing up even once on your board?
Could you try to use UART console and run below command and see if desktop could be back?
sudo service gdm3 status (check the status first)
sudo service gdm3 restart
@WayneWWW yes I have been using the device for some months with no problems until I flashed a new OS to overcome the OTA update issue. I am unable to issue commands via the UART console. It stops with that login prompt, but it does not take input and I am in any case not able to go through the board setup to set login credentials in the first place.
1 Like
Hi,
It seems we have multiple issues here.
- The uart has no response
- You didn’t give set any login credentials but the login prompt shows up.
- Device cannot enter the desktop.
For (1), I would suspect your UART RX does not connect well so that it cannot receive anything from your keyboard.
For (2), Have you tried to use oem-config to setup already?
For (3), let’s wait for issue 1 and 2 to be resolved.
I have solved the first issue. The NX develop guide mentions that minicom may have problems with the UTF-8 character set (weird) so I used gtkterm instead. Now I can enter credentials at the login. I tried my old credentials for kicks, which of course didn’t work. I tried nvidia/nvidia which also did not work. I have tried re-flashing again and running oem-config with monitor and keyboard, but it never launches the oem-config tool. I re-flashed again (so that oem-config tool would run instead of being de-activated on second boot) and tried to run oem-config over the USB connection and again over serial UART, but again it never gets as far as launching the oem-config tool. So my understanding is that rebooting disables the oem-config tool. Rebooting after failing to run the oem-config the first time apparently causes it to go straight to a login (over serial connection), but no credentials are set. Attached is screenshot showing the state after the initial boot after a fresh OS flash. And of course I have tried to complete configuration setup on serial port provided by USB connection at /dev/ttyACM0 (the confirmed location of the USB connection to device). EDITED: There’s no option to upload screenshot. The last line of output is:
“A start job is running for End-user configuration after initial OEM installation (Debconf UI) …”
Well this is very odd, but after re-flashing I don’t know how many times, I re-flashed yet again with the SDK manager while leaving the HDMI cable connected (as I have many times before), and it spontaneously entered the oem-config GUI (without rebooting) and I was able to complete the setup. SDK components are installing now. I’m glad that’s over, but I don’t know why that happened. I’ve set up several Nanos and Xaviers and have set this NX up a couple of times and never had problems. Have a great weekend.
Hi,
OEM-config will not show if you connect the HDMI. It will only show on the serial console on your host with interface /dev/ttyACM0 when no monitor is connected.
Hi, I am currently having a strange problem. I have a Jetson Nano 2gb device and today I’ve made an upgrade but when I reboot my system I encounter a black screen with a blinking cursor. I tried this method you mentioned here and it actually worked and I accessed my desktop. However when I tried to reboot again I still encounter the same black screen.When I checked the status it gives:
gdm.services - GNOME Display Manager
Loaded: loaded //lib/systemd/system/gdm.service; static; vendor preset: enabled)
Active: inactive (dead)
I think it shouldn’t say inactive (dead). How can I resolve that?
Hi,
This is jetson nx forum board. Please check your topic on Jetson Nano forum.
Also, your issue has been reported by other users too. You can find the topic there.