[Doxygen-users] another rtf example, why is this happening.

[woody <kn...@re...>]

::Some more items that are missing
 From the .rtf file

These routines are interrupt handlers, and the last routine is code to 
write a byte of data to the flash on a Silabs 8051 processor.
You will notice that the line     "References, and . " Don't have anything 
listed..  in the first case it should be

"References bttn1_debounce and bcount" OR  since this is an embedded 
project, EX0 is defined in a file that was not processed, but represents a 
specific bit in a specific register,
so it should also be included, even though it is not listed anywhere other 
than within the body of this code, it should be picked up because of that.
It is not a local
it is a global, but doxygen does not have knowledge of it.
but it *is* referenced within the function.....

References:
bttn1_debounce
EX0
bcount


void button_scan_interrupt_1 ()

Definition at line 5719 of file xxx.
References , and .
  5720     {
  5721     EX0=0;// disable any further interrupts from this pin to let 
bouncing settle
  5722     bttn1_debounce=20;                 // 20 miliseconds
  5723     bcount=0;                          // start the 2 x per second 
counter at 0
  5724     }
::void button_scan_interrupt_2 ()

Definition at line 5734 of file xxx.
References , and .
  5735     {
  5736     EX1=0;// disable any further intterupts from this pin to let 
bouncing settle
  5737     bttn2_debounce=20;                 // 20 miliseconds
  5738     bcount=0;                          //
  5739     }


::char erase_flash (unsigned char *  page_address) 
<<<<<<<<<<<<<<<<<<<<<<<<?????????????????  This got listed but without 
anything else.

::void FLASH_ByteWrite (unsigned int  addr, char  byte)

Definition at line 8420 of file xxx.
References .
Referenced by , and .
  8421 {
  8422     saved_ie=IE;
  8423     EA = 0;                    // disable interrupts
  8424     PSCTL = 0x00;              // MOVX writes target XRAM to keep 
interrupt from happening
  8425     EA=0;
  8426     RSTSRC = 0x02;                   // enable VDD monitor as a 
reset source
  8427     FLKEY = 0xa5;              // 1st FLASH key sequence
  8428     FLKEY = 0xf1;              // 2nd FLASH key sequence
  8429     PSCTL = 0x01;              // MOVX writes target FLASH memory
  8430     ((unsigned char volatile xdata *) 0)[addr]=byte;
  8431     PSCTL = 0x00;              // MOVX writes target XRAM
  8432     IE=saved_ie;
  8433 }

Again, saved_ie is a global, so not sure why it got missed.

This function is called by  configure_me, which is in turn called from main.
It is also called by main in a different place,

The caller graph which could not be pasted here, shows
main calling configure_me and configure_me calling FLASH_ByteWrite, AND it 
shows a line from main directly to FLASH_ByteWrite, so the caller graph is 
correct.


Based on this, the lines should look like:
void FLASH_ByteWrite (unsigned int  addr, char  byte)

Definition at line 8420 of file medbest_310_o_split.c.
References saved_ie
Referenced by configure_me  and main.

Why is this happening