background image

Clara Holoscan Developer Kit User Guide 

 

 

 

 

 

 

 

The Clara Holoscan Developer Kit includes a pre-installed 500GB m.2 solid-state drive (SSD), 
but this drive is not partitioned or mounted by default. This page outlines the steps to partition 
and format the drive for use after the initial SDK installation. 

 

Note: 

 

If the Clara AGX Developer Kit is re-flashed with a new JetPack image, the partition table 

of the m.2 drive will not be modified and the contents of the partition will be retained. In 
this case, you can skip the Create Partition steps; however, you should still follow the Mount 

Partition steps to remount the partition.

 

Any state, binaries, or docker images that persist on the m.2 drive after flashing the system 

may be incompatible with new libraries or components that are flashed onto the system. 

You  may  need  to recompile or rebuild these persistent objects to restore runtime 

compatibility with the system.

 

 

Note:

 

The following steps assume that the m.2 drive is identified by the Clara Holoscan Developer 

Kit as 

/dev/nvme0n1

. This is the case if no additional drives have been attached, but if 

other drives (such as USB drives) have been attached, then the disk identifier may change. 
You  can  verify this  by looking at the symlink to the drive that is created for the m.2 
hardware address on the system. If the symlink  below shows something other than 

../../nvme0n1

, replace all instances of “nvme0n1”  in the instruction below with the 

identifier that is being used by your system:

 

$ ls -l /dev/disk/by-path/platform-14160000.pcie-pci-0004\:01\:00.0-nvme-1 

lrwxrwxrwx 1 root root 13 Jun  2 14:14 /dev/disk/by-path/platform-

14160000.pcie-pci-0004:01:00.0-nvme-1 -> ../../nvme0n1 

 
Create the Partition 

1.

 

Launch fdisk utility: 

$ sudo fdisk /dev/nvme0n1  

2.

 

Create a new primary partition using the “n” command, then accept the defaults by 
pressing Enter for the next 4 questions. This will create a single partition that uses the 
entire drive.

 

Command (m for help): n 

Partition type 

   p   primary (0 primary, 0 extended, 4 free) 

   e   extended (container for logical partitions) 

Select (default p): 

  

Using default response p. 

Partition number (1-4, default 1): 

Summary of Contents for Clara Holoscan

Page 1: ...p the Developer Kit 2 Hardware Setup 2 Requirements 2 Precautions 2 System Overview 3 Main Components 3 Tech Specs 3 I O and external interfaces 5 Powering up the System 7 Flashing and Updating the Cl...

Page 2: ...A compatible cable should meet the following requirements Provides a certified local 3 prong AC power plug Provides a C13 connector Supports ratings of 100 120VAC 6A 200 240VAC 3A or higher with a mi...

Page 3: ...nents The Clara Holoscan Developer Kit contains the following major components AGX Orin 32 GB module RTX A6000 discrete GPU ConnectX 6 DX 500GB removeable SSD Tech Specs CPU 8 core Arm Cortex A78AE v8...

Page 4: ...X A6000 48 GB GDDR6 768 GB s 10 752 CUDA cores 3rd gen 336 Tensor Cores Storage 500GB SSD I O Micro USB Type B 2x USB3 0 USB C HDMI In 5x DisplayPort 1 100 GbE Expansion N A Power Supply 850W 100 240V...

Page 5: ...Clara Holoscan Developer Kit User Guide I O and external interfaces 1 Power cable connection 2 Power switch 3 DisplayPort DP output port from Jetson Orin module 4 Micro USB Type B...

Page 6: ...elow Unscrew the two Phillips screws that secure the cover at the back of the machine Next push and slide the cover towards the back of the machine without lifting step 1 It should slide about 0 5 inc...

Page 7: ...ction error during the flashing process 3 Using a VM as your host machine isn t officially supported but it is possible with certain VMs such as VMWare Workstation 16 If using a VM ensure the ports th...

Page 8: ...tup mode may cause flashing to stall Connect the Clara Holoscan Developer Kit to the Internet using one of the following methods An Ethernet cable connected to a router or Wi Fi extender A USB Wi Fi r...

Page 9: ...nts may also be provided with the install command nvgpuswitch py install h usage nvgpuswitch py install h f d i v l LOG r L4T_REPO iGPU dGPU positional arguments iGPU dGPU install iGPU or dGPU driver...

Page 10: ...until it is changed again with nvgpuswitch py Reinstalling Optional SDK Packages This section only applies if you have selected Additional SDKs in Step 01 of the SDK Manager installation process When...

Page 11: ...he m 2 drive is identified by the Clara Holoscan Developer Kit as dev nvme0n1 This is the case if no additional drives have been attached but if other drives such as USB drives have been attached then...

Page 12: ...94912 819200 884736 1605632 2654208 4096000 7962624 11239424 20480000 23887872 71663616 78675968 102400000 Allocating group tables done Writing inode tables done Creating journal 262144 blocks done Wr...

Page 13: ...r io 2 Create a Docker data directory on the new m 2 SSD partition This is where Docker will store all of its data including build cache and container images These instructions use the path media m2 d...

Page 14: ...pt where it says SDK Manager is about to flash your Clara AGX Developer Kit module in Step 3 it has been observed that if you choose Automatic Setup even if your Developer Kit had been flashed before...

Page 15: ...the f option when running nvgpuswitch py to force the reinstall of the dGPU stack sudo nvgpuswitch py install dGPU f Additional Resources For other documentation and release notes see the Clara Holos...

Reviews: