Group Actions
Engagement
  • Author Author: jomoenginer
  • Date Created: Date Created
  • Views 3129 views
  • Likes 10 likes
  • Comments 12 comments
Related
Recommended

NVIDIA Jetson Nano

jomoenginer

I recently received the NVIDIA Jetson Nano Developers Kit I had ordered.

https://www.nvidia.com/en-us/autonomous-machines/embedded-systems/jetson-nano/

 

Now it's time to build a JetBot for running ROS.  Let the fun begin.

 

image

Parents Comment Children
  • in reply to DAB

    I plan to cover this in future postings, however from the NVIDIA Jetson Nano User's Guide:

     

    The carrier board consumes between 0.5W (at 2A) and 1.25W (at 4A) with no peripherals attached

     

    There are two options to power the Jetson Nano:

    1. 5V 4A Switching Power supply to the carrier board barrel jack. (A jumper is required to turn off the USB power option)

    2. 5V 2.5 A USB power supply

     

    However, I have yet to get the board to fully power on with any of the multiple power supplies I have on hand.  All I get is the NVIDIA Splash Screen.  Others have posted something similar on the NVIDIA forums which now includes me as well.

  • in reply to jomoenginer

    That seems like an odd way to spec power consumption.  Maybe to account for power regulators in the path?

     

    Please post how you resolve your problem as I’ll be getting one in a few weeks.

  • in reply to jomoenginer

    Since the Jetson Nano is really a SOM on top of a carrier board, perhaps the power statement seems to be associated with the carrier board.

     

    The boot issue was resolved by reflashing the uSD card with Etcher (I'm using Ubuntu 16.04.6 LTS) and then running GParted on the uSD device and letting it allocate the rest of the space on the card.  Initially, when plugging the uSD back in to my PC there were errors reported and after looking this up I found the solution with GParted.  Although, there is a statement of such in the dmesg message.

     

    This is what was seen before running GParted

    [ 3480.214799] usb-storage 2-4.4:1.0: USB Mass Storage device detected
[ 3480.214986] scsi host7: usb-storage 2-4.4:1.0
[ 3481.245848] scsi 7:0:0:0: Direct-Access Mass Storage Device 1.00 PQ: 0 ANSI: 0 CCS
[ 3481.246297] sd 7:0:0:0: Attached scsi generic sg4 type 0
[ 3481.496082] sd 7:0:0:0: [sdd] 62521344 512-byte logical blocks: (32.0 GB/29.8 GiB)
[ 3481.496698] sd 7:0:0:0: [sdd] Write Protect is off
[ 3481.496702] sd 7:0:0:0: [sdd] Mode Sense: 03 00 00 00
[ 3481.497336] sd 7:0:0:0: [sdd] No Caching mode page found
[ 3481.497342] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[ 3481.506470] GPT:Primary header thinks Alt. header is not at the end of the disk.
[ 3481.506473] GPT:25165823 != 62521343
[ 3481.506474] GPT:Alternate GPT header not at the end of the disk.
[ 3481.506476] GPT:25165823 != 62521343
[ 3481.506476] GPT: Use GNU Parted to correct GPT errors.
[ 3481.506500] sdd: sdd1 sdd2 sdd3 sdd4 sdd5 sdd6 sdd7 sdd8 sdd9 sdd10 sdd11 sdd12

    And fddisk

    sudo fdisk /dev/sdd

Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

GPT PMBR size mismatch (25165823 != 62521343) will be corrected by w(rite).
GPT PMBR size mismatch (25165823 != 62521343) will be corrected by w(rite).

Command (m for help): q