MAX10 10M50SCE144C8G trouble on programming

[Altera_Forum]

part 10M50SCE144C8G on custom board 

first time got programmed, it was working with an issue, corrected the core never load again on device.   Quartus Lite 15.1   Quartus Lite 16.1 won't compile and say pin 26 too close to pin 27 clock issue.  Compiled design on 15.1 16.1 programmer perform same way don't program.   tested all work around found here and on site, no success.   Device is forever detected regardless of Jtagen and confign signal level.  Erase is executed, I clearly see first working Image was erased.   Program as SOF say it 100 % (Succesful) but doesn't seem work.   Program as POF say failure at 0%   verify, blank check say failure at 0%   examine take a long time with progressing bar incrementing 1% every second/ two or more then say 100 % (Succesful) Examine what?   Checked all workaround i seen but none is working, I feel this device as not mature, also software is not so reliable, 15.0 look better but has limited support.   I also don't like incompatible pinout migration on same casing for 02 04-25 the another different pinout for 40 50.  Now this completely stuck me at final step blocking production.  Design was fine on bga484 and all was tested on bemicro max and deca.   Checked Config done, NConfig, but program of pof report failure forever.  Someone has idea why cannot reprogram device?  Programming console on next  Best regards  Roberto

[Altera_Forum]

Console output: 

Examine: Info (209060): Started Programmer operation at Sun Feb 5 22:54:28 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209038): Examining devices Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Sun Feb 5 23:00:56 2017  program configure POF Info (209060): Started Programmer operation at Sun Feb 5 23:02:39 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209060): Started Programmer operation at Sun Feb 5 23:02:40 2017 Info (209016): Configuring device index 1 Info (209017): Device 1 contains JTAG ID code 0x031850DD Error (209012): Operation failed Info (209061): Ended Programmer operation at Sun Feb 5 23:02:41 2017 Error (209012): Operation failed Info (209061): Ended Programmer operation at Sun Feb 5 23:02:41 2017   ERASE Info (209060): Started Programmer operation at Sun Feb 5 23:06:06 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209044): Erasing MAX 10 configuration device(s) Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Sun Feb 5 23:06:06 2017  Program SOF NConfig High: Info (209060): Started Programmer operation at Sun Feb 5 23:06:06 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209044): Erasing MAX 10 configuration device(s) Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Sun Feb 5 23:06:06 2017 NConfig Low: Info (209060): Started Programmer operation at Sun Feb 5 23:10:54 2017 Info (209016): Configuring device index 1 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209007): Configuration succeeded -- 1 device(s) configured Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Sun Feb 5 23:11:03 2017 Info (209060): Started Programmer operation at Sun Feb 5 23:12:01 2017 Info (209016): Configuring device index 1 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209007): Configuration succeeded -- 1 device(s) configured Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Sun Feb 5 23:12:10 2017  program pof Info (209060): Started Programmer operation at Sun Feb 5 23:13:31 2017 Info (209016): Configuring device index 1 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209007): Configuration succeeded -- 1 device(s) configured Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Sun Feb 5 23:13:39 2017 Error (209012): Operation failed Info (209061): Ended Programmer operation at Sun Feb 5 23:13:39 2017

[Altera_Forum]

I did not understand "first time got programmed, it was working with an issue, corrected the core never load again on device." What was the issue? 

Did you check the power supplies?

[Altera_Forum]

--- Quote Start ---  I did not understand "first time got programmed, it was working with an issue, corrected the core never load again on device." What was the issue? Did you check the power supplies?  --- Quote End ---    On IP core one signal was at default, iIPCORE display on an LCD two different windows. Due to this error on LCD an image was present where it was expected to be blank, after correcting design was never possible to load again an image to device.  About power supply, I can test it, LCD is lit on, on previous an image was present, after erase was no more possible load core so no image is on display.  I see report from console got lost, so I post again a new one.

[Altera_Forum]

