Ultra Low Power Wi-Fi SoC for battery powered IoT devices
The DA16200 SoC is the world's first Wi-Fi SoC delivering year plus battery life for always connected Wi-Fi IoT devices. DA16200 is low power Wi-Fi networking SoC that delivers a dramatic breakthrough in battery life even for devices that are continuously connected to the Wi-Fi network. In most applications, one year plus battery life is achievable. There is no tradeoff in output power or range as the SoC’s range is industry leading. The chip also features very strong IoT security, including WPA3 and TLS for authentication and encryption at Wi-Fi and higher stack layers. The DA16200 is a full offload device, meaning the the entire Wi-Fi and TCP/IP networking stack and even end product application code can run on chip with no external CPU or MCU required. Alternatively, a small inexpensive MCU can send the DA16200 commands and the SoC will still perform the full offload networking stack functions.
The DA16200 modules are the perfect complement to the DA16200 ultra low power Wi-Fi SoC.
20 MHz channels
Three sleep modes
Cortex M4F processor
Hardware encryption engine
Integrated PA and LNA
Hostless or hosted mode
Low power Wi-Fi
Enables year-plus battery life for most applications
Strong security at Wi-Fi layer
Strong security at upper stack layers
Long battery life even when continously connected
Full offload, runs entire stack on chip
Run without any external CPU or MCU
Otpionally can run with external MCU
Multiple sleep modes for different applications
Available as SoC or module
Processes analog or digital sensor info on chip
Video door bells
Other wireless sensors
Garage door openers
QFN-48 (6 x 6 x 0.9 mm)
FcCSP-72 (3.8 x 3.8 x 0.68mm)
Our VirtualZero™ products are supported by development kits to help you create applications that exploit the unique benefits of the VirtualZero™ family to the fullest. These tools help you minimize your time to market.
The Promise of the Smart Home
5 days ago
DA16200 - SDK threads crashing when using a HTTP serverPosted by l.wassermann 15 points 4 replies
I am using the Generic SDK for DA16200 and have issues with some threads causing a reboot of the system (umac_fc9k, WLANx_IP or http server thread).
The project mainly consists in a HTTP server hosting a graphical user interface. The HTTP server is configured as described in the documentation and uses the nx_http_server_web_open/close/get_size/get_payload functions to retreive and send the resources (HTML, CSS and JS files) requested by a client.
When browsing the interface on a web browser, it occasionally happens that a thread from the SDK (either umac_fc9k or WLANx_IP) or sometimes the HTTP server thread himself causes a reboot.
Here is the console log from when one of these reboot occurs :
[[OOPS Dump : c0f0]] [[Hard Fault]] --RTC Time : 00000000.26d7b5d3 Register-Dump R0 :00000000, R1 :00000000, R2 :00000090, R3 :000002bc R4 :00000000, R5 :000cce80, R6 :000002bc, R7 :000f83e4 R8 :00000090, R9 :00000000, R10 :000cb5a4, R11 :000f7c78 R12 :f7a018fe, SP :000cce58, LR :00037d57, PC :00037d6e PSR :61000000, EXC :fffffffd, Fault Status SHCSR :00000000, CFSR :00000400, HFSR :40000000 DFSR :00000000, MMFAR :e000ed34, BFAR :e000ed38 AFSR :00000000, FC9K SysInfo SICS = 00300000 SICS = 00000000 SICS = 00000000 SICS = 00000000 SICS = 00000000 SICS = 0132bb1b Stack Stack-Dump (48) [0x000cce58] : 000002BC 0008B9D0 000CE204 00000800 000F83E4 00092644 000CB5A4 00125AE7 [0x000cce78] : 00000000 00000000 00000000 000CCEF4 000F7C84 000F84B4 00004288 000CCEF4 [0x000cce98] : 000CE204 000F7C78 000F84B4 00142138 000925FC 000CB5A4 00000000 00141535 [0x000cceb8] : 20000000 000CCEF4 000CCF1C 00141961 000F7C84 001409D5 000F7C78 000F7C78 [0x000cced8] : 000CFC60 00000000 000F84B4 00000000 00000000 00141F61 000CCF50 000F7C78 [0x000ccef8] : 000CB5A4 000CE204 000CFC60 000D0C00 00000000 00000000 00000000 00000000 Thread: umac_fc9k stack ptr : 000ccef0 stack base: 000cc788 stack end : 000ccf83 stack high: 000ccc40 max usage : 00000094 suspend : 00000000 Thread Stack (32) [0x000ccef0] : 000CCF50 000F7C78 000CB5A4 000CE204 000CFC60 000D0C00 00000000 00000000 [0x000ccf10] : 00000000 00000000 00000000 000CCF1C 000CCF1C 00000000 00003FA2 00092648 [0x000ccf30] : 001108A0 00000000 00090050 00000000 00000000 000CC788 00000000 0010FFF3 [0x000ccf50] : 000F7C78 00000000 00090020 00080774 00080778 00003805 00000000 00000000 >>> P.TIM is relocated to RETMEM (0x20f835c0, 4) dpm_init_retmemory::406 DPM INIT CONFIGURATION(1) Wakeup source is 0x0
If this can be of any help, the size of the data handled by the HTTP server can reach about 15 kB.
I could not determine a specific way to cause a reboot. It seems to happen randomly when browsing the website. It also seems to only happen when the HTTP server is receiving requests from a client.
I am therefore looking for some technical support as it seems that I do not have access to the code of these threads (or else I could not find it).
Thanks in advance