Skip to content
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

MKS Robin nano v.2 bootloop #19709

Closed
Malderin opened this issue Oct 12, 2020 · 22 comments
Closed

MKS Robin nano v.2 bootloop #19709

Malderin opened this issue Oct 12, 2020 · 22 comments

Comments

@Malderin
Copy link
Contributor

Marlin 2.0.Bugfix.
After update:
#19192
the board is rebooted upon loading after the start logo. Next comes the endless reboot (bootloop).
File configuration.h set parameters:
#define MKS_TS35_V2_0
#define TFT_LVGL_UI

@tpruvot
Copy link
Contributor

tpruvot commented Oct 12, 2020

was due to 0988af4

may have been fixed today with tft refactor commit

@Malderin
Copy link
Contributor Author

Marlin 2.0.7.2 (stable).
File configuration.h set parameters:
#define MKS_TS35_V2_0
#define TFT_LVGL_UI
The board boots, but the color gamut is incorrect. Tried adding parameters:
#define TFT_COLOR TFT_COLOR_RGB
#define TFT_COLOR TFT_COLOR_BGR
to configuration.h, nothing changes.
See video: error
My fork with configurations: https://github.com/Malderin/Marlin_2.0.x_official/tree/Marlin2.0.7

@Malderin
Copy link
Contributor Author

after rolling back this commit:
fea0db47d
board started normally.

@rhapsodyv
Copy link
Sponsor Member

Please try #19710 . It's fixed now.

Thanks!

@Malderin
Copy link
Contributor Author

Please try #19710 . It's fixed now.

Thanks!

  1. Marlin 2.0.7.2 problem solved
  2. Marlin 2.0.bugfix, the color scheme has become normal (visible on the splash screen), but the bootloop is still

@rhapsodyv
Copy link
Sponsor Member

rhapsodyv commented Oct 13, 2020

What are your configs?

You need to disable "TOUCH_SCREEN" when using LVGL.

@Malderin
Copy link
Contributor Author

Malderin commented Oct 13, 2020

What are your configs?

You need to disable "TOUCH_SCREEN" when using LVGL.

Found the reason. If #define USE_WATCHDOG is uncommented in Configuration_adv.h then the board goes into reboot.

My configurations:
Conf.zip
or in my fork:
https://github.com/Malderin/Marlin_2.0.x_official/tree/Marlin2.0.7_bugfix

@rhapsodyv
Copy link
Sponsor Member

The watchdog problem is fixed here: #19724

@Malderin
Copy link
Contributor Author

The watchdog problem is fixed here: #19724

the fix did not help, the bootloop was preserved

@rhapsodyv
Copy link
Sponsor Member

I tested your configs in my Nano V2 + MKS TS 35, using #19724, it boot normally. 100%

@th0m4sek
Copy link

Problem is still there and it's seems to be related to watchdog. My MKS robin nano 1.2 is not starting every time. With new bug fix problem is still present. I've commented #define USE_WATCHDOG and it's booting.

@Malderin
Copy link
Contributor Author

Problem is still there and it's seems to be related to watchdog. My MKS robin nano 1.2 is not starting every time. With new bug fix problem is still present. I've commented #define USE_WATCHDOG and it's booting.

I confirm, I still have a problem with active USE_WATCHDOG

@rhapsodyv
Copy link
Sponsor Member

@makerbase-mks is possible of some nano boards came with the hardware watchdog enabled? Or some bootloader version turning watchdog on before marlin start?

@rhapsodyv
Copy link
Sponsor Member

Problem is still there and it's seems to be related to watchdog. My MKS robin nano 1.2 is not starting every time. With new bug fix problem is still present. I've commented #define USE_WATCHDOG and it's booting.

I confirm, I still have a problem with active USE_WATCHDOG

The problem is with nano v1.2 or nano v2?

@Malderin
Copy link
Contributor Author

Problem is still there and it's seems to be related to watchdog. My MKS robin nano 1.2 is not starting every time. With new bug fix problem is still present. I've commented #define USE_WATCHDOG and it's booting.

I confirm, I still have a problem with active USE_WATCHDOG

The problem is with nano v1.2 or nano v2?

I have nano v.2, @th0m4sek have v.1.2.
It looks like problems are encountered on both board versions.

@rhapsodyv
Copy link
Sponsor Member

Here, both nano v1.2 and nano v2 with bugfix + watchdog enabled.

Or we are testing different marlin code base, or MKS have different setups for the same board...

IMG_0203
IMG_0204

@Malderin
Copy link
Contributor Author

Here, both nano v1.2 and nano v2 with bugfix + watchdog enabled.

Or we are testing different marlin code base, or MKS have different setups for the same board...

IMG_0203
IMG_0204

Oк. You can test this firmware for Robin nano v.2?
This is compiled from the latest bugfix sources and causes a bootloop on my board.

Robin_nano35.zip

@rhapsodyv
Copy link
Sponsor Member

Robin_nano35.zip

Your firmware reboot my board. So, the problem is not the board. Seems your marlin codebase is outdated.

Can you test with a "fresh" copy and build?

Try this firmware that I compiled now, for nano v2:

Robin_nano35.bin.zip

@Malderin
Copy link
Contributor Author

Robin_nano35.zip

Ваша прошивка перезагрузит мою плату. Значит, проблема не в плате. Кажется, ваша кодовая база марлина устарела.

Можете ли вы протестировать «свежую» копию и собрать?

Попробуйте эту прошивку, которую я скомпилировал сейчас, для nano v2:

Robin_nano35.bin.zip

Indeed, the problem seems to be in my copy of marlin. The question is closed, thanks!

@Malderin
Copy link
Contributor Author

@rhapsodyv , I found where I had the problem that was causing the bootloop.
In file Marlin\src\lcd\extui\lib\mks_ui\SPI_TFT.cpp in section:
void TFT::LCD_init() {
tftio.InitTFT();
#if PIN_EXISTS(TFT_BACKLIGHT)
OUT_WRITE(TFT_BACKLIGHT_PIN, LOW);
#endif
delay(100);
LCD_clear(0x0000);
LCD_Draw_Logo();
#if PIN_EXISTS(TFT_BACKLIGHT)
OUT_WRITE(TFT_BACKLIGHT_PIN, HIGH);
#endif
#if HAS_LOGO_IN_FLASH
delay(2000);
#endif
}
Instead of delay (2000) I had delay (4000) specified. I returned 2000 and the bootlap was gone. It's strange ...

@th0m4sek
Copy link

I'm suspecting some problems with my microsd card because firmware upload was also not always success. I used different card this time and i will observe printer.

@github-actions
Copy link

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.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants