This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR6843AOPEVM: AWR6843AOPEVM Linux/ARM64

Part Number: AWR6843AOPEVM
Other Parts Discussed in Thread: IWR6843AOPEVM,

Hi,

We have been working on using IWR6843AOPEVM for altimetry on an industrial drone.

We want to interface IWR6843AOPEVM with an Linux/ARM64 (Jetson Nano)

Previously,  one TI expert mentioned it is easy to use the serial peripherals (USB,SPI, UART, I2C) to connect to a Linux/ARM64 host

Here are the issues:

1- SDK does not seem to support ARM64 (although it may be available for Ubonto). So USB communication is not an option with Linux/ARM64

2- I2C port which is available on AWR6843AOPEVM (through a 4-pin connector) does not seem to provide RADAR data (e.g., range, point cloud, etc). It is for PMIC, temperature etc.

Question: 

Is there anyway to interface AWR6843AOPEVM with Jetson Nano through USB or serial peripherals?

Thanks,

POUYA

  • Hello, 

    There is no dependency on the mmWave SDK in order to use the AOP EVM with your jetson board. Therefore, you will not have issues here. In order to use the mmWave SDK, I would suggest using another computer. The SDK should be used to create a binary that the sensor is flashed with. In this case, it seems like you are using the Out of box demo. 

    Your I2C port is partially true. You can re-write the demo firmware to provide point cloud over I2C, although this is not commonly done. 

    Yes, you can connect the AOP to a jetson using the USB port. When you connect the sensor's microUSB to the jetson's USB port, check your devices in /dev/. You should either see /dev/ttyACM0 and /dev/ttyACM1 or /dev/ttyUSB0 and /dev/ttyUSB1.  

    To get started using the Jetson with AOP, I would suggest you have a look at the remote streaming tool in the Industrial toolbox. It will send configuration file and receive data stream. Please read the instructions for more information. Note that this tool is only supported with the Out of Box demo. 

    https://dev.ti.com/tirex/explore/node?node=ALDijvgBJo0jeTVqhHhhMQ__VLyFKFf__LATEST 

  • Hi,

    Thanks for the response.

    "There is no dependency on the mmWave SDK in order to use the AOP EVM with your jetson board. Therefore, you will not have issues here": Our firmware expert believes SDK is not compatible with ARM64 (this is different from Linux or Windows compatibility).

    Using a Intel X86 to create the binary is a good solution.

    At this point, we have been able to connect AOP OEM to Jetson through USB (UART) without SDK running on Jetson.

    We are trying to make sense of the received data at this point (range data).

    We will try your suggestion for I2C as well. If we could get useful (range) data out of I2C, it would make things a lot simpler.

    Best regards,

    POUYA

  • Hi,

    Please try out the remote streaming tool, it sounds like good fit for what you are trying to accomplish with jetson. Is I2C necessary for your application?

  • Hi Sabeeh,

    I2C communication simplifies everything. We would then be able to use a microcontroller (ARM Cortex M4) instead of Jetson to communicate with AOP EVM and handle the range/point cloud data. According to datasheet of the IC and EVM, I2C seems to be used for PMIC/Temp.

    Also, 3 follow up questions:

    1- "Your I2C port is partially true. You can re-write the demo firmware to provide point cloud over I2C, although this is not commonly done. " Which demo you are referring to?

    2- Is the an SPI port available on AOP EVM? We cannot use the boos board due to size/weight

    3- Is there a UART port available on AOP EVM?

    Best regards,

    POUYA

  • Hi Pouya,

    Thanks for this. I now understand that your intended deliverable is to use a microcontroller connected to the radar instead of the Jetson. 

    Answering #1: Any demo. You would have to re-write the chosen demo to provide data over I2C rather than UART. 

    For #2 and #3: Both UART and SPI are available on the AOP sensor, but not directly from the EVM. You can use the ICBOOST to bring out the signals. Please check the schematics for both the AOP EVM and ICBOOST for more details. On the EVM, a UART to USB transceiver is used to easily connect to a host PC and get started with evaluation. Again, please see schematics. 

    If there are further size/weight constraints, consider developing your own board. 

  • Hi Sabeeh,

    Thanks for the clarification.

    MCU is the preferred solution. We will move on to Jetson only if we cannot make it work on an MCU.

    Let us work on the solutions you provided and get back to you in case there were more questions.

    Best regards,

    POUYA