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

AIROC™ Wi-Fi and Wi-Fi Bluetooth Combos Forum Discussions

GrCa_1363456
Level 5
Level 5
First comment on KBA First comment on blog 250 sign-ins

The following error occurs when attempting to run an AT_CMD program from Murata on one  PC.

====================The specific error is:

tools/makefiles/wiced_config.mk:433: *** tiny_bootloader application does not support QUICKSILVER_EVL platform. Stop.
make.exe[2]: *** No rule to make target 'build/waf.tiny_bootloader-NoOS-NoNS-QUICKSILVER_EVL-P200-SoC.43909/config.mk', needed by 'main_app'. Stop.
WICED/platform/MCU/BCM4390x/BCM94390x_targets.mk:243: recipe for target 'build/test.at_cmd-QUICKSILVER_EVL/tiny_bootloader_bin2c.o' failed
make.exe[1]: *** [build/test.at_cmd-QUICKSILVER_EVL/tiny_bootloader_bin2c.o] Error 2
make.exe[1]: *** Waiting for unfinished jobs....

====================The full console is:

15:44:07 **** Build of configuration Default for project 43xxx_Wi-Fi ****
"C:\\Users\\XXXXXXXX\\Documents\\WICED-Studio-6.6\\43xxx_Wi-Fi\\make.exe" test.at_cmd-QUICKSILVER_EVL download run
MAKEFILE MAKECMDGOALS=test.at_cmd-QUICKSILVER_EVL download run OTA2_SUPPORT is disabled
Applying changes made to: WICED/WICED.mk apps/test/at_cmd/at_cmd.mk
+-----------------------------------------------------------------------------------------------------+
| IMPORTANT NOTES |
+-----------------------------------------------------------------------------------------------------+
| Wi-Fi MAC Address |
| The target Wi-Fi MAC address is defined in <WICED-SDK>/generated_mac_address.txt |
| Ensure each target device has a unique address. |
+-----------------------------------------------------------------------------------------------------+
| MCU & Wi-Fi Power Save |
| It is *critical* that applications using WICED Powersave API functions connect an accurate 32kHz |
| reference clock to the sleep clock input pin of the WLAN chip. Please read the WICED Powersave |
| Application Note located in the documentation directory if you plan to use powersave features. |
+-----------------------------------------------------------------------------------------------------+
MAKEFILE MAKECMDGOALS=test.at_cmd-QUICKSILVER_EVL download run OTA2_SUPPORT is disabled
Building Bootloader waf.bootloader-NoOS-NoNS-QUICKSILVER_EVL-P200-SoC.43909
Building Tiny Bootloader waf.tiny_bootloader-NoOS-NoNS-QUICKSILVER_EVL-P200-SoC.43909
tools/makefiles/wiced_config.mk:433: *** tiny_bootloader application does not support QUICKSILVER_EVL platform. Stop.
make.exe[2]: *** No rule to make target 'build/waf.tiny_bootloader-NoOS-NoNS-QUICKSILVER_EVL-P200-SoC.43909/config.mk', needed by 'main_app'. Stop.
WICED/platform/MCU/BCM4390x/BCM94390x_targets.mk:243: recipe for target 'build/test.at_cmd-QUICKSILVER_EVL/tiny_bootloader_bin2c.o' failed
make.exe[1]: *** [build/test.at_cmd-QUICKSILVER_EVL/tiny_bootloader_bin2c.o] Error 2
make.exe[1]: *** Waiting for unfinished jobs....
prgm hdr cnt=3
total_size = 14712, entry_point = 0x696000
Loadsegment_offset = 0xA0 segment_size = 14432, segment_pad = 0
Loadsegment_offset = 0x3900 segment_size = 32, segment_pad = 0
Loadsegment_offset = 0x3920 segment_size = 248, segment_pad = 0
Finished Building Bootloader

make: *** [main_app] Error 2
Makefile:351: recipe for target 'main_app' failed

15:44:29 Build Finished (took 21s.450ms)

====================The last line in the tiny_bootloader.mk file is:

VALID_PLATFORMS := BCM943909* BCM943907* BCM943903* CYW943907* Quicksilver* CYW954907*

====================tiny_bootloader.mk is located at:

<Project_Folder>/43xxx_WiFi/apps/waf/tiny_bootloader/tiny_bootloader.mk

=====================

This same setup appears to work on a different PC.

One difference is the PC that is failing has some document paths modified with "OneDrive/UserData/"

I attempted to test a path length issue by moving the WICED folder to a longer path on the PC that's working. I could not replicate the error.

Greg

 

1 Reply
Zhengbao_Zhang
Moderator
Moderator
Moderator
First comment on KBA 10 questions asked 5 questions asked

Hello:

     Would you please uninstall the SDK and restart the PC, then do a re-install process?

I think it may be caused by some unexpected failure when installing SDK.

You can do this also:

1.  restart the PC and enter with an Administrator role.

2. kill other running applications as possible, disable all system protection tools, then do the install act. 

0 Likes