[BUG] Marlin doesn't work on LERDGE-K on Marlin 2.0.9.3 and up. Display doesn't work on LERDGE-K on Marlin 2.0.8.2-2.0.9.2 #24355

odbee · 2022-06-14T19:23:30Z

Did you test the latest `bugfix-2.1.x` code?

Yes, and the problem still exists.

Bug Description

i have tried getting marlin to work on my LERDGE-K board with no success so far.
Building works in most versions so far.

With versions 2.0.8.2 to 2.0.9.2 i get a reading using the serial port communcation, so marlin is successfully installed, but the display doesn't work.

With versions 2.0.9.3 and upwards the board doesn't work at all after flashing the firmware no matter what I do.

Bug Timeline

No response

Expected behavior

No response

Actual behavior

No response

Steps to Reproduce

set Configuration.h to:

#define MOTHERBOARD BOARD_LERDGE_K
#define SERIAL_PORT 1
#define TFT_GENERIC
#define TFT_INTERFACE_FSMC
#define TFT_RES_480x320
#define TFT_COLOR_UI

as well as

#define TFT_DRIVER AUTO
or
#define TFT_DRIVER ST7796

Version of Marlin Firmware

all versions

Printer model

No response

Electronics

No response

Add-ons

No response

Bed Leveling

No response

Your Slicer

No response

Host Software

No response

Don't forget to include

A ZIP file containing your Configuration.h and Configuration_adv.h.

Additional information & file uploads

Config.zip

The text was updated successfully, but these errors were encountered:

Bob-the-Kuhn · 2022-06-17T22:33:19Z

Confirmed: (mostly)
2.0.8.1 - LCD and USB work
2.0.8.2 - LCD and USB work - strange, version is 2.0.8.1 in configuration.h, 2.0.8.2 in powerup text on USB
2.0.9.0 - LCD and USB work
2.0.9.1 - LCD and USB work
2.0.9.2 - LCD and USB work
2.0.9.3 - doesn't proceed beyond firmware update OK! boot screen - no LCD, no USB after power cycle
bugfix_2.1.x - doesn't proceed beyond firmware update OK! boot screen - no LCD, no USB after power cycle

Bob-the-Kuhn · 2022-06-18T03:12:42Z

I see only one 2.0.9.3 commit that mentions Lerdge.

Delete after encrypt. Lerdge encrypt only once (b4904cc)

odbee · 2022-06-19T15:22:23Z

Confirmed: (mostly) 2.0.8.1 - LCD and USB work 2.0.8.2 - LCD and USB work - strange, version is 2.0.8.1 in configuration.h, 2.0.8.2 in powerup text on USB 2.0.9.0 - LCD and USB work 2.0.9.1 - LCD and USB work 2.0.9.2 - LCD and USB work 2.0.9.3 - doesn't proceed beyond firmware update OK! boot screen - no LCD, no USB after power cycle bugfix_2.1.x - doesn't proceed beyond firmware update OK! boot screen - no LCD, no USB after power cycle

could i get your config file to try out the LCD on older versions? or did you use the one i uploaded?

Bob-the-Kuhn · 2022-06-19T15:35:16Z

I just made the changes listed in this post.

I did set TFT_DRIVER to ST7796 in all cases except with 2.0.9.2 I tried both.

odbee · 2022-06-19T16:37:14Z

I just made the changes listed in this post.

I did set TFT_DRIVER to ST7796 in all cases except with 2.0.9.2 I tried both.

this is very weird. for me it doesn't recognize the display at all.
is it possible for you to send me the whole "Lerdge_K_system" folder you upload to the lerdge board? also, which Version of the display do you have? I have V1.0.2

Bob-the-Kuhn · 2022-06-19T22:04:23Z

Which version?

Also, I use VSCode to compile Marlin.

Bob-the-Kuhn · 2022-06-19T22:15:06Z

Here's 2.0.9.2 .

If you want you can post your config files & I'll compile & post the bin file.

odbee · 2022-06-19T22:39:46Z

Which version?

Also, I use VSCode to compile Marlin.

i meant the compiled folder you upload to the lerdge board. The "Lerdge_K_system" folder

Bob-the-Kuhn · 2022-06-19T22:44:31Z

It's in there.

Bob-the-Kuhn · 2022-06-19T22:49:40Z

Lerdge_K_system.zip

Bob-the-Kuhn · 2022-06-19T23:14:29Z

My LCD has the V1.04 bootloader on it.

V1.0.2 is on the LCD's silkscreen.

V1.0.1 is on the LerdgeK's silkscreen.

rhapsodyv · 2022-06-20T02:17:20Z

Check if this make any difference for you: #24353 (comment)

it seems some of the casts are making the compiler behave crazy in some overload optimizations.

Bob-the-Kuhn · 2022-06-20T03:30:43Z

No luck. Bugfix_2.1.x still hangs after loading the new firmware and is dead after a power cycle.

thisiskeithb · 2022-06-20T03:33:46Z

Sounds like the same issues we’re seeing on BX builds.

odbee · 2022-06-20T10:01:30Z

My LCD has the V1.04 bootloader on it.

V1.0.2 is on the LCD's silkscreen.

V1.0.1 is on the LerdgeK's silkscreen.

My setup is the same except I have the lerdge V1.0.0.
I have uploaded your firmware with no success on the LCD even though I also have the V1.0.2 LCD.

EDIT:
weirdly enough, after flashing it for the 20th time it worked (on 2.0.9.2)

rhapsodyv · 2022-06-20T12:59:12Z

did you try disable SDSUPPORT?

Bob-the-Kuhn · 2022-06-20T13:11:03Z

Yes, SDSUPPORT is disabled.

rhapsodyv · 2022-06-20T13:12:39Z

I have a ledge kit here. I will try use git bisect to find the bad commit.

Bob-the-Kuhn · 2022-06-20T13:28:55Z

I just tried the #define FTOP(S) (reinterpret_cast<const char* const>(S)) change on 2.0.9.3 and it also hangs after succesful firmware update.

Bob-the-Kuhn · 2022-06-20T13:55:28Z

@rhapsodyv - if you can get me started I can do the git bisect.

Perhaps these are the steps:

download first failing ZIP (2.0.9.3)
pull up a command window
$ git bisect start
$ git bisect bad
$ git bisect good v2.0.9.2

ellensp · 2022-06-20T14:16:46Z

you must use git, needs the full commit history

git clone https://github.com/MarlinFirmware/Marlin.git
git bisect start
git bisect good {commit where it still works}
git bisect bad {commit where it is broken}

git will then select a commit half way between these two commits,
You need to add configs and test this version and confirm is it good or bad
after testing revert these changes (ready for next iteration) and tell git the result with one of these

git bisect good or git bisect bad

git now repeats using a new commit mid way between the new good and bad commits

This is repeated a bunch till it finds the one commit that broke it.

Bob-the-Kuhn · 2022-06-20T15:34:09Z

Stuck at specifying the good and bad commits. a185ce2, 2.0.9.2, and V2.0.9.2 all come back as:

fatal: Needed a single revision
Bad rev input: 2.0.9.2

rhapsodyv · 2022-06-20T15:44:54Z

Hint: You can the the commit of version number checking the history of Version.h file:

https://github.com/MarlinFirmware/Marlin/commits/2.1.x/Marlin/Version.h

here you can get the commit for each release, for example.

Bob-the-Kuhn · 2022-06-20T15:53:54Z

I've tried the following - all with the above results.

- git bisect good https://github.com/MarlinFirmware/Marlin/commit/a185ce22cf6e4fb15250815c5c39318606a7e65a
- git bisect good a185ce22cf6e4fb15250815c5c39318606a7e65a
- git bisect good a185ce2
- git bisect good 2.0.9.2
- git bisect good V2.0.9.2

Finally got commit numbers that were accepted by doing a git log.

I can do one bisect then can't get past the "commit or stash" changes error message.

Time for someone that knows what they're doing to jump in.

Bob-the-Kuhn · 2022-06-20T21:30:46Z

Finally stumbled through all the git bisect steps.

The offending commit is:

commit 6cf6c4cd852bd09c509407057e81e37e36bad52e
Author: Scott Lahteine <[email protected]>
Date:   Tue Oct 19 02:56:44 2021 -0500

    🔨 Delete after encrypt. Lerdge encrypt only once

Interesting - same label as mentioned previously but different commit number.

rhapsodyv · 2022-06-20T21:41:47Z

The only meaningful change I see was the removed the
board_build.encrypt = firmware.bin
try add it back and see if it works.
The addition of the script might be the issue too.

Bob-the-Kuhn · 2022-06-20T22:41:10Z

I was able to get 2.0.9.3 to build & run by just backing out the marlin.py changes.

Doing the same change to bugfix_2.1.x did not work. Usual hang at "firmware update OK" with no USB coms.

What I did on 2.0.9.3:

Backed out stm32f4.ini changes - hang & no com
Backed out marlin.py changes - boots & runs
Restored stm32f4.ini changes - boots & runs

What I did on bugfix_2.1.x:

Backed out marlin.py changes - hang & no com
Tried the Marduino.h FTOP(S) change - hang & no com

Someone needs to verify marlin.py changes is all that was needed on 2.0.9.3.

rhapsodyv · 2022-06-20T23:01:41Z

Changing stm34f4.ini + marlin.py didn’t work for 2.1?

Bob-the-Kuhn · 2022-06-21T00:01:42Z

bugfix_2.1.x works when both are backed out!

rhapsodyv · 2022-06-21T00:05:44Z

Only changing stm32f4.ini isn’t enough?

Bob-the-Kuhn · 2022-06-21T02:04:00Z

Both are neeeded.

I've tried with & without the marlin.py changes several times. Reverting marlin.py is required for it to get past the "firmware update OK" screen.

With the old INI and the new PY, VSCode gives the following:

