Wi-Fi Development using AT Command Set
- Quick and easy path for fast prototyping
- Fully Featured AT Command set
- Ready2Go SW examples and applications
- Recommended for new development
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.
Features
802.11n 1X1
2.4 GHz
20 MHz channels
Three sleep modes
Wi-Fi Certified
Cortex M4F processor
SRAM
Hardware encryption engine
Integrated PA and LNA
OTA engine
Multiple I/Os
ADC engine
Hostless or hosted mode
Benefits
Low power Wi-Fi
Enables year-plus battery life for most applications
Superior range
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
Applications
Thermostats
Door locks
Security cameras
Video door bells
Temperature sensors
Smoke detectors
Other wireless sensors
Garage door openers
Pet trackers
Asset trackers
Home automation
Commercial
Industrial
Residential
Packages
QFN-48 (6 x 6 x 0.9 mm)
FcCSP-72 (3.8 x 3.8 x 0.68mm)
Wi-Fi AT Command Set
Access the industry-leading low power features of the DA16200/DA16600 family simply, quickly and without having to develop any complex software on the Wi-Fi side.
Renesas and Dialog Have Joined Forces
More than 10 Winning Combinations
with Low Power Wi-Fi
Stay connected
Get in touch with us directly through our worldwide sales offices, or contact one of our global distributors and representatives.
Inquiries Distributors and Representatives Register for newslettersWi-Fi Development using AT Command Set
- Quick and easy path for fast prototyping
- Fully Featured AT Command set
- Ready2Go SW examples and applications
- Recommended for new development
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.
DA16200 Video
The Promise of the Smart Home
You can no longer post questions or comments on this page. All product forum activity on the Dialog Semiconductor website has been migrated to a new platform called RenesasRulz. Renesas Electronics Corporation (“Renesas”) will be the service provider and processor managing this move on behalf of Dialog Semiconductor PLC. (“Dialog Semiconductor”). Please post your questions there:
Back to results
Wi-Fi
5 months ago
How To Create Bootloader Image For Custom DA16200 Board
Posted by jlcoleman 187 points 7 repliesWe have designed a custom DA61200 board that uses the DA16200-00000F22 CSP device. The board is designed with the WInbond W25Q32JWSSIQ 4MB Flash Memory Device.
We will be using the UART Sflash Downloader to Flash the Bootloader Image, Main RTOS Image and System Library Image.
How do we create the Bootloader Image with the correct SFDP memory type for the W25Q32JWSSIQ memory? It is not clear to me how to create this file or is this file provided in the SDK?
I have also attached a copy of our DA16200 custom board schematic for reference.
| Attachment | Size |
|---|---|
| DA16200 Custom Board Schematic | 496.1 KB |
5 months ago
5 months ago
Thanks for your help on this. We will try and see how we make out.
James
4 months ago
Hello,
We received our new custom boards that uses the DA16200-00000F22 and W25Q32JWSSIQ memory device. We are getting a CRC/Magic Code Error on boot. Please see below.
What causes this error and what do we need to do correct this problem? Is there something in the SDK configuration that we need configure in order to fix this problem?
Thanks,
James
4 months ago
Hi James,
Could you kindly attach the image showing the CRC/Magic Code Error during boot? Sorry, but I am not able to find it in your previous reply.
Thanks, PM_Dialog
4 months ago
Provided below is the CRC/Magic Code Error that we see in the console.
Load Y-Modem (Load Offset:f6684)
CCCC
xyzModem - CRC mode, 2(SOH)/91(STX)/0(CAN) PKTs, 10 retries, err:Timed out
## Total Size = 0x000168a0 = 92320 Bytes
[MROM] loady 23000
Load Addr: 000f6684
To cancel a session, press Ctrl+X
Load Y-Modem (Load Offset:f6684)
CCÿDA16200_FRTOS-GEN01-01-15022-000000.img968640 14167055414 100644-ÿDA16200_FRTOS-GEN01-01-15022-000000.img968640 14167055414 100644-ÿDA16200_FRTOS-GEN01-01-15022-000000.img968640 14167055414 10
No such command - type help
[MROM] loady 23000
Load Addr: 000f6684
To cancel a session, press Ctrl+X
Load Y-Modem (Load Offset:f6684)
CCC
xyzModem - CRC mode, 1(SOH)/946(STX)/0(CAN) PKTs, 8 retries, err:Timed out
## Total Size = 0x000ec7c0 = 968640 Bytes
[MROM] boot
Wrong magic code: fcecffec - 4b394346
[MROM]
4 months ago
Any update are suggestions on why we are getting the Wrong magic code error? Did we not configure a parameter correct in the software tools? Do we have a problem with our memory (i.e. not writing properly or a read or erase problem).
We are stuck at this point and not able to move forward with the hardware and software validation of our custom prototype hardware.
Thanks,
James
5 months ago
Hi jlcoleman,
Thanks for your question on our public Wi-Fi forums.
This could be done through the Eclipse IDE. The first time you are going to build the project via the Eclipse IDE, the Generate Configuration pop-up window is displayed automatically so that the flash memory type can be selected. Select the flash type and press generate to create the appropriate flash configuration file required to build the firmware.
The flash configuration can be changed by running the Generate Configuration tool which is provided by the SDK. Generate Configuration can be run by going to the Run->Externel Tools menu and selecting either Generate Configuration For Window or Generate Configuration For Linux.
Of course the scripts_project should be imported as a project first. In the Eclipse Project Explorer navigate to the <sdk_top_directory>/utility/j-link/project/ and then right click on that directory andselect Import as Project.
Thanks, PM_Dialog