- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a Arria 10 SoC FPGA.
From the board, I am connected to the ethernet port, HPS debug UART, and USB blaster cable. From a PC I am able to communicate to the board across all three interfaces. The HPS sends serial data and I'm able to write basic scripts to modify the LEDs and the LCD along with the push buttons using either the actual memory locations for name based locations under /sys/class/...
I have a Furuno GT-100 GPS connected to the HPS-USB port. It uses a USB-C FTDI cable to output serial information. When connected to a linux PC, I'm able to see the serial output just fine setting the device accordingly.
But, I am unable to see any serial information on the Arria 10. The arria 10 itself does NOT identify the USB/COM connection when connected as the PC does.
This does not allow me to open the device under tty. But, from the dmesg, the kernel does identify the device as a USB 2.0 but doesn't assign any device.
I've tried modifying the device tree and added the Furuno to the compatible devices and I've also attempted to access the memory directly using the base address of the USB(s) without any luck.
The serial uses the standard baud of 115200 which I also added to the device tree.
My overall goal is to read the serial data, parse the coordinates and display to the LCD. The latter of the two I've already done so to speak, but I haven't been able to read the data.
My HPS-USB cable is connected to J4 on the board.
I've also modified some of the jumpers to see if that was the issue but I don't believe so. The HPS-USB is able to identify a standard flash drive without any problems.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello!
Your Arria 10 SoC detects the USB GPS device but doesn’t assign a tty interface, likely due to missing FTDI driver support or incomplete device tree configuration. To fix this, ensure ftdi_sio and usbserial kernel modules are loaded, verify the device tree includes FTDI compatibility, and check dmesg for binding messages. You may also need to manually bind the device or add udev rules to enable /dev/ttyUSBx creation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi SempreScott,
This forum is designed for questions about the Edge Software Catalog and the software packages hosted on ESC. I recommend posting your question on the Altera forums: https://community.altera.com/category/forums
Regards,
Jesus
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page