-
-
Notifications
You must be signed in to change notification settings - Fork 19.3k
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] Robin Nano 1.2 boot issue #26577
Comments
recent changes to U8glib-HAL have broken things MarlinFirmware/U8glib-HAL@c1ec1a4 |
fixing your max temp to #define HEATER_0_MAXTEMP 260 and forcing marlin to use older U8glib-HAL Change features.ini line Will allow you to build right now, till this issue is fixed properly |
Can also be fixed by editing .pio/libdeps/mks_robin_nano_v1v2/U8glib-HAL/src/clib/u8g.h And adding the block
after the block
|
Issue opened on U8glib-HAL MarlinFirmware/U8glib-HAL#32 |
It compiles but screen freezes at: Updating 100%
…On Wed, Dec 27, 2023 at 6:01 PM ellensp ***@***.***> wrote:
Can also be fixed by editing
.pio/libdeps/mks_robin_nano_v1v2/U8glib-HAL/src/clib/u8g.h
And adding the block
/* OLED 128x64 Display with SSD1309 Controller - Fast Single Page */
extern u8g_dev_t u8g_dev_ssd1309_128x64_f_sw_spi;
extern u8g_dev_t u8g_dev_ssd1309_128x64_f_hw_spi;
extern u8g_dev_t u8g_dev_ssd1309_128x64_f_i2c;
after the block
/* OLED 128x64 Display with SSD1309 Controller */
extern u8g_dev_t u8g_dev_ssd1309_128x64_sw_spi;
extern u8g_dev_t u8g_dev_ssd1309_128x64_hw_spi;
extern u8g_dev_t u8g_dev_ssd1309_128x64_i2c;
—
Reply to this email directly, view it on GitHub
<#26577 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFWG4XF2FLTMZY3LYRUXBLYLQZ55AVCNFSM6AAAAABBELKT3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZQGM4DINZWGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The same happens with this solution stuck at 100% :(
…On Wed, Dec 27, 2023 at 4:42 PM ellensp ***@***.***> wrote:
fixing your max temp to #define HEATER_0_MAXTEMP 260 and forcing marlin to
use older U8glib-HAL
Change feature.ini line
HAS_MARLINUI_U8GLIB = marlinfirmware/U8glib-HAL@~0.5.2
to
HAS_MARLINUI_U8GLIB = ***@***.***
Will allow you to build right now, till this issue is fixed properly
—
Reply to this email directly, view it on GitHub
<#26577 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFWG4U7CPOMN2NEVA4IKX3YLQQWHAVCNFSM6AAAAABBELKT3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZQGMYTQNJSGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
In addition to the |
If it is confirmed that rolling back that commit fixes an issue then I need another set of eyes on bd36644. I don't see how that commit changes anything that would affect a Robin Nano 1.2 (or indeed anything at all, since it just moves the u8g assignments to the HALs but does not change them). |
Once U8G 0.5.4 propagates to the PIO registry the build issue will be fixed and this can be closed.
That may or may not be related to the U8G changes. When was the last time you re-flashed Marlin before today? |
For completeness, I forced Marlin to use Not sure about ahmetcemturan's issue though. |
Rolling Back still does not work for me. It gets stuck at 100% and after
Reboot "Booting...."
I want to mention that my nano 1.2 is the one with the onboard drivers..
That's what I got after frying the other one :(
Maybe it makes a difference..
…On Thu, Dec 28, 2023 at 2:40 AM Keith Bennett ***@***.***> wrote:
Once U8G 0.5.4 propagates to the PIO registry the build issue will be
fixed and this can be closed.
For completeness, I forced Marlin to use 0.5.4 with HAS_MARLINUI_U8GLIB =
U8glib-HAL=
https://github.com/MarlinFirmware/U8glib-HAL/archive/refs/tags/0.5.4.zip
with current bugfix-2.1.x and tested changes on a BTT Mini 12864 V2 (with
NeoPixels) and it works fine.
Not sure about ahmetcemturan's issue though.
—
Reply to this email directly, view it on GitHub
<#26577 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFWG4UG6CROGHZR6ARE6VLYLSWVJAVCNFSM6AAAAABBELKT3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZQGY4TIMRUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
To clarify: I am not using github for tracking. So I downloaded from
https://github.com/MarlinFirmware/Marlin/tree/c485f513d70acc838b7a1554c955fdaf5ef3df7f
Adapted my Configuration files and I changed features.ini. That's all..
|
On board drivers? url to the board? as thats not standard and I wonder if other things have been changed, |
I think it is called nano s. I will open it up and look at the board when I get home
|
Have you successfully ran a prior version of Marlin on this board or is it brand new? |
Yes of course.. I am reverting to it every time.
#define STRING_DISTRIBUTION_DATE "2023-10-12"
…--
Ahmet Cem Turan
+90 555 455 5444
14:06, 28 December 2023, Keith Bennett ***@***.***>:
Have you successfully ran a prior version of Marlin on this board or is it
brand new?
—
Reply to this email directly, view it on GitHub
<#26577 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFWG4W56ETWUKJ5Y7WTOXTYLVHCLAVCNFSM6AAAAABBELKT3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZRGA3DENJVHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
and the board is marked as: MKS Robin Nano-S V1.3
https://github.com/makerbase-mks/MKS-Robin-Nano-V1.X
|
So you were running this version prior to updating? I think you just happened to get caught in that u8glib error like everyone else and it's not related. Would you be able to test some The strategy is to find a commit from some point in the "distant" past where the feature works (2023-10-12 in your case). Then, test a commit from halfway between that date and today… And then you keep going to the commit halfway in between your "known to work" commit and your "known to be broken" commit until you find the exact day where it broke. If you started from a point 256 commits in the past, it would take no more than 8 tests to find the exact commit that broke it. You can do this manually from the Manually Test Commits
|
Iteration.. OK I will do it..
…On Thu, Dec 28, 2023 at 6:22 PM Keith Bennett ***@***.***> wrote:
#define STRING_DISTRIBUTION_DATE "2023-10-12"
So you were running this version prior to updating? I think you just
happened to get caught in that u8glib error like everyone else and it's not
related.
Would you be able to test some bugfix-2.1.x commits
<https://github.com/MarlinFirmware/Marlin/commits/bugfix-2.1.x> to narrow
this down?
The strategy is to find a commit from some point in the "distant" past
where the feature works (2023-10-12 in your case). Then, test a commit from
halfway between that date and today… And then you keep going to the commit
halfway in between your "known to work" commit and your "known to be
broken" commit until you find the exact day where it broke.
If you started from a point 256 commits in the past, it would take no more
than 8 tests to find the exact commit that broke it.
You can also do this manually from the bugfix-2.1.x commit history if
that's easier:
Manually Test Commits
1.
To manually test commits, browse bugfix-2.1.x's commit history
<https://github.com/MarlinFirmware/Marlin/commits/bugfix-2.1.x> using
the *< >* button on the right:
[image: image]
<https://user-images.githubusercontent.com/13375512/248270287-2d2620f8-9675-4d66-9c6b-42838ac543fa.png>
2.
Click on the green *< > Code ▼* button and then "Download ZIP":
[image: Download ZIP]
<https://user-images.githubusercontent.com/13375512/248270679-351b76b6-9c4a-4b56-88b4-c7174ed3fec9.png>
3.
Apply your minimal config changes, build & flash Marlin to your
printer, and observe if the reported issue can be reproduced.
—
Reply to this email directly, view it on GitHub
<#26577 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFWG4SF3SFOXMJDXL6YUSTYLWFBVAVCNFSM6AAAAABBELKT3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZRGI3DSNJUGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I fucked up. Really sorry about it. When updating the config files I
somehow took the config file of my old board (the fried one) for
reference.. So the board was wrong. It has to be
BOARD_MKS_ROBIN_NANO_V1_3_F4
Noticed that when starting the iteration...
So your fix with the tilde removal worked. (not tested but Printer boots)
Again really sorry.
On Thu, Dec 28, 2023 at 7:46 PM Ahmet Cem TURAN ***@***.***>
wrote:
… Iteration.. OK I will do it..
On Thu, Dec 28, 2023 at 6:22 PM Keith Bennett ***@***.***>
wrote:
> #define STRING_DISTRIBUTION_DATE "2023-10-12"
>
> So you were running this version prior to updating? I think you just
> happened to get caught in that u8glib error like everyone else and it's not
> related.
>
> Would you be able to test some bugfix-2.1.x commits
> <https://github.com/MarlinFirmware/Marlin/commits/bugfix-2.1.x> to
> narrow this down?
>
> The strategy is to find a commit from some point in the "distant" past
> where the feature works (2023-10-12 in your case). Then, test a commit from
> halfway between that date and today… And then you keep going to the commit
> halfway in between your "known to work" commit and your "known to be
> broken" commit until you find the exact day where it broke.
>
> If you started from a point 256 commits in the past, it would take no
> more than 8 tests to find the exact commit that broke it.
>
> You can also do this manually from the bugfix-2.1.x commit history if
> that's easier:
> Manually Test Commits
>
> 1.
>
> To manually test commits, browse bugfix-2.1.x's commit history
> <https://github.com/MarlinFirmware/Marlin/commits/bugfix-2.1.x> using
> the *< >* button on the right:
> [image: image]
> <https://user-images.githubusercontent.com/13375512/248270287-2d2620f8-9675-4d66-9c6b-42838ac543fa.png>
> 2.
>
> Click on the green *< > Code ▼* button and then "Download ZIP":
> [image: Download ZIP]
> <https://user-images.githubusercontent.com/13375512/248270679-351b76b6-9c4a-4b56-88b4-c7174ed3fec9.png>
> 3.
>
> Apply your minimal config changes, build & flash Marlin to your
> printer, and observe if the reported issue can be reproduced.
>
> —
> Reply to this email directly, view it on GitHub
> <#26577 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAFWG4SF3SFOXMJDXL6YUSTYLWFBVAVCNFSM6AAAAABBELKT3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZRGI3DSNJUGU>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
U8Glib version 0.5.4 is now available in PIO's registry, so it'll be used when compiling new firmware (and I opened a PR to update our |
Y Endstop is unresponsive. Not inverted. |
If you can't find a resolution post a new issue about it and there we can work towards a solution. In the meantime, you might enable |
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. |
Did you test the latest
bugfix-2.1.x
code?Yes, and the problem still exists.
Bug Description
When trying to compile for the Robin NAno 1.2 I get the following message:
Bug Timeline
It is existent in the latest bugfix
Expected behavior
Compile correctly
Actual behavior
Fails and gives following error:
Steps to Reproduce
I have attached my config files.
Version of Marlin Firmware
2.1.2 or 2.1.bugfix
Printer model
Sapphire Pro
Electronics
Robin Nano 1.2
LCD/Controller
No response
Other add-ons
No response
Bed Leveling
None
Your Slicer
None
Host Software
None
Don't forget to include
Configuration.h
andConfiguration_adv.h
.Additional information & file uploads
Marlin.zip
I tried to compile by commenting out the whole section that throws the errors and it compiled but then the printer got stuck at "updating 100%" . After reboot it hangs at "booting".
The text was updated successfully, but these errors were encountered: