Keil 4 to Kiel 5 upgrade

[brian fleming]

I am rebuilding my computer after experiencing a corrupt boot sector and am reinstalling all my apps.  I am moving from Kiel 4 to Kiel 5.  My project loads, but it says that it needs the ARM Tool chain which is not installed. I installed the Toolchain on WIN 10 and it seemed to install smoothly, however in the Project menu, the Options menu item and those below it are all disabled.  Can you guide me through this? 

I notice in the readme.txt in * Architecture options usage * there is a considerable amount ot config options, is this a necessary requirement for the nRF51422 ?  

Thanks,

Brian Fleming

[Amanda Hsieh]

Hi,

Please contact Keil support for tool's problem

http://www.keil.com/support/

 

I cannot find the readm.txt with that statement.

Where do you get the readme.txt? Where do you get? 

 

-Amanda H.

[brian fleming]

Hello here is the readme which popped up after the install.

Fullscreen Toolchain.txt Download

GNU Tools for Arm Embedded Processors
Version: 8

Table of Contents
* Installing executables on Linux
* Installing executables on Mac OS X
* Installing executables on Windows
* Invoking GCC
* Architecture options usage
* C Libraries usage
* Linker scripts & startup code
* Samples
* GDB Server for CMSIS-DAP based hardware debugger

* Installing executables on Linux *
Unpack the tarball to the install directory, like this:
$ cd $install_dir && tar xjf gcc-arm-none-eabi-*-yyyymmdd-linux.tar.bz2

If you want to use gdb python build (arm-none-eabi-gdb-py), you'd
install python2.7.

For some Ubuntu releases, the toolchain can also be installed via
Launchpad PPA at https://launchpad.net/~team-gcc-arm-embedded/+archive/ubuntu/ppa.

* Installing executables on Mac OS X *
Unpack the tarball to the install directory, like this:
$ cd $install_dir && tar xjf gcc-arm-none-eabi-*-yyyymmdd-mac.tar.bz2

* Installing executables on Windows *
Run the installer (gcc-arm-none-eabi-*-yyyymmdd-win32.exe) and follow the
instructions. The installer can also be run on the command line. When run on
the command-line, the following options can be set:
  - /S Run in silent mode
  - /P Adds the installation bin directory to the system PATH
  - /R Adds an InstallFolder registry entry for the install.

For example, to install the tools silently, amend users PATH and add registry
entry:
> gcc-arm-none-eabi-*-yyyymmdd-win32.exe /S /P /R

The toolchain in windows zip package is a backup to windows installer for
those who cannot run installer.  We need decompress the zip package
in a proper place and then invoke it following instructions in next section.

To use gdb python build (arm-none-eabi-gdb-py), you need install 32 bit
python2.7 no matter 32 or 64 bit Windows. Please get the package from
https://www.python.org/download/.

* Invoking GCC *
On Linux and Mac OS X, either invoke with the complete path like this:
$ $install_dir/gcc-arm-none-eabi-*/bin/arm-none-eabi-gcc

Or set path like this:
$ export PATH=$PATH:$install_dir/gcc-arm-none-eabi-*/bin
$ arm-none-eabi-gcc

On Windows (although the above approaches also work), it can be more
convenient to either have the installer register environment variables, or run
INSTALL_DIR\bin\gccvar.bat to set environment variables for the current cmd.

For windows zip package, after decompression we can invoke toolchain either with
complete path like this:
TOOLCHAIN_UNZIP_DIR\bin\arm-none-eabi-gcc
or run TOOLCHAIN_UNZIP_DIR\bin\gccvar.bat to set environment variables for the
current cmd.

* Architecture options usage *

This toolchain is built and optimized for Cortex-A/R/M bare metal development.
the following table shows how to invoke GCC/G++ with correct command line
options for variants of Cortex-A/R and Cortex-M architectures.

