-
Notifications
You must be signed in to change notification settings - Fork 954
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support GCC #197
Comments
Additional gcc discussion at #110 |
Before GCC support can be added RTX needs to be updated. The version of RTX used by DAPLink doesn't have support for GCC, but newer versions do. |
Does the USB stack already support gcc? |
I don't think the USB stack has strong ties to any toolchain, so it should be fairly straight forward to update to use GCC. |
Can we track who has the knowledge and who has the time to obtain a basic "this is as far as I/we got" to facilitate PR's for doc and possible forks to show their results be they ever so humble with possible PR's to code with possible problems not solved at the moment. |
@c1728p9 named RTX.
Given no cost, and if the RTX refered to is the one I found, the github seems to be a start for compiling? Additional links found |
Hi @OwenBrotherwood, yep that is the right RTX. Since it's open source anyone who is interested could start the porting process. |
In order to create a form for "if someone suddenly does not have the time", the problem needs to be broken up into blocks that are describable as start/finish such that one can build up to the final result |
It would seem that the correct branch is this for micro:bit |
Actually @OwenBrotherwood this is the right place for micro:bit https://github.com/mbedmicro/DAPLink/tree/microbit-0234 (that's the schools drop) and https://github.com/mbedmicro/DAPLink/tree/v0241 (the base that Farnell used for the newer firmware) |
So many micro:bits out there and so many people wanting to do cool things with them. |
Dunno if this merge of code gives anyone any ideas. I haven't gone thru the code to see if it needs Kiel Note:
|
@OwenBrotherwood I'm afraid that branch is so far out of date that it's not much help. https://github.com/OwenBrotherwood/DAPLink/tree/freescale is a very old DAPLink version, right after the folder structure started being reorganized. Neither source branch supported gcc. (Unless I missed something.) |
yep: afraid it was so. At least I learned some more git techniques: I am not a programmer in my day time job (and sometimes it shows :) ) And of course, it doesn't do too much harm to give the issue a bump every now and then. "Everybody is talking about apathy, but nobody is doing anything about it" :) |
Hey, I created eclipse_gcc_arm project and got following error: 11:12:37 **** Incremental Build of configuration Default for project stm32f103xb_nucleo_f103rb_if **** Is it because the generated makefile does not reference to LD script? I am trying to understand how much work is needed to enable GCC ARM build; I will be grateful for the feedback. |
Any news? |
Just like everyone else, I wish to compile a DAPlink with gcc (open software disciple) To me, to fix this situation, some of the necessary (not sufficient) conditions are:
comments? |
DAPLink is created, developed and maintained by ARM MBED Team. They control management, architecture, internals, design and documentation. There are some good news you may want to read at #482 :-) As stated by @flit:
|
Thank you for the response. Good news. |
But DAPLink works fine already on a wide range of boards, targets and interfaces.. I use it everyday with no problem.. its far more effective than old tools that I have used or even created myself years ago.. What keeps you away from current DAPLink and what would GCC really solve for you @vaughanatworld ? |
@cederom For me this question is really easy to answer: The available to build it myself and contribute and thus integrate one in my own circuits. At the moment it's more of a use it on the micro:bit and get a "FRDM board just to drive foreign MCUs" kind of affair... |
Sure thing! Looks like it should be here quite soon.. I am waiting for that too :-) |
I see that this issue is still in backlog and we are well into Q1 2019 :) Is there any plan/roadmap for this issue? I would like to run DAPLink on not supported yet platform but Keil requirement is showstopper for me. |
+1 :-) |
We are actually making progress towards this goal. The first step was to move to mbed-cli for building DAPLink. This has been accomplished. Right now we're actively working on switching the RTOS, but are having size problems with RTX5 and the bootloader. I'll work on creating some issues and linking them to this one so that the progress is more clear. |
Great news! Thanks for linking issues here. |
Everything was going well until I hit the compile button on Keil and got the "linker" size limit error lol. I have tried the mBed CLI but I keep getting errors about missing json files. I might give it a shot again. Since Since Keil basically belongs to ARM cant they just do like a conditional license where you can just remove the restrictions of the free version to compile DapLink... Isnt Keil professional free to use for Stm32G0/L0/F0 cant Dap run on those? and thus Keil allow us to compile it? |
Any news regarding this topic? I would be very interested in porting DapLink to some microcontroller boards which not yet support DapLink. And I definitely need GCC for that ... |
Not to mention the impossibility to build it on Linux without proprietary tools , because it requires either Keil or ARM Compiler (which is provided free by Mbed Studio, which is not available on Linux...). Supporting GCC will just solve this issue |
There is currently no immediate plan to complete the referenced tasks above (RTX5, USB stack - main dependencies on ARMC5). Switching to RTX5 should not be difficult with the latest changes - my assumption, will need to study further the latest code base here (appreciate any help here, PR welcome). |
Update: The port to gcc is almost complete. I just decided to bite the bullet and do it. 😁 It's currently on my feature/gcc branch. Everything except the Musca-B1 boards builds (their Below is the only documentation right now. If you don't understand any steps, please wait until the real documentation is ready. How to buildRequires project-generator from the dev_v0.10 branch to be installed in your virtualenv. Commands are to be run from DAPLink root.
Or use:
The progen eclipse_make_gcc_arm tool also works so you can use GNU MCU Eclipse to build and debug (with pyOCD, of course!). Just import the projects under If you test and run into problems prior to gcc support being finalized, please create issues and (preferrably) PRs on my fork and not this upstream repo. |
Great, I will try to transplant it to my project.😀 |
The build for stm32f103xb are successfully, but then the FW doesn't work. |
Hello, We are thinking of helping with these items (as an intern project this summer). What setup would be needed to start on this? Thanks, |
Hello, I would like to know the status of this threat. I have a project running and working using the ARM compiler, however, Keil's 1 month free linenship is over and I would like to know if I can migrate to GCC. I use STM32F103 as HIC and LPC1857 as target. Can anybody help me? What is the problem today when trying to compile DAPLink for HIC STM32F103? Thank you very much for your attention! |
Can't wait |
@ffjunq Sorry I didn't see your comment! The work has picked back up (finally have time now that I'm on vacation for the holidays). It's currently being done on my feature/gcc branch (based on a few other branches to break the work into more mergeable chunks). We're planning to move this branch to this (upstream) repo soon so it's more visible. We need someone to test the STM32F103 port! If you could help, that would be great! Anyone that can help test the gcc port on any HIC would be greatly appreciated. |
I have some boards will be happy to test builds and runs on FreeBSD :-) |
Many thanks for the reply.
I have some cards here, I can dedicate some time to help with tests,
especially if it involves the micro STM32F072.
Update me with whatever you need!
Em sáb., 12 de dez. de 2020 às 18:54, Tomasz CEDRO <notifications@github.com>
escreveu:
… I have some boards will be happy to test builds and runs on FreeBSD :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#197 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQT6FZAIXLA7FLYBPVLZHPTSUPRAVANCNFSM4CYA3RZA>
.
|
I can assist with cypress based targets next year if timing aligns. The HIC will not however be cypress based. 😉 |
Hi everyone, I just wanted to draw your attention to #750. Note:
|
I a new in develop with MAKE! (I use only IDEs) |
Fixed in v0257 |
MISSION ACCOMPLISHED! 😎 |
It would be nice if you didn't have to spend thousands on a Keil license to compile this!
The text was updated successfully, but these errors were encountered: