cancel
Showing results for 
Search instead for 
Did you mean: 

WICED Studio Bluetooth

NiLi_2861801
New Contributor II

Hi ,

   I have three CYW920719Q40EVBoards

   One of them have this problem while downloading:

Detecting device...
Device found


Downloading application...
****Download failed ****


A total of 1 contiguous memory areas were filled:
[00500000..00500041] DATA (66 bytes)
Download config error trying to write 240 bytes to address 0x005042D0    (SOURCE:  CONFIG   Configuration data   build/mesh_battery_client-CYW920719Q40EVB_01-rom-ram-Wiced-release/mesh_battery_client-CYW920719Q40EVB_01-rom-ram-Wiced-release.hex)
Download failed. This WICED platform of the SDK only supports download to 207x9B1 devices.
Follow the instructions in the 20719-B1 README.txt for downloading the application.

11:34:36 Build Finished (took 14s.559ms)

  

  Another question is why they need to be reset to factory defaults every download.  only reset will cause  this:

Detecting device...

+------------------------------------------------------------------------------------------+

| No CYW207x9 device detected.                                                            

| 1. Verify the CYW207x9 WICED eval board is connected _AND_ powered                      

| 2. Verify all switches are set to the default positions                                 

|    - see "Connect the WICED Evaluation Board" in the Quick Start Guide or Kit Guide     

|      for defaults                                                                       

| 3. Press the reset button on the WICED eval board and retry                             

|                                                                                         

| See 20719-B1_Bluetooth/README.txt for more info.                                        

| If this problem persists, the board EEPROM may need to be reset to factory defaults.    

| Please see Recovery instructions in the Quick Start Guide or Kit Guide.                 

+------------------------------------------------------------------------------------------+

thanks

0 Likes
1 Solution
Anonymous
Not applicable

If you are able to program other board, there might some issue with the board. Have you not been able to program the board even once?

For the second question, which version of WICED are you using? Also try adding the UART=COmxx command in the make target.

Why recovery mode needs to be used before programming?

- If your application makes use of wiced UART, i.e. has the wiced_transport_init(), then it might be configured for a different baudrate than the default(115200). So the 'get_com_port' perl script might not be able to communicate with the device, because of which the device might not be detected. Sometimes, the device might be detected but the device might not respond to the RESET command sent.

View solution in original post

0 Likes
3 Replies
NiLi_2861801
New Contributor II

no problem now

0 Likes
Anonymous
Not applicable

If you are able to program other board, there might some issue with the board. Have you not been able to program the board even once?

For the second question, which version of WICED are you using? Also try adding the UART=COmxx command in the make target.

Why recovery mode needs to be used before programming?

- If your application makes use of wiced UART, i.e. has the wiced_transport_init(), then it might be configured for a different baudrate than the default(115200). So the 'get_com_port' perl script might not be able to communicate with the device, because of which the device might not be detected. Sometimes, the device might be detected but the device might not respond to the RESET command sent.

View solution in original post

0 Likes
NiLi_2861801
New Contributor II

Hi yssu,

   The first problem resolved.

    WICED is 6.1.0.85.   wiced_transport_init() called for HCI_CONTROL.

0 Likes