cancel
Showing results for 
Search instead for 
Did you mean: 

WICED Studio Wi-Fi Combo

Anonymous
Not applicable

There's a typographical makefile error in WICED-SDK/tools/makefiles/wiced_apps.mk that causes WICEDv3.1.2 to fail to build, but only in the event that APP2 is defined. The APP0_DOWNLOAD target gets defined twice assuming both APP0 and APP2 are defined. In the seccond instance should really be APP2_DOWNLOAD. See makefile excerpt below.

ifneq ($(APP0),)
APP0_DOWNLOAD:  $(APP0_DOWNLOAD_DEPEDENCY)
$(QUIET)$(ECHO) Downloading APP0 ($(APP0)) at sector $(APP0_SECTOR_START)...
$(call CONV_SLASHES,$(OPENOCD_FULL_NAME)) -f $(OPENOCD_PATH)$(JTAG).cfg -f $(OPENOCD_PATH)$(HOST_OPENOCD).cfg -f apps/waf/sflash_write/sflash_write.tcl -c "sflash_write_file $(APP0) $(APP0_SECTOR_ADDRESS) $(SFLASH_APP_PLATFROM_BUS) 0 $(SFLASH_APP_BCM4390)" -c shutdown #$(DOWNLOAD_LOG) 2>&1
endif

ifneq ($(APP1),)
APP1_DOWNLOAD:  $(APP1_DOWNLOAD_DEPEDENCY)
$(QUIET)$(ECHO) Downloading APP1 ($(APP1)) at sector $(APP1_SECTOR_START)...
$(call CONV_SLASHES,$(OPENOCD_FULL_NAME)) -f $(OPENOCD_PATH)$(JTAG).cfg -f $(OPENOCD_PATH)$(HOST_OPENOCD).cfg -f apps/waf/sflash_write/sflash_write.tcl -c "sflash_write_file $(APP1) $(APP1_SECTOR_ADDRESS) $(SFLASH_APP_PLATFROM_BUS) 0 $(SFLASH_APP_BCM4390)" -c shutdown #$(DOWNLOAD_LOG) 2>&1
endif

ifneq ($(APP2),)
APP0_DOWNLOAD:  $(APP2_DOWNLOAD_DEPEDENCY)
$(QUIET)$(ECHO) Downloading APP2 ($(APP2)) at sector $(APP2_SECTOR_START)...
$(call CONV_SLASHES,$(OPENOCD_FULL_NAME)) -f $(OPENOCD_PATH)$(JTAG).cfg -f $(OPENOCD_PATH)$(HOST_OPENOCD).cfg -f apps/waf/sflash_write/sflash_write.tcl -c "sflash_write_file $(APP2) $(APP2_SECTOR_ADDRESS) $(SFLASH_APP_PLATFROM_BUS) 0 $(SFLASH_APP_BCM4390)" -c shutdown #$(DOWNLOAD_LOG) 2>&1
endif

0 Likes
Reply
1 Reply
Anonymous
Not applicable

Hi,

Thank you for your post. The above mentioned bug have been already identified and should be fixed in the next release. There is also another related one regarding booting from OTA applications. have a look at:

Can't boot from OTA

This should be fixed in next release.

Regards,

Bassem

0 Likes
Reply