This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Firmware and application cohabitation on the same device

Hello,

I would like to create a firmware and an application running on the same device.

The application needs to call some functions of the firmware. The application can be updated whereas the firmware is still the same.

Therefore, i want to have 2 projects: one for the firmware (C coded) and one for the application (C coded).

I have seen that it's possible to forbid idata, xdata and code area in order to prevent the application to overwrite the firmware and its variables, but I have no clues on how to give my firmware prototype to my application.
Of course parameters and functions' addresses must map with the firmware mapping.

Does anyone have an idea how I can do this?

Thanks for your help!
Damien.

Parents
  • You started with "want to" and ended with "need to".

    If you only "want to" let the firmware control the hardware, then you only "want to" implement an interface for the two to interact.

    It is only when you have a hard requirement to control the hardware from your boot loader/monitor/bios that you "need" the interaction part.

    Why do I mention this? It is absolutely vital to never mix up "want" and "need" in a development process. Such a tiny little error may multiply the development and/or product cost by a very high factor!

Reply
  • You started with "want to" and ended with "need to".

    If you only "want to" let the firmware control the hardware, then you only "want to" implement an interface for the two to interact.

    It is only when you have a hard requirement to control the hardware from your boot loader/monitor/bios that you "need" the interaction part.

    Why do I mention this? It is absolutely vital to never mix up "want" and "need" in a development process. Such a tiny little error may multiply the development and/or product cost by a very high factor!

Children