VISUALGDB SUPPORT FOR NORDIC NRF52 V15.2 SDK

[engicoder]

Any plans to update the NRF52X device package to support the 15.2 SDK?

Thanks

[support]

Hi,

Yes, we are currently running internal tests on it and expect to release it in a few next weeks (there have been non-trivial changes to the Nordic samples).

[grindstaffp]

While not perfect, running SDK 15.2 through VisualGDB’s BSP Tool yielded a workable BSP which I have been using since 15.2 was released. Unfortunately, the officially tested and released BSP from sysprogs will be coming not long before the next official SDK (rumored over on devzone).

[support]

Thanks for sharing this. Yes, our internal BSP build is somewhat usable, although a few example projects from Nordic use library settings that were not present in the previous SDKs, so we are making sure that VisualGDB can clone them properly. We also understand that it took us longer than usual to process this, so we will give a higher priority to supporting the next Nordic SDK so it won’t take that long.

[grindstaffp]

Apologies for coming across so critically. Obviously with the number of platforms that you guys support there will be some delay between the SDK release and you guys being able to pull it into visualgdb.

Fortunately it wasn’t too difficult this time (who knows what changes Nordic will make that break the bsp tool in the future) to have a usable, but not polished 15.2 bsp. While it isn’t supported and doesn’t pull the examples through, it works with a bit of tweaking. But tweaking is the name of the game I guess since Nordic doesn’t support visualgdb out of the box, however much we wish they did.

[support]

No worries. We usually schedule the BSP updates based on the popularity of the device families. Nordic devices are quite popular (and are, in our opinion, the best choice for Bluetooth LE), so our normal internal guideline is to have a BSP ready in 1-2 months after the official SDK release. However, unfortunately we did get a few interruptions along that path, so it took longer than we expected. It should be out fully tested and supported in 1-2 weeks based on what we see currently. Sorry for the wait.

[Author]

Posts