- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I successfully programmed my EVAL board CYBT_333047-02 with "ezserial_343026-CYBT_343026_EVAL-rom-ram-Wiced-release.hex",
I checked the code is running using my iPhone and turned bluetooth scanning "on". Immediately the iPhone found a bluetooth device "EZ-Serial 17:1C:B1_BT". So the WICED code is running.
Now I wanted to make use of the HCI commands on the USB side on my Linux Raspberry Pi. When I plugin the EVAL board USB cable into my Raspberry Pi two interfaces are added (similar to Windows COM8 and COM9) called /dev/ttyACM0 and /dev/ttyACM1.
As usual for Linux I was using the "hciattach" Linux command to attach the Bluez Linux socket to the HCI interface of the EVAL board.
# hciattach -s 115200 /dev/ttyACM0 any 115200 noflow nosleep
# device setup complete
So this works. Then I looked to the hci devices attached using the command "hciconfig"
# hciconfig
# hci1: Type: Primary Bus: UART
BD Address: F9:9C:84:17:1C:B1 ACL MTU: 1021:6 SCO MTU: 64:1
DOWN
RX bytes:113 acl:0 sco:0 events:9 errors:0
TX bytes:40 acl:0 sco:0 commands:10 errors:0
You see Linux bluetooth stack has attached to the F9:9C:84:17:1C:B1 device which is the EZ-serial device. And also you see there is a bidirectional communication running over /dev/ttyACM0 based on the RX/TX bytes counted. So this seems to work fine also.
Now usual in Linux is to bring up a HCI device into "UP" state using "hciconfig hci1 up" command
# hciconfig hci1 up
# Can't init device hci1: Device or resource busy (16)
But as you can see Linux is giving back an error. Do you have idea why this happens?
I read on the forum that a patch is needed to support the full range of HCI commands. Is this true? Where to I get this patch from?
Thank you
Armin
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The CYBT-333047 is a CYW20706 based module. It is shipped with EZ-Serial FW.
I just tested on the 333047 kit board with cybluetool. If the device is in recover mode, it only receives the HCI reset command.
You need to pull the CTS to high then it can receive all the standard HCI command. So please pull CTS to high in step 4. You can double check it on your own kit board.