Wi-Fi Combo Forum Discussions
The version of SDK is 3.1.2
To test the https_server i need to modify the CLIENT_AP_SSID/CLIENT_AP_PASSPHRASE Wi-Fi credentials in the wifi_config_dct.h header file, but there is no this header file under the https_server folder.
Quesitions:
1. I want to think which wifi_config_dct.h header file is used for the project of https_server.
2. And there are several projects such as tcp_client, tcp_server and so on. there are no this header file under each folder too. Are they treated as the same way.
3. If i want to add the wifi_config_dct.h header file to each project, what should i do?
Looking forward to your reply!
Thank you!
All the best wiches for you !
Show Less
I wonder if it's possible that there was a bug introduced in 3.5.2 that caused wiced_framework_set_boot() to fail.
We have developed our own OTA system, and in 3.5.2 the following returns WICED_ERROR:
result = wiced_framework_set_boot( DCT_APP0_INDEX, WICED_FRAMEWORK_LOAD_ONCE );
I traced this down finally to some code in wiced_waf_common.c that I believe is now erroneous considering the changes to the way wiced_dct_write() has been modified under 3.5.2. The existing code looks like this:
wiced_result_t wiced_waf_app_set_boot(uint8_t app_id, char load_once)
{
boot_detail_t boot;
boot.entry_point = 0;
boot.load_details.load_once = load_once;
boot.load_details.valid = 1;
boot.load_details.destination.id = INTERNAL;
if ( wiced_dct_get_app_header_location( app_id, &boot.load_details.source ) != WICED_SUCCESS )
{
return WICED_ERROR;
}
if ( wiced_dct_write( &boot, DCT_INTERNAL_SECTION, OFFSETOF( platform_dct_header_t, boot_detail ), sizeof(boot_detail_t) ) != WICED_SUCCESS )
{
return WICED_ERROR;
}
return WICED_SUCCESS;
}
I noted that a new function was introduced in 3.5.2 to do the job of setting boot parameters. I modified the above code to look like the following:
wiced_result_t wiced_waf_app_set_boot(uint8_t app_id, char load_once)
{
boot_detail_t boot;
boot.entry_point = 0;
boot.load_details.load_once = load_once;
boot.load_details.valid = 1;
boot.load_details.destination.id = INTERNAL;
if ( wiced_dct_get_app_header_location( app_id, &boot.load_details.source ) != WICED_SUCCESS )
{
return WICED_ERROR;
}
return wiced_dct_write_boot_details ( &boot );
}
I'd just like to confirm that what I've done is correct, and that there is indeed a bug. Or, if I am missing something, please let me know.
Show LessWe use a bcm43570 ( wifi/bt ) chipset for our solution.
Does this device have internal power management for wlan ?
Is there an android tool to validate this feature if any ?
Show LessPlease share BCM43242 Windows driver (from AARDVARK-6.37.114.20-Win-MFGTools) mentioned in documentation (https://www.google.com.ua/search?num=100&safe=off&q=bcm43242+windows+driver&oq=bcm43242+windows+driver&gs_l=serp.3...594… )
Show LessI have tow BCM943341WCD1 board, run with bt_dualmode_server example on wiced idk 3.7.0, one is the server, and the other be a client. I use wiced_bt_dev_sec_bond(p_inq->remote_bd_addr, 0, BT_TRANSPORT_BR_EDR, 0, NULL) to initiate bonding to the server, but server returns:
DCT BT NAME: WICED Server407
Local Bluetooth Address: [51:34:20:AA:BB:CC]
WICED DCT BT DEVICE CLASS : 20 04 1c
00:00:00.010000 GKI_create_task func=0x80187e5 id=1 name=BTU stack=0x0 stackSize=6144
00:00:00.019000 GKI_create_task func=0x801efd1 id=0 name=HCISU stack=0x0 stackSize=4096
Bluetooth Management Event: 0x15
Unhandled Bluetooth Management Event: 0x15
Bluetooth Management Event: 0x0
Bluetooth enabled (success)
Local Bluetooth Address: [43:34:1B:00:1F:AC]
WICED DCT BT ADDR 0x51:0x34:0x20:0xaa:0xbb:0xcc
rfcomm create_connection result:0
Waiting for RFCOMM connection (scn=1)...
Bluetooth Management Event: 0x14
Unhandled Bluetooth Management Event: 0x14
Bluetooth Management Event: 0x14
Unhandled Bluetooth Management Event: 0x14
Bluetooth Management Event: 0x9
IO_CAPABILITIES_BR_EDR_RESPONSE_EVT auth, 3 io cap1 oob0
Bluetooth Management Event: 0x8
BTM_PAIRING_IO_CAPABILITIES_BR_EDR_REQUEST_EVT 3 io cap1 oob0
Bluetooth Management Event: 0xb
BTM_PAIRING_COMPLETE_EVT: failed! status 5 bonding_status0
Bluetooth Management Event: 0xb
BTM_PAIRING_COMPLETE_EVT: failed! status 5 bonding_status8192
==================================================================================
DCT BT NAME: WICED client
WICED DCT BT DEVICE CLASS : 20 04 1c
00:00:00.006000 GKI_create_task func=0x8018665 id=1 name=BTU stack=0x0 stackSize=6144
00:00:00.014000 GKI_create_task func=0x801eea1 id=0 name=HCISU stack=0x0 stackSize=4096
Bluetooth Management Event: 0x15
Unhandled Bluetooth Management Event: 0x15
Bluetooth Management Event: 0x0
Bluetooth enabled (success)
Local Bluetooth Address: [43:34:1B:00:1F:AC]
WICED DCT BT ADDR 0x21:0x34:0x20:0xaa:0xbb:0xcc
Bluetooth Management Event: 0x14
Unhandled Bluetooth Management Event: 0x14
Bluetooth Management Event: 0x14
Unhandled Bluetooth Management Event: 0x14
Bluetooth Address: [CC:BB:AA:20:34:51] device class: 0x20041c
wiced_bt_dev_sec_bond rst 1
uuid0 80004d5
Bluetooth Address: [01:20:B5:05:00:08] device class: 0xd50400
Bluetooth Management Event: 0x8
BTM_PAIRING_IO_CAPABILITIES_BR_EDR_REQUEST_EVT 3 io cap1 oob0
I'm the Initiator!
Bluetooth Management Event: 0xb
BTM_PAIRING_COMPLETE_EVT: failed! status 5 bonding_status0
Bluetooth Management Event: 0xb
BTM_PAIRING_COMPLETE_EVT: failed! status 5 bonding_status8192
Show LessIf WICED_COUNTRY_WORLD_WIDE_XX is configured and the module joins a existing Access Point (e.g. FritzBox7490) it connects using 802.11g only. A connection to a 802.11n-only AP can not be established.
If a different country code is configured (e.g. WICED_COUNTRY_UNITED_STATES or WICED_COUNTRY_GERMANY) the module connects using 802.11n.
This happens both with our own ported version of WWD and with the SDK 3.1.2 test.console application.
Does anyone have an explanation for the behaviour?
Show Lesswiced_dct_read_wifi_config_section() read from DCT_WIFI_CONFIG_SECTION,
but wiced_dct_write_wifi_config_section() write to DCT_SECURITY_SECTION.
I believe current code is simply wrong.
I found a very old thread about this bug report.
https://community.cypress.com/message/17842#17842
I'm surprised it's still not fixed in latest SDK.
Show LessHi,
I'm using SDK 3.7.0 with the Avenet BCM94343W module. Does anyone know how to set the BLE connection parameters such as the slave latency and connection interval?
Thanks,
-Rob
Show LessWe are trying to develop a IoT device using the BCM 43362 device.
Is there a process that will make a BCM43362 device( SDK2.3) NOT default to a 802.11N fomat when connecting to a WAP... but rather at 802.11B or G format?
Range and connectivity, are more important than data speed.
Thank you
dave w
Show Less