Discussion in 'Software' started by hiabcwelcome. Keil Tools.ini' does not contain a path. You have selected a device where no toolchain has been installed. Mar 22, 2018 - I recently installed GNU ARM Embedded Toolchain on windows plataform to use it with Eclispe Neon.3. I had to install 32 bit version because I. Nordic Q&A Keil toolchain/compiler configurations incorrect. MDK-Lite Version: 4.72.1.0 Toolchain Path: C: Keil ARM. 1 Hardware-Breakpoints: 4 Software.

• Software Keil Tools Ini Toolchain Not Installed

Let’s explain now how to configure Proteus VSM to work with C Keil IDE. The interaction beetwen Proteus and C Keil is achieved via the Virtual Debug Monitor (VDM) interface. if Keil C and Proteus are properly installed , copy the dll VDM51.dll from for example C: Program FileLabcenter Electronics Proteus X ProfessionalMODELSVDM5 1. Dll to the C: Program Fileskeil C51BIN directory.

use Notepad for editing the file C:keilTOOLS. INI file

under the section [C51] you’ ll find the line

TDRV0=BINMON51.DLL (“Keil Monitor-51 Driver”)

immediately below add the line that specifies the location of the dll

TDRV1 = BINVDM51.DLL (“Proteus VSM Monitor-51 Driver”)

then save the tools.ini file.

Now open the Keil IDE to create a new project

select the CPU AT89C51

the Source file is the following:

# define LEDS 6

# include “reg5 1. h”

unsigned char code Select [] = {0x0 1, 0x02, 0x04, 0x08, 0x1 0,0 x20};

unsigned char code LED_CODES [] =

{0xc0, 0xF9, 0xA4, 0xB0, 0x99, // ​​0-4

0x92, 0x82, 0xF8, 0x80, 0x90, // ​​5-9

0 x 8 8, 0 x 8 3, 0 x C 6, 0 x A 1, 0 x 8 6, // ​​A, b, C, d, E

0x8E, 0xFF, 0x0C, 0x89, 0x7F, 0xBF // F, space , P, H,., -};

void main ()

{

char i = 0; long intj; while (1)

{P2 = 0;

Software Keil Tools Ini Toolchain Not Installed

P1 = LED_CODES ;

P2 = Select ;

for (j = 3000; j> 0; j –); // This LED models pulsed light , pulsed light by the //i-th bit , it will modify cycles , changing light delay before the next one , //get a different display.

i ++;

if (i> 5) i = 0;

}

}

click the “Project menu/Options for Target” option

In the dialog box that appears, on “Debug” tab, select “Proteus VSM Monitor-51 Driver” as shown in the image

Click “Use” ,then click “Setting” button to set the communication interface, in “Host” add “127.0.0.1”. As number of port edit 8000.Finally, compile the project.

Proteus settings

Into the Proteus ISIS, click the left mouse button on the menu “Debug”, select “use remote debuger monitor”, as shown below.

Click the Start button to run the simulation, we can observe each pin frequency variation, red for high power frequency, blue represents low-frequency.

Hi,

I am trying to setup programming with the EFM8 busy bee + SiLabs USB Debug Adapter. I have installed the 8051 IDE, but I can't get the Keil toolchain to install. Please see image. I believe this is the correct path to the toolchain, but the 'Detected toolchains' never populates. I am trying directories:

/Applications/Simplicity Studio.app/Contents/Eclipse/developer/toolchains/keil_8051/9.53

/Applications/Simplicity Studio.app/Contents/Eclipse/developer/toolchains/keil_8051

/Applications/Simplicity Studio.app/Contents/Eclipse/developer/toolchains

...and nothing seems to detect. I tried on both OSX and on Windows 7. Simplicity Studio is v4 and fully updated.

Thanks!

Derek

• 8-bit MCUs
• Development Environments
• Discussion Forums
• Simplicity Studio
• Answered

• 
  

  Just for the record, attached is what it looks like in Windows

• Employee
  
  

  Hi @perlmonkey,

  Please launch the Package Manager (Update icon) and verify that the 8051 IDE is installed from the Tools tab:

  Thank you,

  jpitt

• 
  

  That was it. I had blue giga IDE installed (or something like that for BGM113 project), installed the 8051 IDE, then it recognized the keil toolchain.

  -would be nice to have some kind of warning or something.

  Thanks.

  Derek

• Employee
  
  

  Hi @perlmonkey,

  I'm glad that solved the issue for you. If the EFM8 product family is selected on the Install Wizard 'Select by Product Group' tab when Simplicity Studio is first installed (or later if no EFM8 support was installed initally) then that package should have been automatically installed or at least selected to be installed.

  Thank you,

  jpitt