WICED not seeing target Quicksilver Board

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

cross mob
MiRo_263836
Level 5
Level 5
100 replies posted 50 likes received 50 replies posted

I created a project on one laptop which displays data from a sensor over a UART in a Tera term window.  It works fine. Something happened on my other laptop, because WICED doesn't see my Quicksilver board when it is plugged.  I double click on the same make target and it fails on the download. 

14:29:02 **** Build of configuration Default for project 43xxx_Wi-Fi ****

"

Making QS101key.ch1.QS_blinkled-Quicksilver_EVL.bin

QS101key.ch1.QS_blinkled-Quicksilver_EVL

----------------------------------|---------|---------|

  |         |  Static |

Module |  Flash  |   RAM   |

----------------------------------+---------+---------|

App |       0 |      38 |

crc |       0 |    1060 |

Interrupt Vectors | 0 |     292 |

libc |       0 |   30317 |

Networking | 0 |   15457 |

NetX-Duo - Interfaces & Stacks    |       0 | 16 |

NVRam |       0 |    2210 |

Other |       0 |   57075 |

Packet Buffers | 0 |   71659 |

platform |       0 |     616 |

RAM Initialisation |      32 |       0 |

resources |       0 |      32 |

Ring_Buffer | 0 |     138 |

Startup Stack & Link Script fill  |       0 |     186 |

ThreadX |       0 |   12136 |

WICED |       0 |    4244 |

Wiced_RO_FS | 0 |     566 |

WWD |       0 |    1551 |

----------------------------------+---------+---------|

TOTAL (bytes) | 0 |  197593 |

----------------------------------|---------|---------|

Creating Filesystem BCM94390x_targets.mk ...

Downloading DCT ... build/QS101key.ch1.QS_blinkled-Quicksilver_EVL/DCT.bin @ SFLASH_DCT_LOC=0x00008000

./tools/common/Win32/mk_wicedfs32 build/QS101key.ch1.QS_blinkled-Quicksilver_EVL/filesystem.bin build/QS101key.ch1.QS_blinkled-Quicksilver_EVL/resources/Staging/

Creating Filesystem Done

WICED/platform/MCU/BCM4390x/BCM94390x_targets.mk:372: recipe for target 'download_dct' failed

  1. make.exe[1]: *** [download_dct] Error 1

Makefile:351: recipe for target 'main_app' failed

make: *** [main_app] Error 2

14:40:44 Build Finished (took 11m:42s.746ms)

This is the same error that I get if the board is unplugged.

I opened up TeraTerm and it is still sending out sensor data from the download and run from last week.

I looked at Device Manager, and  Quicksilver  Board show up as COM14.

How do I check in WICED where the COM Port is selected?  Did it get deselected somehow?

Thanks,

Mike Roberts

0 Likes
1 Solution
PriyaM_16
Moderator
Moderator
Moderator
250 replies posted 100 replies posted 50 replies posted

Hello mroberts_arrowuser_249199259

Can you post the snap of your devive manager?

The WICED board will appear under libusbK devices:

pastedImage_0.png

The COM port for viewing the UART logs will appear under Ports(COM & LPT).

In case your device doesn't appear under libusbK USB devices, check the device in Universal serial bus devices.

You are not able to download through your another laptop beacuse the board is  bind to some driver, other then libusbK.
Kindly change the drivers to libusbK using zadig.

View solution in original post

2 Replies