Hi I've been using Win10 with the Nuc (nuc6cays) for a couple years now but like others I'm having trouble getting my new Samsung HDTV (49" QN49Q6F) to recognize it through the HDMI port. I have searched through the forums and gotten some help and tried a few things, but I'm having trouble with upgrading my NUC. I've successfully flashed the bios with AYAPLCEL.86A.0049.EB but I'm confused about the HDMI firmware upgrade "NUC6CAY-NUC7ixBN-HDMI-Update-1.72". I found this reference in an old post as a possible fix to the HDMI problem, but I'm a little confused on how to work the "Bobcat Aux ISP Tool" software. It seems I'm using this program to run the files found in the "bin" folder, but no matter what file I run, it fails. First all, is this firmware update still relevant? When it comes to flashing bios and firmware/driver updates I'm of the mindset that if it ain't broke don't fix it. If anyone can advise me on which updates to apply to fix this problem please let me know. I was able to find a tutorial on how to install the HDMI firmware, but it said nothing about how to use Bobcat and I don' know what "FW" refers to. The other possible problem is that the tutorial says I must be hooked up to an HDMI 2.0 compliant device which is impossible in terms of the Samsung as hooking up is the problem. I did run bobcat while hooked up to a different HDMI monitor, but I was unable to be certain if this was HDMI compliant.
Beyond that I've confirmed the HDMI cable is fine and that HDMI works fine with the HDTV using a different PC. I spend two or three hours trying to get the HDMI to work including returning and getting the same TV thinking the problem might be with the "ONE CONNECT" box that comes with the TV. This box attaches to the TV with it's own priority cable. At one point, the one connect box feel 2 feet to the floor, then when I picked it up, the HDMI port was recognized, but only for as long as the TV was on. After that it went back to being unable to detect the PC, although it's clear the HDTV knew something was connected to the HDMI port. Hot swapping didn't work and I've tried all 4 HDMI ports available on the TV. I don't get a blank screen or a boot screen or anything. Just the Samsung screen showing it failed to establish a connection.
I realize there are other posts on this topic which I am still exploring.
I understand that you are currently experiencing issues with the connection of the NUC to the TV via HDMI.
Regarding this, I would like to begin by asking for an Intel ® System Support Utility report, this report can be generated with our tool which you can download from the link below:
Also, to better assist you with your request, I will need to check some information about your computer. Please follow these steps:
1. In the keyboard, press WinLogo key + R.
2. In the Run box please type dxdiag and hit Enter.
3. Click on Save All Information (save it in your desktop).
Make sure to attach the reports to this thread. Something else I would like to ask is if you have tried different TVs or monitors to see if they work properly so as to isolate the problem and makes sure if it is only that specific Samsung* TV. Are you able to connect the HDMI cable to the TV directly instead of the One Connect* box? If so, please try it and let me know the outcome of this.
I hope to hear from you.
Before we get into all that, could you simply confirm if "NUC6CAY-NUC7ixBN-HDMI-Update-1.72" is a proper update for the 6cays and tell me how to install it? I've already spend several hours trying to solve this issue and I'm about ready to throw the NUC away and just buy another non-intel PC. Old forum posts indicate this is a common issue with the NUC and likely not related my personal settings.
"You did read the part where your 4K monitor/TV needs to be connected to the HDMI output while you install the update, right?"
Thanks for your response. Yes, I referred to that in my OP. The problem is if I could connect the NUC to the HDMI 2.0 complaint HDTV, I wouldn't care about updating the HDMI in the first place. I have tried hot swapping the cable from a working monitor to the Samsung, but no luck. One thing I could try is to have the mouse precisely placed such that I could run the update without having to actually see the screen. Then I could hotswap knowing I'll have no picture, but still be able to run the update. However, I don't know if this would count as "connected to HDMI 2.0 device" and even if it did, the software used (bobcat) is not so straight forward. Running the program (bobcat) seems to create some sort of data file, but there's also the option to run one of the three individual files found in the bin folder and there are two ways to do that. I can't do that in the dark. Perhaps with some sort of command line parameter using dos. And so this is why I've started a post on how to run the firmware.
EDIT: Also, I can confirm that when I did run bobcat, I was connect to a monitor via HDMI, but it was too old to be HDMI 2.0 so it's understandable why the upgrade didn't work.
That you for your help. I'll try to get the information you require, but the NUC does not currently have an internet connection, nor is it part of my wifi network. I will need to use a flash drive to collect and return the information. I'll try to get that done and get back to you, but I will still have my question regarding how to use bobcat.
Also, the ONLY way to connect HDMI to the Samsung TV is by using the ONE CONNECT box.
- You need to have the 4K TV connected to the HDMI connector while you apply F/W update.
- The 4K TV will not work until this update is applied.
- You need another monitor connected so that you can use it to log into Windows and apply the F/W update.
- Unless you upgraded to Windows 10 Pro or Windows 10 Enterprise, you cannot use a remote monitor (i.e. use the Remote Desktop Connection tool from another Windows-based PC).
- What method is left to hook up another monitor? The VGA connector.
Okay, so you're suggesting I run the NUC hooked up with two monitors, one VGA, and the other the Samsung HDMI 2.0. That sounds like a good idea, but I'll need a little time to check and get back to you.
In the meantime, running the bobcat software it's unclear to me what's happening. Just by running BobcatAuxISPTool, is the patch/firmware being applied? There seems to be more to it. Under ISP File Setup there's a browse function for "Driver File" and another browse function for "FW File". When browsing, they start in the "bin" folder that was unzipped along with bobcat. Bin folder contains the following:
Each of these three files can be selected and run, but I'm not sure which one if any is appropriate and I'm not sure if I should be running them under the "Driver File" path or the "FW file" palth.
There's a similar active thread in this same forum:
On this thread, Intel Tech, "Wanner G." is instructing that OP how to install the same HDMI firmware with the instructions:
"-There can only be one video device plugged into the HDMI port and it must be an HDMI 2.0 device."
While it sounded like a good idea to me, it now seems that having the NUC output to monitor via VGA (so I can see it) while also having it output to my Samsung via HDMI would not be a good solution because only ONE video device may be plugged in. Unless of course this was just a precaution by Wanner G. Either way, I'm not sure how I can plug into a 2.0 HDMI video device and run the software when my problem is I can't see anything using the HDMI 2.0 compliant device (Samsung).
Again, I could hot swap with my mouse right on the file to execute, then hook it up to the Samsung and click/run bobcast in-the-dark, so to speak, but again the problem is the way the software runs requiring you to browse for a bin file.
You are plugging the second monitor into the VGA port, which is a totally separate hardware interface from that for the HDMI interface. The update is modifying the firmware stored in the LSPcon IC used to generate the HDMI output. What Wanner is trying to say (though very awkwardly) is that the TV/Monitor must be connected to the NUC directly; there cannot be any intervening device, such as a Receiver or a HDMI switch.
Bottom line, there is no conflict here. This is exactly how I configured my NUC6CAYS to run the update.
Are you using the attached instructions? It specifically tells you to select file "BobcatIsp_v1.02_cut2.2_aux_SA_signed.bin" as the Driver File and select file "MCDP2800_C21_C22_V1.72.00_LSPCON_MP_FHC_SIGNED_CMDB_AY.bin" as the FW File. The third file, MCDP2800_C21_C22_V1.72.00_LSPCON_MP_FHC_SIGNED_CMDB_BN.bin is for the update of the BN NUCs and will not be used in the update of your AY NUC.
Now, generating this response got me thinking. In a previous post, you said: "Also, the ONLY way to connect HDMI to the Samsung TV is by using the ONE CONNECT box.". This might be a problem, since this box is essentially a HDMI switch...
Hope this helps,
"Are you using the attached instructions? It specifically tells you..."
OMG! lol. Scott, you've been extremely helpful, but you have to realize those instructions have only JUST NOW been put there by Cvare and that the whole reason I started this thread was to get proper instructions in the first place.
Using the VGA and HMDI ports at the same time as described by Scott and using the updated instructions provided by Cvare, I was finally able to correctly run the firmware described in my OP.
Cvare, your instructions were very clear! Perhaps this is obvious to most, but It might be helpful to add that the user can still use the VGA port while the HDMI is in use. Also, were it not for your old posts on this topic I probably wouldn't have gotten this far. Oh, and I don't think the HDMI firmware update is included in the "bundle" of upgrades you can download as one zip for the NUC.
Anyway, I'm grateful to you guys for helping me resolve this issue! I can now use my Samsung HDTV. Thank you so much!
On the other hand, I can't help but point out that if someone from Intel had just clarified the instructions as I asked in the originally OP, I would haven't have had to spend several frustrating hours on a wild goose chase. In particular, I'm frustrated with "David V" who, after asking me for reports I didn't think were necessary, never once bothered to respond or follow up on this thread even after I provided the information he requested. Likewise, on an active thread during this same time period, "Wanner G." gave the same firmware to a user and when the user pointed out that the instructions were incomplete, Wanner refused to acknowledge anything and instead went off on another tangent.
Thanks for sticking with me on this.
I think the "one connect" box is really just a way for Samsung to cut costs and provide different ports for different TVS. The cable that connects the "one connect" to the Samsung looked proprietary.
Actually, I received these instructions on November 1, 2017 (that's the date on the file I have archived in my offline database). Of course, I could have gotten them through unofficial channels (I do visit the development and support teams from time to time, just to keep them on their toes). Puzzled by why you seemed so confused regarding the files provided (as I stared at my offline copy, which explained it all quite simply), I finally looked at the version posted on the downloads page and only then realized that the wrong document was posted. I didn't even realize until afterwards that Chris had also posted a copy of the correct instructions in this conversation. Chris (cvare), could you please fix the downloads page as well?
pmole So glad to hear you're up and running again!
To be honest I can't fault David V or Wanner G for knowing the instructions were wrong since I just found out and I wrote them!
I'll be working with the team to make sure everyone is aware that the instructions were not correct and I have just updated them, they should go live soon.
My complaint wasn't really about the instructions at all, but the way the issue was or rather wasn't addressed. But don't make too much of it. Here I am coming as a total stranger to a bunch of folks who are helping me for free and I'm complaining about it? No more of that. Without this forum I'd either still be troubleshooting or off shopping for a new NUC-like PC to replace my 6CAYS. Thanks again.