IAR 8.20.2 crashes on Win8 when stopping debug

http://e2e.ti.com/support/wireless_connectivity/f/155/p/248699/875780

Finally, found solution about IAR8.20.2 running on Windows 8 will cause crash when stopping debug. This issue troubles me several months.

Still have problem on register view, even if I delete some in .sfr.
I decided to change to IAR 8.30.
But it needs to modify the below file.

• EW24413: Linker configuration files (with the filename extension .xcl) from version 8.20 or older contain:
  -Z(DATA)VREG+_NR_OF_VIRTUAL_REGISTERS=08-7F.
  In the 8.30.1 release this internal _NR_OF_VIRTUAL_REGISTERS symbol was deprecated. In the new version of these files, this changed to:
  -Z(DATA)VREG=08-7F.
  This change is now also applied to the Texas Instruments (Chipcon) linker configuration files.

Open $PROJ_DIR$\..\..\common\cc2540\ti_51ew_cc2540b.xcl  

Change -Z(DATA)VREG+_NR_OF_VIRTUAL_REGISTERS=08-7F to -Z(DATA)VREG=08-7F

micro manager resource information

Micro-Manager Programming Guide

https://micro-manager.org/wiki/Micro-Manager_Programming_Guide

Building Micro-Manager Device Adapters

https://micro-manager.org/wiki/Building_Micro-Manager_Device_Adapters

Building Micro-Manager Device Adapters

http://valelab.ucsf.edu/~nstuurman/MMweb/raw_content/mmdevicekit.htm

http://valelab.ucsf.edu/~aedelstein/mm_doc/html/files.html

http://valelab.ucsf.edu/~nstuurman/MMweb/overview.php

What is the size limit of a get / post request?

There is no defined maximum size for HTTP POST requests. If you notice such a limit then it's an arbitrary limitation of your HTTP Server/Client.

No limit by specification. The limit is MIN(browser_limit,server_limit).

As per this the default is 2 MB for tomcat.

I just ran some tests on 3 somewhat current browsers (IE9, FF 10 ESR, Chrome 24) and they all submitted hidden input values of 100KB without any problem. So the problems with text inputs don't seem to apply here.–  Oliver Jan 30 '13 at 14:27 While GET is limited to as low as 1024 characters, POST data is limited to 2 MB on IIS 4.0, and 128 KB on IIS 5.0. Each name/value is limited to 1024 characters, as imposed by the SGML spec. Of course this does not apply to files uploaded using enctype='multipart/form-data' ... I have had no problems uploading files in the 90 - 100 MB range using IIS 5.0, aside from having to increase the server.scriptTimeout value as well as my patience! :-)  from http://classicasp.aspfaq.com/forms/what-is-the-limit-on-form/post-parameters.html http://www.w3schools.com/tags/ref_httpmethods.asp Get: Yes, when sending data, the GET method adds the data to the URL; and the length of a URL is limited (maximum URL length is 2048 characters) Post:No restrictions

Suggest that package size is smaller than 2KB.
http://stackoverflow.com/questions/2364840/what-is-the-size-limit-of-a-post-request

Eye detection - openCV

http://romanhosek.cz/android-eye-detection-and-tracking-with-opencv/

BLE "insufficient authentication" issue

For TI CC254x, if BLE is not paired with encryption. Although attribute sets GATT_PERMIT_AUTHEN_READ_WRITE, the stack still responses ATT_ERR_INSUFFICIENT_ENCRYPT. In order to solve this problem, need to manual handle error code without stack. Simple way is:
1. set all  characteristics to GATT_PERMIT_READ_WRITE
2. in ReadAttrCB / WriteAttrCB to check link encryption status then manual feed back ATT_ERR_INSUFFICIENT_AUTHEN.
someReadAttrCB()
{
  bStatus_t status = SUCCESS;
<-- -->
  // Require security for all characteristics
  if ( linkDB_Encrypted( connHandle ) == FALSE )
  {
    return ATT_ERR_INSUFFICIENT_AUTHEN;
  }
<-- -->

The issue is about 
" from J.Sample
When the iOS device forgets the CC2540, then when it tries to write to a characteristic with permissions of GATT_PERMIT_AUTHEN_READ_WRITE theCC2540 returns an ATT_ERR_INSUFFICIENT_ENCRYPT since it still thinks it's paired with the iOS device - instead of an ATT_ERR_INSUFFICIENT_AUTHEN which it returns when it's not paired.
"
 or when do bluetooth certification, some cases need to show ATT_ERR_INSUFFICIENT_AUTHEN.


For my test, iOS still doesn't work.
may use ATT_ERR_INSUFFICIENT_AUTHOR instead. It works.
The suggested solution works for me but I have to return ATT_ERR_INSUFFICIENT_AUTHOR instead of ATT_ERR_INSUFFICIENT_AUTHEN.
3.9 Pairing The accessory should not request pairing until an ATT request is rejected using the Insufficient Authentication error code. See the Bluetooth 4.0 specification, Volume 3, Part F, Section 4 for details. If, for security reasons, the accessory requires a bonded relationship with the Central, the Peripheral should reject the ATT request using the Insufficient Authentication error code, as appropriate. As a result, the Apple product may proceed with the necessary security procedures. Similarly, if the iOS device acts as a Central and a GATT server, it may reject an ATT request using the Insufficient Authentication error code. The accessory should initiate the security procedure for pairing in response. Pairing may require user authorization depending on Apple product. Once an accessory is paired with an Apple product, it shall retain the distributed keys of both central and peripheral for future use. If the pairing is no longer required, the accessory shall delete both sets of keys.  (from Apple) https://developer.apple.com/hardwaredrivers/BluetoothDesignGuidelines.pdf

http://e2e.ti.com/support/wireless_connectivity/f/538/p/453316/1633279#1633279

Reference link:
https://e2e.ti.com/support/wireless_connectivity/f/538/p/259197/907091#907091&nbsp;
https://e2e.ti.com/support/wireless_connectivity/f/538/p/232666/1003797
https://e2e.ti.com/support/wireless_connectivity/f/538/p/245279/857934#857934
http://connectivity198.rssing.com/chan-4845084/all_p147.html

Wechat platform - infomration

1. 微信接口调试工具使用
http://jingyan.baidu.com/season/49878