search

MarlinFirmware / Marlin

Marlin is an optimized firmware for RepRap 3D printers based on the Arduino platform. Many commercial 3D printers come with Marlin installed. Check with your vendor if you need source code for your specific machine.
https://marlinfw.org
GNU General Public License v3.0
16.18k stars 19.22k forks source link

[BUG] Cannot compile Marlin for SKR mini E3-DIP V1.1 #20778

Closed Auravendill closed 3 years ago

Auravendill commented 3 years ago

I cannot compile the current Marlin 2.0.x branch for my SKR mini E3-DIP V1.1. I've tried on both Windows and Linux and switched back to the example config from Configurations-release-2.0.7.2 for this board in an Ender 3 to minimize all error sources as far as I can. Compiling for other boards like the SKR v1.3 works totally fine.

This is the output in Platformio (VS Code, Debian 10):

Processing STM32F103RC_btt_USB (platform: ststm32@~6.1; board: genericSTM32F103RC; framework: arduino)

Verbose mode can be enabled via -v, --verbose option CONFIGURATION: https://docs.platformio.org/page/boards/ststm32/genericSTM32F103RC.html PLATFORM: ST STM32 (6.1.1) > STM32F103RC (48k RAM. 256k Flash) HARDWARE: STM32F103RCT6 72MHz, 48KB RAM, 256KB Flash DEBUG: Current (blackmagic) External (blackmagic, jlink, stlink) PACKAGES:

Environment Status Duration

STM32F103RC_btt_USB FAILED 00:01:37.791 ======================================================= 1 failed, 0 succeeded in 00:01:37.791 ======================================================= Der Terminalprozess "pio 'run'" wurde mit folgendem Exitcode beendet: 1.

Das Terminal wird von Aufgaben wiederverwendet, drücken Sie zum Schließen eine beliebige Taste.

qwewer0 commented 3 years ago

`rom' overflowed by 4476 bytes

This Issue Queue is for Marlin bug reports and development-related issues, and we prefer not to handle user-support questions here. (As noted on this page.) For best results getting help with configuration and troubleshooting, please use the following resources:

After seeking help from the community, if the consensus points to a bug in Marlin, then you should post a bug report.

Auravendill commented 3 years ago

But something in Marlin changed and now I cannot build for this one mainboard anymore. Neither with my own config files nor with the example files that are linked within Marlin itself. Reading documentations (again) on how to config marlin won't change that. I am usually more than capable to get my configs to work, my other printer all run just fine with 2.0.7.2, but with different mainboards.

On the printer in question is currently running Marlin 2.0.6.1. So it was obviously possible to compile for it back then.

In "Check All" it says: Marlin/src/pins/pins.h:747: [high:error] #error Unknown MOTHERBOARD value set in Configuration.h [preprocessorErrorDirective] even though the mainboard is defined in boards.h (Not sure if that means anything though)

I can of course ask on Discord too, but I rather doubt, that they will find the issue... But I wouldn't mind getting proven wrong.

ellensp commented 3 years ago

".rodata' will not fit in region rom'"

The firmware you have created is to large for the amount of flash on your controllers. Disable some features.

ellensp commented 3 years ago

also use bugfix for this board or wait to next release. They use ststm32@~10.0 the produces much smaller code.

Auravendill commented 3 years ago

But if compile with STM32F103RC_btt_512K_USB (which works (but might be unstable etc or will just crash)), it says, I am using 46,1% flash (241948 bytes), which means I should still be safe with only the 256k I normally have with the option I used before.

And the example config already uses less features than I am currently using in 2.0.6.1 and apparently doesn't fit anymore? Did 2.0.7.2 get so much worse in terms of space efficiency or are new features enabled in the background that I haven't noticed yet?

But if those issues will be fixed in the next release, I will be looking forward to it. If my board crashes with the 512K version, I might consider trying bugfix, but I prefer to use a stable branch as much as possible.

Thank you very much for your help!

github-actions[bot] commented 3 years ago

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.