Answering my own question....
When I copied 'an existing target' to a new name and edited it, I found that the target name is very important!
But this works:
This is not clear in the video instructions. Just added the '-BCM920736TAG_Q32' to the name and it worked (well, it failed for other reasons...).
10:13:39 **** Build of configuration Release for project WICED-Smart-SDK ****
"C:\\Users\\acowan\\Documents\\WICED\\WICED-Smart-SDK-2.1.1\\WICED-Smart-SDK\\make.exe" WICED_Sense-BCM920736TAG_Q32 download
The make file name is extremely important within the SDK environment as the build process uses those names to find the necessary files needed for the build.
It looks in the /apps directory of the SDK for "heart_rate_monitor"
Then it looks in the /platforms directory for "BCM920736TAG_Q32"
If there is a typo in either, the compiler will throw errors.
I also discovered that the name
won't build, but the name
will build. <sigh>
Interesting. This didn't seem to be a problem for me when I ran through the example I just provided here: Can I run any of the included profiles within the SDK on the WICED Sense EVB?
I used this make target: heart_rate_monitor-BCM920736TAG_Q32 download
My device is bricked now, so I need to unbrick it and figure out how to run it off USB power.