Wi-Fi Combo Forum Discussions
I am trying to connect Murata SN8000 to STM32F4 Discovery kit through SDIO bus. Everything works fine (reading/writing broadcom chip's registers, downloading firmware) until start of communication through SDPCM protocol - wiced_send_iovar() (SDPCM.c) timeouts on wiced_ioctl_sleep semaphore. Wiced thread is running. Here is console dump of snip.udp_transmit-SN8000x-SDIO (all prints enabled):
Starting Wiced v2.4.1
Platform SN8000x initialised
Star▒Starting Wiced v2.4.1
Platform SN8000x initialised
Started FreeRTOS v7.1.0
Initialising LwIP
Wcd:> Sending pkt 0x20004B44
Could not turn on APSTA
Could not set AMPDU parameters
Error 2 while starting WICED!
WWD SDIO interface initialised
WLAN MAC Address : 02:00:00:00:00:00
WLAN Firmware :
It prints the same with ThreadX, so I assume it isn't OS issue. Raw SDIO works, everything works also fine with SPI bus, so it isn't probably hardware issue.
Murata SN8000 module's GPIO0, GPIO1, RST_N, VDD_3V3_EN pins are connected to STM32F4 Discovery kit. SLEEP_CLK is driven by PWM.
I am using Wiced SDK 2.4.1 almost untouched (I modified makefile commands running OpenOCD to connect to st-link)
Show Less
I have posted this issue on the Broadcom CSP site a while ago but haven't got it resolved. I want to see if any of you have tried it and how it goes for you.
I tested snip.p2p with Wiced-SDk-2.4.0 with my smart phone(Andriod) and a Nexus Pad, but the application failed in mid of WPS procedure.
my phone - Android version 4.1.2.
Nexus pad- Android version 4.3
And the console output:
Platform SN8200x initialised
Started ThreadX v5.5
Initialising NetX v5.6
Creating Packet pools
Starting Wiced v2.4.0
WWD SDIO interface initialised
WLAN MAC Address : 00:0B:6C:41:6E:C1
STA MAC: 02:0B:6C:41:6E:C1
P2P discovery enabled. Advertised as 'WICED-P2P'
Found P2P device: Android_85e9
P2P negotiation complete...
Starting WPS Enrollee
Joining 'DIRECT-Vu-Android_85e9'
Sending Identity
Sending Identity
Sending nonce
Sending hashes
WPS Procedure failed. Restarting with 113 seconds left
Joining 'DIRECT-Vu-Android_85e9'
Looking for WPS AP
WPS timed out
WPS complete
Show LessDear Madam/Sir?
As we know, BCM43362 now can be used with Cortex-M4 + FreeRTOS/LwIP architecutre, My situation is not M4, but other micro-controller.
I didn't use FreeRTOS, but I can migrate LwIP onto my platform, technically I think, BCM43362 should only relay on LwIP, not FreeRTOS or M4, am I right? If yes, Can I use BCM43362 with my special micro-controller on which LwIP is ready?
Kerr
Show LessDoes anyone test the BCM43362 WIFI-direct data throughput?
I'm using the BCM4343WWCD_EVB with WICKED SDK 3.5.2 and when I enable the bluetooth stack the power consumption doesn't drop below 9mA. Calling wiced_platform_mcu_enable_powersave doesn't have any effect. Is there a way to reduce the power consumption? I'm going to be running this device off of batteries and 9mA is very high.
Thanks,
-Rob
Show LessI have a function that's interacting with a serial NOR flash chip over SPI. But every time it executes, it seems like it's terminated early after a second or so. I noticed this because it would be printing out messages, and then all of a sudden stop and the messages from the next function starts to print. I don't even know where to begin troubleshooting this. Is there a length limit on how long a function would run? I'm using ThreadX by default and not using any thread management functions yet. I also noticed that the problem went away when I put the device under GDB. It seems like having breakpoints in the middle of the function forces it to run till completion. Any ideas why?
Show LessHi,
I am trying to add MQTT to a project. I am using Wiced 4.1.1 and an LSR Sterling 00950. I am trying to run the snip.secure_mqtt as an example. Running the example using the preconfigured test using mosquito works. The snip subscribes to the topic, publishes a message, and receives the message back. When switching to our broker an error is thrown when a publish is attempted. By commenting out the publish attempt I was able to subscribe to a topic and receive messages on that topic, so I know that I am in fact connecting to the broker and receiving messages from the broker. Knowing that publishing is the problem, I began to try to debug. I have determined the error happens in mqqtt_wait_for(). There is a check to see if event matches expected event. The event is WICED_MQTT_EVENT_TYPE_PUBLISHED but for some reason the expected event is WICED_MQTT_EVENT_TYPE_DISCONNECTED. I believe the error is deeper in the code but I can't determine what is causing the disconnect because the expected event is being set in mqtt_connection_event_cb() and wiced_mqtt_publish() is returning success. I haven't been able to isolate what is causing the disconnection and triggering the callback.
Show LessHi guys,
I need your help.
There has been a discussion as to putting web content onto external flash:
Keep web content (.html, .js) on external flash in a filesystem
What this solution does is it builds filesystem.bin (with all the content in resources folder) and writes that onto external flash at address 0 (sector 0).
In my case I would like to have WAF on external flash that will have FR_APP, FR_DCT, FILESYSTEM_IMAGE, WIFI_FIRMWARE and APP0.
Basically, I now need to place:
filesystem.bin -> FILESYSTEM_IMAGE
a copy of main app -> FR_APP,
a copy of DCT -> FR_DCT,
wifi driver -> WIFI_FIRMWARE,
Please help. Any ideas, examples?
Best wishes,
Oleg
Show LessIs is possible to download the minidriver (patchram) in H5 mode?
After setting up an H5 Link, I'm sending HCI Reset, HCI Read Local Version Information, HCI Read Local Name.
Then, I send the Download Mini Driver Command (FC2E) with H5 Seq nr. 3. Next, I get the HCI Command Complete with H5 Ack nr. 3.
This means, it received and processed the Download Mini Driver Command, without confirming on H5 that it received it???
Then, I get a weird packet with seq 0, ack 0 that has packet type HCI event, but isn't a valid HCI Event:
0x75, 0xD8, 0x21, 0x00, 0x02, 0x00,
Independent of the unexpected seq nr, this packet should have a length of 2 + 0xD8 bytes. Also, there is no official HCI Events with an opcode of 0x75.
350 ms later, we get an H5 Ack packet for the Download Mini Driver Command.
I've read that ".. this command triggers the device to reboot into a state where it is prepared to receive a download of a minidriver." Does this confuse the H5 state?
Is it possible to first upload the mini driver and then switch to H5 since we really need H5 mode?
Thanks for any hints!
Matthias
A bit lof log:
[Apr 24 13:59:16.119] [HCI COMMAND] [FC2E] VSC - Download Mini Driver
[Apr 24 13:59:16.119] [NOTE] hci_transport_h5.c.357: hci_transport_link_send_queued_packet: seq 3, ack 3, size 3. Append dic 1, dic = 0x5265
[Apr 24 13:59:16.119] [NOTE] btstack_util.c.225: 0x2E, 0xFC, 0x00,
[Apr 24 13:59:16.119] [NOTE] hci_transport_h5.c.240: slip: send 12 bytes
[Apr 24 13:59:16.135] [NOTE] hci_transport_h5.c.531: process_frame, reliable 1, packet type 4, seq_nr 3, ack_nr 3 , dic 1
[Apr 24 13:59:16.135] [NOTE] btstack_util.c.225: 0xDB, 0x64, 0x00, 0xC0,
[Apr 24 13:59:16.135] [NOTE] btstack_util.c.225: 0x0E, 0x04, 0x01, 0x2E, 0xFC, 0x00,
[Apr 24 13:59:16.135] [NOTE] btstack_util.c.225: 0xBC, 0x80,
[Apr 24 13:59:16.135] [HCI EVENT] Command Complete [FC2E] - Download Mini Driver
[Apr 24 13:59:16.135] [NOTE] hci.c.1298: Command complete for expected opcode fc2e at substate 9
[Apr 24 13:59:16.135] [NOTE] hci_transport_h5.c.368: send ack 4
[Apr 24 13:59:16.135] [NOTE] btstack_util.c.225: 0x20, 0x00, 0x00, 0xDF,
[Apr 24 13:59:16.135] [NOTE] hci_transport_h5.c.240: slip: send 6 bytes
[Apr 24 13:59:16.151] [NOTE] hci_transport_h5.c.531: process_frame, reliable 1, packet type 4, seq_nr 0, ack_nr 0 , dic 1
[Apr 24 13:59:16.151] [NOTE] btstack_util.c.225: 0xC0, 0x64, 0x00, 0xDB,
[Apr 24 13:59:16.151] [NOTE] btstack_util.c.225: 0x75, 0xD8, 0x21, 0x00, 0x02, 0x00,
[Apr 24 13:59:16.151] [NOTE] btstack_util.c.225: 0x34, 0xE8,
Show LessHi,
is it possible to get some example for sending packets in so called raw mode? In the SDK, there are examples only for AP/STA modes. Something similar to for example CC3000 Transmitter Testing Using RAW Socket - Texas Instruments Wiki or at least some pointers how to achieve it for a start. Thanks!
Show Less