Known WICED example code conversion problems.

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

cross mob
Anonymous
Not applicable

Are there any known code conversion problems in the WICED examples? All of the Example code is made for the old broadcom BCM92073(6/7) devices so I have to compile it to run on the CYBLE_013025_EVAL. When I look at the platform.h file for the different target types, the CYBLE model platform file does not have as many pins defined in it, and it doesn't show as having a write protect pin for NVRAM. I'm wondering if some of these differences cause any known misbehavior in the example code after non-defined defines are resolved.

Right now I am trying to get the ota_firmaware_upgrade and ota_secure_firmware_upgrade to work without success. I have also been trying to get some UART data back on those examples from the ble_trace data, but no uart data is coming through from them. I have also posted some other questions about this device here: Read Flash Memory from CYBLE-013025 Device

Cant get Cyble-013025 dev kit to run over the air firmware updates.

0 Likes
1 Solution
Anonymous
Not applicable

skuv

So I tried your code on a different devkit ble board, same model, and the Uart print statement came through clean, so the board I was working on appears to have a dirty PUART output for some reason.

However, I still tried to do the OTA update and the furthest it is still geting, is after pressing start, it shows the abort button but nothing happens. I made sure that I have followed all of the steps in the document, which is the same way I was doing it, BUT my device manager properties for the bluetooth device does not show a power management tab for the "hello" device. Does your's show a power management tab? If so maybe the PC isn't installing the bluetooth device properly in a way that it is able to control both the power management and the firmware update.

I am running on Windows 10.

View solution in original post

0 Likes
13 Replies
MichaelF_56
Moderator
Moderator
Moderator
250 sign-ins 25 comments on blog 10 comments on blog
0 Likes
Anonymous
Not applicable

mifo

I'm almost certain that that page is the location I got the platform files. I know I have platform files for CYBLE-013025-EVAL but as for the KBA220379 extension i'm not certain. I just noticed that this board has the same model number http://www.cypress.com/documentation/development-kitsboards/cyble-013025-eval-ez-ble-module-arduino-...  but has a different layout than mine. My board has only 4 switches and 2 buttons which are smaller buttons. So I think there is a possibility of difference in the platform files. The eeprom and idfile appears to be identical between the linked library and the one I am using.

0 Likes

I'm hoping skuv​ on the applications team can help when he gets into the office (different time zone).

0 Likes
Anonymous
Not applicable

Ok, thanks. Is there a different model page for this board I have than the one I am looking at? The Numbers are the same, but the board is clearly different. WIN_20171024_14_09_30_Pro.jpg

While I am looking at CYBLE-013025-EVAL EZ-BLE™ Module Arduino Evaluation Board | Cypress Semiconductor

The ID on the actual ble cover is CYBLE-013025-00 fcc id:wap3025 ic:7922a-3025

0 Likes

Hi,

I will run the ota_firmaware_upgrade on CYBLE-013025 and get back to you with my observations asap.

Thanks,

Santhosh.

Anonymous
Not applicable

Awesome, thanks. If you get it working, It would be awesome to get a copy of the project files if you don't mind.

0 Likes
lock attach
Attachments are accessible only for community members.

tyler.cox_2489271

Tested attach project for OTA and PUART.

This board has GPIO_PIN_UART_TX and RX are set to 24 and 25 respectively. (You should see PUART print in the attached project).

I was able to do OTA as well, I hope you are aware of the procedure for OTA. Let me know if you need steps for OTA.

Thanks,

Santhosh.

Anonymous
Not applicable

The puart is working, however I have been getting corrupt data from it as well as on other attempts at this project, i'm not sure why.

Capture.PNG

I tried reading the Uart both over the Board with the switches positioned as (on,on,off,off), as well as reading Uart from a different usb-uart board.

I also tried running a firmware update. What software are you using to run the update? I am using the peerapps WsOtaUpgrade C++ code, which gets stuck at this point:

Capture.PNG

Opening interface:\\?\BTHLE#DEV_20737A117124#7&1D97B5DA&0&20737A117124#{781AEE18-7733-4CE4-ADD0-91F41C67B592}

OpenBleService Opening interface:\\?\BTHLEDEVICE#{9E5D1E47-5C13-43A0-8635-82AD38A1386F}_20737A117124#8&1AE9DC6E&7&FF00#{9E5D1E47-5C13-43A0-8635-82AD38A1386F}

BluetoothGATTSetDescriptorValue hr:0x0

OpenBleService Opening interface:\\?\BTHLEDEVICE#{9E5D1E47-5C13-43A0-8635-82AD38A1386F}_20737A117124#8&1AE9DC6E&7&FF00#{9E5D1E47-5C13-43A0-8635-82AD38A1386F}

BluetoothGATTRegisterEvent hr:0x0

OpenBleService Opening interface:\\?\BTHLEDEVICE#{9E5D1E47-5C13-43A0-8635-82AD38A1386F}_20737A117124#8&1AE9DC6E&7&FF00#{9E5D1E47-5C13-43A0-8635-82AD38A1386F}

BluetoothGATTSetDescriptorValue hr:0x0

OpenBleService Opening interface:\\?\BTHLEDEVICE#{9E5D1E47-5C13-43A0-8635-82AD38A1386F}_20737A117124#8&1AE9DC6E&7&FF00#{9E5D1E47-5C13-43A0-8635-82AD38A1386F}

I also have the CySmart 1.2 software, but it doesn't show any supported or unsupported targets.

Capture.PNG

I think I have a decent idea of OTA procedure, but this is my first OTA firmware update project. I know that it is loading into a second set of ROM and then switches over to it when it is verified.

0 Likes
lock attach
Attachments are accessible only for community members.

tyler.cox_2489271

Try to use below statement, i don't see any weird characters on the TeraTerm

     puart_print("timer \n");

I'm assuming that you are using 20702 based Dongle connected preferably to Win10 machine with appropriate drivers installed. I attached a document for reference which describes the steps to perform OTA.

Thanks,
Santhosh.

Anonymous
Not applicable

skuv

So I tried your code on a different devkit ble board, same model, and the Uart print statement came through clean, so the board I was working on appears to have a dirty PUART output for some reason.

However, I still tried to do the OTA update and the furthest it is still geting, is after pressing start, it shows the abort button but nothing happens. I made sure that I have followed all of the steps in the document, which is the same way I was doing it, BUT my device manager properties for the bluetooth device does not show a power management tab for the "hello" device. Does your's show a power management tab? If so maybe the PC isn't installing the bluetooth device properly in a way that it is able to control both the power management and the firmware update.

I am running on Windows 10.

0 Likes
Anonymous
Not applicable

Hi Tyler,

What is the Windows 10 version? Is it greater than 1703?

Can you test on a Windows 8 PC?

0 Likes
Anonymous
Not applicable

Any ideas why my OTA update gets stuck at the start of the update process? Could you send your visual studio project for the windows OTA updater tool in case there is something wrong with mine?

0 Likes
Anonymous
Not applicable

skuv

just checking to see how that firmware upgrade example is going but I also had a question that maybe you can answer. Our hardware guy is looking at the spec sheet on the CYBLE-013025 module and it says we can source 16mA of current, but it doesn't say how much the open drain limit is. We are running an open drain on pin 27 along side a pwm for dimming an LED, but we aren't sure of the limitations of that pin on sinking.

0 Likes