Console output: 

  Erase  Jtagen High Info (209060): Started Programmer operation at Mon Feb 6 23:35:46 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209044): Erasing MAX 10 configuration device(s) Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Mon Feb 6 23:35:46 2017 low  Info (209060): Started Programmer operation at Mon Feb 6 23:36:14 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209044): Erasing MAX 10 configuration device(s) Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Mon Feb 6 23:36:15 2017   Program SOF  Jtagen High/Low Info (209060): Started Programmer operation at Mon Feb 6 23:37:14 2017 Info (209016): Configuring device index 1 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209007): Configuration succeeded -- 1 device(s) configured Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Mon Feb 6 23:37:23 2017  Info (209060): Started Programmer operation at Mon Feb 6 23:37:54 2017 Info (209016): Configuring device index 1 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209007): Configuration succeeded -- 1 device(s) configured Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Mon Feb 6 23:38:02 2017  Blank check  Jtagen High Info (209060): Started Programmer operation at Mon Feb 6 23:38:47 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209060): Started Programmer operation at Mon Feb 6 23:38:48 2017 Info (209016): Configuring device index 1 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209007): Configuration succeeded -- 1 device(s) configured Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Mon Feb 6 23:38:57 2017 Error (209012): Operation failed Info (209061): Ended Programmer operation at Mon Feb 6 23:38:57 2017  Jtagen Low Info (209060): Started Programmer operation at Mon Feb 6 23:40:20 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209060): Started Programmer operation at Mon Feb 6 23:40:21 2017 Info (209016): Configuring device index 1 Info (209017): Device 1 contains JTAG ID code 0x031850DD Error (209014): CONF_DONE pin failed to go high in device 1. Make sure all communication cables are securely connected, select a different device, check the power on the target system, or make sure all nCE pins are connected to GND. The Altera Knowledge Database contains many articles with specific details on how to resolve this error. Visit the Knowledge Database at https://www.altera.com/support/support-resources/knowledge-base/search.html and search for this specific error message number.  Error (209012): Operation failed Info (209061): Ended Programmer operation at Mon Feb 6 23:40:29 2017 Error (209012): Operation failed Info (209061): Ended Programmer operation at Mon Feb 6 23:40:29 2017  Info (209060): Started Programmer operation at Mon Feb 6 23:40:57 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209060): Started Programmer operation at Mon Feb 6 23:40:57 2017 Info (209016): Configuring device index 1 Info (209017): Device 1 contains JTAG ID code 0x031850DD Error (209014): CONF_DONE pin failed to go high in device 1. Make sure all communication cables are securely connected, select a different device, check the power on the target system, or make sure all nCE pins are connected to GND. The Altera Knowledge Database contains many articles with specific details on how to resolve this error. Visit the Knowledge Database at https://www.altera.com/support/support-resources/knowledge-base/search.html and search for this specific error message number.  Error (209012): Operation failed Info (209061): Ended Programmer operation at Mon Feb 6 23:41:06 2017 Error (209012): Operation failed Info (209061): Ended Programmer operation at Mon Feb 6 23:41:06 2017  Examine JTAG low Info (209060): Started Programmer operation at Mon Feb 6 23:41:50 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209038): Examining devices Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Mon Feb 6 23:48:15 2017  program POF JTAGEN low nCONFIG HIGH Info (209060): Started Programmer operation at Mon Feb 6 23:50:13 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209060): Started Programmer operation at Mon Feb 6 23:50:14 2017 Info (209016): Configuring device index 1 Info (209017): Device 1 contains JTAG ID code 0x031850DD Error (209014): CONF_DONE pin failed to go high in device 1. Make sure all communication cables are securely connected, select a different device, check the power on the target system, or make sure all nCE pins are connected to GND. The Altera Knowledge Database contains many articles with specific details on how to resolve this error. Visit the Knowledge Database at https://www.altera.com/support/support-resources/knowledge-base/search.html and search for this specific error message number.  Error (209012): Operation failed Info (209061): Ended Programmer operation at Mon Feb 6 23:50:23 2017 Error (209012): Operation failed Info (209061): Ended Programmer operation at Mon Feb 6 23:50:23 2017  Nconfig Low Info (209060): Started Programmer operation at Mon Feb 6 23:50:53 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209060): Started Programmer operation at Mon Feb 6 23:50:54 2017 Info (209016): Configuring device index 1 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209007): Configuration succeeded -- 1 device(s) configured Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Mon Feb 6 23:51:02 2017 Error (209012): Operation failed Info (209061): Ended Programmer operation at Mon Feb 6 23:51:02 2017  Info (209060): Started Programmer operation at Mon Feb 6 23:52:01 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209060): Started Programmer operation at Mon Feb 6 23:52:02 2017 Info (209016): Configuring device index 1 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209007): Configuration succeeded -- 1 device(s) configured Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Mon Feb 6 23:52:10 2017 Error (209012): Operation failed Info (209061): Ended Programmer operation at Mon Feb 6 23:52:10 2017  second attempt erase program Info (209060): Started Programmer operation at Mon Feb 6 23:52:40 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209044): Erasing MAX 10 configuration device(s) Info (209011): Successfully performed operation(s) Info (209061): Ended Programmer operation at Mon Feb 6 23:52:40 2017 Info (209060): Started Programmer operation at Mon Feb 6 23:52:47 2017 Info (209017): Device 1 contains JTAG ID code 0x031850DD Info (209060): Started Programmer operation at Mon Feb 6 23:52:47 2017 Info (209016): Configuring device index 1 Info (209017): Device 1 contains JTAG ID code 0x031850DD Error (209014): CONF_DONE pin failed to go high in device 1. Make sure all communication cables are securely connected, select a different device, check the power on the target system, or make sure all nCE pins are connected to GND. The Altera Knowledge Database contains many articles with specific details on how to resolve this error. Visit the Knowledge Database at https://www.altera.com/support/support-resources/knowledge-base/search.html and search for this specific error message number.  Error (209012): Operation failed Info (209061): Ended Programmer operation at Mon Feb 6 23:52:56 2017 Error (209012): Operation failed Info (209061): Ended Programmer operation at Mon Feb 6 23:52:56 2017

