CC2640 vs CC2541

1. compare CC2640 and CC254x.
http://referencedesigner.com/blog/ti-cc2640-vs-cc2540-ble/2506/

2. Compare CC26xx and Nordic nrf52832
http://referencedesigner.com/blog/ti-cc2650-cc2640-vs-nordic-nrf52832/2489/

3. The difference between CC2640 and CC2650:

Q: What is the difference between CC2640 and CC2650?

The multi-standard CC2650 wireless MCU supports BLE as well as other wireless protocols, such as 802.15.4. The CC2640 supports Bluetooth Low Energy only. All code generated from the BLE-Stack 2.0 SDK is binary compatible with both the CC2650 & CC2640. Additionally, IDE project configuration settings in the BLE-Stack v2.0 SDK for CC2650 & CC2640 are cross-compatible; however, it is strongly recommended to not change the CPU settings in the IDE. Although the CC2650 has the HW & ROM capability to support additional wireless protocols, a given SW build can only support one wireless protocol. from TI BLE wiki.

4. TI engineer answer:

https://e2e.ti.com/support/wireless_connectivity/f/538/p/417820/1486886#1486886

1) Basically because the radio is totally redesigned. 
2) This is just because the modern ARM processors are more efficient than the old 8051. Additionally we are using new production process, new technology, etc. Adding a built-in DCDC regulator also increases efficiency. Keep in mind though, that none of the numbers in the datasheet are for running both cores simultaneously. 
3) You are correct on CC2640. CC2541 will not be able to fulfill all of 4.1 due to RAM limitations.
4) How many BLE devices may handle the cc2640? There was a limit of.... 3 (AFAIR) in cc2541? 

Our current number is 8

5) Everything is faster in the CC2640 compared to the CC2541. Really.
6) The CC2541 will still be supported by us. We also plan to update the BLE stack for CC254x to 1.4.1 this year. It you prefer a device that have been in the market for several years and is mature, and you can live with the current consumption and the 8051 core, the CC2541 is still a good part to use.
7) You can get the CC26xx SensorTag for $29 with a low cost debugger for just additional $15. Get a kit and check it out! 

from Fredrik K 

Check .Net Framework version

Here have a tool to check your .Net framework installed list.
http://www.azofreeware.com/2012/04/asoft-net-version-detector-xi-net.html

Android Studio - Study

Eclipse + plug-in Android ADT -->  Eclipse ADT bundle -> Android Studio
Good materials (Chinese)
http://www.sdk.tw/2014/12/android-sdk-android-studio.html

Download Android Studio 1.4.1 is about 1.2 GB.

There is a known issue about Tools.jar is not in Android Studio classpath.
Just change your JAVA_HOME to JDK path. The tools.jar is not in JRE but in JDK.

Connect cp2102 or FTDI to Android 3.1 +

The issue here is that the CP210x driver is not enabled in the Android kernel by default. So you will either need to build this driver in to your kernel to get the tty access and ability to use JavaComm.

The other option is to use the USB Host functionality and access your CP210x directly with it's API.

from Preston answered Dec 10 '13 at 15:19

Roger Clark  https://groups.google.com/forum/?fromgroups#!searchin/usb-serial-for-android/CP2102/usb-serial-for-android/KI-Dq1Ka7Cg/PCe2lfoPtucJ The other people trying experience, still not work. http://www.crifan.com/add_rts_and_dtr_support_for_silicon_labs_cp2102_in_usb_serial_for_android/ CP210x driver on Android 4.0.4 http://124.16.139.131:24080/lxr/source/kernel/omap/drivers/usb/serial/cp210x.c?v=android-4.0.4 It works if your Android kernel support CP210x or FTDI driver by using this App. "USB Serial Terminal Lite" https://play.google.com/store/apps/details?id=com.oneman.freeusbtools&hl=zh_TW

6/26/14

Ok.

Eventually solved my own problem.

When I imported the projects into Eclipse, the default Java Build path -> Source   location settings are are for /src and /gen
However the project sources for this are in /java/src/...

So I've moved the files into /src as this seem to be the default (possibly current best practice ???) - as I said, I'm new to Android dev, so I'm not sure what the norms are, but when you create an empty project in the latest version of Eclipse it puts the source files in /src

The issue of the library name was just syntax, i.e the project can be renamed in Eclipse from "main" to USBSerialLibrary using the Refactor -> Rename command.

The stuff in the HowTo about linking the library seems to be out of date as well. As far as I can see (and it works for me in Eclipse ADT  v22.6.2-1085508), is just to add the USBSerialLibrary project as a library to the Android setting in Properties.

BTW. I seem to need to compile as Android 4.2.2 because of a reference to JELLYBEAN in the code

I'm also getting lots of warnings, but normally isn't good news, however the only ones that probably needs to be dealt with in the long term is that

import android.widget.TwoLineListItem;

appears to be deprecated.

Anyway, I hope this helps anyone else just starting out on this journey ;-)

After trying to use this sample codes, it doesn't work.