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

[BUG] FLSUN HISPEED Stuck in boot loop with SD inserted #21524

Closed
Savage79 opened this issue Apr 2, 2021 · 9 comments
Closed

[BUG] FLSUN HISPEED Stuck in boot loop with SD inserted #21524

Savage79 opened this issue Apr 2, 2021 · 9 comments

Comments

@Savage79
Copy link

Savage79 commented Apr 2, 2021

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

Yes, and the problem still exists.

Bug Description

Newest Marlin Bugfix downloaded April 2/2021.
Changed Env. to accommodate FLSUN_Hispeed motherboard.
Compiles no errors, copied .bin file to SD card, updates firmware, then gets stuck on Marlin boot screen, reboots and repeats.

Bug Timeline

Unknown

Expected behavior

Expected to finish update cycle with SD card inserted.

Actual behavior

Boot loop with SD card left in, NO SD card will boot as required

Steps to Reproduce

  1. compiled firmware as I normally do.
  2. copy Robin_mini.bin to SD card and proceeded to update motherboard
  3. get stuck on Marlin Boot screen, last 10 seconds, reboots and repeats

Version of Marlin Firmware

Marlin Bugfix 2.0.X

Printer model

Flsun QQS Pro

Electronics

Flsun HISPEED V1

Add-ons

TMC2208 in UART

Your Slicer

Prusa Slicer

Host Software

OctoPrint

If SD card is left in the motherboard it will remain in a boot-loop, however
when card is removed boots as normal.

Marlin.zip

@Savage79 Savage79 changed the title [BUG] FLSUN HISPEEP Stuck in boot loop with SD inserted [BUG] FLSUN HISPEED Stuck in boot loop with SD inserted Apr 3, 2021
@chrisjenda
Copy link

I have tracked commit 6e0b79a to be the root cause of this issue.
Pulling the latest commit of Bugfix Branch "Bump distribution date (2021-04-03)" (dd76a50) and reverting the commit fixes the issue.

@rhapsodyv
Copy link
Member

@chrisjenda thanks! I was suspecting of this too. But I didn’t had time to check.

If you don’t mind to test, I can send you a PR.

Probably it’s failing to use 4 bit.

@chrisjenda
Copy link

chrisjenda commented Apr 3, 2021

I am 100% free to test anything to get this to work! I'll give that PR a go!

@Foxies-CSTL
Copy link
Contributor

Hello,
I also had this problem that I solved by commenting in the line "//#define SDIO_READ_RETRIES 16" of the PINS file.
I have not revalidated it since.

@petergebruers
Copy link

I can confirm the problem (branch bugfix-2.0.x Commit 0bd113b) causes a boot loop on my QQ-S Pro if I leave the SD card in the printer. Tried 2 different cards 4GB white label vs Samsung 32 GB.

I solved by commenting in the line "//#define SDIO_READ_RETRIES 16" of the PINS file.

I can confirm that this fixes the boot loop for me as well.

I only started using Marlin a week ago on my first 3d printer, I cannot add much weight to this discussion. I do toy with MCUs and I am wondering why "16" instead of "3" causes is issues, or why it was set to 16 in the first place (I ran git blame, does not give a hint). So consider this to be "a vote up" for that solution from "an informed noob"

@dredivan
Copy link

dredivan commented Nov 18, 2021

I have same problem on BOARD_FLSUN_HISPEED FLSUN HiSpeedV1 STM32F103VET6 with latest bug-fix

//#define SDIO_READ_RETRIES 16
don`t help me without RESET EEPROM,
after reset eeprom boot all OK!

@tpruvot
Copy link
Contributor

tpruvot commented Nov 18, 2021

You can try to reduce the clock here :
Marlin/src/pins/stm32f1/pins_FLSUN_HISPEED.h:258: #define SDIO_CLOCK 4500000 // 4.5 MHz

But your case may be due to the quality of your SD card or just to some errors on it, in general a fresh format fixes the problem too...

a common cheap SD card (not latest ones) can run between 18 and 20MHz if properly wired (not on a long flat cable without shielding)

@github-actions
Copy link

github-actions bot commented Oct 8, 2023

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.

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 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants