Excited to recieve my Jetson Nano today. Saddly its DOA serial dump at head

[0000.163] [L4T TegraBoot] (version 00.00.2018.01-l4t-e82258de)
[0000.168] Processing in cold boot mode Bootloader 2
[0000.173] A02 Bootrom Patch rev = 1023
[0000.177] Power-up reason: pmc por
[0000.180] No Battery Present
[0000.182] pmic max77620 reset reason
[0000.186] pmic max77620 NVERC : 0x40
[0000.189] RamCode = 0
[0000.191] Platform has DDR4 type RAM
[0000.195] max77620 disabling SD1 Remote Sense
[0000.199] Setting DDR voltage to 1125mv
[0000.203] Serial Number of Pmic Max77663: 0x1126ed
[0000.211] Entering ramdump check
[0000.214] Get RamDumpCarveOut = 0x0
[0000.217] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8
[0000.222] Last reboot was clean, booting normally!
[0000.227] Sdram initialization is successful
[0000.231] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000
[0000.237] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000
[0000.242] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000
[0000.248] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000
[0000.254] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000
[0000.260] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000
[0000.266] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000
[0000.272] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000
[0000.288] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000
[0000.294] Platform-DebugCarveout: 0
[0000.297] Nck Carveout Base=0x00000000ff080000 Size=0x00200000
[0000.303] Non secure mode, and RB not enabled.
[0000.307] BoardID = 3448, SKU = 0x0
[0000.311] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.314] Nano-SD: checking PT table on QSPI …
[0000.319] Read PT from (2:0)
[0000.334] Using BFS PT to query partitions
[0000.338] PT: Partition TBC NOT found !
[0000.342] Warning: Find Partition via PT Failed
[0000.346] BoardID = 3448, SKU = 0x0
[0000.350] QSPI-ONLY: SkipQspiOnlyFlag = 0
[0000.353] Nano-SD: checking PT table on QSPI …
[0000.358] PT: Partition TBC NOT found !
[0000.361] Warning: Find Partition via PT Failed
[0000.366] Error is 1

Serial output unter bootin

Attempted to run SDK Manager but its requirements allude me running only Opensuse, Fedora, and POP I have been thwarted. I guess it’s time to just return the brick? Your system is very un-flexable and every step difficult. I thought I would use this platform as a first step but it seems like the wrong step. I may look into the docker but I have no experience with that and found your instructions useless. Thanks I guess.

ok
went ahead and installed ubntu 18 and got sdk rolling but I cannot get this thing in recovery mode.
set for barrel jack power short buttons on 3/4 4/5 power on holding 3/4 cycle 4/5 and nothing except for the light resets.

Please check quick start guide for how to set device into recovery mode.

1 Like

actually yes it was 9/10 7/8 didn’t see the 1 at the opposite end where the leds are plugged from the pc button set. Went by the screen prints.

Still no luck.

Hi,

If the recovery pin is 9/10 on your board, it should be B01 carrier board.
The steps should be

  1. Plug the power jack so the Led should light up.
  2. Jumper → 9/10 and hold
  3. Jumper → 7/8 → this will reset the board, so LED will blink for a second
  4. Remove jumper on 7/8
  5. Remove jumper on 9/10

How did you know you fail to enter recovery mode?

1 Like

ok I have movement. I swapped the usb to another socket on the second usb controller on my pc and it showed up. This was after sitting for a bit in recovery. funny thing is it was there previously.

1 Like

Flashing OS 99% and seems to be stuck.

Do I want to wait???

[1229.488] [L4T TegraBoot] (version ��]!���^�e)
[1229.492] Processing in recovery mode
[1229.496] A02 Bootrom Patch rev = 1023
[1229.499] Power-up reason: pmc por
[1229.502] Established communication link with host
[1230.668] NvTbootI2cWrite(): error code 0x00045100 Error while starting write transaction
[1230.676] NvTbootI2cDeviceRead(): error code 0x00045001 Error while sending the offset to slave
[1230.685] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with error code 0x00045001

Please directly go to Linux_for_Tegra on your host and use flash.sh to flash your board.

The quick start guide I posted earlier has some guidance of how to run flash.sh.

