BOTTOM LINE: If you’re having problems uploading the master code to your Cortex while using the utility.
UNPLUG AS MANY OTHER USB DEVICES AS YOU CAN!!!
I have a NC1 Cortex, Windows 7 x64, all of this on regular old USB 2.0 ports w/ a run of the mill A-A cable. Yes it’s an old Cortex model, not an excuse - you build it, you sell it, YOU SUPPORT IT.
I tried to update the firmware at least 30x times, failed every time, usually on the very first block (James believes that block 1-8 aren’t written to so block 9 is first). I unplugged all but my USB keyboard and mouse and the dang thing worked the very first time. In fact just to be sure I uploaded the master firmware again and it worked without issue.
Write this line as an instruction into the firmware upgrade utility manual: “blah blah blah, if NC1 or failing on block 9, unplug all other USB devices and try again, blah blah blah.”
I met you at the event at the event at CU Boulder I believe.
I have never had an issue with this. I had a cortex plugged in, (I tried it with 3 or 4 different cortexes (or is it cortecies???), running the upgrade utility through both PROS and the ifi download off of a usb stick with 2 usb sticks, a usb mouse, keyboard and an external harddrive with no problems? try reinstalling the utility, or resetting the firmware first on a different computer adn then on yours.
I remember having an issue with this when I helped a few schools update the older version of the Cortex. I had played with all the drives and devices… and it took me a while to finally update one. It kept getting hung at some point.
I don’t think it was me, I haven’t been to a VEX event this year, nor Boulder.
If I had to guess I’d say this is an issue specific to the NC1 Cortex. My joysticks all updated fine with my regular I/O plugged in. I don’t know what is different about the early Cortex model but obviously something is.
That sounds like you didn’t have the correct driver installed. Believe me I went through this too, but I was able to figure it out on my own.
This is exactly what I had going on but worse (probably due to the number of USB devices I had plugged in). This also confirms my suspicion that the issue is limited to the NC1 (the flat ones). Thanks!