--------------------------------------------------------------------------
| Arm core   | Command Line Options                       | multilib     |
|------------|--------------------------------------------|--------------|
| Cortex-M0+ | -mthumb -mcpu=cortex-m0plus                | thumb        |
| Cortex-M0  | -mthumb -mcpu=cortex-m0                    | /v6-m        |
| Cortex-M1  | -mthumb -mcpu=cortex-m1                    |              |
|            |--------------------------------------------|              |
|            | -mthumb -march=armv6-m                     |              |
|------------|--------------------------------------------|--------------|
| Cortex-M3  | -mthumb -mcpu=cortex-m3                    | thumb        |
|            |--------------------------------------------| /v7-m        |
|            | -mthumb -march=armv7-m                     |              |
|------------|--------------------------------------------|--------------|
| Cortex-M4  | -mthumb -mcpu=cortex-m4                    | thumb        |
| (No FP)    |--------------------------------------------| /v7e-m       |
|            | -mthumb -march=armv7e-m                    |              |
|------------|--------------------------------------------|--------------|
| Cortex-M4  | -mthumb -mcpu=cortex-m4 -mfloat-abi=softfp | thumb        |
| (Soft FP)  | -mfpu=fpv4-sp-d16                          | /v7e-m       |
|            |--------------------------------------------| /fpv4-sp     |
|            | -mthumb -march=armv7e-m -mfloat-abi=softfp | /softfp      |
|            | -mfpu=fpv4-sp-d16                          |              |
|------------|--------------------------------------------|--------------|
| Cortex-M4  | -mthumb -mcpu=cortex-m4 -mfloat-abi=hard   | thumb        |
| (Hard FP)  | -mfpu=fpv4-sp-d16                          | /v7e-m       |
|            |--------------------------------------------| /fpv4-sp     |
|            | -mthumb -march=armv7e-m -mfloat-abi=hard   | /hard        |
|            | -mfpu=fpv4-sp-d16                          |              |
|------------|--------------------------------------------|--------------|
| Cortex-M7  | -mthumb -mcpu=cortex-m7                    | thumb        |
| (No FP)    |--------------------------------------------| /v7e-m       |
|            | -mthumb -march=armv7e-m                    |              |
|------------|--------------------------------------------|--------------|
| Cortex-M7  | -mthumb -mcpu=cortex-m7 -mfloat-abi=softfp | thumb        |
| (Soft FP)  | -mfpu=fpv5-sp-d16                          | /v7e-m       |
|            |--------------------------------------------| /fpv4-sp     |
|            | -mthumb -march=armv7e-m -mfloat-abi=softfp | /softfp      |
|            | -mfpu=fpv5-sp-d16                          |              |
|            |--------------------------------------------|--------------|
|            | -mthumb -mcpu=cortex-m7 -mfloat-abi=softfp | thumb        |
|            | -mfpu=fpv5-d16                             | /v7e-m       |
|            |--------------------------------------------| /fpv5        |
|            | -mthumb -march=armv7e-m -mfloat-abi=softfp | /softfp      |
|            | -mfpu=fpv5-d16                             |              |
|------------|--------------------------------------------|--------------|
| Cortex-M7  | -mthumb -mcpu=cortex-m7 -mfloat-abi=hard   | thumb        |
| (Hard FP)  | -mfpu=fpv5-sp-d16                          | /v7e-m       |
|            |--------------------------------------------| /fpv4-sp     |
|            | -mthumb -march=armv7e-m -mfloat-abi=hard   | /hard        |
|            | -mfpu=fpv5-sp-d16                          |              |
|            |--------------------------------------------|--------------|
|            | -mthumb -mcpu=cortex-m7 -mfloat-abi=hard   | thumb        |
|            | -mfpu=fpv5-d16                             | /v7e-m       |
|            |--------------------------------------------| /fpv5        |
|            | -mthumb -march=armv7e-m -mfloat-abi=hard   | /hard        |
|            | -mfpu=fpv5-d16                             |              |
|------------|--------------------------------------------|--------------|
| Cortex-M23 | -mthumb -mcpu=cortex-m23                   | thumb        |
|            |--------------------------------------------| /v8-m.base   |
|            | -mthumb -march=armv8-m.base                |              |
|------------|--------------------------------------------|--------------|
| Cortex-M33 | -mthumb -mcpu=cortex-m33                   | thumb        |
|  (No FP)   |--------------------------------------------| /v8-m.main   |
|            | -mthumb -march=armv8-m.main                |              |
|------------|--------------------------------------------|--------------|
| Cortex-M33 | -mthumb -mcpu-cortex-m33                   | thumb        |
| (Soft FP)  | -mfloat-abi=softfp -mfpu=fpv5-sp-d16       | /v8-m.main   |
|            |--------------------------------------------| /fpv5-sp     |
|            | -mthumb -march=armv8-m.main                | /softfp      |
|            | -mfloat-abi=softfp -mfpu=fpv5-sp-d16       |              |
|            |--------------------------------------------|--------------|
|            | -mthumb -march=armv8-m.main                | thumb        |
|            | -mfloat-abi=softfp -mfpu=fpv5-d16          | /v8-m.main   |
|            |                                            | /fpv5        |
|            |                                            | /softfp      |
|------------|--------------------------------------------|--------------|
| Cortex-M33 | -mthumb -mcpu=cortex-m33                   | thumb        |
| (Hard FP)  | -mfloat-abi=hard -mfpu=fpv5-sp-d16         | /v8-m.main   |
|            |--------------------------------------------| /fpv5-sp     |
|            | -mthumb -march=armv8-m.main                | /hard        |
|            | -mfloat-abi=hard -mfpu=fpv5-sp-d16         |              |
|            |--------------------------------------------|--------------|
|            | -mthumb -march=armv8-m.main                | thumb        |
|            | -mfloat-abi=hard -mfpu=fpv5-d16            | /v8-m.main   |
|            |                                            | /fpv5        |
|            |                                            | /hard        |
|------------|--------------------------------------------|--------------|
| Cortex-R4  | [-mthumb] -march=armv7-r                   | thumb        |
| Cortex-R5  |                                            | /v7-ar       |
| Cortex-R7  |                                            |              |
| Cortex-R8  |                                            |              |
| (No FP)    |                                            |              |
|------------|--------------------------------------------|--------------|
| Cortex-R4  | [-mthumb] -march=armv7-r -mfloat-abi=softfp| thumb        |
| Cortex-R5  | -mfpu=vfpv3-d16                            | /v7-ar       |
| Cortex-R7  |                                            | /fpv3        |
| Cortex-R8  |                                            | /softfp      |
| (Soft FP)  |                                            |              |
|------------|--------------------------------------------|--------------|
| Cortex-R4  | [-mthumb] -march=armv7-r -mfloat-abi=hard  | thumb        |
| Cortex-R5  | -mfpu=vfpv3-d16                            | /v7-ar       |
| Cortex-R7  |                                            | /fpv3        |
| Cortex-R8  |                                            | /hard        |
| (Hard FP)  |                                            |              |
|------------|--------------------------------------------|--------------|
| Cortex-R52 | [-mthumb] -mcpu=cortex-r52                 | thumb        |
| (No FP)    |--------------------------------------------| /v7-ar       |
|            | [-mthumb] -march=armv8-r+crc               |              |
|------------|--------------------------------------------|--------------|
| Cortex-R52 | [-mthumb] -mcpu=cortex-r52                 | thumb        |
| (Soft FP)  | -mfloat-abi=softfp -mfpu=neon-fp-armv8     | /v7-ar       |
|            |--------------------------------------------| /fpv3        |
|            | [-mthumb] -march=armv8-r+crc               | /softfp      |
|            | -mfloat-abi=hard -mfpu=neon-fp-armv8       |              |
|------------|--------------------------------------------|--------------|
| Cortex-R52 | [-mthumb] -mcpu=cortex-r52                 | thumb        |
| (Hard FP)  | -mfloat-abi=hard -mfpu=neon-fp-armv8       | /v7-ar       |
|            |--------------------------------------------| /fpv3        |
|            | [-mthumb] -march=armv8-r+crc               | /hard        |
|            | -mfloat-abi=hard -mfpu=neon-fp-armv8       |              |
|------------|--------------------------------------------|--------------|
| Cortex-A*  | [-mthumb] -march=armv7-a                   | thumb        |
| (No FP)    |                                            | /v7-ar       |
|------------|--------------------------------------------|--------------|
| Cortex-A*  | [-mthumb] -march=armv7-a -mfloat-abi=softfp| thumb        |
| (Soft FP)  | -mfpu=vfpv3-d16                            | /v7-ar       |
|            |                                            | /fpv3        |
|            |                                            | /softfp      |
|------------|--------------------------------------------|--------------|
| Cortex-A*  | [-mthumb] -march=armv7-a -mfloat-abi=hard  | thumb        |
| (Hard FP)  | -mfpu=vfpv3-d16                            | /v7-ar       |
|            |                                            | /fpv3        |
|            |                                            | /hard        |
--------------------------------------------------------------------------

