- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello
We tried to work with the device CYBT-343026 in HCI mode.
For short period it was working and now we can’t receive any feedback.
We tried to do the hard reset with no success.
We tried to communicate using UART communication which the hex code:
01 03 0c 00.
We tried to rewrite the FW using the Bootloader Host, but we received communication error
When trying to flash the image firmware although the port is connected with baud rate of 115,200
(Screen shot attached)
Solved! Go to Solution.
- Labels:
-
BTWi-Fi Bridging
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok guys thanks for the help
It’s look like the chip was gone
We replaced it and disabled the flow control, now it’s works thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi I tried to work with the issue as it describe in the link.
This time I tried to load an hcd file from:
Documents/WICED-Studio-6.4/20706-A2_Bluetooth/build/hci_audio_remote_control-CYW920706WCDEVAL-rom-ram-Wiced-release/hci_audio_remote_control-CYW920706WCDEVAL-rom-ram-Wiced-release.hcd
Used the WICED Client Control but it’s failed again.
Screen information attached
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There are two HCI mode for the device:
1. standard HCI mode which can accept the HCI command defined in the spec
2. WICED HCI mode which can accept the wiced-defined HCI command. You can refer to the document "WICED-HCI-Control-Protocol.pdf" under the doc folder for details.
If you want to use the standard HCI command:
1. Please download and program the application in the attachment of the blog.Run CYW20706 in HCI Mode
2. Pull CTS to high during the power on reset
3. Use the HCI baudrate defined in the application which is 115200.
Then the device will receive all the HCI command defined in the bluetooth spec.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can’t download anything .
Did you see the attachment ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you try again? The crucial part is the steps in bringing the board into HCI mode.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1. I set the CTS to high
2. All the switches set to the direction of the USB connector (For uSB power)
3. I connected the Rx To Tx PC
4. I connected the Tx To Rx PC
5. I connected the ground to ground PC
6. I connected the USB to PC for power.
It’s supposed to start in HCI mode (Because of the CTS high as describe)
I forgot something ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am using the 343026 EVAL board and so I don't have to do the above.
For the 343026 module, the Recover button actually sets SPI2_MOSI (Pin 9 of the module) to ground for the recovery process.
Can you do the below?
1) Set Pin 9 to ground and hold
2) Reset
3) Release Pin 9 after 1s
4) Do the download again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you talking about pin 9 near J7 same problem
I connected Pin 9 to ground and reset the power by unplugging and plugging back the USB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was referring to Pad 9 (SPI2_MOSI) of the physical module (CYBT-343026). This pad has to be brought to GND before resetting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As I saw in the scheme it’s the I2C_SDA (E8)
No change
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok guys thanks for the help
It’s look like the chip was gone
We replaced it and disabled the flow control, now it’s works thanks!