- Silicon Labs Community
- Welcome and Announcements
- Silicon Labs Knowledge Base
- 8-bit MCU
- 32-bit MCU
- Bluetooth / Wi-Fi
- Other Products Category
- Optical/RH/Temp Sensor
- Other Products
- Hardware and Software Tools
- Simplicity Studio and Software
- General Discussions and Suggestions
- Chinese Forum
- Software Libraries
- Development Kits
- Reference Designs
- Third Party Tools
- White Papers
- Official Blog of Silicon Labs
- Chinese Blog
08-05-2016 01:20 PM - edited 08-10-2016 04:01 PM
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.
MCU Applications and Support Manager
08-12-2016 12:29 AM
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?
08-15-2016 04:35 AM
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!
10-06-2016 05:42 PM
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.
10-11-2016 05:48 AM
@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.
10-11-2016 05:58 PM
@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).