Wi-Fi Combo Forum Discussions
Hi
We are trying to implement OTA2 on modified WM-BN-BM-22 module which has STM32F412 microcontroller, 256KB SRAM, 1MB internal flash, 4 MB external QSPI flash. QSPI flash is memory mapped and can be used for code and data. Could you suggest what would be configuration and other changes required and also let us know if any reference platforms in SDK use a similar configuration.
Thanks
Hemanth
Show LessHi Guys,
Similar to this thread: OpenOCD Failed
I am also facing the same issue. Below is the log captured in build/openocd_log.txt.
Open On-Chip Debugger 0.10.0-dev-00225-gb0314be-dirty (2017-03-09-14:50)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
Warn : target name is deprecated use: 'cortex_m'
jtag_init
Warn : Using DEPRECATED interface driver 'ft2232'
Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/...
Error: unable to open ftdi device: device not found
Open On-Chip Debugger 0.10.0-dev-00225-gb0314be-dirty (2017-03-09-14:50)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
Warn : target name is deprecated use: 'cortex_m'
jtag_init
Warn : Using DEPRECATED interface driver 'ft2232'
Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/...
Error: unable to open ftdi device: device not found
Open On-Chip Debugger 0.10.0-dev-00225-gb0314be-dirty (2017-03-09-14:50)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
Warn : target name is deprecated use: 'cortex_m'
jtag_init
Warn : Using DEPRECATED interface driver 'ft2232'
Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/...
Error: unable to open ftdi device: device not found
Open On-Chip Debugger 0.10.0-dev-00225-gb0314be-dirty (2017-03-09-14:50)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
Warn : target name is deprecated use: 'cortex_m'
jtag_init
Warn : Using DEPRECATED interface driver 'ft2232'
Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/...
Error: unable to open ftdi device: device not found
Open On-Chip Debugger 0.10.0-dev-00225-gb0314be-dirty (2017-03-09-14:50)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
Warn : target name is deprecated use: 'cortex_m'
jtag_init
Warn : Using DEPRECATED interface driver 'ft2232'
Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/...
Error: unable to open ftdi device: device not found
Open On-Chip Debugger 0.10.0-dev-00225-gb0314be-dirty (2017-03-09-14:50)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
Warn : target name is deprecated use: 'cortex_m'
jtag_init
Warn : Using DEPRECATED interface driver 'ft2232'
Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/...
Error: unable to open ftdi device: device not found
Open On-Chip Debugger 0.10.0-dev-00225-gb0314be-dirty (2017-03-09-14:50)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
Warn : target name is deprecated use: 'cortex_m'
jtag_init
Warn : Using DEPRECATED interface driver 'ft2232'
Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/...
Error: unable to open ftdi device: device not found
Show LessWe need to integrate wiced wifi with our already existing project which is based on freeRTOS v6,If there is any WICED release with FreeRTOS version 6,
please let Us know.It will greatly help us.
Regards,
Suresh
Show LessI am having issues installing WICED Studio on my Mac. I have followed the extra steps outlined here: WICED-Studio-6.2.1 (OSX) . Everything seems to go normally but once the installer has completed and I try to open the application I receive a warning:
I have attached the log file but an excerpt is shown below.
`
!ENTRY org.eclipse.cdt.autotools.core 4 0 2018-07-09 08:46:30.336
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.cdt.autotools.core [43]
Unresolved requirement: Require-Bundle: org.eclipse.cdt.managedbuilder.core; bundle-version="5.0.100"
-> Bundle-SymbolicName: org.eclipse.cdt.managedbuilder.core; bundle-version="8.3.0.201502131403"; singleton:="true"
org.eclipse.cdt.managedbuilder.core [78]
Unresolved requirement: Require-Bundle: org.eclipse.cdt.core; bundle-version="[5.0.0,6.0.0)"
-> Bundle-SymbolicName: org.eclipse.cdt.core; bundle-version="5.9.1.201502131403"; singleton:="true"
org.eclipse.cdt.core [53]
Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))"
at org.eclipse.osgi.container.Module.start(Module.java:434)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
`
My guess is it was a Java version mismatch, but I've since tried with Java versions 9, 8, and 7 with the exact same result. The macOS version I am using is 10.12.6.
I've tried version 6.2.1 and 6.1.0 again with the same results. I'm kind of at a loss of what to try next.
Show LessMy design uses an external ECC device from Atmel, the ATECC508A/ATECC608A.
The device securely stores the private key internally and cannot be retrieved, so all ECC functions is handled by the chip.
I need to use this with mbedTLS and wiced_tls.
I do no understand how to set a client certififcate in wiced_tls without the private key. The underlying calls into mbedTLS looks like it requires the private key as well.
I have a slight idea of how to add alternate functions to mbedTLS for ECDH / ECDSA functions.
Has anyone done this? Any ideas?
Show LessHello,
I want to create an application that communicates with our web server using the HTTP client module of WICED SDK (6.2.1).
Our web server always uses Transfer-Encoding: chunked encoding in response, but the chunked encoding is not yet implemented in the HTTP client module.
WICED-Studio-6.2/43xxx_Wi-Fi/libraries/protocols/HTTP_client/http_client.c, line 526
if ( strnstrn( (char*)data, fragment_available_data_length, HTTP_HEADER_CHUNKED, sizeof( HTTP_HEADER_CHUNKED ) - 1 ) )
{
//TODO : Implement code to handle chunked encoding response.
}
When will the chunked encoding response be implemented?
Thanks you.
Show LessHi. I've tried to install WICED Studio 6.2.1 on the current macOS. However, the 43xxx_Wi-Fi folder only contains the arm-eabi toolchain, but nothing else.
In 6.1, here has been way more, like apps, doc, include, libraries, platforms...
Any ideas?
Thanks
Matthias
Show LessI am building the ble_hello_sensor snip for the BCM94343WWCD1 in the 6.1 and 6.0 WICED SDKs The console window build summary is listed below for each SDK. As you can see in WICED 6.1 most of the flash values are missing. That's probably a mistake...
An interesting thing is that the WICED_Bluetooth_Firmware_Driver which is about 36 kB in size is located in RAM in SDK 6.1 but it was located in flash in 6.0.
This seems to be the way the build is configured. When I build our Wi-Fi / BLE application that runs fine on SDK 6.0 it does not have enough RAM on SDK 6.1 even though no platform, source or config files were changed between the two.
As you can see the same application uses 36 k more RAM in 6.1 than it did in 6.0
SDK 6.1 snip.bluetooth.ble_hello_sensor-BCM94343WWCD1-ThreadX-NetX-SDIO
----------------------------------|---------|---------|
| | Static |
Module | Flash | RAM |
----------------------------------+---------+---------|
Bluetooth_Embedded_Low_Energy_Stac| 0 | 57 |
bluetooth_low_energy | 0 | 9248 |
Host MCU-family library | 0 | 376 |
Interrupt Vectors | 0 | 0 |
libc | 0 | 3064 |
Other | 0 | 275 |
platform | 0 | 292 |
RAM Initialisation | 39580 | 0 |
Ring_Buffer | 0 | 0 |
Startup Stack & Link Script fill | 0 | 7 |
ThreadX | 0 | 400 |
WICED | 0 | 862 |
WICED_Bluetooth_Firmware_Driver_fo| 0 | 36987 |
WWD | 0 | 60 |
----------------------------------+---------+---------|
TOTAL (bytes) | 0 | 51628 |
----------------------------------|---------|---------|
SDK 6.0 snip.bluetooth.ble_hello_sensor-BCM94343WWCD1-ThreadX-NetX-SDIO
----------------------------------|---------|---------|
| | Static |
Module | Flash | RAM |
----------------------------------+---------+---------|
Bluetooth_Embedded_Low_Energy_Stac| 164 | 64 |
bluetooth_low_energy | 78302 | 9308 |
Host MCU-family library | 8214 | 376 |
Interrupt Vectors | 388 | 0 |
libc | 30068 | 3064 |
Other | 3245 | 271 |
platform | 1364 | 292 |
RAM Initialisation | 2596 | 0 |
Ring_Buffer | 112 | 0 |
Startup Stack & Link Script fill | 0 | 7 |
ThreadX | 7048 | 396 |
WICED | 2103 | 854 |
WICED_Bluetooth_Firmware_Driver_fo| 36691 | 0 |
WWD | 677 | 60 |
----------------------------------+---------+---------|
TOTAL (bytes) | 168376 | 14692 |
----------------------------------|---------|---------|
Show LessHello,
If I do not download the firmware through JTAG and I use the gang writer to write firmware to an external flash, is it possible to boot?
Thanks and Regards,
David
Show Less