Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Novice
1,618 Views

Unable to program stratix 10 development kit

Hello Intel forums,

 

I have recently started working with a stratix 10 GX development kit (L-tile). I have created and compiled my design (with the device set to 1SG280LU3F50E3VGS1).

 

I connected the microUSB port to my PC. I created a signalTap instance for debugging, and when I went to program the device, I saw two options in the Device setting:

 

@1: 5M(1270ZF324|2210Z)/EPM2210 (0X020A40DD)

@2: (0XC32150DD)

 

When I use the @1: 5M(1270ZF324|2210Z)/EPM2210 (0X020A40DD) Device, I get this error:

Info(209060): Started Programmer operation at Tue Jan 8 12:55:29 2019 Info(18942): Configuring device index 1 Error(18952): Error status: Detected unrecognized JTAG ID code 020A40DD. Make sure the correct device is connected. Error(209012): Operation failed Info(209061): Ended Programmer operation at Tue Jan 8 12:55:29 2019

and when I use the @2: (0XC32150DD) device, I get this error:

Info(209060): Started Programmer operation at Tue Jan 8 13:01:14 2019 Error(18939): Unexpected error in JTAG server -- error code 35 Error(209012): Operation failed Info(209061): Ended Programmer operation at Tue Jan 8 13:01:15 2019

I am unsure which device is the correct one. I assume one of them is the Max 10 FPGA and the other is the stratix 10.

 

I have tried modifying my design for the h-tile kit, incase I misunderstood which device I had, but I had the same problem.

 

I am using

Quartus Prime Design Software Version 17.1.0 Build 240 10/25/2017 SJ Pro Edition

Any help would be very appreciated.

Thanks,

-Sam

0 Kudos
4 Replies
Highlighted
Employee
68 Views

Hi,

 

Could you try to change the TCK frequency (jtagconfig --setparam 1 JtagClock 16M)? Could you update your Quartus to 18.1 and see if you are facing the same issue?

0 Kudos
Highlighted
Novice
68 Views

Thanks for the suggestions.

 

Unfortunately, the device I'm using (stratix 10 ES dev kit) is only supported in Quartus 17.1 (nothing earlier or later).

 

I'll try changing the TCK frequency and see what that does.

 

-Sam

0 Kudos
Highlighted
Novice
68 Views

I have solved the problem. It turns out the documents included with the development kit had the wrong device ID listed. The documents claimed it was an ES edition dev kit, but it turns out it was a development edition kit.

 

-Sam

0 Kudos
Highlighted
Employee
68 Views

Hi,

 

I am glad the issue has been resolved.

0 Kudos