[Altera_Forum]

--- Quote Start ---  I did not understand "first time got programmed, it was working with an issue, corrected the core never load again on device." What was the issue? Did you check the power supplies?  --- Quote End ---     Hi sherif123, you asked me to check the power supply, is this general request or you experienced something on PSU behaviour?  PSU is on board, can deliver 2A@3.3V 3A peak, it feed just MAX10, a 50MHz oscillator, 3 i2C expander, power LED and an SRAM, board is 4 layer with solid ground and power plane under ETQFP, an additional ground plane is under case to help raise down impedance and also transfer away heat.  Some more idea about?  Thank

[Altera_Forum]

Hi rommano, 

 I have a similiar case with M16SAE144C8G with custom board.   As you explained the device can be detected always.  Program as SOF say it 100 % (Succesful) but doesn't seem work. Program as POF say failure at 0% verify, blank check say failure at 0% Examine take a long time with progressing bar incrementing 1% every second/ two or more then say 100 % (Succesful)  Did you find any solution for this issue?

[Altera_Forum]

Hi rromano001, 

 Perhaps, you can try to use the latest Quartus stand alone programmer v17.0. You don’t need to install the full Quartus v17.0 version. You only need to install the stand alone programmer. Then you can try to erase the MAX 10 CFM/UFM block and reprogram your .pof file.  https://dl.altera.com/17.0/?edition=standard&platform=windows&download_manager=dlm3&product=qprogrammer#tabs-4 Since you are using E144 package device, make sure the exposed pad on the MAX10 E144 package connected to the ground plane on your board.   Regards, nyusof (This message was posted on behalf of Intel Corporation)

[Altera_Forum]

--- Quote Start ---  Hi rommano,  I have a similiar case with M16SAE144C8G with custom board.    Yes, I solved this issue, I was using all pin of MAX10, pin 38 config Done was assigned to interrupt of PCA9535EC and PCA8574 I2C expander, one of this when powered up was driving IRQ line low. Also board was unresponsive, removing offending pin from Config Done got again High releasing my board from trouble.  As rule check all status pin are free and can be pulled up, Nstatus and Config done in particular but also some other can be the solution to problem.  Telll me about your progress too.   Actually I still experience trouble with compiler and some strange behaviour with a very simple SRAM controller.  New Quartus after release 15 abort compilation of design when pin near clock input not at ground. I cannot use new quartus and this is a bigger issue, I commissioned a new board but pin are not enough, release 15 output was ok and no jitter issue was noticed, the two pin are low speed and appear as not disturbing ...  Quartus Linux version also seems to lose performance after release 15, about 20 year ago I migrated away from a competitor due to switch from unix to M$, I DON'T wish at all have again to deal with M$ based product.  Best regards.  Roberto

[Altera_Forum]

Hi Nyusof, I downloaded release 17.0 and may be i get 17.1 too but when hardware lock is active I fear newest version fail too. 

As I wrote issue came from Config done, first .pof got these pin disabled but I learned this:  If config done and or nStatus get stucked low at startup MAX remain in config mode and never got user mode so never load image nor permit program nothing.  I checked about soldering but it was working at first glance, never after rework got working again, both chip got soldered first time on reflow oven second time on IR rework with preheating seat so as I noted when I discovered the cure nothing on hardware was broken. I also think first chip was ok,  After learning also pinout was not portable across all series I modified the layouts and discarded the 40 and 50 version in favour of 25, this is enough for ip core test, final core can be on 04 or 08, I am afraud also 02 can be used but again is not pinout compatible.  I hope in future some new release can be pinout portable from 02 to hi ghest LE.  Next week I plan to install new version, I try again to lock device and see if succeed or not on programming.  Best regards  Roberto