3689671345?profile=original

NVIDIA's press release states that "Jetson TX1 is the first embedded computer designed to process deep neural networks -- computer software that can learn to recognize objects or interpret information." The 3.4x2inch module includes a Tegra X1 ARM Cortex-A57 processor with 256-core NVIDIA Maxwell graphics, 4GB of LPDDR4 memory, 16GB of eMMC storage, 802.11ac WiFi and Bluetooth, and Gigabit Ethernet support.

AnandTech Article: http://www.anandtech.com/show/9779/nvidia-announces-jetson-tx1-tegra-x1-module-development-kit

The Jetson TX1 Development Kit will be available for preorder starting Nov. 12 for $599 in the United States. The kit includes the Jetson TX1 module, a carrier board (pictured below), and a 5MP camera. The stand-alone module will be available in early 2016 (for $299 in bulk).

3689671210?profile=original

The Jetson TK1 (not TX1) was released in 2014 to encourage the development of products based on the Tegra K1 processor. However, according to AnandTech, developers were using the Jetson TK1 outright as a production board, choosing to focus on peripheral and software development instead of system hardware development. With the new TX1, all of the I/O connectivity is provided on a carrier board, enabling rapid development on the credit-card sized TX1 module. After development is finished, the TX1 module can be directly deployed in products, such as drones. 

NVIDIA used a drone application to promote the Jetson TX1

https://twitter.com/NVIDIATegra/status/664238535096926208

3689671216?profile=original

