Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
21615 Discussions

MSEL wrong configuration

Altera_Forum
Honored Contributor II
2,736 Views

Hello,  

 

I designed a board using a EP4CE22F17C6N and I made a wrong connection on MSEL. I put it on MSEL[2..0] 001 instead of MSEL[2..0] 010. Besides the high level is tied to VCCio e.g 3,3V instead of VCCa which is 2,5V. 

 

When I try to program via JTAG the Conf_done fails to go high. Normally whatever the MSEL connection the JTAG should be master.  

 

Is the wrong voltage the source of the problem? If I let MSEL0 floating, will I be able to use JTAG programmation?
0 Kudos
7 Replies
Altera_Forum
Honored Contributor II
1,107 Views

My experience with S5GX: setting wrong bit configuration on MSEL give no access through jtag, and power consumption out of specs. 

 

Michele.
0 Kudos
Altera_Forum
Honored Contributor II
1,107 Views

even if I leave it floating?

0 Kudos
Altera_Forum
Honored Contributor II
1,107 Views

In my case I put a pull-up where should be a "0". Removing the PU, which meant to leave it floating, worked fine.

0 Kudos
Altera_Forum
Honored Contributor II
1,107 Views

Hi there,  

while it was a different device (Cyclone IV IIRC) there was some similar behaviour for a wrong MSEL connection. Even with floating pins the JTAG I/F did not work. There seems to be some ambiguity in the datasheet as I would also have expected the JTAG I/F should work for all MSEL connections...  

Maybe trying to modify HW to have MSEL floating will give you a chance to test the rest of the board nevermind.
0 Kudos
Altera_Forum
Honored Contributor II
1,107 Views

Hi, 

 

I have a similar issue with a Cyclone IV "EP4CE15M8I7N". 

 

I have (accidentally set MSEL[2..0] = 001 which is an invalid setting (Not in the selection table in the datasheet). 

When I try to use JTAG, I get this message: "Error (209014): CONF_DONE pin failed to go high in device 1" 

According to datasheet (Notes to Table 8-5): Connect MSEL to VCCA or GND. So JTAG should technically work regardless of this setting. 

 

Can anyone confirm that the MSEL[2..0] = 001 would cause this issue? 

Is there a workaround as the BGA has extremely fine pitch and almost impossible to re-work. 

 

I have checked the CONF_DONE pin and it never goes high. 

JTAG device can read the device ID without any issues. 

 

Many Thanks.
0 Kudos
Altera_Forum
Honored Contributor II
1,107 Views

Hi, 

 

I have found that the wrong MSEL connections were causing this issue: "Error (209014): CONF_DONE pin failed to go high in device 1".  

Cyclone IV E, MSEL[2..0] = 001 was not overwritten by JTAG connection. Therefore JTAG was unable to program the device. Maybe the datasheets should reflect this. 

 

After correcting the MSEL[2..0] = 010, the JTAG became responsive. 

 

Regards, 

James.
0 Kudos
Altera_Forum
Honored Contributor II
1,107 Views

 

--- Quote Start ---  

Hi, 

 

I have found that the wrong MSEL connections were causing this issue: "Error (209014): CONF_DONE pin failed to go high in device 1".  

Cyclone IV E, MSEL[2..0] = 001 was not overwritten by JTAG connection. Therefore JTAG was unable to program the device. Maybe the datasheets should reflect this. 

 

After correcting the MSEL[2..0] = 010, the JTAG became responsive. 

 

Regards, 

James. 

--- Quote End ---  

 

 

Hi James, I totally agree with you that the datssheet should reflect this for beginner. I think the idea is that JTAG configuration is able to overwrite any other configuration scheme but the MSEL pin setting ought to be in valid position in the first place. Cheers =D
0 Kudos
Reply