-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Startup issue (flashreload?) #3194
Comments
My first Q is have you tried recompiling your |
Recompiled "luac.cross" from https://github.com/nodemcu/nodemcu-firmware/archive/dev.zip, recompiled "lfs.img", works. TY for quick response! I'm curious about this: "luac.cross -v" tells the identical signature than the version I downloaded Oct2019. Does GH repackage that *.zip every new commit, or when? "Copyright (C) 1994-2011"... :) |
I am not sure about the whats and why but without a Minimal, Complete, and Verifiable example test case, I am left with crystal ball gazing. Sorry. |
Sorry, @TerryE , please re-open. The old master works, but the problem is there when using
as stated in OP; I'm very sorry for confusement! Let's hopefully restart from §2.
I compiled&used
as of https://github.com/nodemcu/nodemcu-firmware/archive/dev.zip 1.7.2020. The problem is still as described above: The dev starts up being freshly (erased&)flashed, but enters a boot loop (wdt) after lfs.img was What can I provide to you to catch that one? (a swarovsky type crystal ball?:) Mem dumps? |
How about a private copy of you source -- or at least as small a subset that recreates the problem. Just do a remote compile on my blog.ellisons.org.uk service and let me know. I should be able to find this because I only GC the source files daily. |
TY very much for your offer! So I tried to create a minimal LFS with the problem inside -- and landed at just having Terminal dump (freshly flashed fw):
...<74480 noise>...
...reboot. Some steps bevore, I tried a lfs with a modified _init inside; the modification was just a few
after boot (and then reboots). As the SPIFFS is empty (so, no Can you reproduce my findings? |
I tried to pull the new enhancements (pcallx et al) on my devices, but there's a showstopper.
The dev stops working with new firmare(commit: 310faf7), when LFS comes into game:
goes up and reformats SPIFFS, then, after uploading 'lfs.img' (which proofed worked bevore):
Crash "��r���n���l���".
So it seems that "node.flashreload" puts the device mad. Given that 'flashreload' doesn't overwrite any firmware code, there obviousely is a code fragment in firmware that hicks up to something in LFS(?!).
I'm not sure how to track that down, as my serial isn't able to listen on 74480, I have no chance to decrypt "��r���n���l���" things.
Helping hand, anyone? Seen that bevore?
Status: Every ~5sec (HWD):
as of https://github.com/nodemcu/nodemcu-firmware/archive/dev.zip 1.7.2020
The text was updated successfully, but these errors were encountered: