Wi-Fi Combo Forum Discussions
Dear Sir:
Is it possible using POST method to handle upload file request in WICED SDK? And how?
// getenv("CONTENT_LENGTH") seems return NULL.
Show LessHi,
We are running Linux Kernel 3.14 with BCM43362 (sn8000 from Murata) and the Linux driver in an AM335x from Texas.
MMC in the kernel is corretly initialized in the Device Tree.
When the driver module is inserted into the kernel and the SDIO is activated, we see the errors below (bold)
Any idea of what could be happening?
Rgds.
.....
[ 1.591591] mmc0: new high speed SDIO card at address 0001
....
[ 28.030980] omap_hsmmc 48060000.mmc: enabled
[ 28.031026] mmc0: starting CMD52 arg 80022040 flags 00000195
[ 28.031107] mmc0: req done (CMD52): 0: 00001040 00000000 00000000
00000000
[ 28.031179] mmc0: starting CMD52 arg 80022200 flags 00000195
[ 28.031231] mmc0: req done (CMD52): 0: 00001000 00000000 00000000
00000000
[ 28.031420] mmc0: starting CMD52 arg 80042000 flags 00000195
[ 28.031474] mmc0: req done (CMD52): 0: 00001000 00000000 00000000
00000000
[ 28.031575] mmc0: starting CMD52 arg 80042202 flags 00000195
[ 28.031627] mmc0: req done (CMD52): 0: 00001002 00000000 00000000
00000000
[ 28.031666] mmc0: starting CMD52 arg 80022040 flags 00000195
[ 28.031717] mmc0: req done (CMD52): 0: 00001040 00000000 00000000
00000000
[ 28.031741] mmc0: starting CMD52 arg 80022200 flags 00000195
[ 28.031790] mmc0: req done (CMD52): 0: 00001000 00000000 00000000
00000000
[ 28.031814] mmc0: starting CMD52 arg 80042000 flags 00000195
[ 28.031863] mmc0: req done (CMD52): 0: 00001000 00000000 00000000
00000000
[ 28.031918] mmc0: starting CMD52 arg 80042202 flags 00000195
[ 28.031966] mmc0: req done (CMD52): 0: 00001002 00000000 00000000
00000000
[ 28.032016] SDIO: Enabling device mmc0:0001:1...
[ 28.032028] mmc0: starting CMD52 arg 00000400 flags 00000195
[ 28.032076] mmc0: req done (CMD52): 0: 00001000 00000000 00000000
00000000
[ 28.032100] mmc0: starting CMD52 arg 80000402 flags 00000195
[ 28.032148] mmc0: req done (CMD52): 0: 00001002 00000000 00000000
00000000
[ 28.032272] mmc0: starting CMD52 arg 00000600 flags 00000195
[ 28.032324] mmc0: req done (CMD52): 0: 00001002 00000000 00000000
00000000
[ 28.032351] SDIO: Enabled device mmc0:0001:1
[ 28.034037] mmc0: starting CMD52 arg 92001400 flags 00000195
[ 28.034111] mmc0: req done (CMD52): 0: 00001000 00000000 00000000
00000000
[ 28.034157] mmc0: starting CMD52 arg 92001600 flags 00000195
[ 28.034214] mmc0: req done (CMD52): 0: 00001000 00000000 00000000
00000000
[ 28.034240] mmc0: starting CMD52 arg 92001818 flags 00000195
[ 28.034299] mmc0: req done (CMD52): 0: 00001018 00000000 00000000
00000000
[ 28.034342] mmc0: starting CMD53 arg 15000004 flags 000001b5
[ 28.034358] mmc0: blksz 4 blocks 1 flags 00000200 tsac 1000 ms nsac 0
[ 28.034466] mmc0: req done (CMD53): 0: 00001000 00000000 00000000
00000000
[ 28.034478] mmc0: 4 bytes transferred: 0
[ 28.034508] brcmfmac: F1 signature read @0x18000000=0x1591a962
[ 28.034523] mmc0: starting CMD52 arg 92001c28 flags 00000195
[ 28.034574] mmc0: req done (CMD52): 0: 00001028 00000000 00000000
00000000
[ 28.034605] mmc0: starting CMD52 arg 12001c00 flags 00000195
[ 28.034655] mmc0: req done (CMD52): 0: 00001068 00000000 00000000
00000000
[ 28.034687] mmc0: starting CMD52 arg 92001c28 flags 00000195
[ 28.034737] mmc0: req done (CMD52): 0: 00001028 00000000 00000000
00000000
[ 28.034764] mmc0: starting CMD52 arg 12001c00 flags 00000195
[ 28.034813] mmc0: req done (CMD52): 0: 00001068 00000000 00000000
00000000
[ 28.034841] mmc0: starting CMD52 arg 12001c00 flags 00000195
[ 28.034890] mmc0: req done (CMD52): 0: 00001068 00000000 00000000
00000000
[ 28.034918] mmc0: starting CMD52 arg 92001c21 flags 00000195
[ 28.034967] mmc0: req done (CMD52): 0: 00001021 00000000 00000000
00000000
[ 28.035060] mmc0: starting CMD52 arg 92001e00 flags 00000195
[ 28.035109] mmc0: req done (CMD52): 0: 00001000 00000000 00000000
00000000
[ 28.035138] mmc0: starting CMD53 arg 15000004 flags 000001b5
[ 28.035152] mmc0: blksz 4 blocks 1 flags 00000200 tsac 1000 ms nsac 0
[ 28.035243] mmc0: req done (CMD53): -110: 00000000 00000000 00000000
00000000
[ 28.035255] mmc0: 0 bytes transferred: -110
[ 28.035291] brcmfmac: brcmf_sdiod_request_data: failed to read data
F1@0x08000, err: -110
[ 28.045984] mmc0: starting CMD53 arg 15000004 flags 000001b5
[ 28.045999] mmc0: blksz 4 blocks 1 flags 00000200 tsac 1000 ms nsac 0
[ 28.046052] mmc0: req done (CMD53): -110: 00000000 00000000 00000000
00000000
[ 28.046064] mmc0: 0 bytes transferred: -110
[ 28.046087] brcmfmac: brcmf_sdiod_request_data: failed to read data
F1@0x08000, err: -110
[ 28.056743] mmc0: starting CMD53 arg 15000004 flags 000001b5
[ 28.056757] mmc0: blksz 4 blocks 1 flags 00000200 tsac 1000 ms nsac 0
[ 28.056808] mmc0: req done (CMD53): -110: 00000000 00000000 00000000
00000000
[ 28.056820] mmc0: 0 bytes transferred: -110
[ 28.056843] brcmfmac: brcmf_sdiod_request_data: failed to read data
F1@0x08000, err: -110
[ 28.065473] brcmfmac: brcmf_sdiod_regrw_helper: failed with -110
[ 28.071815] brcmfmac: brcmf_sdio_chip_recognition: chip backplane
type 15 is not supported
[ 28.080546] brcmfmac: brcmf_sdio_probe_attach: brcmf_sdio_chip_attach
failed!
[ 28.088077] brcmfmac: brcmf_sdio_probe: brcmf_sdio_probe_attach failed
[ 28.094955] SDIO: Disabling IRQ for mmc0:0001:2...
[ 28.094969] mmc0: starting CMD52 arg 00000800 flags 00000195
[ 28.095007] mmc0: req done (CMD52): -110: 00000000 00000000 00000000
00000000
[ 28.095037] SDIO: Disabling IRQ for mmc0:0001:1...
[ 28.095050] mmc0: starting CMD52 arg 00000800 flags 00000195
[ 28.095083] mmc0: req done (CMD52): -110: 00000000 00000000 00000000
00000000
[ 28.095238] SDIO: Disabling device mmc0:0001:2...
[ 28.095254] mmc0: starting CMD52 arg 00000400 flags 00000195
[ 28.095291] mmc0: req done (CMD52): -110: 00000000 00000000 00000000
00000000
[ 28.095320] SDIO: Failed to disable device mmc0:0001:2
[ 28.095335] SDIO: Disabling device mmc0:0001:1...
[ 28.095346] mmc0: starting CMD52 arg 00000400 flags 00000195
[ 28.095386] mmc0: req done (CMD52): -110: 00000000 00000000 00000000
00000000
[ 28.095409] SDIO: Failed to disable device mmc0:0001:1
[ 28.095424] brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19...
[ 28.187886] omap_hsmmc 48060000.mmc: disabled
Show Less
Hi,
I want to design a WICED module based on WM-N-BM-02 SIP module and need module package information such as
package dimension and pins description. Would you please share the datasheet of the module WM-N-BM-02 ?
Thanks and Best Regards.
Phuong
Show LessHi @ all,
I investigate the SN800 EVB and try to find an Demo without a RTOS. I`ve found the File "NoOS_canned_send.c", looks and sounds like a demo I`m looking for.
How can I build and use it?
Please find my informations below.
Thanks for helping,
Jan Gottwald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I'm working on a Windows Vista PC (32Bit). I`ve installed the WICED SDK 3.0.1 and added the patch for SN8000-Files, but can't find an make target for an non-OS demo. Therefor, I first tried to build the prepared target "snip.scan-BCM943362WCD4 download". That looks fine so far.
For the SN800x I copy & paste the prepared target an renamed it into "snip.scan-SN8000x download". That works for me, the scanner was running an found the local WLAN networks.
Now I needed a non-OS demo and, like the other make targets, I created & tried a new target "wwd.canned_send-SN8000x download". But it dosent works. Console output:
---
tools/makefiles/wiced_config.mk:276: *** canned_send application does not support ThreadX-NetX_Duo combination. Stop.
make: *** No rule to make target 'build/wwd_canned_send-SN8000x/config.mk', needed by 'main_app'. Stop.
---
Show LessCan you provide the maximum throughput for the BCM43362 modules through the UART and SPI interfaces? Does it vary by manufacturer?
Thank you.
Show LessI have called wiced_network_register_link_callback(sta_link_up, sta_link_down);
in my application and add print "Link UP" and "Link Down" in the callbacks.
I just leave my device on the desk and no network traffic for a while,
sometimes I found my console shows "Link UP/Link Down" multiple times like
below:
Link UP
Link Down
Link UP
Link Down
Link UP
Link Down
Link UP
Does that mean the system automatically calls link_up/link_down callbacks when
I actually doing nothing? Is this normal (for BCM4390)?
Thanks.
Show LessHi,
Test with sdk-3.1.0 + FreeRTOS on BCM4390.
Calling wiced_framework_perform_factory_reset(WICED_FACTORY_RESET_MAGIC_VALUE);
then the device hangup and not able to reboot anymore.
I need to re-download the image via jtag to fix it.
Show LessWhat is the maximum data throughput that can be achieved using WICED BCM43362 wifi + application in WICED sdk ? we are planning to use a STM32 M3/M4 interface to BCM43362 via SDIO or SPI.
Regards
Shafy
Show LessThere is this new Raspberry Pi WiFi dongle (with USB), promised as WICED device.
There is statement on online shop site as:
"Additionally, the specification includes support for Broadcom WICED SENSE functionality with an optional Bluetooth 4.1 dongle."
What does it mean?
Please, could the WICED community elaborate if WICED is stated on package - there is WICED inside?
What would be needed to have also BLE and WICED (Smart) running on Raspberry Pi?
Why do I need anything in addition if the WICED logo tells me it is already supported?
(WICED is BLE for me, WICED WiFi is different for me. If I see WICED - I expect to get BLE with it. Or is just WICED Smart = BLE?).
I guess, just WICED WiFi, not WICED Smart (BLE) is ment.
How to upgrade later to WICED SENSE?
What does WICED SENSE mean here? I thought there is a WICED SENSE Kit, for mobile sensors.
a) could such a WICED SENSE Kit, BLE device, be connected to this WICED WiFi dongle (needs BLE as well !)?
b) or even more: can the Raspberry Pi with this WICED dongle act as a mobile WICED SENSE (sensor) device?
c) Which SW, tools will come to Raspberry Pi, e.g. WICED SDK, so that WICED SENSE Apps can be developed with Raspberry Pi?
Thank you for any help to get a clue.
Show Less