Firmware and application cohabitation on the same device

That's a good idea, I'll try that! But I have some libs and I don't have its source code, so I can't define them all in my firmware ASM file. I'll have to make a new ASM file for the application including all firmware variables. Too bad :(
If you do not have the source , you simply CAN NOT do what you want (see below)

Why do have I to set function reentrant? I'm not using any OS, so when I'm running a firmware function, the application can not perform something else.

let us take an example:
BB (bootloader BIOS) is compiled and linked separately, app is compiled and linked separately, all BB global varibales are avoided by the app.

the app
void main (void)
{
U8 var1; // placed by the linker at end of globals
U16 var2; // placed by the linker at end of globals+1
  BBfunc1()
}

void BBfunc1(void)
(

// the BB is not 'aware' that the app placed temp variables by the call tree

U8 bvar1; // placed by the linker at end of globals
U16 bvar2; // placed by the linker at end of globals+1
}

Thus you need reentranr, not for reentancy, but for no call tree.

Erik

That's a good idea, I'll try that! But I have some libs and I don't have its source code, so I can't define them all in my firmware ASM file. I'll have to make a new ASM file for the application including all firmware variables. Too bad :(
If you do not have the source , you simply CAN NOT do what you want (see below)

Why do have I to set function reentrant? I'm not using any OS, so when I'm running a firmware function, the application can not perform something else.

let us take an example:
BB (bootloader BIOS) is compiled and linked separately, app is compiled and linked separately, all BB global varibales are avoided by the app.

the app
void main (void)
{
U8 var1; // placed by the linker at end of globals
U16 var2; // placed by the linker at end of globals+1
  BBfunc1()
}

void BBfunc1(void)
(

// the BB is not 'aware' that the app placed temp variables by the call tree

U8 bvar1; // placed by the linker at end of globals
U16 bvar2; // placed by the linker at end of globals+1
}

Thus you need reentranr, not for reentancy, but for no call tree.

Erik

Ok! Thanks!!

If I specify a new zone for my application's global variable (_IBIT_GROUP_, _DATA_GROUP_, _IDATA_GROUP_, _XDATA_GROUP_), then I don't need to define them as reentrant?

BL51 linker:

XDATA([...], _XDATA_GROUP_ (0x1806))

It will use more memory, but it will be possible to call functions from my library, right?

Damien.

If I specify a new zone for my application's global variable (_IBIT_GROUP_, _DATA_GROUP_, _IDATA_GROUP_, _XDATA_GROUP_), then I don't need to define them as reentrant?
you define functions as reentrant Please read the manual as to how.

Erik

I'm sorry, I don't understand "Please read the manual as to how".

Does it mean "Read the manual to know how reentrant function works, please"?

Then I'm sorry to disappoint you, but I did. From this article http://www.keil.com/support/docs/1854.htm , I understand that normal function use _DATA_GROUP_ for local variables.

From this article: http://www.keil.com/support/man/docs/c51/c51_le_reentrantfuncs.htm
Reentrant directive inform the compiler/linker to not use _DATA_GROUP_ but a separate stack (XDATA for me, because I use LARGE model).

So I thought that if I declare two different _DATA_GROUP_, one for my firmware, and one for my application, I don't need reentrant functions. Let me explain:

FIRMWARE

void BBfunc1(void)
(
   U8 bvar1;
   U16 bvar2;
}

APPLICATION

void main (void)
{
   U8 var1;
   U16 var2;

      BBfunc1()
}

I specify the _XDATA_GROUP_ (LARGE model) for application at 0xEC00

_XDATA_GROUP_ for the firmware is placed by the linker, I do not give any specification: 0x1800 is the address of the _XDATA_GROUP_ of the firmware.

Once complied/linked, I'll have:
FIRMWARE

SEGMENT                          XDATA_GROUP
  +--> CALLED SEGMENT          START    LENGTH
----------------------------------------------
?PR?BBFUNCT1?FIRMWARE_FUNC     1808H    0006H

APPLICATION

SEGMENT                          XDATA_GROUP
  +--> CALLED SEGMENT          START    LENGTH
----------------------------------------------
?PR?MAIN?MAIN                  EC00H    0006H
  +--> ?PR?BBFUNCT1?FIRMWARE_FUNC

==> var1/var2 and bvar1/bvar2 are not located at the same address because _XDATA_GROUP_ are not located at the same address.

==> Do I still need reentrant functions?? I don't think so. Am I wrong?

Damien.

I just read up on reentrant (which I never have or would use) and saw the thing about 'stack location'. I, incorrectly, assumed it was like it was once (passing parametres on the internal st6ack) MY BAD.

Now, for your thingy you need contact Keil support (since you use allmost 64k, you must have a license) and find out how to avoid having separate stack pointers.

Erik