Arm Keil Studio Download

[Leronne Washington]

Ive been using successfully using the desktop Mbed Studio for several weeks with a NUCLEO-F401RE and NUCLEO F446RE. However, when I try connecting to Keil Studio Cloud the hardware is found and successfully connects and it seems to compile on run project but fails shortly after the "Build succeeded" message. This occurs even with a simple example blinky program.

Thus far I've tried a few similar boards. I've updated their firmware to the latest version. I tried changing the connection mode to each of the 4 available options based on suggestions from the Known issues and troubleshooting section of the documentation site, but saw no change.

Each device I have attempted works just fine from the desktop "Mbed Studio", just not when attempting to run a project from the cloud studio. I have tried using Chrome, and Edge as browsers and have even tried disabling my antivirus and firewall but so far the issue remains consistent.

The Arm Keil Studio Pack installs recommended extensions for embedded and IoT software development on Arm-based microcontroller (MCU) devices. The extensions included are listed in the Details of the pack in Visual Studio Code and described in Extensions available in the pack.

The main Keil Studio extensions available with the pack are Arm CMSIS Solution, Arm Device Manager, and Arm Debugger. The extensions enable you to manage CMSIS solutions (csolution projects), run projects on a hardware device, and undertake debugging. You can use the extensions together or individually.

This README file explains how to install the extensions with Visual Studio Code Desktop. When you have installed the pack, read the documentation available on Arm Developer to get started. You can import a solution example from keil.arm.com, download a μVision project from keil.arm.com, create a solution from scratch, or convert an existing μVision project.

Embedded and IoT software development using CMSIS-Packs and solutions (csolution projects): The Common Microcontroller Software Interface Standard (CMSIS) provides driver, peripheral, and middleware support for thousands of MCUs and hundreds of development boards. Using the csolution project format, you can incorporate any CMSIS-Pack based device, board, and software component into your application. For more information about supported hardware for CMSIS projects, go to the Boards and Devices pages on keil.arm.com. For information about CMSIS-Packs, go to open-cmsis-pack.org.

Enhancement of a pre-existing Visual Studio Code embedded software development workflow: You can adapt USB device management and embedded debug to other project formats (for example, CMake) and toolchains without additional overhead. This use case requires familiarity with Visual Studio Code to configure tasks. See the individual extensions for more details.

Arm Environment Manager (Identifier: arm.environment-manager): This extension installs the tools that you specify in a manifest file in your environment. For example, you can install Arm Compiler for Embedded, CMSIS-Toolbox, CMake, and Ninja to work with CMSIS solutions.

Arm Virtual Hardware (Identifier: arm.virtual-hardware): This extension allows you to manage Arm Virtual Hardware models and run embedded applications on them. An authentication token is required to access the service.

Memory Inspector (Identifier: eclipse-cdt.memory-inspector): This extension allows you to analyze and monitor the memory contents in an embedded system. It helps you to identify and debug memory-related issues during the development phase of your project.

Peripheral Inspector (Identifier: eclipse-cdt.peripheral-inspector): This extension uses System View Description (SVD) files to display peripheral details. SVD files provide a standardized way to describe the memory-mapped registers and peripherals of a microcontroller or a System-on-Chip (SoC).

This extension collects usage telemetry and sends it to Arm to help improve our products. This extension respects the Visual Studio Code telemetry settings described in the Visual Studio Code documentation. Modify telemetry options in the settings menu.

I only use the nano stm32L432.

I currently have about 10 projects.

But when converting to studio keil, none of this works. When will the online mbed compiler stop?

Is there an offline compiler for this problem?

Gr Jos v. Engelen

Hi @Jos_Engelen_van. Do you mean that you have 10 projects that you have imported from the Online Compiler to Keil Studio Cloud? Could you expand a little on the issues you are facing so we can take a look?

this is not error but only a warning. This information want to tell you - Care this is not recommended to use in new programs, because in a future major release (probably something like MbedOS 7) this will be removed.

Just visit the mbed web documentation - Ticker - API references and tutorials Mbed OS 6 Documentation

Examples do not show that, but description yes - Mbed OS Reference TickerBase Class Reference

After following the steps here -bootloader-update/ to change the bootloader to maintenance keil studio keeps on giving me "The connected device is unsupported" and "A problem was detected communicating with the detected device 'DAPLink CMSIS-DAP', it may be in use or need reconnecting"

Very strange, this is the first time I saw this error, may I ask if there are others occupying CMSIS-DAP?

Please try restarting the computer, only open Keil MDK, and try to select CMSIS-DAP as Debugger.

The only thing I can think of is that Keil Studio Cloud does not support the update that changed the board from bootloader to maintenance. My friend got the same board and hers works perfectly. Is there a way to revert the board's original state and get back the old bootloader version?

We do provide this file in our SDK. You can find it under [SDK Install Path]\mspm0_sdk_2_00_01_00\source\ti\devices\msp\m0p\startup_system_files\keil. There you will find the startup files for all of our devices. You can choose the one for your device and add this to your project.

For those who may find this thread / who have a similar issue, this issue is expected to be patched in the next release of the Keil Pack files. If you run into a similar problem, please check to see if the Keil Pack files have been updated since the posting of this comment. If not, please check back once they have been updated.

I have been developing my code on NRF52840 based on nrfsdk v1.7. Since keil free version has a limit of 32kb i am moving my code to VS code. VS by default adds 2.0 latest sdk. But i dont want to use Zephyr rtos. When i try to manually set the sdk to 1.7 the softwares throws error for cmake files. I tried making cmake files and editing json files to work with 1.7. Is there a instruction set for this particular problem?

The nRF Connect for VS Code extension is made for the nRF Connect SDK, and it does not have support for nRF5 SDK. For nRF5 SDK you can either use SEGGER Embedded Studio (SES) or make. For SES you can follow the guide here: Getting started with nRF5 SDK and SES (nRF51 & nRF52 Series). The best guides for using gcc and make are in nRF5 SDK for Thread and Zigbee documentation. The tools and how to do things are the same as in the regular nRF5 SDK, so you can follow these guides and just ignore the parts about downloading the Thread and Zigbee SDK etc. These guides can be found here: Installing the toolchain, Building examples and Running examples.

3a8082e126