If you create a folder on your PC… c:\spark and copy the dfu-util files into it (4 of them in the win32 folder of the zip file, if you run windows) then you can copy your bin file into there and run the CLI from that folder. or you could put -usb at the end and do it through USB, which as I’m sure you know dfu-util comes in to it all. some of the bin files are known by the CLI… like tinker, so you can just put spark flash 0123456789ABCDEFGHI tinkerĪnd it will know what bin file to flash to your spark core, still wirelessly too. When you use the CLI its also sending a bin file to the spark core, thats a binary file and just lots and lots of 1’s and 0’s. The CLI has advantages too… is quick and simple, with just a few words you can re-flash your core. then it connects through the web to your core and says “hey i have a new ‘bin’ file for you, here it is” and sends it wirelessly which is about as easy as it gets. When you type your code in the Web IDE, spark build it compiles it into a ‘bin’ file. The web IDE does a really good job at hiding all that from us, much like the arduino program does for the arduino. The Spark is alot more complicated than the arduino… they have lots and lots of code to make everything easy for us, as they need to interface a couple of very complicated chips the STM32 and the CC3000. Sorry for the delay in replying, been traveling home You dont need the command line for anything anymore. You can compile and download to the spark core all within the IDE. Here is a video link i made showing all the steps needed to compile locally on windows. and look out for the - that the webpage adds when you copy… its caught a few people out Particle – 29 Jan 14 How to video for compiling locally in Windows in the comments of the video on youtube there is a line of paths to add… just add the dfu-util relevent one instead of all of them. This video shows how to set up a local build environment, and there is a small part that covers path variables and where to set them. There is 2 options, one way is to copy the 3 or 4 dfu files to the same folder as the bin file you will be flashing and run it straight from there, or you will need to set up path variables… there is no easy “install” its just a zip file. To make it global you will probably need to add to the path. Thanks for testing and proving this method works *If you miss out this step, Spark-cli will be grumpy! This will allow DFU-util to be executed globally in command prompt. Launch ‘cmd’ (make sure your path is that where dfu-util.exe is) WARNING: Make sure you are using DFU-Util 0.8 It will show ‘Driver installed successfully!!!’ (ok not so many ! :)).So far, ‘libusbK’ is proven working with the core Select ‘CORE DFU’ and ‘libusbK’ for the driver.In Zadig, Click on ‘Options’ -> 'List all devices’ Under ‘downloads’ grab the (windows vista and above or windows xp) Make sure you 'check' the > ‘delete the driver software’ Look for something like libusbk USB devices.If you have somehow done this process previously but is unable to use dfu-util successfully, you will need to uninstall the DFU-driver 1st Release the Mode button once the core start blinking yellow.So it seems like some owners want to go slightly advanced but instructions for installing the DFU-driver is a little vague.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |