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

Studio Bluetooth Forum Discussions

ViBi_4484621
Level 1
Level 1
First like given

We have custom board with CYBT-353027 module and third-party mcu.

Our goal is to update bluetooth module firmware by uploading it from the 3rd party mcu.

We have followed instructions from the "WICED-HCI-Control-Protocol.pdf" document.

Also we've aligned our code with Wiced Studio upload flow. On each command we receive a correct response from the module.

But after uploading there is no logs at the PUART and no advertising device with specified name visible (module is not able to startup).

After uploading by Wiced Studio we have the device running and scannable, but when using the same flow and 3rd party mcu we have fail.

Can someone clarify updating process a little by answering next questions?

1) It's not clear whether or not we need to upload a minidriver?

2) Do we need to pull SPI2_CS_N to VDD and pull UART_CTS to GND while resetting to enter recovery mode and only then upload firmware?

3) Why Wiced Studio while downloading new firmware sends reset command twice?

4) What is the purpose of "01 4D FC 05 1C D2 00 00 01" command right after the first reset command?

5) Is there some document which describes firmware update sequence, required commands order and timings?

6) Which tools (hardware or software) we can use to debug module at the startup?

0 Likes
1 Solution
Owen_Zhang123
Moderator
Moderator
Moderator
500 solutions authored 250 sign-ins 1000 replies posted

The minidriver is needed during the download. The recovery procedure is also recommended.

Could you download the module programmer to program the device: WICED Module Programmer User Guide – KBA225060

Druing the programming, choose "edit->preferences->set application to log" to everything. Then you will see all the HCI command and reply during the programming. You can refer to the command and send the same command with your MCU for the programming.

View solution in original post

4 Replies
Owen_Zhang123
Moderator
Moderator
Moderator
500 solutions authored 250 sign-ins 1000 replies posted

The minidriver is needed during the download. The recovery procedure is also recommended.

Could you download the module programmer to program the device: WICED Module Programmer User Guide – KBA225060

Druing the programming, choose "edit->preferences->set application to log" to everything. Then you will see all the HCI command and reply during the programming. You can refer to the command and send the same command with your MCU for the programming.

Hi OwenZ_26,

Thanks for the tip. We are using similar approach. We were able to catch all the data using logic analyzer.

So now we could compare data packets more detailed.

I think this is the way to get it work.

0 Likes
SheetalJ
Moderator
Moderator
Moderator
750 replies posted 500 likes received 500 replies posted

Hi ViBi_4484621​,

Following are my answers to your queries-

1. Yes you need to use download minidriver command - Programming SPI Flash in CB-343026-01 Module

2. Yes you need to recover the device by following procedure given in WICED Module Programmer User Guide – KBA225060  and then program it.

3. Where did you notice this? Please provide more details.

4. This is the READ-RAM command; I do not see any instruction to use this command after reset in WICED HCI UART control protocol pdf.

5. You can refer /20706-A2_Bluetooth/doc/WICED-HCI-Control-Protocol.pdf. Also, check 7.Software chapter in https://www.cypress.com/file/468621/download

6. You can use BTSpy in WICED Studio to check the commands or packets.

Hi  Sheetalj_96,

Thanks for detailed answers.

1) Yes, now I can confirm that minidriver is a must. By the way it is uploaded even when we use recovery procedure and ChipLoad.exe app with -NODLMINIDRIVER flag. But in this case there is no special command (01 2E FC 00).

2) We would like rather avoid using recovery as SPI2_CS_N pin is not currently available (but agree that it should be present) and it should be possible to not use this pin as WICED is able to upload new firmware without it.

3 and 4) Attached logic analyzer catch with proofs We've duplicated this flow just in case.

LogicCatch.png

5) We're already using the first document, second link was helpful.

6) Thanks we'll give it a try.

We need some time to check all options.

0 Likes