Application Acceleration With FPGAs
Programmable Acceleration Cards (PACs), DCP, FPGA AI Suite, Software Stack, and Reference Designs
477 Discussions

How to identify which USB blaster is connected to which board when there are multiple boards with same hardware and working remotely using RDC

DJiva1
Beginner
‎03-30-2020 12:44 PM
451 Views

Hi,

My hardware setup has four same application boards with same FPGA devices (MAX10-50) and all boards are connected with USB baster on the server.

All board have it's own functionality and have different RTL code base.

I am working remotely using remote desktop connection and want to test and debug all four four board functionality using with its own respective STP files.

 

During setup the hardware with server, I was forgot to check the which board is connected to which USB blaster and now it is not possible for anyone reach at setup place and not possible to visually identify the USB blaster No. by verifying blaster LEDs by JTAG chain auto detect feature.

 

Can anyone help me on how I can identify which blaster is connected to which board without anyone human support. Or is there any way like we can get device ID of individual board etc..

 

Thanks

Dipenkumar

0 Kudos

Link Copied

1 Reply
YuanLi_S_Intel
Employee
‎03-31-2020 03:25 AM
369 Views

Hi Dipenkumar,

 

I would recommend to use this unique chip ID IP. You may distinguish different MAX 10 with this unique ID.

https://www.intel.com/content/www/us/en/programmable/documentation/sam1412052977775.html

0 Kudos
Copy link
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.