Adding support for ARM DS5 tool chain. #273
Conversation
|
Are you saying the pull request is a conceptual idea or you are looking for help in solving the problem as opposed to something you claim is working and production worthy? We don't have or use DS5 licenses so we can't test such a thing and I wouldn't want to accept this without knowing what the status is. |
|
I am looking for help to solve the problem why it will not build the supplied MF samples with DS5. . I think it is very close to working given the MDK and DS5 compilers are the "same" and the edits are simply to do with paths to folders. Currently the compiler is throwing up errors on inline __ASM(...) statements. . . |
|
Unfortunately, I don't have DS5, so this is pretty wild guess, but try adding the following lines to |
Define the DEVICE_TYPE in the DeviceCode/Targets/Native *.settings files under COMPILER_TOOL==DS5 Condition In Framework/Tools/BuildTasks/ScatterFile.cs, add DS5 as a valid COMPILER_TOOL option along with RVDS and MDK to ensure the scatter files are processed. Keil MDK 5.05 compiler is the same as DS5 version 5.05 compiler, so copy the existing MDK scatter files to DS5 equivalients for the build system to be happy. Longer term solution is to consider defining a common ARM tool name to avoid duplications for RVDS, MDK and DS5. Add DS5 block to setenv_base.cmd. Note the ARMCC50BIN, ARMCC50LIB and ARMCC50INC are not used and can be deleted. (Consider removing from MDK block too) Modify tools/Targets/Microsoft.SPOT.System.Targets to include quotes around file names and paths. Needs review of other Settings/Targets files. This is to copy with end users who may have a '+' or ' ' in the folder names. Add Settings/Targets files for DS5 based on MDK versions with pre v 5.05 MDK items removed.
|
Thank you for our suggestion. It help get me going down the right path. I have made progress to the point I can delete BuildOutput folder and go through the steps to build the SDK and then build the STM32F4DISCOVERY solution using DS5.. I have forced a push to reset ARM_DS5 to include all the changes required. It was necessary to add DS5 to Framework/Tools/BuildTasks/ScatterFile.cs to process the Scatter files. To keep things interesting I had a "+" character in a folder name in my project hierarchy. This breaks the MSBuild scripts where a COPY xxx + yyy zzz is performed as the current MSBuild scripts do not quote all file names. I have made some changes to tools/Targets/Microsoft.SPOT.System.Targets to add escaped quotes. Probably need to apply this to all other files where a similar action is performed. I do not have the STM32F4DISCOVERY hardware to load and run the images created. |
|
@doingnz What's the status of this PR? At this stage it seems incomplete and would require manual merging so should be re-worked and re-submitted so I'm closing it at this point. |
I need to add support for ARM DS5 or RVDS 4.1
Preference is for ARM DS5 as this is in theory the same compiler (5.05) as included in MDK and is the tool chain supported by ARM going forward. There are some differences in the install paths and folders for the ARM DS5 tools, library, and include files compared to what was setup for MDK..
The following files are based on the MDK files and edited to remove legacy MDK versions prior to 5.05, and accommodate the folder names etc.
They assume
If I try build either MCBSTM32F400 or STM32F4DISCOVERY then I get the following errors.
I have tried with and without the following line. I would have not expected it was required as MDK 5.05 did not needed it.
Has anyone else managed to get DS5 to work correctly to build the sample projects?
Thank you for your help.
Richard
PS: I am a newbie to Git, sorry if this is the wrong way to present the new material with questions. Wiki pages suggest its an iterative process.