@SachinG007 I think this pR is mostly done? Can you just double check the README steps and sign off so that we can merge this.

@metastableB I am a bit concerned about the complexity of step 1 in README.md. It was not straightfoward for me. Can we try another way of setting up MXChip? Like use VSCode/Iot DevKit/ and https://github.com/IoTDevEnvExamples/DevKitKeywordSpotter/blob/master/README.md, and dropping in some extra files? Or do you think there is hope of simplifying or documenting step 1 better?

I'm waiting for a fresh machine to replicate these steps. Once I get my hands on one, I'll try to simplify things.

The VSCode/IoT Devkit version hasn't worked very well yet because of some mbed related incompatibilities. This route, if it works, will be much simpler though.

I plan to finish this within the next couple of weeks. If mbed errors persist in VSCode, I'll go with VSChina route (as currently done). If things work with VSCode fine, I'll gladly switch over.

@SachinG007 We need to sync up on this.

I'm waiting for a fresh machine to replicate these steps. Once I get my hands on one, I'll try to simplify things.

The VSCode/IoT Devkit version hasn't worked very well yet because of some mbed related incompatibilities. This route, if it works, will be much simpler though.

I plan to finish this within the next couple of weeks. If mbed errors persist in VSCode, I'll go with VSChina route (as currently done). If things work with VSCode fine, I'll gladly switch over.

@SachinG007 We need to sync up on this.

I have mailed you a new Readme (not in proper format) which I followed to set up the wake word on MXChip detection from scratch. I have mainly simplified the STEP 1, and included the direct links to the mbed-cli installers. @metastableB , once you review it, I will write the same in a proper format.