[BUG] Trigorilla Pro for HAL/STM32 broken

[rq3]

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

1. Compile and load Marlin under the standard Trigorilla Pro environment
2. Witness a dead display and touch screen
3. Compile and load Marlin under the Trigorilla Pro Maple environment
4. Witness a fully functional display and touchscreen

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

[thinkyhead]

Continue to use the Maple environment. The correct trigorilla_pro environment has simply not been established. Hopefully someone with the Trigorilla Pro board will figure it out and send us the corrections.

[ellensp]

Does the non maple build environment actually boot? can you talk to it over serial?

[rq3]

Continue to use the Maple environment. The correct trigorilla_pro environment has simply not been established. Hopefully someone with the Trigorilla Pro board will figure it out and send us the corrections.

I have the board, schematics, and pinout. Specifically, what do you need?

[rq3]

Does the non maple build environment actually boot? can you talk to it over serial?

No. It does not boot or communicate over serial USB. The Maple environment boots and communicates over USB.

[ellensp]

You need to work out whats different from the
[env:trigorilla_pro_maple] to [env:trigorilla_pro]
Other than the change from

platform = ststm32@~12.1
board_build.core = maple
to
platform = ststm32@~12.1
board_build.core = stm32

normally you would attach a debugger to the controller and find out where it stopping, then work out why

[ellensp]

Just had a little look, first thing I see is that env:trigorilla_pro_maple has the firmware at 0x08000000
but env:trigorilla_pro puts its at 0x08007000

In ini/stm32f1.ini is the following

[env:trigorilla_pro]
platform             = ${stm32_variant.platform}
extends              = stm32_variant
board                = genericSTM32F103ZE
board_build.variant  = MARLIN_F103Zx
board_build.offset   = 0x7000
build_flags          = ${stm32_variant.build_flags}
                       -DENABLE_HWSERIAL3 -DTIMER_SERIAL=TIM5
build_unflags        = ${stm32_variant.build_unflags}
                       -DUSBCON -DUSBD_USE_CDC

Try changing board_build.offset = 0x7000 to board_build.offset = 0x0000

This moves the firmware back to 0x08000000

[thinkyhead]

I'm not entirely clear on whether the board_upload.offset_address / board_build.offset options apply to both the maple and the stm32 environments…. Need to look closer at that.

[rq3]

Just had a little look, first thing I see is that env:trigorilla_pro_maple has the firmware at 0x08000000
but env:trigorilla_pro puts its at 0x08007000

In ini/stm32f1.ini is the following

[env:trigorilla_pro]
platform             = ${stm32_variant.platform}
extends              = stm32_variant
board                = genericSTM32F103ZE
board_build.variant  = MARLIN_F103Zx
board_build.offset   = 0x7000
build_flags          = ${stm32_variant.build_flags}
                       -DENABLE_HWSERIAL3 -DTIMER_SERIAL=TIM5
build_unflags        = ${stm32_variant.build_unflags}
                       -DUSBCON -DUSBD_USE_CDC

Try changing board_build.offset = 0x7000 to board_build.offset = 0x0000

This moves the firmware back to 0x08000000

Downloaded the latest bugfix and associated configuration files for the Trigorilla Pro.
Changed the offset to 0x0000.
Does not compile: error: the value of 'SystemCoreClock' is not usable in a constant expression
Also will not compile under the Maple environment.

[ellensp]

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.

[ellensp]

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.

[rq3]

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.

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.

[ellensp]

I always the the latest bugfix, freshly git pulled every compile and cannot replicate this error.

[ellensp]

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.)

[rq3]

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.

That is also what I have been using for testing.