SDK 2.4.0 How to Build a Program

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

cross mob
Anonymous
Not applicable

Greetings,

I have installed the WICED SDK 2.40 on an XP 32bit machine. The program is installed properly. I have downloaded the MinGW GCC and set it as my current toolchain. The Gnu make builder is the current builder. I have a SN8200 wireless module. Everytime that I am trying to build the 'snip.https_client-BCM943362WCD4 download run' file from the Make Target tab i get the error

make *** No rule to make target 'snip.https_client-BCM943362WCD4 download run'. Stop.

Any help would be appreciated

Best Regards

1 Solution
Anonymous
Not applicable

There is no need to download GCC as the SDK comes with the complete toolchain required to build applications.

The WICED SDK is designed to run only with the make executables provided at the root directory of the SDK.

Open a command prompt and change to the root directory of the SDK to execute the make command.

e.g:

C:\Wiced-SDK\make snip.https_client-BCM943362WCD4 download run

View solution in original post

10 Replies
Anonymous
Not applicable

I could build it on my XP environment.

Installation may be not completed.

Please check if https_client.mk exists in snip\https_client folder.

And have you tried other build target like snip.ping_powersave ?

0 Likes
Anonymous
Not applicable

There is no need to download GCC as the SDK comes with the complete toolchain required to build applications.

The WICED SDK is designed to run only with the make executables provided at the root directory of the SDK.

Open a command prompt and change to the root directory of the SDK to execute the make command.

e.g:

C:\Wiced-SDK\make snip.https_client-BCM943362WCD4 download run

Anonymous
Not applicable

Greetings,

Thank you for your help. It seems to work better. The application is built successfully. However, when i make use of the download and run parameters i get the OpenOCD failed message. I read in the manual that probably i am not selecting the correct device, but i do not know which one to choose. I am using the SN8220 Murata module. The command that I am using is the make snip.scan-BCM943362WCD4 download run

and 

make snip.https_client-BCM943362WCD4 download run

Thank you

0 Likes
Anonymous
Not applicable

Please check in the Control Panel/Device Manager that the USB driver has been properly installed. Take a quick look at the top of the list to ensure there are no yellow question marks. If there are then try updating the driver for each.

The driver is updated by right click and select "Update Driver..", point to the drivers folder in the SDK installations directory. You can see my example path below.

C:\Users\johan\Documents\WICED_2.4.0\Wiced-SDK-2.4.0\WICED-SDK\Drivers\BCM9WCD1EVAL1_Drivers

Best Regards,

Johan

0 Likes
Anonymous
Not applicable

Greetings,

Thank you but there is no issue with the drivers. After some research I found out that for the sn8200 module i should use the BCM943362WCD2 platform. So now the command is

make snip.https_client-BCM943362WCD2 download run

The program is built and downloaded properly on the module. I am using HTERM and i can see the initialization platform messages. However, the I cannot see the outputs of the program because, after debuging i found out that the program breaks within the wiced_bus_init() function.


Regards.

0 Likes
Anonymous
Not applicable

Hi,

Please add -debug at the end of the build string and rebuild. Run JTAG debugging and observe in the debugger where the program breaks.

Thanks.

Aji

0 Likes
Anonymous
Not applicable

Greetings,

Thank you very much. This is what I am doing actually. However, the debugging process is a bit funny so it is not that clear the point that the whole thing crushes.

Best Regards,

Asterios

0 Likes
Anonymous
Not applicable

I'm also having a similar isuue. I want to build a target from the .snip dir then use that as the beginnings for a new piece of code, So I can copy/paste the folder-rename it and I am up and running.

I invoke the make from a conmmand line

make apps.snip.easy_setup -d

.................and the lower part of the debug stream is below.

Reading makefiles...

Reading makefile 'wiced_config.mk'...

Reading makefile 'wiced_toolchain_common.mk' (search path) (no ~ expansion)...

find_and_set_shell() setting default_shell = cmd.exe

wiced_config.mk:171: Wiced/Platform//.mk: No such file or directory

wiced_config.mk:178: *** No matching toolchain found for architecture .  Stop.

Reading makefile 'Wiced/Platform//.mk' (search path) (no ~ expansion)...

Reading makefile 'wiced_toolchain_ARM_GNU.mk' (search path) (no ~ expansion)...

Reaping losing child 0096F1C8 PID 9896384

Removing child 0096F1C8 PID 9896384 from chain.

Failed to remake target file 'build/apps_snip_easy_setup/config.mk'.

Pruning file 'wiced_toolchain_common.mk'.

Pruning file 'Makefile'.

Updating goal targets....

Considering target file 'apps.snip.easy_setup'.

File 'apps.snip.easy_setup' does not exist.

  Considering target file 'main_app'.

   File 'main_app' does not exist.

    Considering target file 'build/apps_snip_easy_setup/config.mk'.

    Recently tried and failed to update file 'build/apps_snip_easy_setup/config.

mk'.

make: *** No rule to make target 'build/apps_snip_easy_setup/config.mk', needed

by 'main_app'.  Stop.

Thank in advance

Scott

0 Likes
Anonymous
Not applicable

Hi Scott,

Your make command "make apps.snip.easy_setup -d" is not valid as it does not have a platform specified

0 Likes
Anonymous
Not applicable

Discussion is being locked. If you have any follow-up, please start a new discussion.

0 Likes