This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Regards compatibilities of demo code in different SDK ?

As a small team, we have to find silicons from retell market. Sometimes even the trader can not promise its source and batch. Here is a small list of nRF51822 available from the market.

nRF51822-QFAAC0-1311AH
nRF51822-QFAAC0-1322AY
nRF51822-QFABA0-1326AW
-------------------------
nRF51822-QFAAG3-1438AU
-------------------------
nRF51822-QFAAH0-1517DF
nRF51822-QFAAH0-1512BX
nRF51822-QFAAH0-1527HU
nRF51822-QFAAH0-1544MG
nRF51822-QFACA1-1506AJ

nRF51822-QFAAF1-1621DF ES or nRF51422 ?

nRF52832-QFAA

The 1st generation (C0) silicon is about 15% cheaper than 3rd generation (Hx).

For sure, we want to get latest version, but my development kit is quite old anyway. I compare the source folder for different SDK, v4.4/6.1/8.0...... Quite a lot of changes. For example, there are no UART applications and DFU in v4.4.

Does anyone try to backport these applications into older silicon ? Or we should simply drop this idea since it doesn't worth to try to load new SD/SDK...

  • According to compatibility matrix it is highly not recommended to use new softdevces/SDKs on old chips. You can ofc use old chips and old SD, and old SDK, but... is it really worth it? Soon, rev 1 chips will completely be gone, and you will have to move to new ones anyway. new SD and SDK provides bugfixes etc, also chips have hardware improvements. You do what you must, but I really recommend going rev. 3.

    There are some workarounds (not recommended in production) to use new SD on rev.2 chips, but using on rev.1 is not possible afaik.

  • Thanks for your comments. Saving time and money.

Related