It will tell us whether the flash process is done quickly.

The difference is flash.sh only install the OS while the sdkmanager will do both installing OS and all other SDK.

Since we are dealing with system side issue now, we should have quick check on system issue first. Those SDK can be installed later.

Is this bad? Cant imagine the flash is progressing.

[0053.893] Established communication link with host
[0055.038] NvTbootI2cWrite(): error code 0x00045100 Error while starting write transaction
[0055.046] NvTbootI2cDeviceRead(): error code 0x00045001 Error while sending the offset to slave
[0055.054] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with error code 0x00045001







user@ubuntu1804:~/nvidia_Tegra_Linux/Linux_for_Tegra$ sudo ./flash.sh jetson-nano-devkit mmcblk0p1
###############################################################################
# L4T BSP Information:
# R32 , REVISION: 5.1
###############################################################################
# Target Board Information:
# Name: jetson-nano-devkit, Board Family: t210ref, SoC: Tegra 210, 
# OpMode: production, Boot Authentication: , 
# Disk encryption: disabled ,
###############################################################################
./tegraflash.py --chip 0x21 --applet "/home/user/nvidia_Tegra_Linux/Linux_for_Tegra/bootloader/nvtboot_recovery.bin" --skipuid --cmd "dump eeprom boardinfo cvm.bin" 
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands


 
[   0.0018 ] Generating RCM messages
[   0.0034 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm /home/user/nvidia_Tegra_Linux/Linux_for_Tegra/bootloader/nvtboot_recovery.bin 0 0
[   0.0048 ] RCM 0 is saved as rcm_0.rcm
[   0.0048 ] RCM 1 is saved as rcm_1.rcm
[   0.0048 ] List of rcm files are saved in rcm_list.xml
[   0.0048 ] 
[   0.0048 ] Signing RCM messages
[   0.0054 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[   0.0067 ] Assuming zero filled SBK key
[   0.0109 ] 
[   0.0110 ] Copying signature to RCM mesages
[   0.0123 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[   0.0141 ] 
[   0.0142 ] Boot Rom communication
[   0.0153 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml --skipuid
[   0.0164 ] RCM version 0X210001
[   0.1750 ] Boot Rom communication completed
[   1.2631 ] 
[   1.2631 ] dump EEPROM info
[   1.2647 ] tegrarcm --oem platformdetails eeprom /home/user/nvidia_Tegra_Linux/Linux_for_Tegra/bootloader/cvm.bin
[   1.2658 ] Applet version 00.01.0000

Serial output:

0053.860] Enabled early print
[0053.863] [L4T TegraBoot] (version ���!����^�e#�h�spS��1�V���O���&�6�Ka        ����5�#
VU��]����{��c�"\i��F��, G�0�UAl�$��K�q��3����r�$��z?�*'+���[lp.�E
�H7�����8�ຜ_+~��W�ʥ�=ڑ��;�٭?�h�G�H�)
[0053.883] Processing in recovery mode
[0053.887] A02 Bootrom Patch rev = 1023
[0053.890] Power-up reason: pmc por
[0053.893] Established communication link with host
[0055.038] NvTbootI2cWrite(): error code 0x00045100 Error while starting write transaction
[0055.046] NvTbootI2cDeviceRead(): error code 0x00045001 Error while sending the offset to slave
[0055.054] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with error code 0x00045001

Is this a ubutnu host but not VM ?

1 Like

Arrrg Yes

Instated to bare metal now and progressed further. Nano boots to desktop now

Thanks for the help WayneWWW!

However my PC system seems very unstable under Ubuntu 18.4 unless it is the nano software. Whole system crash if the screen times out to turn off on or if I try to go into settings to turn off the timer. I had to sit and bump the mouse every now and than to make sure I would not crash out mid process.

infuriating little piece!

Just going to name this thing crash. Cant seem to update without having to start over with a new flash install. Is it normal for the things to fail during apt upgrade?

No, this is not normal. Always share us a log so we can see what’s going on.

I think I figured it out. The 64gb Samsun evo sd cards I was attempting to use were getting very hot. Not up to the long write times? I Switched over to a kown good 32gb Sandisk and things seem stable since.

Again I do appreciate the help.

1 Like