[BUG] Malyan M200 v2 / MonoPrice Select Mini V2 boot loop

[doucettom]

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

No, but I will test it now!

Bug Description

I tried to recompile a fresh Marlin 2.0.9.3 and realized that the reboot loop bug is still there.
#20824

Bug Timeline

Old, since 2.0.7.2

Expected behavior

Not rebooting

Actual behavior

Reboots every few seconds

Steps to Reproduce

No response

Version of Marlin Firmware

2.0.9.3

Printer model

MP Select Mini V2

Electronics

stock

Add-ons

None

Bed Leveling

No Bed Leveling

Your Slicer

Cura

Host Software

OctoPrint

Additional information & file uploads

Marlin.zip

[doucettom]

Duplicate of #20824

[doucettom]

This is reproducible on 3 different MP Select Mini v2's.

[tablatronix]

Yeah Same here anyone figure out what the issue is before I stick a debugger on this, that issue was closed with no help

[doucettom]

https://www.reddit.com/r/MPSelectMiniOwners/comments/l08gyq/marlin_2072_on_mp_select_mini/hzjkoue/?context=3

[thisiskeithb]

Looks like the bug was introduced in #19693.

If commenting out the following works, then I can put in a PR to remove it from the M200 pins file:

Marlin/Marlin/src/pins/stm32f1/pins_MALYAN_M200.h

Lines 36 to 37 in 323ac94

	// Prevents hanging from an extra watchdog init
	#define DISABLE_WATCHDOG_INIT

[thisiskeithb]

Anyone have a V1? Since this setting is inherited, it may not apply to all versions.

[doucettom]

I don't but the v2 has its own file that refers to v1's file. Le 6 mars 2022 20 h 39 min 26 s Keith Bennett ***@***.***> a écrit :

…

Anyone have a V1? Since this setting is inherited, it may not apply to all versions. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: ***@***.***>

[thisiskeithb]

I don't but the v2 has its own file that refers to v1's file.

That’s why I’m asking. The setting is inherited from the V1’s pins file, so I don’t want to disable it on the V1 if it’s not affected.

[tablatronix]

Right, but disabling a watchdog is not a fix for anything, also I tried that and it never boots..
I will check again, as this mentions double wd

[thisiskeithb]

also I tried that and it never boots..

So that means the linked Reddit post was not correct / doesn’t apply here.

if someone can get a debugger on the board and watch the boot process to see where it’s hanging up, that’d help.

[github-actions]

This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 10 days.

[julian-weinert]

May I bump this? I think I'm running into the same issue, but am not entirely sure.
I'm new to Marlin and all this, but my LCD module properly boots, but the motor drivers stay enabled and the main board doesn't seem to report parameters to the LCD module.
Commenting out the line mentioned by @thisiskeithb didn't solve the issue for me.

[thinkyhead]

Please try disabling the display and other features one-by-one, in case any particular feature is contributing to the problem.

[dzid26]

Anyone have a V1? Since this setting is inherited, it may not apply to all versions.

Just tried Merlin for the first time using [env:STM32F103CB_malyan] and this configuration and it build fine using Platformio. But I am getting the boot loop on MP Select mini V1 as well. Just before it resets I can hear the extruder stepper vibration, but it's not rotating.
In between the resets I can shortly control the printer via LCD (except the extruder).
Also, Octoprint is able to establish a connection:

Trying port /dev/ttyACM0, baudrate 500000
Connecting to port /dev/ttyACM0, baudrate 500000
Handshake attempt #1 with timeout 2.0s
Connected to: Serial<id=0x6fd8b370, open=True>(port='/dev/ttyACM0', baudrate=500000, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0*125
Recv: ok
Changing monitoring state from "Detecting serial connection" to "Operational"
Send: N0 M110 N0*125
Recv: ok
Send: N1 M115*39
Recv: FIRMWARE_NAME:Marlin bugfix-2.1.x (Feb 26 2023 22:22:05) SOURCE_CODE_URL:github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:Malyan M200 EXTRUDER_COUNT:1 UUID:cede2a2f-41a2-4748-9b12-c55c62f367ff

---------------------------------------------------------------------------
Your printer's firmware is a development build of Marlin (build date
20230226). It might be more unstable than a release version and should be
kept up-to-date.

Learn more at https://faq.octoprint.org/warning-firmware-development
---------------------------------------------------------------------------
Recv: Cap:SERIAL_XON_XOFF:0
Recv: Cap:BINARY_FILE_TRANSFER:0
Recv: Cap:EEPROM:0
Recv: Cap:VOLUMETRIC:1
Recv: Cap:AUTOREPORT_POS:0
Recv: Cap:AUTOREPORT_TEMP:1
Recv: Cap:PROGRESS:0
Recv: Cap:PRINT_JOB:1
Recv: Cap:AUTOLEVEL:0
Recv: Cap:RUNOUT:0
Recv: Cap:Z_PROBE:0
Recv: Cap:LEVELING_DATA:0
Recv: Cap:BUILD_PERCENT:0
Recv: Cap:SOFTWARE_POWER:0
Recv: Cap:TOGGLE_LIGHTS:0
Recv: Cap:CASE_LIGHT_BRIGHTNESS:0
Recv: Cap:EMERGENCY_PARSER:0
Recv: Cap:HOST_ACTION_COMMANDS:0
Recv: Cap:PROMPT_SUPPORT:0
Recv: Cap:SDCARD:1
Recv: Cap:MULTI_VOLUME:0
Recv: Cap:REPEAT:0
Recv: Cap:SD_WRITE:1
Recv: Cap:AUTOREPORT_SD_STATUS:0
Recv: Cap:LONG_FILENAME:1
Recv: Cap:LFN_WRITE:0
Recv: Cap:CUSTOM_FIRMWARE_UPLOAD:0
Recv: Cap:EXTENDED_M20:1
Recv: Cap:THERMAL_PROTECTION:1
Recv: Cap:MOTION_MODES:0
Recv: Cap:ARCS:0
Recv: Cap:BABYSTEPPING:0
Recv: Cap:CHAMBER_TEMPERATURE:0
Recv: Cap:COOLER_TEMPERATURE:0
Recv: Cap:MEATPACK:0
Recv: Cap:CONFIG_EXPORT:0
Recv: ok
Send: M21
Recv: echo:SD card ok
Recv: ok
Send: M155 S2
Recv: ok
Send: M20 L
Recv: Begin file list
Recv: PUMPHO~1.GCO 7446555 Pump holder.gcode
Recv: End file list
Recv: ok
Recv:  T:41.13 /0.00 B:20.77 /0.00 @:0 B@:0
Recv:  T:40.97 /0.00 B:20.71 /0.00 @:0 B@:0
Unexpected error while reading serial port, please consult octoprint.log for details: SerialException: 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)' @ comm.py:_readline:3997
Please see https://faq.octoprint.org/serialerror for possible reasons of this.
Changing monitoring state from "Operational" to "Offline after error"
Connection closed, closing down monitor

[github-actions]

Greetings from the Marlin AutoBot!
This issue has had no activity for the last 90 days.
Do you still see this issue with the latest bugfix-2.1.x code?
Please add a reply within 14 days or this issue will be automatically closed.
To keep a confirmed issue open we can also add a "Bug: Confirmed" tag.

Disclaimer: This is an open community project with lots of activity and limited
resources. The main project contributors will do a bug sweep ahead of the next
release, but any skilled member of the community may jump in at any time to fix
this issue. That can take a while depending on our busy lives so please be patient,
and take advantage of other resources such as the MarlinFirmware Discord to help
solve the issue.