DCT download fails - Githubissues

From gitter chat:
the upload of the DCT has sometimes been a bit hit and miss
I'm having the same issue on linux. The error openocd spits out is
Error: timeout waiting for algorithm, a target reset is recommended
Error: error executing stm32x flash write algorithm
Doing it "manually" doesn't always work either.
tve 17:31
What is the DCT to begin with? I see it's a Device Configuration Table and it has wifi settings, but beyond that? Is it an stm32 concept or a wiced concept?
Is there any short readme on how to set-up an application source tree outside of the wiced tree?
paulreimer 17:35
I am also curious about the reliability of uploading the DCT. I usually try randomly:
• a full clean/re-build
• USB-cycling the programmer
• trying again repeatedly
and sometimes it can take upwards of 20 tries. If it doesn't fully program, then the GDB eclipse debugger has trouble attaching.
paulreimer 17:49
Some questions: why does it not flash reliably (when the bootloader and app seem to have no problems)? Why does it re-compile the DCT blob, even if I don't change any wifi-related settings/defaults? How are other people coping with this problem?
emilf 19:20
I don't know why the DCT doesn't flash reliably, but I either do VERBOSE=1 and copy the openocd command line for flashing it or just try repeatedly. It seems to work reliably when I do the openocd command line.
It's a WICED concept afaik, and holds all sorts of config data, both custom to your application and generic for the WICED framework. It works as an MBR (master boot record).
I'll see if I can work out what's wrong, as it's rather frustrating, but hasn't bugged me enough to do anything about it.
MXCHIP-EMW / WICED-for-EMW

DCT download fails #11