E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • Developer

    6 cameras.. sounds like some full 360 views are the target, love it!

  • We are preparing a setup to connect up to 6 video sources to the Jetson TX1 dev kit. We create a new camera interface board for the Jetson TX1 dev kit. It features 6 CSI-2 connectors with 15 pins. These have the pinout of the Raspberry Pi camera connector (with 2 CSI-2 data lanes) and therefore support the Pi Camera and our B101 HDMI to CSI-2 bridge module. This setup with 6 B101 modules is shown in the 3D images below.3702271469?profile=original3702271518?profile=original3702271365?profile=original

  • Developer

    Looking good Jurgen!

  • The J120 now features an HDMI input. Ridgerun has finalized the port of the TC358743 driver for the B102 (4 lane CSI-2) and the J120. It supports the following resolutions today: 1080p60, 1080p50, 720p60, 720p50 and 640x480p60. We have made the firmware with compiled driver and kernel available for download. So this setup now works out of the box. It may be downloaded from the support page on the auvidea.eu website. The source code for the driver is available.

    Download firmware for J120 and B102

    The list price for the B102 is €139 net. The J120 with IMU is €219 net. A bundle of both is available at €319 net (€39 savings). Next we plan to get the B101 and B102 modules to work on the J100. As the J100 uses 2 I2C busses for the 4 CSI-2 connectors, only 2 of the B101/B102 modules may be connected to the J100 today. Rev 3 of the J100  will connect 4 I2C interfaces, so 4 modules may be connected. Today these modules support video only. But audio support is planned for an upcoming release.

    We are looking at developing a replacement for the camera interface board of the dev kit, to support 6 FPC connectors (with 2 lanes each - pinout of the 15 pin connector on the Raspberry Pi) for the B101 or camera sensor modules.

    3702270517?profile=original

  • Developer

    @Martin,

    Thanks for giving it a try and reporting back.  Kai (from EnRoute) also bumped into that problem with the wlan0 vs wlan1 when he flashed his board with the "tx1_backup_v0.10.img.tar.gz" image from firmware.ardupilot.org.  If you were using the v10 image then I think the problem is that I forgot to run this "persistent net" step.  This has something to do with Linux's desire to permanently attach a wlanX name to a particular MAC address.

    Kai's got a new image that's coming shortly that has OpenCV3.0, Caffe and OpenKai on it.  I know there's not many users of the last one but.. that's what we're using instead of DroneKit.

    ArduPilot firmware : /Companion
  • @Jurgen, Randy, All

    Using one of Randy's images I have just set up a Jetson TX1 on an Auvidea J100 carrier board as the companion computer to a Pixhawk running Arducopter. Apart from random characters appearing down the serial link, which is also the case on Randy's J120 integration, the solution works fine on the bench and connects to a ground station perfectly. (I added an extra --out to the Mavproxy startup script which may not be needed.)

    A few things to note should anyone wish to do likewise.

    At the top of rc.local there is a call to send the TX1's IP address to a host computer. This prevents the startup script from working when running standalone (obviously).
    When the TX1 is installed on the Nvidia development board the wifi device is wlan1 whereas on the J100 it is wlan0.
    Flashing the image was a bit of a struggle initially. There's a thread on the Nvidia developers forum about this.

    TX1/R23.1: New Flash Structure...How to Clone?

    https://devtalk.nvidia.com/default/topic/898999/?comment=4921812
  • Developer

    @Jurgen, All,

    I would like to enable flow control on the UART0 (I'm trying to reduce the corruption that I'm seeing on the serial connection between the Pixhawk and the TX1/J120) but according to this NVidia doc (see page 7, 8) it seems hardware flow control isn't possible for UART0.

    3702262492?profile=original

    This seems to contradict page 12 of the J120 datasheet which shows that "J7" / UART0 has CTS and RTS pins available.  I've created an issue here on the NVidia forum but if anyone knows whether flow control is possible on UART0 or whether we can access UART2 or UART3 on the J120 I'd love to hear about it.

    3702262588?profile=original

    http://developer.download.nvidia.com/embedded/L4T/r24_Release_v1.0/Docs/Tegra_Linux_Driver_Package_…
  • Thank's for sharing Randy !

    Here is the SVG file for laser cutting a box with 3mm material for TX1 + J100 : http://trancept.free.fr/hfr/boitierTX1.svg

    Warning : the hdmi port is in wrong position, I mismatch the side of assembly :-(

    The box just push down over the TX1, no bottom. A margin exist to handle the fan cable.

  • Cool!  Snap a video of the drone landing.

    We've released the latest 64-bit L4T BSP and JetPack for TX1, version R24.1.

    BTW, I have a robotics colleague at NVIDIA from Tokyo who works on Jetson, if you can meet up sometime.  He uses J120 too.

    L4T
    NVIDIA L4T 32.2.1 supports Jetson AGX Xavier series, Jetson TX2 series, Jetson TX1, and Jetson Nano. It is included as part of JetPack 4.2.2 and incl…
  • Hi Randy and Patrick,

    thank you Randy for the work to interface the J120 to the Pixhawk. 

    We are starting to work on the CSI-2 interface for our J100 and J120 carrier boards. We are porting the driver to support the B101 and B102 HDMI to CSI-2 modules with the Toshiba TC358743 chip. Hopefully this will complete shortly.

    Next I am working with a customer to interface a 41 megapixel imager via CSI-2 to the J100/J120. It should support 4k with 60 frames (2160p60). 

    Last, we are completing the design of the J130:

    J130:
    - 2x CAN
    - 1x GbE (Gigabit Ethernet)
    - mini HDMI out
    - USB 3 hub (Cypress chip) for 5 USB3 ports in total
    - high USB 3 power (on board 5V 10A power supply)
    - PCIe slot with 4 lanes
    - SATA connector
    - HDMI input with 2160p30 (4k) with 8 CSI-2 lanes - TC358840
    - HDMI input with 1080p60 with 4 CSI-2 lanes - TC358840
    - size: 74 x 110 mm
    - first prototypes July/August 2016

    There will be multiple stuffing options for the J130 at various price points. Budgetary pricing:

    J130 without HDMI in: €299 net

    J130 with one HDMI in (2k): €399 net

    J130 with one HDMI in (4k): €499 net

    J130 with 2 HDMI in (4k and 2k): €599 net

    3702255540?profile=original

This reply was deleted.