-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
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] Trigorilla Pro for HAL/STM32 broken #22708
Comments
Continue to use the Maple environment. The correct |
Does the non maple build environment actually boot? can you talk to it over serial? |
I have the board, schematics, and pinout. Specifically, what do you need? |
No. It does not boot or communicate over serial USB. The Maple environment boots and communicates over USB. |
You need to work out whats different from the platform = ststm32@~12.1 normally you would attach a debugger to the controller and find out where it stopping, then work out why |
Just had a little look, first thing I see is that env:trigorilla_pro_maple has the firmware at 0x08000000 In ini/stm32f1.ini is the following
Try changing board_build.offset = 0x7000 to board_build.offset = 0x0000 This moves the firmware back to 0x08000000 |
I'm not entirely clear on whether the |
Downloaded the latest bugfix and associated configuration files for the Trigorilla Pro. |
That makes zero sense, as that variable only effects env:trigorilla_pro it doesn't touch env:trigorilla_pro_maple. Also I compiled it fine. |
You keep saying " configuration files for the Trigorilla Pro." but marlin has configuration for Printers and board options for those printers. The Only Config files that uses this board that I can see are CONFIG_EXAMPLES_DIR "delta/Anycubic/Predator" Which is what I've been using for testing. |
I repeat. I downloaded the latest bugfix and the latest configuration files. It will not compile whether maple or not. I applied the offset of 0x0000 you suggested only to the non-maple ini. I agree that maple should not affect the standard environment, but now it does. |
I always the the latest bugfix, freshly git pulled every compile and cannot replicate this error. |
delete your Marlin/.pio folder and try again. If it still fails attach the build log in its entirety. (zip it up and drop zip into message, also include your Config files.) |
That is also what I have been using for testing. |
@ellensp, attached is a zip file containing the build logs for the "standard" environment, and the "Maple" environment (which recently worked but now does not). I deleted the .pio directory and adjusted the offset in the standard environment to 0x0000 per your request. As mentioned, the configuration files are the same ones that you are using, located in the CONFIG_EXAMPLES_DIR "delta/Anycubic/Predator" directory, with no modifications. |
Did you not see all the warinings at the start
|
check that these files exsist |
@ellensp, of course I saw them. Are you saying now that you now can't comile also? What am I supposed to do with these warnings? Tell me PRECISELY what you need. |
I do not get those warning, only you are having issues compiling. |
@ellensp, my apologies. I deleted the entire existing Marlin file, and downloaded fresh copies of both the latest bugfix and 2.0.9.1, along with their associated configuration files for the Anycubic Predator. After making sure that the offset in STM32F1.ini was set to 0x0000, and that the directory structure was intact, these are the results:
|
No. initial bug is real, just lost in superfluous issues when testing the fix. Creating PR with offset correction |
Thank you for your efforts and diplomacy! It is interesting to note that, for the first time, this printer and its display can now use the Color_UI instead of the Classic_UI. I had to disable the mesh overlay to get it to compile, but it looks very nice on the printer. |
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. |
Did you test the latest
bugfix-2.0.x
code?Yes, and the problem still exists.
Bug Description
Compiling latest bugfix with example configurations for the Trigorilla Pro goes fine, with no errors. Howver, when installed, the display is still dead.
HOWEVER, if compiled using the "Autobuild Marlin" extension in PlatformIO, and choosing the Trigorilla Pro Maple environment, the compiled firmware.bin works fine. Display is proper, and touchscreen works as expected.
Obviously, there is a fatal disconnect somewhere between the two build environments,
Bug Timeline
Old. I never could get any Marlin after 2.0.9 to work if not built using the Maple environment.
Expected behavior
I expect compiling the latest bugfix with the latest configuration files to yield a functional firmware.bin file under any available environment.
Actual behavior
Only the Maple environment yields a functional compile.
Steps to Reproduce
Version of Marlin Firmware
latest bugfix (9/3/2021)
Printer model
Anycubic Predator
Electronics
stock Trigorilla Pro
Add-ons
none
Bed Leveling
No response
Your Slicer
No response
Host Software
No response
Additional information & file uploads
No response
The text was updated successfully, but these errors were encountered: