System does not fully boot after reflashing a Tegra device on DrivePX2

Autonomous Vehicles DRIVE PX 2 DRIVE - Linux
1

I am trying to just flash “Tegra b” on my DrivePX2. The steps I followed is

  1. Put the “Tegra b” into recovery mode from Aurix

    shell> tegrarecovery b on
    shell> tegrareset b

  2. On the host “cd vibrante-t186ref-foundation/utils/scripts/bootburn”

    ./bootburn.sh -b p2379c01-t186b -l

    (The above command flashes the Tegra b)

  3. reset the Tegra b from recovery mode through Aurix

    shell> tegrarecovery b off
    shell> tegrareset b

  4. “Tegra b” boots up

    On the UART console of “Tegra b” it hangs after the following output
    :
    :
    :
    OK ] Started Getty on tty1.
    target=drive-px2-b, card=, kernel=4.4.38-rt49-tegra
    [ OK ] Started CUPS Scheduler.
    [ OK ] Started Board specific initialization.
    [ OK ] Reached target Companion services for Nvidia Tegra.
    Starting devOTA setup…
    devOTA service started …
    Launching devOTA setup …
    Current PDK version is 4.1.8.0.9387945.9408590
    SSL cert hash files missing! Performing rehash
    [ 36.888719] bash[2048]: starting Aurix FW checking…
    [ 36.896668] bash[2048]: Checking arguments…
    [ 36.904607] bash[2048]: Aurix OTA is only valid for DrivePX2 Tegra A and ACR
    [ 36.917091] bash[2048]: Created symlink from /etc/systemd/system/nv_aurix_check_fw.service to /dev/null.

  5. I can ssh into “Tegra b”, but console is hung as shown in step 4

Any comments will be greatly appreciated

Thanks
Anup

2

Dear anup.pemmaiah,

Could you please refer to below link to flash?
There’s a bit more clear description of the flashing commands here. Thanks.

3

Hi SteveNV.

Thank you for you comments. Earlier I was following the link Autonomous Vehicle Development Platforms | NVIDIA Docs

But for the recent try, I followed the link that you referred. I still see the same issue.

The steps I followed is

  1. Put “Tegra b” into recovery mode from Aurix

    shell> tegrarecovery b on
    shell> tegrareset b

  2. On the host, executed the following commands

    • For P2379 Tegra B:
    cd /vibrante-t186ref-foundation/
    make -f Makefile.bind BOARD=p2379c01-t186b PCT=linux
    ./utils/scripts/bootburn/bootburn.sh -b p2379c01-t186b -H

  3. Connect to the “Tegra b” UART /dev/ttyUSB6, and removed the board from forced recovery mode

    shell> tegrarecovery b off
    shell> tegrareset b

The console is hung after the following output
:
:
:
:
target=drive-px2-b, card=, kernel=4.4.38-rt49-tegra
[ OK ] Started Board specific initialization.
[ OK ] Reached target Companion services for Nvidia Tegra.
Starting devOTA setup…
devOTA service started …
Launching devOTA setup …
Current PDK version is 4.1.8.0.9387945.9408590
SSL cert hash files missing! Performing rehash
[ 39.096554] bash[2012]: starting Aurix FW checking…
[ 39.104678] bash[2012]: Checking arguments…
[ 39.112706] bash[2012]: Aurix OTA is only valid for DrivePX2 Tegra A and ACR
[ 39.117341] bash[2012]: Created symlink from /etc/systemd/system/nv_aurix_check_fw.service to /dev/null.
[ 124.991502] NOHZ: local_softirq_pending 80

4

It is was trying to start Xserver (startx). One hack was I killed the startx and got the console access.

5

Solved the issue. I was just working on Console. Since it was hung on startx, I hooked up a monitor to the HDMI port of Tegra b device and completed the initial tasks and everything looks good