DAPLink icon indicating copy to clipboard operation
DAPLink copied to clipboard

Arm Compiler 6 Support AC6

Open 0Grit opened this issue 5 years ago • 12 comments

@ARMmbed/team-embeddedplanet cannot build daplink since we do not have AC5. I am expressing our desire to at least be able to build with AC6.

0Grit avatar Jul 12 '19 17:07 0Grit

If someone could get this ported to at the very least ac6 @team-embeddedPlanet could start making contributions to this project.

@maclobdell @flit @blackstoneengineering

40Grit avatar Aug 10 '19 11:08 40Grit

How many errors are there (I haven't yet tested it with AC6) ?

I can help fixing some but can't commit to fully enable this at the moment 😢

0xc0170 avatar Aug 12 '19 08:08 0xc0170

We tested Ac6 once and it seemed non-trivial to port, However we were in a rush at the time.

We have initial protos coming in for a board that we want to make into a product for generic debug and device flashing. It will also provide an interface for our Mbed Enabled + Pelion ready modules and kits.

Unless we are missing something simple that will enable ac6 to build daplink, we wont be able to use our protos when they come in this week.

By the way, good to have you back.

@brianesquilona

40Grit avatar Aug 12 '19 11:08 40Grit

My first thought was about our current RTX here (RTX4) being able to support AC6. We rather move to RTX5. I'll catch up with @brianesquilona if we can switch (there is size increase as I was told so might not be able to do it completely).

0xc0170 avatar Aug 12 '19 11:08 0xc0170

@millerc-ep

0Grit avatar Aug 12 '19 15:08 0Grit

Yes, switching to RTX5 will have size increase but bootloaders are already in the no-rtos codes, so only the interface codes will need to be migrated. All the interfaces/headers conforms to RTX5 already.

brianesquilona avatar Aug 16 '19 15:08 brianesquilona

We tried building daplink with mdk5-lite but the build is too big for it. failedARMC5Build

millerc-ep avatar Aug 20 '19 16:08 millerc-ep

We tried building daplink with mdk5-lite but the build is too big for it.

The current master builds with lite (32k linker limit) for your interface? Oh wait, you are just trying to build it but hitting the limit, is that correct ? I assumed initially you already swapped RTX4.

0xc0170 avatar Aug 21 '19 14:08 0xc0170

Correct, we are trying to build it but we are hitting the 32k linker limit.

millerc-ep avatar Aug 22 '19 17:08 millerc-ep

@0xc0170 We have not swapped RTX4 for RTX5 nor tried.

We want to be able to contribute back to the project in it's current state so we can add support for our Debug & Test board sooner than later.

The swap would imply getting our changes onto master and getting that released which I presume will take a while.

0Grit avatar Aug 22 '19 17:08 0Grit

I have been working on this in https://github.com/mathias-arm/DAPLink/tree/feature/armclang. It builds on the GCC support @flit started. To test you need also the changes in project-generator/project_generator#474.

mathias-arm avatar Dec 15 '20 05:12 mathias-arm

Hi everyone, I just wanted to draw your attention to #750.

Note: I have only tested with the new make_armclang toolchain option from project-generator/project_generator#475, there is also a cmake_armclang option with project-generator/project_generator#475)

Once you have installed the Python requirements and the proper version of project-generator:

$ progen generate -t make_armclang -p <project-name>
$ make -C projectfiles/make_armclang/<project-name>

mbrossard avatar Dec 17 '20 03:12 mbrossard