About the return code "3004" (PBC OVERLAP) of "wiced_wps_enrollee()".

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
KAYA_4808816
Level 1
Level 1
5 replies posted 5 sign-ins First reply posted

When I perform WPS with the library "wiced_wps_enrollee ()" of WICED-Studio-5.0, the code "3004" (PBC OVERLAP) is returned and WPS fails.
It occurs only when the wireless router (Buffalo: WTR M2133HP) is opposed to the confirmed range.
Could you please tell me the cause or possibility of this event?

 

// In Japanese.

WICED-Studio-5.0のライブラリ"wiced_wps_enrollee()"でWPSを行った際、"3004"(PBC OVERLAP)というコードが返ってきてWPSが失敗します。
確認出来た範囲で、無線ルータ(Buffalo製:WTR M2133HP)対向の場合のみ発生します。
本事象の発生原因或いは、可能性を教えて頂けませんか?

0 Likes
1 Solution
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

Yea, WinUSB will work as it's a generic USB driver provided by Microsoft. For your API related query, do you need this specific API in your application?

Thanks

Aditi

View solution in original post

0 Likes
8 Replies
KAYA_4808816
Level 1
Level 1
5 replies posted 5 sign-ins First reply posted

Hi, Aditi-san.

Thank you for your comment.
I'm sorry, we don't have an environment to run WICED_6.6, so it's difficult to check with WICED_6.6.
Is it possible that WICED_6.6 will resolve this issue?
Is there a difference in WPS functionality between WICED_5.0 and WICED_6.6?

Best regards.

 

0 Likes
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

The latest versions of WICED usually comes with some fixes to the problems that we might face in the older versions. So, it's usually good to check your use case in 6.6 as WICED 5.0 is pretty old version. Also, it might help us to isolate the issue.

Thanks

Aditi

0 Likes

Hi,

Sorry for late response.

I'm currently trying to upgrade to the latest version.

However, the following error occurs and the download cannot be performed.

Do you know where the problem is?

===

Creating Filesystem BCM94390x_targets.mk ...
Downloading DCT ... build/fg_apt-BCM943907WCD2/DCT.bin @ SFLASH_DCT_LOC=0x00008000 
./tools/common/Win32/mk_wicedfs32 build/fg_apt-BCM943907WCD2/filesystem.bin build/fg_apt-BCM943907WCD2/resources/Staging/
Creating Filesystem Done
WICED/platform/MCU/BCM4390x/BCM94390x_targets.mk:395: recipe for target 'download_dct' failed
make.exe[1]: *** [download_dct] Error 1
Makefile:351: recipe for target 'main_app' failed
make: *** [main_app] Error 2

===

Best regards.

0 Likes
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

Can you provide your make target that you're using for the build?

Thanks

Aditi

0 Likes
lock attach
Attachments are accessible only for community members.

Thank you for your cooperation.

I'll send you the "BCM94390x_target.mk" I'm using.

Best regards.

0 Likes

Hi,

Additional information.

There was evidence of an error in openocd_log.

Do you know how to avoid the error?

(This error does not occur in WICED 5.0.)

<\WICED-Studio-6.6\43xxx_Wi-Fi\build\openocd_log.txt>

Licensed under GNU GPL v2
For bug reports, read
 http://openocd.org/doc/doxygen/bugs.html
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
trst_and_srst separate srst_nogate trst_push_pull srst_open_drain connect_assert_srst
adapter speed: 100 kHz
adapter_nsrst_delay: 100
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
jtag_ntrst_delay: 100
post_init_psoc6_setup
Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
Error: no device found
Error: unable to open ftdi device with vid 15ba, pid 002a, description 'Olimex OpenOCD JTAG ARM-USB-TINY-H', serial '*' at bus location '*'

----------

Best Regards.

0 Likes

Hi,

After replacing the OLIMEX-ARM-USB-TINY-H driver with WinUSB(by zadig), I was able to download it.

Is this corrective?

And I have another question.

I think some APIs have been removed between WICED 5.0 ​​and WICED 6.6. (For example, "wiced_pwm_set_duty_cycle ()")

Is there a way to think of these alternatives?

Best regards.

0 Likes
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

Yea, WinUSB will work as it's a generic USB driver provided by Microsoft. For your API related query, do you need this specific API in your application?

Thanks

Aditi

0 Likes