Hi,
FYI: We received some Reach’s recently that had fairly new firmware and were able to update them to the latest firmware without a problem using the Wi-Fi connection. But, we could not get them to be recognized as a valid RNDIS network device on Windows 7 or 10 with Intel’s driver installed. After searching a bit, I came across this post:
https://communities.intel.com/thread/107720
Following the solution below documented in the “Answer” posting above fixed the problem:
‘The command fw_setenv can be used to change the parameters that uboot passes to the kernel. This allows for choosing between RNDIS and CDC mode. First, check the current mode via “fw_printenv bootargs_ethconfig”. Then change the mode to RNDIS using the command “fw_setenv bootargs_ethconfig rndis”. Then reboot the Edison. The mode can be changed back to CDC ECM using the command “fw_setenv bootargs_ethconfig cdc” and rebooting again.’