stuck - build fails: Platform makefile not found

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable

After following the videos to install IDE and SDK, I'm getting:

09:50:35 **** 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 download

Makefile:194: *** Platform makefile not found: Platforms//.mk.  Stop.

09:50:35 Build Finished (took 110ms)

Anybody know how to fix this?

-AC

0 Likes
1 Solution
Anonymous
Not applicable

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!

This fails:

   WICED_Sense download

But this works:

  WICED_Sense-BCM920736TAG_Q32 download

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

Compiling spar_setup.c

Compiling wiced_sense.c

...

View solution in original post

0 Likes
4 Replies
Anonymous
Not applicable

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!

This fails:

   WICED_Sense download

But this works:

  WICED_Sense-BCM920736TAG_Q32 download

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

Compiling spar_setup.c

Compiling wiced_sense.c

...

0 Likes

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.

For example:

heart_rate_monitor-BCM920736TAG_Q32 download

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.

0 Likes
Anonymous
Not applicable

I also discovered that the name

     WICED_Sense-BCM920736TAG_Q32

won't build, but the name

    WICED_Sense-BCM920737TAG_Q32

will build. <sigh>

0 Likes

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.

0 Likes