-
-
Notifications
You must be signed in to change notification settings - Fork 348
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
Spiffy crash during build #228
Comments
@tprochazka What is the spiffy source/version? Did you try one from here ? |
@kireevco which version should b supported with Sming? I have found many different versions/forks out there...we should recommend the proper one in the wiki or readme so everyone is using the proper version. |
I used this link to download spiffy I hope, that it should be right version. |
So it is exactly the same file. |
@tprochazka default spiffy size is 196608(192KB). Propably your files bigger than 192kb and thats why its crashing. I am trying to add auto size calculation in spiffy. i will push shen its ready. |
@alonewolfx2 |
@flexiti i am building on windows. just change your msys mingw order in your system path. msys should first |
@alonewolfx2 btw. spiffs.h It should be the same as those in the Sming spiffs directory? |
looks like a msys/mingw problem to me. Make sure to change their paths On Tue, Sep 29, 2015 at 9:12 AM, flexiti notifications@github.com wrote:
|
its ok now thanks |
@flexiti : Wait a few days and you will see the workflow as we see it now 😄 |
@hreintke |
I changed in spiffs.h in @alonewolfx2 spiffy Generate firmware images successully in folder out/firmware. Generating spiffs_binChecking for spiffs files but in both cases (modemcu and alonewolfx2 spiffy) the file size application.txt = 0 (read by ftp) |
@flexiti On Tue, Sep 29, 2015 at 1:06 PM, flexiti notifications@github.com wrote:
|
C:\Users\mariuszb>echo %PATH% C:\Users\mariuszb>echo %SMING_HOME% C:\Users\mariuszb>echo %ESP_HOME% C:\Users\mariuszb>dir %SMING_HOME% Katalog: C:\tools\sming\Sming 2015-09-01 11:13 .2015-09-01 11:13 .. 2015-09-05 13:17 6 723 .cproject 2015-08-31 16:18 815 .project 2015-09-01 11:11 .settings 2015-09-01 11:11 appinit 2015-09-01 11:11 apptest 2015-09-01 11:11 compiler 2015-09-01 11:11 include 2015-09-05 13:17 Libraries 2015-08-31 16:18 7 687 License.txt 2015-08-31 16:18 6 504 Makefile 2015-08-31 16:18 576 Makefile-bsd.mk 2015-08-31 16:18 567 Makefile-linux.mk 2015-08-31 16:18 567 Makefile-macos.mk 2015-08-31 16:18 10 975 Makefile-project.mk 2015-08-31 16:18 512 Makefile-windows.mk 2015-09-08 11:38 out 2015-09-01 11:11 Services 2015-09-01 11:11 SmingCore 2015-09-01 11:11 system 2015-09-01 11:11 Wiring 9 plik(ów) 34 926 bajtów 13 katalog(ów) 98 314 981 376 bajtów wolnych C:\Users\mariuszb>dir %ESP_HOME% Katalog: c:\Espressif 2015-08-25 09:19 .2015-08-25 09:19 .. 2015-07-09 22:34 17 319 changelog.txt 2015-05-21 21:52 2 061 Command line Unofficial Development Kit for Espressif ESP8266.lnk 2015-04-11 23:37 186 DevKit web site.url 2015-08-25 09:18 docs 2015-08-12 13:38 esp8266-github 2015-08-25 09:19 ESP8266_MESH_SDK 2015-08-25 09:19 ESP8266_RTOS_SDK 2015-08-12 13:36 ESP8266_SDK 2015-06-10 15:46 ESP8266_SDK_094 2015-06-10 15:46 ESP8266_SDK_095 2015-06-10 15:46 ESP8266_SDK_101 2015-06-10 15:46 ESP8266_SDK_110 2015-08-25 09:18 ESP8266_SDK_120 2015-04-11 23:37 180 Espressif web site.url 2015-08-26 13:21 examples 2015-06-10 15:46 extra 2015-03-25 09:16 137 750 Install.ico 2015-07-06 16:41 sdk [c:\Espressif\ESP8266_SDK] 2015-08-10 22:56 628 701 unins000.dat 2015-06-10 15:44 1 312 112 unins000.exe 2015-08-10 22:56 23 001 unins000.msg 2014-11-21 10:45 147 878 Uninstall.ico 2015-08-12 13:38 utils 2015-06-10 15:44 xtensa-lx106-elf 9 plik(ów) 2 269 188 bajtów 17 katalog(ów) 98 314 981 376 bajtów wolnych |
ok it seems there is no mingw in your path. try this
|
I added, but unfortunately no change In file included from src/main.c:1:0: |
i dont have errno.h and here is my result on windows
|
@flexiti your error seems your system still using mingw first. you can try restart machine. you need msys first for building spiffy |
If you renamed the variable you'd also need to rename it where it's used. Otherwise those uses of the variable will be referring to the existing errno function, not the newly named local variable. This reminds me of a problem @robotiko fixed for someone the other day, random compile errors that didn't occur for anyone else (building esptool2 on windows). Turned out the person had half a dozen different sdks and compilers installed and stuff was getting picked up from all over the place. Might be worth rationalising your environment and making sure you have a single good base to work from. |
@alonewolfx2 C:\mingw\msys\1.0\bin;C:\mingw\bin; --- is it not ok ? (system was restarted) |
btw. |
Just curious why don't you want to use a binary? Sent from my iPhone
|
Could you explain more? |
@alonewolfx2 : When I clone spiffy from xlfe/spiffy (think the version you adapted) I can compile with mingw\bin\gcc -> looks like the issue is caused by your updates. |
changing s32_t errno to errnos ( in all spiffy files) makes the compilation is correct ... that does not change the fact that I still does not have the files on the ftp :) |
@flexiti we had same issue with @kireevco and my lastest repo compiling fine on windows with msys. @hreintke i didnt tried lastest xlfe's spiffy. sming using different flash block sizes and thats why we cant use if xlfe not changed that. but if he change its not working on nodemcu. if we need main xlfe's repo to use (its not necessary i think) we need to push all changes into the both xlfe and nodemcu repo. |
@flexiti you dont need any changes in my repo including errno.h. if you changed errno's it cant run on chip. i mean it can run but wrong. i saw all what you saw. i had same issues what you had. |
@alonewolfx2 if I do not change in Your repo my compilation is with errors. my PATH: C:\mingw\msys\1.0\bin;C:\mingw\bin;...... |
it should be ok with this orders but is it system path or user path? |
system, user is empty |
@alonewolfx2 with Yours spiffy.exe works ok |
@alonewolfx2 : |
@hreintke we can't use xlfe spiffy because it doesn't have enough features (specify directory, specify spiffs size), but we need to see if we can make it work with all compilers. But is this really such a priority? |
@kireevco virtually any WWW application with internet access required web pages,other files - You want always to manually load each via FTP ?? |
@kireevco : If you read my post above you see that I know we cannot use xlfe spiffy. |
@flexiti What do you mean? Spiffy takes 'files' directory and makes a filesystem bin. Uploading via FTP is not a production way. @hreintke I do read posts. |
@kireevco You are reading posts ? When I read your response I'm not sure |
At least 4 examples need Spiffy, and I all the day write here that I (see not only I) have the problems with spiffy so @kireevco "But is this really such a priority?" - exactly what you mean by writing this ? You previously written: |
@flexiti you seem very frustrated, sorry to hear that.
What I mean is that spiffy has been working OK with mingw gcc for months. Fixing it to work in all possible environments takes time, which could be solved somewhere else in development, so "is this really such a priority?"
Normally you should do @flexiti when you talk to someone specifically :) I meant, why don't you download spiffy from here? |
@flexiti priority mean update all code for xlfe's repo isn't necessary . We know spiffy necessary for many projects. You can use prebuilded spiffy binary.also we know we need some more information for usage. But.. Almost all spiffy problems come with "file sizes". You need to select right spiff size for correct working and I will add automatic spiff size calculation when I free time or if anyone can pull request it will be fine. |
@hreintke and can you please build from the command line, with |
|
@hreintke i can build both
|
with the gcc from mingw\bin as the first in the path ? |
msys first |
try the other way around |
From the version which has spiffy as make target, I have no problem. |
Very weird thing happen to me. If I run "ALL" target from Eclipse.
Spiffy crash
But if I run from the command line directly
spiffy 524288 web/build
It works correctly.
Does anybody have the same problem?
The text was updated successfully, but these errors were encountered: