Porting code from SDK 1 for BCM20732 to SDK 2 for BCM20736/20737

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable

Hi all,

i would to know if it is easy to port the code from the SDK1 to the SDK2; if in the SDK2 you have resolved the many bug present in the first SDK and if it is easy to debug using a jlink the code on the SDK 2. Is the documentation about the APIs in the SDK 2 is more exaustive than tne documentation about the SDK 1.Thks.

0 Likes
1 Solution
MichaelF_56
Moderator
Moderator
Moderator
250 sign-ins 25 comments on blog 10 comments on blog

In theory, source code from SDK 1.x (A0) should compile and run without any issues on SDK 2.x hardware (20736/37) and firmware (A1),

However, as several users have discovered, there are small undocumented nuances which will require testing on your side to confirm the application works properly.  Many of these nuances you will find are noted here on the forum and several have existed as bugs in SDK 1.x that users leveraged as part of a custom feature.  In this instance, once SDK 2.x fixed the bug, the custom feature went away and they had to figure out a new method to accomplish the same task.

Here is one such example of an issue a customer ran into when moving from SDK 1.1 to SDK 2.x

The good news is that many have made the transition successfully.

The online HTML documentation has been updated in SDK 2.x, but where you will find the most improvements is via the sample applications that are provided (many of them contain documentation inline).

ldgirod

View solution in original post

0 Likes
1 Reply
MichaelF_56
Moderator
Moderator
Moderator
250 sign-ins 25 comments on blog 10 comments on blog

In theory, source code from SDK 1.x (A0) should compile and run without any issues on SDK 2.x hardware (20736/37) and firmware (A1),

However, as several users have discovered, there are small undocumented nuances which will require testing on your side to confirm the application works properly.  Many of these nuances you will find are noted here on the forum and several have existed as bugs in SDK 1.x that users leveraged as part of a custom feature.  In this instance, once SDK 2.x fixed the bug, the custom feature went away and they had to figure out a new method to accomplish the same task.

Here is one such example of an issue a customer ran into when moving from SDK 1.1 to SDK 2.x

The good news is that many have made the transition successfully.

The online HTML documentation has been updated in SDK 2.x, but where you will find the most improvements is via the sample applications that are provided (many of them contain documentation inline).

ldgirod

0 Likes