Thank you SheetalJ_96 for you response.
I solved my problem. The problem was that two USB ports have been mapped into my Windows system. COM8 and COM9. I tried always COM8 cause I thought programming goes through lower COM port number. But this isn't true, it goes trough higher COM port number 9.
With COM9 it works as expected. Finally it says:
Chip reset to address 0x00000000 succeeded
Downloaded 0 code bytes ( 0.0%) and 110570 data bytes (100.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Current state: Completed successfully
A total of 2 contiguous memory areas were filled:
[FF000000..FF000080] DATA (129 bytes)
[FF004000..FF01EF68] DATA (110441 bytes)
Total execution time: 16.09 seconds Net downloading time: 16.09 seconds
But SheetalJ_96 as you can see in the log file it says
Downloaded 0 code bytes ( 0.0%) and 110570 data bytes (100.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).
Why it does say 0 code bytes? So am I right that no firmware code was programmed? Or am I wrong?
You are right.
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"
# hci1: Type: Primary Bus: UART
BD Address: F9:9C:84:17:1C:B1 ACL MTU: 1021:6 SCO MTU: 64:1
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?
Hello SheetalJ_96 I still have no success getting hci interface of EVAL board running with Linux. Please read my previous post.
In another thread I read about a "patch" that is needed to have full HCI access. Where I can find this patch?