Hi all,
and thank you all, in particular Jim (Kangalow) for the video posted here. I wrote a short post on my blog with all my information captured online: Redirecting…
If you see some mistakes I will update my post.
Still TBD on the PCIe drivers. The devkit also has limited power available.
will it be possible to power it from something like https://www.amazon.com/dp/B01K6TA748/ref=psdc_7073960011_t3_B071WNWRNC
So far I can see that it is can be powered with RAVPower RP-PB14 but that appears to be a slightly obsolete model without usb-C out.
will it support displays like ZenScreen MB16AC｜Monitors｜ASUS Global ?
does Xavier have usb-C port?[there my interest is mostly in connecting usb-c display or usb-c power bank]
what are the ports at the image attached?
External Media
any known lte 3g/4g + simcard cellular solution that will integrate into the ecosystem?
some more insights: NVIDIAが自律型ロボット開発に向けた開発ボート「Jetson Xavier」公開【COMPUTEX TAIPEI 2018】 | マイナビニュース
The devkit supports power input from USB-C or barrel jack. The barrel jack is the same as on TX1/TX2.
There are two USB-C ports, and there is an additional eSATA/USB3 hybrid port.
Not sure of the specifics of this display, but external DisplayPort is supported over the USB-C’s.
It would be really cool if Nvidia will release a firmware flasher tool which can take a full backup of existing Jetson Xavier module and then restore it to another Xavier module. Very useful for cloning modules without dealing with JetPack installation.
If this tool could also support TX1/TX2 modules, it would be even better.
-albertr
Hi albertr, you can already do that today with TX1/TX2:
https://elinux.org/Jetson/TX1_Cloning
https://elinux.org/Jetson/TX2_Cloning
Dustin, thanks. I used the steps above once, and while it works, it’s alittle bit involving. I was thinking of something more simplistic, i.e. a developer is using Jetson module to do all work, including changes to:
- device tree
- kernel
- filesystem
When it’s ready for testing or deployment, just put it in recovery mode, run a cloning app (linux/Windows/MacOS - does’t matter) which takes a whole backup of device including all partitions and store it on a filesystem.
Connect another Jetson module in recovery mode, run this app, press “Restore” and it restores ALL partitions (preserving device serial number, MAC addresses, etc).
The point is to eliminate the whole JetPack installation/flashing ordeal for the second and subsequent devices… Not sure that something like this can be easily implemented, but if it could, it would be really nice.
-albertr
The TK1 had an “all” target for cloning which was nice (this is a single binary image encompassing the entire eMMC…one can extract partitions from this on the host using dd if you know the partition offsets).
With TX1/TX2 you can clone all individual partitions, but the non-partition data at the start of the disk would be left out and would need “dd” (and then restoring wouldn’t be possible through the flash tool for that non-partition data…you’d need to use dd from a running system, e.g., through a rescue SD card). I’d like to see a future release add back in target “all” for cloning, or better yet, the ability to read or flash exact byte/sector offset ranges agnostic of partition schemes.
CEO Jensen Huang’s CES presentation in January included a slide that lists 1Gb & 10Gb Ethernet connectivity for Xavier:
(slide 15 with the Xavier die shot)
Can anyone confirm if the Xavier Jetson module will indeed include 10GbE, as other documentation I have seen does not seem to mention it.
Thanks in advance,
Dave
Hi Dave, that bit is under the MIPI CSI block and is referring to the C-PHY/D-PHY signalling with support for SLVS.
Jetson Xavier doesn’t have 10GbE, but it does have PCIe gen4 and more than enough bandwidth for your 10GbE NIC of choice.
I’m curious how one would use the PCIe port on the side of the Jetson Xavier. The TK1 had a mini-PCIe flush mount slot and the TX1/TX2 had a “normal” motherboard style PCIe slot, both of which are straightforward to use. How would you physically connect a PCIe NIC or PCIe discrete GPU or PCIe NVME storage card to the Jetson Xavier? And how would you make use of the 5 different PCIe controllers with one physical PCIe port? Is there some sort of special PCIe cabling for this port? Maybe a daughter card with normal PCIe slots? It is difficult to make out in the photos I’ve seen so far but it doesn’t look like a normal motherboard style PCIe slot.
Thanks.
For reference, the picture shown in the earlier post is here:
[url]https://a70ad2d16996820e6285-3c315462976343d903d5b3a03b69072d.ssl.cf2.rackcdn.com/edd562fa773aea96e46833f5e991cd6d[/url]
That is a picture of the module mounted to a carrier board…that isn’t just the module. The PCIe slot on that carrier is standard from what I can see (other than being the “next generation” PCIe rev. 4). I think the goal is that other developers can sell carrier boards with different options. The module itself can support all of those things if the carrier board it mounts to has the required connectors.
Unfortunately, the picture does not show all sides.
linuxdev’s correct, it’s just a typical desktop PCIe slot that you would plug standard PCIe cards into.
There’s only one controller that’s routed to the devkit’s desktop PCIe slot - the x8 controller. The slot is physically x16, but x8 electrically.
Xavier’s other PCIe controllers are used for other things on the board. There are individual M.2 key E and M.2 key M sites, and an eSATA/USB3 hub.
Thanks for the clarification on the PCIe slot. It was hard to recognize in the photos but if you look carefully at the video posted earlier in this thread, at about 35 seconds and again at about 55 seconds in, you can see that it is a standard PCIe slot with the key notch.
Apparently the PCIe Gen4 standard includes a standardized external PCIe cable called “OCuLink”. External OCuLink cables are already available. One of the intended usages of OCuLink is to easily attach external PCIe NVME storage. Wile it looks like the Jetson Xavier doesn’t include one of these Gen4 external OCuLink ports, possibly they could be added through a PCIe adapter card in the future.
Hi guys, the official devkit I/O specs have been posted here: [b][url]https://developer.nvidia.com/jetson-xavier-devkit[/url][/b]
Thanks Dustin. It’s nice to see that it has both M.2 Key M and M.2 Key E connectors. Also retaining a separate 40-pin header for other interfaces is a good idea. I hope someone can put it on a scale and publish how much it weights.
-albertr
What camera NVidia is planning to bundle with Xavier DevKit (if any)? Any chance we can see support for Raspberry Pi cameras?
-albertr
I am curious if there will be a JTAG interface…or something new? Though I doubt there’d be any JTAG debuggers which would work with it even if the interface exists.
Hi albertr, the devkit itself doesn’t come with a camera, however it has the same camera header as the TX1/TX2 devkits. So you could use the OV5693 module from TX1/TX2, or another module from one of the imaging partners once they update their drivers. I believe that RidgeRun has supported the rPI camera in the past.
Yes, there exists a JTAG interface on the devkit.