Oh and here is a screenshot of the fail that I get. There isn't really any information included in it.
We actually had the binary file being built already, and I checked the setting you pointed me to and it was set correctly. But there is a problem with the binary being build. It allows us to drag and drop the built binary, but then when we open the Sensor Fusion Toolbox and click auto detect it fails to find our device. Below is the error that we are getting.
As for your other suggestions, I am able to flash using the Sensor Fusion Toolbox, as well as drag and drop the pre-complied code provided in the quick start guide, so I don't think it is a problem with the drivers or hardware. The above problem will go away after I do either of these.
Finally, below is a screenshot of the about window from the Toolbox.
I'm sorry you are struggling. If we can't resolve it shortly, I would be happy to schedule a Skype session with you to debug your problem. Most of the time this kind of thing turns out to be simple to resolve once we do that.
The K64F has a couple of UARTs that are of interest for this project. One drives the Bluetooth module, the other the serial/OpenSDA. The version of the kit you have requires you to explicitly program the project's UART to one or the other (see table 2 in the user guide). That might account for why the precompiled binaries work and the one you built doesn't. This is a really common error. So check that first. BTW, just yesterday I posted an early release of Version 5.00 of the sensor fusion library. The new builds work with BOTH wired and wireless connections without this modification.
Other problems I've seen over the years are conflicts for the PC's serial port. To be sure, exit KDS before starting up the fusion toolbox. And make absolutely sure you don't have multiple copies of the fusion toolbox up and running. That will screw you up every time.
When you say you tried drag and drop, was it with a .bin file or a .elf file? The latter is only useful for download within the debugging environment, and frankly I have problems myself in KDS. Another thing I forget to do all the time is to explicitly unplug the OpenSDA after the drag and drop and then reconnect. This forces a reset of the MCU into the downloaded program. Some boards seem to not need that, but the official process is to always reset the board using this technique.
If you see the green blinking LED on the board, you know the fusion software is running. Given what you've described in this last message, I'm betting the wrong UART is programmed. You want UART3 if you are using Bluetooth, UART0 if you are using a wired USB connection. The screen dump below shows the KDS/ProcessorExpert window where you need to make the change.
Regards,
Mike
We are using a wired USB connection, and you were right that we were programming UART3. But when changing this setting I am getting this error.
The problem is that some JTAG settings are conflicting with these settings. I turned them off and at least stopped getting this error. We aren't using JTAG, so I didn't think this would be a problem. Below is what I saw, and unchecking TDI and TDO got rid of the errors. Can you see any problem with doing so? If there is a problem, how can I use UART0?
After turning off those JTAG settings I was able to build the project. As you suggested, I used the drag and drop method (with the binary file) and it looked like it programmed the board. I then closed KDS, unplugged the board, power cycled, plugged it back in, opened the toolbox and hit Auto Detect. Once again, it failed to recognize the board, which is the same problem we have been having. Can you see anything else we should check? If not, I would appreciate having a Skype conversation so we can figure this out.
