Search options (Page 1 of 6)

As I said, the error message is supposed to be generated when a recursive call is found. If it is not the case, it would be nice to send us an example to analyze the situation.
On the principle, when the warning is generated, the overlay is not applied to the branch that is being analyzed. Therefore, YES, the warning can be just ignored. The warning means that the resulting overlay rules could be better, but with a potential risk. Giving up the overlay mechanism is not risky, but the overall data consumption could be higher than the optimal solution.

Thanks for the report. We will fix it (but the fix will not be available in the very next version that is already finalized).
The issue is caused by a combination of several syntactic errors. Typically, adding any instruction after the last if-statement (if(iXhome==1)) will fix the problem. For example a null instruction  (semicolon).

We'll check and fix this issue for the next release (that will come soon).

The general rule for the common binary operators is: when two operators signed/unsigned of the same size are used, both are converted to the 'unsigned' type, and the operation is performed as an unsigned operation.
When the type size are different, the 'bigger' type is choosen (whatever the 'signed' attribute).

Yes, this feature has been implemented under RIDE7. It will be available first for the next 'Primer'.

On the principle, the data overlay does not depend on the bankswitching. These are two independent mechanisms.... I made a simple try, and I don't see the difference. Could you send us a small example that shows the issue ?

Bob,

Behnaz is not at the office this afternoon and I cannot check with her. I read what you wrote, checked with the RIDE 6 version installed on my computer, and I see an extra command 'Code Coverage' (that opens a sub-menu') in the popup menu of the editor view. The sub-menu provides the commands  "Show", "Create a Report" and "Reset".
The 'Create Report' opens a text file that looks like:

     [0x0001]        for (i = 0; i <= SIZE; i++)
                        {
     [0x1491]           if (flags[i])      /* found a prime */
                           {
     [0x0506]              prime = i + i + 3;   /* twice index + 3 */
               
     [0x0506]              for (k = i + prime; k <= SIZE; k += prime)
                              {
     [0x3A97]                 flags[k] = FALSE;   /* kill all multiples */
                              }
               
     [0x0506]              count++;      /* primes found */
                           }
                        }

I don't if it could help.

I believe that, for RIDE6) script files can be executed for some packages only (RKit Entreprise).
Could you let me know if you can (in debug mode) load the following script (and if it is properly executed).

void main ()
   {
   int i;
   i = 0;
   while ( i < 10 ) 
      {
      DebugStepInto(1);
      i = i+1;
      }
   }

To execute it, save the contents into a file named test.wsc, then execute the command RideScript | Load file.
If it works, I will try to write for you a small script that creates a simple report.

In the source view (editor), you have (popup menu) a command that allows to display code coverage, and also another command that creates another report. This report will be a copy of the source file, with the code coverage information on the left side. Don't know if it could help...

Another possibility would be to create a small script to generate a customized report.

The STR912 board used to be delivered with a REVA2 (that has the 20 pin connector on the mother board). There is also a footprint on the daughter board for a mictor connector (to connect JTAGJet-ETM), but the mictor connector was soldered only when sold with a JTAGJet-ETM.
You will find the pinout of the REVA schematic.
For the SWD connection, see also: http://raisonance-forum.xsalto.com/view … hp?id=2449

Ok, I look at the email and I will answer.

I thought you fixed the issue when fixing:
  if(ident & 0x7F == node_id || ident==0 ) //node_id is 0x31
Do you have another problem?
If you have a problem with interrupt, I suggest that you disable the optimization option that make the compiler using the 'Absolute Registers".

ok... I believe that the parenthesis could be NOT supported in this case... (for the directory name).