cancel
Showing results for 
Search instead for 
Did you mean: 

Smart Bluetooth

Anonymous
Not applicable

I'm getting started and could use some help.

I'm trying to get the SDK working from the command line in OSX.

Eval Board: BCM920732TAG_032

SDK: WICED-Smart-SDK-1.1.0

Platform: OSX 10.8.5

From README.txt

./make RAM.automation_io-BCM920732TAG_Q32 download

Build works; download fails.

First problem is, in Makefile, CGS_FULL_NAME and HEX_TO_BIN_FULL_NAME

are not defined on OSX.  wiced_toolchain_common.mk  sets them

for Windows, but not OSX.

So I set them:

CGS_FULL_NAME = Tools/CGS/OSX/cgs

HEX_TO_BIN_FULL_NAME = Tools/IntelHexToBin/OSX/ihex2bin

Second problem:

  Creating OTA images...

  Failed to open input file build//.ota.hex

Caused by OUTPUT_NAME being blank.

I could keep hacking things and maybe get this to work, but am I missing something?

0 Likes
1 Solution
Anonymous
Not applicable

Hello foolography,

You are correct in your statement:

I understand that the SDK 2.0.1 does not support the BCM920732, but only the BCM920736 and BCM920737

Yes, you will have to install the older SDK on the VM Machine.

If plans change, however, we will notify you of the support of Mac OS X.

JT

View solution in original post

0 Likes
7 Replies
Anonymous
Not applicable

Hello Asher,

SDK 1.1 does not support OSX.  The scripts you mentioned below are implemented in SDK 2.0.1 and do work in OSX.

So I don't have an answer for you on SDK 1.1

The SDK 2.0.1 scripts for the make file and creating images need to be compared to hte SDK 1.1 for differences.

We will try to squeeze some time in next week for that comparison if that meets your schedule?

Thanks

JT.

0 Likes
Anonymous
Not applicable

Next week is fine. I will order the newer eval board to work with SDK 2.0.1.

0 Likes
Anonymous
Not applicable

Hi I'd be very interested in getting the SDK 1.1 running on OSX, while waiting for my order of a newer evaluation board too. Any new info on this?

0 Likes
Anonymous
Not applicable

Hello foolography and asher,

The back-porting of the 2.0.1 scripts to the SDK 1.1 proved to be more time consuming than anticipated.

The decision was made to support the OSX scripts on SDK 2.01.

Apologize for the inconvenience.

JT

0 Likes
Anonymous
Not applicable

No problem.

If you figure everything will work on SDK 2.0.1, that's great. I look forward to trying it this week or next.

Appreciate your looking into it.

0 Likes
Anonymous
Not applicable

Hi JT,

that's a shame, as I understand that the SDK 2.0.1 does not support the BCM920732, but only the BCM920736 and BCM920737. Or am I wrong about this (I hope so)?

We plan to use the BCM920732 in upcoming projects, and would like to begin initial development soon. Will it be possible to do this on Mac OS X, or do we have to install the older SDK on a windows VM?

0 Likes
Anonymous
Not applicable

Hello foolography,

You are correct in your statement:

I understand that the SDK 2.0.1 does not support the BCM920732, but only the BCM920736 and BCM920737

Yes, you will have to install the older SDK on the VM Machine.

If plans change, however, we will notify you of the support of Mac OS X.

JT

View solution in original post

0 Likes