I’d like to announce that versions of the Gecko SDK are now available on our GitHub account here:
The main landing page of this repository includes information about how the files are organized and a quick guide on how to install a specific version of the SDK in Simplicity Studio.
We will maintain this going forward so you can always find a particular version of the SDK if you need it.
The documentation for the Gecko SDK is also available here:
Note: If you cloned this repo prior to August 5th, 2016, you will need to reclone it in order to resynchronize with the repo and pull the latest files.
Edit: Updated the link to point directly to the Software Documentation.
Great to finally have it available outside of Simplicity Studio!
For those of us that cannot or choose not to use your IDE, are we likely to see RAIL and other components appearing on github as well?
We are constantly evaluating how we distribute software to make sure that we can support all customers as efficiently as possible. Whether we can and should expand distribution of RAIL to GitHub is not yet determined, but we'll probably use the learnings from putting the Gecko SDK on GitHub to evaluate that.
Marketing speech done, I think you can download the RAIL library and use it with either GCC or IAR, independent of which IDE you are using (as long as the compiler is either GCC or IAR)?
That being said, comments like this is of great value to us in forming our software delivery strategy, so keep them coming!
Thanks for the response (and for making great MCUs!).
You are correct that you can download RAIL, it is however a .exe file which is not immensely useful for non-windows users.
My vote will always be for smaller components, released in a nice version controlled / trackable way, that we can use from non-graphical, non-windows machines.
@Alf I believe putting it on GitHub is a step in the right direction, so kudos for doing that. The next steps would be: 1) accepting community contributions and 2) developing it more openly instead of simply throwing it over the wall. I'd be also interested to see the other SDKs (RAIL, BLE, etc.) become more open.
@ryankurte I agree. (Also a non-windows user here.) However it's not so bad: you can still run the downloaded exe with wine (worked last time I tried), or if you use an OS which you can run Simplicity Studio on, its v4 version can now automatically download all the SDKs for you even if you don't run windows. This is I believe still better than how it was half a year ago.
@Timur It definitely is an improvement! Simplicity Studio can do a bunch of things, but you still have to install it / keep it up to date. Which we do, but, running an IDE to download BSPs / Data sheets is not ideal. Especially when you don't use it for building or anything else.
The CMSIS/BSPs provided are fantastic, I am a /huge/ fan of silabs hardware & software. But the apparent move from distributing things via the web (and in useful formats) is rather a regression.
I would love to see the same! Especially with things like the custom version of mbedtls.
Change tracking & version management is pretty important for more modern development, especially when you are providing/altering a security library.
As it stands, we manually mirror and update these files through git so that we can see differences against the ARMmbed master as well as differences between versions. It would be so valuable to have a public fork against the master with useful commits and version tags so we don't have to establish the provenance of every release ourselves (and then there's the discussion about signing tags/commits, but that is another step up).
Yep! It's on my list to do, and I hope to have it complete by the end of next week.
Thank you @Tabitha I'm just asking because I'd like to rebase my UARTDRV fixes to the new version.
v5.0.0 is now available on GitHub (both Gecko_SDK and Gecko_SDK_Doc are updated)!
is it intentional that the Gecko SDK code on Github (v5.1.2) is no longer in sync with the version that is distributed with Simplicity Studio (v5.2.1)?
I appreciate it very much that you release the code on Github, this makes the changelog clearly available to anybody interested and makes it trivial to see if it is worth to update for existing projects.
Would it be possible to update the released code on Github please? I think that 5.1.3 also did not make it to Github?
We decided to no longer update github with the Gecko SDK since it's now integrated into a larger package that includes software that can only be distributed to certain users. The other reason is we've had issues keeping these synchronized in the past, and it's generally better to have one place serve the content.
The Gecko SDK will now be distributed within Simplicity Studio as part of the Gecko SDK Suite, but we will keep the existing versions of the Gecko SDK on github rather than removing them. I will make a note to update the release notes page to state that the latest versions are available in Simplicity Studio so there's no confusion.
Putting the Gecko SDK on github was a bit of a stop-gap solution since at the time, Simplicity Studio did not let users download various versions of a software package. This became an issue anytime someone needed an older version of the Gecko SDK.
With the latest version of Simplicity Studio v4, you can now view multiple versions of the same software package, their differences, and release notes for the various versions of the Gecko SDK Suite within Simplicity Studio. It's all available in the [Update Software] area of the Launcher view.
If you have any particular feature requests for this system to make it more useful or more user friendly, please let me know, and I can pass this along to our Simplicity Studio team.
Can you provide more information on why you need it in another source? This will help in our discussion for adding this support.
@TabithaSure, I've got two main reasons:
With this workflow, it more is convenient to be able to download the SDK (and its documentation) separately, instead of poking around looking for its source files under Simplicity Studio's folder.
thank you for the update. If you decide to stop supporting Github then it indeed makes sense to add a note to the releases that are on that page. Now it looks like the version that is on the site is the latest, which is not the case.
The reason I asked about the Github update is because I do follow the same approach as @Timur does when including the Gecko SDK in projects: I copy the files into the project and put in under source control. Reasons: I need to be able to decide myself when/if to update the SDK in my projects, I want a project to be independent of a specific SDK version that is released with a specific version of Simplicity Studio and I want to be able to easily replicate the codebase on other machines/developers.
I do understand that release processes change over time and if SiLabs decided to couple the SDK to other code pieces that require authentication then there are little other options than to only release via Simplicity Studio.
Most of interest to users according to me is a clear Changelog. On Github, when the description in the Changelog of a new release was not completely clear, two clicks in the web interface would show the changes in the sourcecode. This advantage is lost when the only option to get the SDK is via Simplicity Studio. This means that we need to checkout the two version and to diff in a separate tool. Not the end of the world, but to me it was an advantage of using the SiLabs toolflow that the SDK source files were easily available.