After some time ago i started to be unable to boot my Nano board.
Device not answer anymore in regular boot.
( environment is Ubuntu 18.04 updated in Intel desktop machine and device connected direct on mainboard USB )
When in recovery mode, it appears on the list properly:
Bus 001 Device 021: ID 0955:7f21 NVidia Corp.
Flash starts properly with:
sudo ./flash.sh jetson-nano-devkit mmcblk0p1
And then after fails.
[ 13.0731 ] tegrahost --updatesigheader tegra210-p3448-0000-p3449-0000-b00.dtb_blheader.encrypt tegra210-p3448-0000-p3449-0000-b00.dtb_blheader.hash zerosbk
[ 13.7955 ]
[ 13.7975 ] Sending bootloader and pre-requisite binaries
[ 13.8013 ] tegrarcm --download ebt cboot.bin.encrypt 0 0 --download rp1 tegra210-p3448-0000-p3449-0000-b00.dtb.encrypt 0
[ 13.8043 ] Applet version 00.01.0000
[ 13.8071 ] Sending ebt
[ 13.8721 ]
Error: Return value 1
Command tegrarcm --download ebt cboot.bin.encrypt 0 0 --download rp1 tegra210-p3448-0000-p3449-0000-b00.dtb.encrypt 0
Failed flashing t210ref.
Further investigation show that using tegrarcm --uid after board is started works on first time, then generates a error on second time
ubuntu@ubuntu:/nvidia/Linux_for_Tegra$ sudo ./bootloader/tegrarcm --uid
BR_CID: 0x32101001644568020000000012fe8400
ubuntu@ubuntu:/nvidia/Linux_for_Tegra$
ubuntu@ubuntu:/nvidia/Linux_for_Tegra$ sudo ./bootloader/tegrarcm --uid
Failed to read UID
I tried with a power measureed 5A external power source and regular 2,5 A USB output, so i can really rule out power issues, so i’m out of ideas.
Any possible extra idea on how to restore board ?
Can you confirm your host PC is a native Ubuntu 18.04? If you use a VM you’ll run into this issue. If you are using Ubuntu 18.04 without a VM, then it should work.
Yes, system is running natively on the hardware.
No VM is involved. Board simply not answer.
It shouldn’t matter, but is this a dev kit, or eMMC model with a third party carrier board? Mostly I am thinking this might be time for RMA, but something as simple as a charger cable replacing the micro-B USB cable of a dev kit could cause a failure during the middle of a flash (the dev kit micro-B USB is very high quality for high speed and sustained data transfer, whereas about 3/4 of all charger cables fail due to poor construction of data wires).
The behavior with both cases are same.Using regular USB and with an external charger.
The charger is providing stable 5A output, measured in a multimeter. This is a eMMC model.
Btw, i forgot to mention on previous post that the boart worked for some time when arrived.
This is the output of serial port during flash. I would appreciate any direction where i can try different approach.
Welcome to minicom 2.7.1
OPTIONS: I18n
Compiled on Aug 13 2017, 15:25:34.
Port /dev/ttyUSB0, 11:22:06
Press CTRL-A Z for help on special keys
[0013.657] Enabled early print
[0013.660] [L4T TegraBoot] (version 00.00.2018.01-l4t-7dfcb60a)
[0013.665] Processing in recovery mode
[0013.668] A02 Bootrom Patch rev = 1023
[0013.672] Power-up reason: pmc por
[0013.675] Established communication link with host
[0014.674] NvTbootI2cWaitForTransferComplete(): error code 0x00000005 I2C Transaction could not complete within time
[0014.684] NvTbootI2cWrite(): error code 0x00000005 Error while starting write transaction
[0014.691] NvTbootI2cDeviceRead(): error code 0x00045001 Error while sending the offset to slave
[0014.700] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with error code 0x00045001
[0018.431] Odmdata from BCT: 0x00094000
[0018.435] DebugPort= 0x3
[0018.448] NvTbootI2cWaitForTransferComplete(): error code 0x00000005 I2C Transaction could not complete within time
[0018.469] NvTbootI2cWaitForTransferComplete(): error code 0x00000005 I2C Transaction could not complete within time
[0018.479] NvTbootI2cWrite(): error code 0x00000005 Error while starting write transaction
[0018.486] NvTbootI2cDeviceRead(): error code 0x00045001 Error while sending the offset to slave
[0018.495] NvTbootI2c: Read failed for slave 0xac, offset 0x00 with error code 0x00045001
[0018.503] Reading Board-Type unsuccessful
[0018.507] BoardId read from EEPROM/NCT: 0
[0018.510] Unsupported Platform 0
[0018.513] Downloaded BCT successfully
Seems i2c problem causes the board info fails to pass to the host side.
If you said this error “suddenly” happens and your board was once working, I think you need to RMA it.
BTW, is your board giving any output from uar console when you try to boot up?
Nope, the board only get some output from UART when i truied to flash ( output above )
On normal mode, no serial output at all.
How can i RMA it ? I
what if you do sdcard image writing to microsdcard without connecting the board to anywhere with any cable [e.g. using card reader at Host PC], but booting from the microsdcard written from sdcard image?
did you try flashing from different PC? with different USB cable?
Ok, just for the sake of “try again”, but as i said before, i used more than one computer, and used high quality Sd cards, and of course direct flash the sd was the first thing i did, but seen like people keeping pointing me out the getting started tutorial over and over.
So the answer is no, no answer from the board in non-recovery mode, not a single UART answer. It simply stop boots.
And yes, i flashed the sd card in three different places, with three different controllers.
Honestly, no clue anymore.
Hello again
Is there any other way to request the RMA beyond the chat ? I already three time waited over an hour with the window opened and no agent answer the chat.
It keeps on “Searching for an available agent”
