-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
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
[BUG] Archim not building in 2.0.6 with Arduino #18860
Comments
Please update description |
Ok. I assumed arduino was the target because in 2.0.5.4, it builds in arduino and not in platformio. Sorry for the missing description. |
Some 32-bit boards/configs can still be built with Arduino IDE, but it's recommended to use VSCode + PlatformIO. |
This is true but the Archim line of boards retained it's ability to be compiled in Arduino IDE I believe due to the unique pinout for the board. For the record I haven't been able to build in Arduino IDE for the Archim 2 since the end of May. |
@ellensp @thisiskeithb is this an issue with marlin or the IDE ? if it's the later can it called a bug with marlin? |
This may be related to the issue I'm having in my thread #18816 (comment). Something may be broken with compiling Marlin with regards to this board. I'm able to complete using VSCode but it's not functioning properly. The manufacture recommended method of compiling is Arduino IDE and as of late May something in the coding changed and is no longer working with Arduino either. |
I don't have an Archim 2, so I can't say anything about running, unfortunately. I can say: 2.0.5.4 builds with arduino, but not platformio. I haven't even looked closely at the error. I assume someone familiar would immediately recognize it. Fundamentally, unless Marlin is willing to just completely give up on arduino building, the boards that can be built in arduino should be tested with the arduino toolchain. Pull requests should be required to pass those builds, or else end users are going to keep finding the errors, reporting issues, and have to convince developers it isn't their fault. |
This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days. |
Is Marlin on arduino officially dead? I know there are many troubles with arduino in windows. Troubles that are very hard to fix. It would be nice to know if we should be working to keep it alive, or pushing it out. |
vscode+platform.io is the tool arduino ide has bugs that we cant fix |
I understand the preference. I prefer it too. But is arduino definitely dead? Is that the project's preferred step forward? If so, is this written down somewhere? There is a lot of documentation for how to build with arduino. We have a parallel doc for platformio. But people still pick up the arduino instructions first (it shouldn't be surprising, after years of marketting it to hobby and beginners). Until it is officially deprecated, issues like this should be fixed. |
Our maintainer @thinkyhead does not use it, nor do i personally due to bugs in arduino ide that we cant fix, arduino ide guys have to do that and they dont So i would say yes to the first 2, but its not written down anywhere, but when people mention arduino ide we say to use vscode+platform.io |
In the readme, the first suggestion is to use arduino. The first instructions are for arduino, and they point here. I understand pointing people to platformio as a work around. I also understand that developers prefer it. I also understand that not every board can work with arduino. I also see the new CreateProcess error in windows as of 2.6.0, and it seems to me like the writing is on the wall. I see all of these things, and I don't think this issue is probably the right place to argue about it. But, it isn't sustainable to direct users to arduino, have them get lots of problems (which many probably assume is there fault) and then come here or another forum and be told they need to use platformio. Because I love Marlin, I hope there is a decision about the future of Marlin in arduino. If it's dead, then we should be clear about that. If support is still wanted, then we shouldn't be responding to all the arduino issues with "use platformio". Until there is a clear deprecation of arduino, this is still an issue. |
@jeffeb3 I agree with you. I don't use Arduino either, but until @thinkyhead announces it is dead and changes the documentation, we shouldn't simply disregard issues like this. In this case, it appears to be an actual code issue of some sort, not the normal Arduino problems related to path lengths, etc. |
@jeffeb3 when was the last time you tried this? I was able to reproduce that error with 2.0.6 on Windows, but not with 2.0.6.1 or bugfix-2.0.x. |
Thanks. It does build with bugfix and 2.0.6.1 in our builder. I haven't had them on since 2.0.6. https://github.com/V1EngineeringInc/MarlinBuilder/pull/23/checks?check_run_id=1124244240 |
Great! Thanks for the update. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Bug Description
I am getting a compile error when building for Archim boards (1&2) in arduino with bugfix-2.0.x and with 2.0.6. The same code builds in platformio.
I have confirmed this with arduino 1.8.12 on my Linux desktop (ubuntu 18.04). But I am also trying to build this automatically. Here is the output from our builder:
https://github.com/jeffeb3/MarlinBuilder/runs/926010778?check_suite_focus=true#step:9:2068
It looks like an error in HAL.h, but I'm not sure why it only affects Archim (the rambo, ramps, skr boards are all fine). I am not sure why it is only a problem in Arduino. Hopefully it is an easy fix.
My Configurations
Archim_Broken.zip
Steps to Reproduce
Expected behavior: [What you expect to happen]
The build succeeds
Actual behavior: [What actually happens]
These errors:
This link is a little weird. I hoped it would point to the exact issue. But it starts on line 2068:
https://github.com/jeffeb3/MarlinBuilder/runs/926010778?check_suite_focus=true#step:9:2068
Additional Information
The text was updated successfully, but these errors were encountered: