I just purchased an EVAL-ADICUP360 eval board for the ADuCM360 and I can't find any documentation on how to flash it. So far I have gotten CrossCore Embedded Studio setup following the instruction here: https://wiki.analog.com/resources/eval/user-guides/eval-adicup360/tools/cces_user_guide. I have been able to compile and run the Blinky and CLI example programs on the board.
Next I am trying to figure out how to program a BIN file to flash memory but have not had any success. I have tried from guides I've found around the AD wikis:
Overall I have found the documentation for this product very confusing and fragmented. Much of it seems very out of date. I would appreciate any help getting this set up with the current preferred method using the free compiler tool-chain.
Dragging and dropping a .BIN file is pretty straight forward. Could you also tell me which version of CrossCore you are using?
All you need to do is create the .bin file while you are building your project from CrossCore. Once created all you need to do is drag it and drop it from the folder it is saved to onto the MBED drive in your directory. Once that happens you simply need to hit the RESET button on the EVAL-ADICUP360 and you should be good to go.
Creating a .BIN file from CrossCore is documented here as a series of steps and gifs. (https://wiki.analog.com/resources/eval/user-guides/eval-adicup360/tools/cces_user_guide#how_to_create_a_binary_bin_or_intel_hex_hex_file_for_an_aducm360_application ) It is extremely important that you turn off semihosting for any application before you build you .bin, otherwise your drag and drop won't work.
Can you please try this again and let me know how it goes?
I have followed the wiki instructions to build the Blinky project and generate a .BIN file. When I run in the debugger the board blinks as expected.
When I drag the BIN file to the MBED drive the DS4 LED goes from blinking to steady for 2 seconds then returns to blinking. Reset does not start the program and MBED has a fail.txt file with TIMEOUT in it.
Sometimes when I try DS4 stays on much longer and I get an SWD ERROR in fail.txt
Does the board need to be in a different mode before programming? I could not find any instructions on your wiki for using this drag-n-drop programming interface and only learned of it from various forum posts.
I just tried programming the board from an Ubuntu 18.04 machine and dragging the .BIN file in worked. After pressing RESET the lights started blinking. However, the program did not persist after power cycling the board. Shouldn't this have flashed to non-volatile memory?
Why can't I program this board over USB from my Windows 10 machine?
I just tried this out with CrossCore 2.8.0 and I used both the blink and the CLI demos from Github and everything worked.
I just took a screen shot for you on the CLI demo. I do have a 4 second video of the blinky working, but my computer won't let me upload it right now.
So I've verified they work, what I need you to do now is follow the steps i did and try this again. Make sure you are working from all updated software. If it still doesn't work, could you take a video of your screen and what you are seeing. Along with the board?
I followed your instructions carefully:
As soon as I drag the file onto MBED the disk disappears and then remounts. Inside is fail.txt file with the message "SWD ERROR" each time.
Note that the MBED drive does not stay mounted continuously on Windows 10. The drive seems to reset every 30 seconds or so, is this normal behavior?