* C Libraries usage *

This toolchain is released with two prebuilt C libraries based on newlib:
one is the standard newlib and the other is newlib-nano for code size.
To distinguish them, we rename the size optimized libraries as:

  libc.a --> libc_nano.a
  libg.a --> libg_nano.a

To use newlib-nano, users should provide additional gcc compile and link time
option:
 --specs=nano.specs

At compile time, a 'newlib.h' header file especially configured for newlib-nano
will be used if --specs=nano.specs is passed to the compiler.

Nano.specs also handles two additional gcc libraries: libstdc++_nano.a and
libsupc++_nano.a, which are optimized for code size.

For example:
$ arm-none-eabi-gcc src.c --specs=nano.specs $(OTHER_OPTIONS)

This option can also work together with other specs options like
--specs=rdimon.specs

Please note that --specs=nano.specs is a both a compiler and linker option.  Be
sure to include in both compiler and linker options if compiling and linking
are separated.

** additional newlib-nano libraries usage

Newlib-nano is different from newlib in addition to the libraries' name.
Formatted input/output of floating-point number are implemented as weak symbol.
If you want to use %f, you have to pull in the symbol by explicitly specifying
"-u" command option.

  -u _scanf_float
  -u _printf_float

e.g. to output a float, the command line is like:
$ arm-none-eabi-gcc --specs=nano.specs -u _printf_float $(OTHER_LINK_OPTIONS)

