unspoorted signal function in keil ini file

MDK ARM version 5.24.1

this is the .ini file that I am used as example:

/*-------------------------------------------*/
/* Create a Signal Function */
/*-------------------------------------------*/

signal void int0_signal (void) {
while (1) {

twatch (200000);
}
}

int0_signal();

//Reset
//RESET

// Debug session is ready

G

error message in keil log: 

signal void int0_signal (void) {

 *** error 76: command not supported 

MDK ARM version 5.24.1

this is the .ini file that I am used as example:

/*-------------------------------------------*/
/* Create a Signal Function */
/*-------------------------------------------*/

signal void int0_signal (void) {
while (1) {

twatch (200000);
}
}

int0_signal();

//Reset
//RESET

// Debug session is ready

G

error message in keil log: 

signal void int0_signal (void) {

 *** error 76: command not supported 

Still not entirely clear how much of that is actually in your Signal function.

Wess said:

int0_signal();

Is that supposed to be invoking the function?

The manual shows no semicolon:

http://www.keil.com/support/man/docs/uv4/uv4_df_signalfunctions.htm

Have you tried do it interactively?

/*-------------------------------------------*/
/* Create a Signal Function                  */
/*-------------------------------------------*/
	
signal void int0_signal (void) {
  while (1) {
      
		twatch (200000);
  }
}

int0_signal();

//Reset
//RESET

// Debug session is ready

G

Basically when I start debug session keil will include this initialization file and at some point it will throw the error mentioned above when parsing this initialization script because of this signal function

I tried also to invoke this signal function in keil command line but then I got the error of undefined identifier

The guide that you sent to me I already took a look into it but doesn't work, for some reason keil doesn't accept this signal keyword in initialization script

again, is the semicolon significant?

In Keil command window when invoking the signal function I removed the semicolon and getting unkown identified for the signal function

and it works with the semicolon when you do it interactively?

it doesn't work also, in all case getting undefined identified

is the signl function usable with real hardware or can be only used in simulation mode?

it look like you don't understand what is going on!

Other thing, I have been working a lot with arm based tools and in many cases arm claim that some features are supported and it turns out that it doesn't work really 

We expect as customer of arm paying a lot of money for licensing and tool to get more credibility when it come to some basic things that they claim it does exist and work in their tool!!!

No - I don't know what's going on!

Trying to remotely debug stuff like this is always difficult - especially when the descriptions of what's happening aren't entirely clear.

You may be right that it only works in Simulation - have you tried that to confirm ... ?

Note that this is a user-to-user forum.

If you have a valid licence, you can contact Keil/ARM direct for support ...

http://www.keil.com/support/man/docs/uv4/uv4_e076.htm

That's not quite the same as Wess showed - is the doc out-of-date?

So you are saying the Signal Functions can only be used in Simulation?

If so, that should be clearly stated in the docs!

Currently, it says (my emphasis):

Signal Functions repeat operations in the background while µVision runs the target program. They help simulating and testing ...

which does suggest that they are not limited just to simulation.

For version 5.24.1 it is VERY clear that signal functions are not supported in Target Mode (i.e. it is only supported in simulation mode)

I don't believe Keil has any intent to support Signal Functions in Target Mode ever.  Causing Physical changes to inputs such as A/D converters and Digital input pins is not really something that can currently be done without external hardware to do it. 

http://www.keil.com/support/man/docs/uv4/uv4_simulation.htm

. 

.