Guiliani::Porting

when Guiliani is currently not supported for a specific platform, it can be of course ported to this platform.

as a rule of thumb porting Guiliani to a new platform means an effort of 2-3 months. this includes the creation of platform-specific libraries using BSP/OS and the desired toolchain. however, this effort can be influenced by various factors.

examples:

  • when using Linux as the target operating system there might be no additional effort for integrating the BSP, since Linux encapsulates these stuff. the rest which needs to be done is integrating the specific toolchain, if it is not yet supported, which means an effort of around 1 month.
  • when switching an already supported platform to a new toolchain, e.g. GCC to IAR the effort might also be around 1 month, provided the BSP/OS-combination already supports this toolchain
  • when switching an already supported platform to a new board, e.g. RZ/A1 to iMX6, this means integrating a new BSP. although the used operating system stays the same, this will still mean an effort of 2-3 months, provided the operating system is already supporting the new BSP.
  • when switching an already suppported platform to a new operating system, e.g. FreeRTOS to SafeRTOS, this means using functions of this new operating system. although the BSP stays the same, this will still mean an effort of 2-3 months, provided the BSP is designed to support this operating system.

NOTE: the listed efforts should be regarded as a reference point for the dimensions. the real effort for a specific platform might be different, regarding any special factors.