![]() Worse, sometimes they don't match up with the current version of Segger (even though they say the best version is the latest one) and just don't work. These instructions are long and complicated, and in some areas vague. Instead, Nordic provide instructions for converting Keil projects to Segger ones. And since Segger has only been the preferred IDE since nRF5 SDK v14.1, Nordic's examples do not include Segger projects for v12.3 and therefore there are no example nRF51 examples with Segger projects provided. The latest nRF5 SDK is version 16, but it doesn't support nRF51, you have to go back to version 12.3 to get nRF51 support. Setting upĪs soon as you start working through Nordic's instructions, it becomes apparent that they have left the nRF51 behind and are only really interested in the nRF52. Since the nRF51-DK comes with a Segger J-Link debugger chip built in and I had previously noted that Segger seemed to be one of the premium brands for ARM Cortex IDEs and debuggers, with matching costs, Segger SES seemed to be the right choice of IDE. While they also provide support for Keil, IAR, and GNU/GCC, the agreement with Segger is that they will licence it for free for use with Nordic chips. Nordic's Getting Started Guide v1.3, which covers the nRF51 DK, recommends Segger SES as the preferred development enviroment and is supported by Nordic. ![]() I decided I didn't need the feature of the nRF52/Cortex M4, which was my first mistake. In comparison, the later nRF52 series are M4 based, more capable but more expensive. It uses the nRF51422 which is Cortex M0 based, so I thought it would be a good way to do some M0 development work. The Development Kit comes in a handy sized board which only needs micro USB for power and data, and has a built in SEGGER JLink debug chip, as well as 4 user buttons and LEDs, and all the usual ports. The host did not find any problems in the process, and it was still very smooth, and the compilation passed.Īfter that, the host will continue to update the settings and debug, etc.The nRF51 is recent enough to be supported by a mature development environment and to have lots of others try it out before me. The project is imported here, and the curve realizes the rapid establishment of the Embedded Studio project. OK The entire import process is completed, execute the compilation, the rocket-like speed is executed, post two comparisons of the compilation time of a larger project, the compiled project is the same project, the keil5 version project generated by cubemx, and then imported with embedded studio, The difference is quite big. Jump to file browsing, select the generated keil 5 project fileĬhoose according to the options in the picture Prepare a project generated by cubemx, and the keil 5 version project generated by the host test Whether it’s opening the software, opening the project, switching the mode, or burning the target file, it’s all in seconds, don’t be too cool, don’t talk nonsense, and business starts.įirst go to the official website to download, all the way down to complete the installation, and then install the necessary Package Tools->Package Manager install several CMSIS packages, then scroll down to find the ST package, and download the support package according to the specific use series. It’s not good, it’s a bit of a twist, and I can’t help the temptation of being easy to use. The host upgraded to version 4.22 and found that it can import the keil project and cooperate with cubemx. SEGGER's stuff has always been NB, and SEGGER Embedded Studio is not bad. With the release of Segger, SEGGER Embedded Studio is fully functional and free for non-commercial applications.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |