Wi-Fi Combo Forum Discussions

  I want to write some user information in the OTP memory at manufacturing. There are about 40 bytes is not used in our 43362's OTP memory. I want to use 32 bytes to save some user information. From page 18 in the "OTP Programming Procedure", the CIS format is <80> <length> <tag> <value>. So I want to add a tag to save this 32 bytes: 80 32 <tag> <32 bytes data>. Can you tell me which tag I can use?

  Another question: I can use IOCTL "cisdump" to dump the OTP by the manufacture firmware, but this command is unsupported in the normal firmware. Can you help to add a command to dump the OTP in the normal firmware?

Thanks!

Hi,

I am very new to Wiced development and just now installed wiced SDK. However I am getting this below error and could not let me build target described in quick start guide section 4. Can anyone please guide me through this?

**** Build of configuration Default for project WICED-SDK-2.4.1 ****

make snip.scan-BCM943362WCD4-debug download run

wiced_toolchain_common.mk:187: *** incorrect 'make' used (/Applications/Xcode.app/Contents/Developer/usr/bin/make) - please use:  (Windows) .\make.exe <target_string>    (OS X, Linux) ./make <target_string>.  Stop.

Thanks,

Best Regards,

Dipen Patel

Dear,

        I am testing the OTA Update using the program of snip.ota_fr in WICED SDK v2.4.1.

         The comments in this ota_fr.c told me that the first step is running this command as follow:

          snip.ota_fr-BCM943362WCD4  OTA=waf.ota_upgrade  SFLASH=app-dct-ota-download

        The platform  I used is BCM9WCDUSI09, so I changed the command as:

         snip.ota_fr-BCM9WCDUSI09  OTA=waf.ota_upgrade  SFLASH=app-dct-ota-download

         But it failed. Is  the RAM too small?

         The Log is in the attachment.

          Could anyone help me to find the problem? Thanks.

          BTW, the SPI Flash in my board is 4MByte.

According to the Platform pin map in platform.h for the BCM943362WCD4, WICED_GPIO_2 or MICRO_ADC_IN1 only has GPIO and TIM2_CH2 and TIM5_CH2 alternate functions. However the input calls it ADC. Can it actually be confirgured as an ADC pin ?

I saw that HomeKit is now available for WICED. Will there be a new release supporting this? or it is a standalone addition?

Hello,

I have a issue with the ca certificate verification on the WICED SDK 3.0.1 and 2.4.0 (both FreeRTOS + LwIP).

I have a server at HomeManager and I have the following CA certificate:

"-----BEGIN CERTIFICATE-----\n"\

  "MIIDIDCCAomgAwIBAgIENd70zzANBgkqhkiG9w0BAQUFADBOMQswCQYDVQQGEwJVUzEQMA4GA1UE\n"\

  "ChMHRXF1aWZheDEtMCsGA1UECxMkRXF1aWZheCBTZWN1cmUgQ2VydGlmaWNhdGUgQXV0aG9yaXR5\n"\

  "MB4XDTk4MDgyMjE2NDE1MVoXDTE4MDgyMjE2NDE1MVowTjELMAkGA1UEBhMCVVMxEDAOBgNVBAoT\n"\

  "B0VxdWlmYXgxLTArBgNVBAsTJEVxdWlmYXggU2VjdXJlIENlcnRpZmljYXRlIEF1dGhvcml0eTCB\n"\

  "nzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAwV2xWGcIYu6gmi0fCG2RFGiYCh7+2gRvE4RiIcPR\n"\

  "fM6fBeC4AfBONOziipUEZKzxa1NfBbPLZ4C/QgKO/t0BCezhABRP/PvwDN1Dulsr4R+AcJkVV5MW\n"\

  "8Q+XarfCaCMczE1ZMKxRHjuvK9buY0V7xdlfUNLjUA86iOe/FP3gx7kCAwEAAaOCAQkwggEFMHAG\n"\

  "A1UdHwRpMGcwZaBjoGGkXzBdMQswCQYDVQQGEwJVUzEQMA4GA1UEChMHRXF1aWZheDEtMCsGA1UE\n"\

  "CxMkRXF1aWZheCBTZWN1cmUgQ2VydGlmaWNhdGUgQXV0aG9yaXR5MQ0wCwYDVQQDEwRDUkwxMBoG\n"\

  "A1UdEAQTMBGBDzIwMTgwODIyMTY0MTUxWjALBgNVHQ8EBAMCAQYwHwYDVR0jBBgwFoAUSOZo+SvS\n"\

  "spXXR9gjIBBPM5iQn9QwHQYDVR0OBBYEFEjmaPkr0rKV10fYIyAQTzOYkJ/UMAwGA1UdEwQFMAMB\n"\

  "Af8wGgYJKoZIhvZ9B0EABA0wCxsFVjMuMGMDAgbAMA0GCSqGSIb3DQEBBQUAA4GBAFjOKer89961\n"\

  "zgK5F7WF0bnj4JXMJTENAKaSbn+2kmOeUJXRmm/kEd5jhW6Y7qj/WsjTVbJmcVfewCHrPSqnI0kB\n"\

  "BIZCe/zuf6IWUrVnZ9NA2zsmWLIodz2uFHdh1voqZiegDfqnc1zqcPGUIWVEX/r87yloqaKHee95\n"\

  "70+sB3c4\n"\

  "-----END CERTIFICATE-----\n";

On the WICED SDK 2.4.0 when I try to connect and verify the server's certificate the chip goes to hardware fault. I have managed to track the error to the file wiced_tls.c in function wiced_tcp_start_tls. When the board enters the do { ... } while(...) loop, it calls the function ssl_handshake_client_async 3 times and the tls_context->context.state goes from 1 to 2 and 3. After 3 it goes to hardware fault.

On the WICED SDK 3.0.1 when I try to connect I get an error (no hardware fault) but still it doesn't want to connect. The SSL certificate on that server is a wildcard, so it is issued for *.homemanager.tv. I have tried the following wiced_https_get commands and got the following errors:

result = wiced_https_get( &ip_address, SIMPLE_GET_REQUEST, buffer, BUFFER_LENGTH, "www.*.homemanager.tv" ); -> error 2

result = wiced_https_get( &ip_address, SIMPLE_GET_REQUEST, buffer, BUFFER_LENGTH, "*.homemanager.tv" ); -> error 65024

result = wiced_https_get( &ip_address, SIMPLE_GET_REQUEST, buffer, BUFFER_LENGTH, "www.homemanager.tv" ); -> error 2

result = wiced_https_get( &ip_address, SIMPLE_GET_REQUEST, buffer, BUFFER_LENGTH, "homemanager.tv" );-> error 65024

The certificate should be ok. It works fine under Linux where I call the SSL_get_verify_result from OpenSSL. I assume that the board has to do more or less the same thing as that OpenSSL function.

Any suggestions? I would prefer a fix for the 2.4.0 version because the end product is based on the USI09 chip.