encrypt([".pio\build\LERDGEK\firmware.bin"], [".pio\build\LERDGEK\firmware.elf"])      
encrypt([".pio\build\LERDGEK\firmware.bin"], [".pio\build\LERDGEK\firmware.elf"])      
*** [.pio\build\LERDGEK\firmware.bin] .pio\build\LERDGEK\firmware.bin: No such file or 
directory
Encrypting .pio\build\LERDGEK\firmware.bin to Lerdge_K_firmware_force.bin

With the old INI and the new PY, a new Lerdge_K_firmware_force.bin is created. The Lerdge firmware loader likes it but it hangs there. Maybe the Lerdge_K_firmware_force.bin file isn't getting encrypted and the Ledge firmware loader is too dumb to notice. The first 320 bytes of the new image is not encrypted so maybe everything the bootloader needs is in the unencrypted section.

I don't see why the old version of the marlin.py program is needed. Seems like the old and new do the same thing.

Bob-the-Kuhn · 2022-06-23T21:27:31Z

@odbee - does this fix your problems?

thisiskeithb · 2022-06-24T05:08:48Z

#24391 has been merged.

Bob-the-Kuhn · 2022-06-24T23:05:20Z

Just tested the latest bugfix-2.1.x. Compiles with no errors and runs on my Lerdge K.

odbee · 2022-07-03T13:07:29Z

@odbee - does this fix your problems?

hey, sorry for the late reply, it seems like the whole issue occured because i fried my display. the new version works now!. ill be running my printer via octoprint for now, thanks alot!!

github-actions · 2022-09-01T14:01:28Z

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.

thisiskeithb added the Bug: Confirmed ! label Jun 18, 2022

thisiskeithb added the A: STM32 label Jun 18, 2022

Bob-the-Kuhn mentioned this issue Jun 23, 2022

Lerdge Boot Fail: Backout Commit b4904cc Changes to stm32f4.ini & marlin.py #24391

Merged

thisiskeithb closed this as completed Jun 24, 2022

github-actions bot locked and limited conversation to collaborators Sep 1, 2022

[BUG] Marlin doesn't work on LERDGE-K on Marlin 2.0.9.3 and up. Display doesn't work on LERDGE-K on Marlin 2.0.8.2-2.0.9.2 #24355

[BUG] Marlin doesn't work on LERDGE-K on Marlin 2.0.9.3 and up. Display doesn't work on LERDGE-K on Marlin 2.0.8.2-2.0.9.2 #24355

Comments

odbee commented Jun 14, 2022 • edited Loading

Did you test the latest bugfix-2.1.x code?

Bug Description

Bug Timeline

Expected behavior

Actual behavior

Steps to Reproduce

Version of Marlin Firmware

Printer model

Electronics

Add-ons

Bed Leveling

Your Slicer

Host Software

Don't forget to include

Additional information & file uploads

Bob-the-Kuhn commented Jun 17, 2022

Bob-the-Kuhn commented Jun 18, 2022

odbee commented Jun 19, 2022

Bob-the-Kuhn commented Jun 19, 2022

odbee commented Jun 19, 2022

Bob-the-Kuhn commented Jun 19, 2022

Bob-the-Kuhn commented Jun 19, 2022

odbee commented Jun 19, 2022

Bob-the-Kuhn commented Jun 19, 2022

Bob-the-Kuhn commented Jun 19, 2022

Bob-the-Kuhn commented Jun 19, 2022 • edited Loading

rhapsodyv commented Jun 20, 2022

Bob-the-Kuhn commented Jun 20, 2022

thisiskeithb commented Jun 20, 2022

odbee commented Jun 20, 2022 • edited Loading

rhapsodyv commented Jun 20, 2022

Bob-the-Kuhn commented Jun 20, 2022

rhapsodyv commented Jun 20, 2022

Bob-the-Kuhn commented Jun 20, 2022

Bob-the-Kuhn commented Jun 20, 2022

ellensp commented Jun 20, 2022 • edited Loading

Bob-the-Kuhn commented Jun 20, 2022 • edited Loading

rhapsodyv commented Jun 20, 2022

Bob-the-Kuhn commented Jun 20, 2022 • edited Loading

Bob-the-Kuhn commented Jun 20, 2022

rhapsodyv commented Jun 20, 2022

Bob-the-Kuhn commented Jun 20, 2022

rhapsodyv commented Jun 20, 2022

Bob-the-Kuhn commented Jun 21, 2022

rhapsodyv commented Jun 21, 2022

Bob-the-Kuhn commented Jun 21, 2022

Bob-the-Kuhn commented Jun 23, 2022

thisiskeithb commented Jun 24, 2022

Bob-the-Kuhn commented Jun 24, 2022

odbee commented Jul 3, 2022

github-actions bot commented Sep 1, 2022

odbee commented Jun 14, 2022 •

edited

Loading

Did you test the latest `bugfix-2.1.x` code?

Bob-the-Kuhn commented Jun 19, 2022 •

edited

Loading

odbee commented Jun 20, 2022 •

edited

Loading

ellensp commented Jun 20, 2022 •

edited

Loading

Bob-the-Kuhn commented Jun 20, 2022 •

edited

Loading

Bob-the-Kuhn commented Jun 20, 2022 •

edited

Loading