• State Accepted Answer
  • Locked Locked
  • Replies 9 replies
  • Subscribers 21 subscribers
  • Views 4616 views
  • Users 0 members are here
Options
Related
How was your experience today?
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

Specific migration related questions from 5.06 to 6.15

Alam

Hello support team and dear fellow engineers,

Brief: There exists an SDK based on the toolchain v5.06, the target is to migrate the sdk to toolchain v6.15. I am only interested in keil armcc toolchain migration to armclang toolchain at this moment.  

I have already looked around the community and the migration application note. Unfortunately, I could not find an answer for the following questions.

Would you let me know how to fix the following issues:

 1. --bss_threshold=0 is not supported in armclang compiler v6.15, what is the equivalent command should be used in a project?

 2. --feedback=".\unused_SoC.txt" is not supported in armclang compiler v6.15, what is the equivalent command should be used in a project?

 3. Scatter file:

Usecase: How to include directory path in v6.15 in a scatterfile?

v5.06

#! armcc -E -I .\,.\..,.\..\sdk\HAL_common_config,.\..\..\..\sdk\HAL_partnum_config\ --cpu Cortex-M0+

v6.15

#! armclang -E <how to include directory path? Write down the compatible command of v5.06 as shared above> --target=arm-arm-none-eabi -mcpu=cortex-m0plus

I look forward for your response, many thanks.

Parents
  • +1 Arm Employee Badge in reply to Alam

    Hi Alum,

    The behavior of -I is generally the same in both  compilers, though as I said I had never used it as part of a preprocessing command for the scatter file.

    Is it possible to specify the path to bsp_common_config.h in the #include statement as a workaround?

    #include  ".\..\..\..\sdk\HAL_partnum_config\bsp_common_config.h"

Reply
  • +1 Arm Employee Badge in reply to Alam

    Hi Alum,

    The behavior of -I is generally the same in both  compilers, though as I said I had never used it as part of a preprocessing command for the scatter file.

    Is it possible to specify the path to bsp_common_config.h in the #include statement as a workaround?

    #include  ".\..\..\..\sdk\HAL_partnum_config\bsp_common_config.h"

Children
  • 0 in reply to Ronan Synnott

    Hi Ronan,

    Good point, I forgot to try this option :-).

    armlink615err

    Unfortunately did not solve the directory path inclusion issue, however I highly appreciate your support.

    I suppose I will rewrite the scatter file, should not take too long just to avoid compatibility issues of armlink.

    Until next time, cheers and have a great rest of the day.

    Alam

  • +1 Arm Employee Badge in reply to Alam

    Hi again Alum

    I had some time to try this out myself... I agree that using -I on the preprocessing command seems to be ignored, however I was able to specify a path (relative to the scatter file) to an include file that successfully built.

    #!armclang -E --target=arm-arm-none-eabi -mcpu=cortex-m7 -xc

#include ".\inc\addresses.h"

LOADREGION BASE_ADDRESS SIZE1
{
	EXECREGION BASE_ADDRESS SIZE2
	{
		* (+RO +RW +ZI)
	}
	ARMLIB_STACK_HEAP STACKHEAP_BASE EMPTY STACKHEAP_SIZE
	{}
}

  • 0 in reply to Ronan Synnott

    Hi Ronan,

    Relative path is also working in my test scatter file.

    The issue was very specific to my SDK architecture, I blocked to access any file upto a certain level from the application layer.

    I confirm and your answer is accepted.

    Br,

    Alam