Nordic 52832 - development

Softdevice - nRF52

• S132 SoftDevice
  The S132 SoftDevice is a Bluetooth low energy central and peripheral protocol stack solution. It supports up to twenty connections with an additional observer and a broadcaster role all running concurrently. The S132 SoftDevice integrates a Bluetooth low energy Controller and Host, and provides a full and flexible API for building Bluetooth low energy nRF52 System on Chip (SoC) solutions.
• S140 SoftDevice
  The S140 SoftDevice is a Bluetooth low energy (BLE) Central and Peripheral protocol stack solution that extends the feature set of S132 v3.0 and supports Bluetooth 5.
• S212 SoftDevice
  The S212 SoftDevice is an ANT™ protocol stack solution that provides a full and flexible Application Programming Interface (API) for building ANT™ System on Chip (SoC) solutions for the nRF52832 chip. The S212 SoftDevice simplifies combining the ANT™ protocol stack and an application on the same CPU.
• S332 SoftDevice
  The S332 SoftDevice is a combined ANT™ and Bluetooth low energy (BLE) protocol stack solution. It supports all four Bluetooth low energy roles (Central, Peripheral, Observer, Broadcaster) and ANT.
• data from Nordic Semiconductor
• 
  

52832 compatible matrix

nRF52832 IC revision	nRF5 SDK	S132 SD	S132 SDS	S212 SD	S212 SDS	S332 SD	S332 SDS
Engineering A	0.9.x1	1.0.0-3.alpha	-	0.2.0-1.alpha	-	-	-
Engineering B	11.0.0-2.alpha	2.0.0-7.alpha	-	0.5.1.alpha	-	-	-
	-	2.0.0-8.alpha	-	0.6.0.alpha	-	0.6.0.alpha	-
Engineering C, Revision 1	11.0.02	2.0.x2	2.0	0.9.x2	-	0.9.x2	-
	12.0.0	3.x.x	3.1	2.0.0	-	2.0.0	-
	12.1.0
	12.2.0
	13.0.0-1.alpha	5.0.0-1.alpha	-
	-	5.0.0-2.alpha	-	-	-	-	-
	-	5.0.0-3.alpha	-	-	-	-	-
	13.0.0	4.0.x	4.1	4.0.2	-	-	-
	13.1.0				-	4.0.2	-
	14.0.0	5.0.0	5.0		-	-	-

Parent topic: Compatibility Matrix

¹ SDK 0.9.x is compatible with nRF52 series only.

² If workaround for anomaly 73 is implemented, nRF5 SDK 11.0.0 can be used for development purposes together with SoftDevice S132 2.0.0/S212 0.9.x/S332 0.9.x on nRF52832 Engineering B. For more information, see nRF52 Engineering B Errata or nRF5 SDK 11.0.0 release notes.

nRF52832 IC revision	Packet variant1	Build code1	Package	Flash	RAM
Engineering A	QFAA	AA0	QFN48	512 kB	64 kB
		AC0
Engineering B	QFAA	BA0	QFN48	512 kB	64 kB
	CHAA	AA0	WLCSP
Engineering C	QFAA	BB0	QFN48	512 kB	64 kB
	CHAA	BA0	WLCSP
	CIAA	BA0	WLCSP
1	QFAA	B00	QFN48	512 kB	64 kB
	QFAB		QFN48	256 kB	32 kB
	CIAA		WLCSP	512 kB	64 kB

Parent topic: Compatibility Matrix

¹ Packet variant and build code can be read from markings on top of the nRF52 IC.

Fourier transform 說明_中文 (好文)

http://blog.xuite.net/lapuda.chen/PaulBlog/221866406-%E5%A6%82%E6%9E%9C%E7%9C%8B%E4%BA%86%E6%AD%A4%E6%96%87%E4%BD%A0%E9%82%84%E4%B8%8D%E6%87%82%E5%82%85%E9%87%8C%E8%91%89%E8%AE%8A%E6%8F%9B(Fourier+Transform)%EF%BC%8C%E9%82%A3%E5%B0%B1%E9%81%8E%E4%BE%86%E6%8E%90%E6%AD%BB%E6%88%91%E5%90%A7!

BLE White List note

1. Chinese article
http://thinkingiot.blogspot.tw/2015/02/ble-security-3-ble-denial-of-service.html
http://www.deyisupport.com/question_answer/wireless_connectivity/bluetooth/f/103/t/87181.aspx

http://e2e.ti.com/support/wireless_connectivity/bluetooth_low_energy/f/538/p/414562/1475140

The difference between .net framework 4.0 and client profile (Chinese)

https://dotblogs.com.tw/regionbbs/2010/03/25/vs2010_net_4_client_profile

C code static - Chinese

Good content explain static.
http://archerworks.blogspot.tw/2010/07/cstatic.html

1. Advertising package detail: (Chinese)
http://www.race604.com/ble-advertising/

2. Device name:

1down voteaccepted

Assuming that you are able to get connected with the GATT Server, when you parse the GAP profile of the device, you will find an attribute for Device Name under Generic Access Profile (GAP).UUID for GAP is 0x1800, and that for the Device Name Characterstic is 0x2A00. This pageexplains that the Device Name characteristic is a part of the GAP. from http://stackoverflow.com/questions/33113141/how-do-you-get-the-actual-name-of-a-bluetooth-low-energy-device

3. GATT UUID (chinese)

https://www.bluetooth.com/zh-cn/specifications/gatt

4. ScanRSP local name and GATT device name (Chinese)

http://www.deyisupport.com.edgekey.net/question_answer/wireless_connectivity/bluetooth/f/103/p/61359/136416.aspx

4. For TI update device name use APIs.

GAPRole_SetParameter( GAPROLE_SCAN_RSP_DATA,);

GAP_UpdateAdvertisingData();
GGS_SetParameter( GGS_DEVICE_NAME_ATT, GAP_DEVICE_NAME_LEN,name);//attDeviceName );

用这三个函数 就可以了 

Nordic nRF51 dongle for NUS peripheral solution

1. Evaluate feasibility -
https://devzone.nordicsemi.com/question/44948/ble_peripheral-on-pca10031-dongle/

2. Virtual COM
Refer to user manual
http://infocenter.nordicsemi.com/pdf/nRF51_Dongle_UG_v1.0.pdf
P0.09 TXD
P0.11 RXD