For more about the difference and usage, please refer the README.nano in the
source package.

Users can choose to use or not use semihosting by following instructions.
** semihosting
If you need semihosting, linking like:
$ arm-none-eabi-gcc --specs=rdimon.specs $(OTHER_LINK_OPTIONS)

** non-semihosting/retarget
If you are using retarget, linking like:
$ arm-none-eabi-gcc --specs=nosys.specs $(OTHER_LINK_OPTIONS)

* Linker scripts & startup code *

Latest update of linker scripts template and startup code is available on
https://developer.arm.com/embedded/cmsis

* Samples *
Examples of all above usages are available at:
$install_dir/gcc-arm-none-eabi-*/share/gcc-arm-none-eabi/samples

Read readme.txt under it for further information.

* GDB Server for CMSIS-DAP based hardware debugger *
CMSIS-DAP is the interface firmware for a Debug Unit that connects
the Debug Port to USB.  More detailed information can be found at
http://www.keil.com/support/man/docs/dapdebug/.

A software GDB server is required for GDB to communicate with CMSIS-DAP based
hardware debugger.  The pyOCD is an implementation of such GDB server that is
written in Python and under Apache License.

For those who are using this toolchain and have board with CMSIS-DAP based
debugger, the pyOCD is our recommended gdb server.  More information can be
found at https://github.com/mbedmicro/pyOCD.

[brian fleming]

As you know I am not an expert at setting up keil project, but I am wondering since the 'main porogram' compiles that ther is some thing wrong with the configuration or setup of the sample device.

[Amanda Hsieh]

Hi Brian, 

You should add to the "Include paths" in the Option for target -> C/C++ tab as 

-Amanda H.

[brian fleming]

Thank you again for your continuing support!

I copied and pasted the Processor Symbols/Define and the Include Paths from the nrf51422_xxac to the soft device C/C++ and now I am seeing this error:

Rebuild started: Project: ble_app_uart_pca10028_s130
*** Using Compiler 'V5.06 update 6 (build 750)', folder: 'C:\Keil_v5\ARM\ARMCC\Bin'
Rebuild target 'flash_s130_nrf51_2.0.1_softdevice'
compiling main.c...
linking...
..\..\..\..\..\..\components\softdevice\s130\hex\s130_nrf51_2.0.1_softdevice.sct(7): error: L6236E: No section matches selector - no section to be FIRST/LAST.
Not enough information to list image symbols.
Not enough information to list load addresses in the image map.
Finished: 2 information, 0 warning and 1 error messages.
"..\..\..\..\..\..\components\softdevice\s130\hex\s130_nrf51_2.0.1_softdevice.hex" - 1 Error(s), 0 Warning(s).

[Amanda Hsieh]

Hi Brian,

Did you add startup files, arm_startup_nrf51.s and system_nrf51.c? You can add them into the Device (green) folder under the project or go through Project > Manage > Run Time Environment. 

You also could try the suggestion in this thread. 

--

You should in general always use the softdevice that comes with the sdk version you are using (check the folder: nRF5_SDK_12.3.0_d7731ad\components\softdevice\s130\hex). You never want to compile the softdevice. 

If you go back to the softdevice hex file folder, you notice that the softdevice hex file has become a Windows Script component now. Delete all the files that were created in that folder, download the correct softdevice hex file & put it back in that folder.

Here is a link to the correct softdevice needed:

s130_nrf51_2.0.1_softdevice.hex

Once you have done this, erase the nrf51 chip, program the chip with the softdevice hex file (Flash -> Download tab or press F8 instead of F7) & then go back to the application & flash the program to the nrf51.

-Amanda H.

[brian fleming]

For your first paragraph, the files you described were there.

Second paragraph, I saved (and deleted) the files in a sub-folder, and copied the .hex file from a backup and placed it in the hex folder.  I can now upload the soft device and the main app to the nRF51 Development Kit and it seems to work.

Thanks for the tip about not compiling the soft device.

I think everything has been resolved.

Thanks, 

Brian Fleming

[Amanda Hsieh]

Hi Brian,

Good to hear the success and happy to support this case.

Please kindly verify the answers as the solutions. Thanks.

-Amanda H.