-
-
Notifications
You must be signed in to change notification settings - Fork 757
ESP8266 NONOS SDK 2.1/2.2/2.2.1 #1207
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
Comments
Code changes: |
@gfwilliams, please let me know if this can go to Espruino master, so I can prepare the PRs. |
V2.2 is out now. ESP8266 non-OS SDK V2.2.0 | NON-OS SDK | V2.2.0 | 2018.02.07 | https://www.espressif.com/en/support/download/sdks-demos?keys=&field_type_tid%5B%5D=14 |
We are still getting the V2.0 tool chain from tve's server: https://github.com/espruino/Espruino/blob/master/scripts/provision.sh#L60-L69
Once 2.2 is tested and working, this could be updated and moved to here: |
Eep. Yes, we should definitely be trying to drag stuff from EspruinoBuildTools now :) |
2.2 has some link issues |
Can you elaborate - Are there library changes that need changes to the makefile? What tool chain are you using? |
version:
like this:
|
build chain plus SDK 2.2 https://github.com/espruino/Espruino/blob/master/README_Building.md#under-macos |
Ok, have to replace the LD file with the new version coming with der SDK 2.2. |
There are some issue named for 2.2 at https://github.com/espressif/ESP8266_NONOS_SDK/issues |
SDK 2.2 sounds very promising (release notes) will use this wifi test created by tve to get a go or nogo for this SDK |
added ESP82666 SDK to Build 2.0, 2.1 and 2.2 to EspruinoBuildTools |
Build and change result for Espruino 1.96 with SDK 2.1 - Status: stable
|
Build result for Espruino 1.96 with SDK 2.2 - Status: infinitely reboot loop after flash using the targets/esp8266/eagle.app.v6.new.2048.ld ld complains:
|
@MaBecker This means that the RAM parts of firmware are now to big to fit within the RAM memory area. Are there constants that are not declared as constants that could to ROM? have you tried comping turning some features of such as Crypto? |
Looks like sdk 2.2 libs Need more space. https://github.com/espressif/ESP8266_NONOS_SDK/blob/master/lib/readme.md |
Thanks @wilberforce for that hint. Removing CRYPTO and GRAPHICS does not help.... Looks like Espressif did changes to their libs and now lots of stuff is puled into .irom0.text increasing Memory
result:
Sorry no idea how to handle this. |
Could need some help. |
It is ram that is the issue. You are constrained by the amount of physical ram -- so changing sizes won't help. Try reducing the jsvars to see if for you can get a build. I seem to recall the libc.a was added to the project at some point - you might want to link against the latest version. |
Well removing CRYPTO, GRAPHICS and shrink variable to 500 does not fix this. |
Change everything back to default and run a test with this ld file https://github.com/nodemcu/nodemcu-firmware/blob/master/ld/nodemcu.ld linking now works again
|
now way to boot this ..... |
put this 2.2 on hold and run test for esp01 and esp12 with sdk 2.1 |
SDK after 2.2 do not work with because Espressif decided to compile some libraries with -ffunction-sectons -fdata-sections and modify ld to put this.text.* into .irom0.text Question is it possible to reverse this with ld? |
Is it bad that they've put the text sections into irom0? I would have thought that'd be good? |
Any idea of much it is too big by? What size is the 4Mb firmware? |
No, but see attached file for all sections created with
|
like to switch to SDK 2.2 or 2.2.1 for 4mb boards. Gordon, how do you think about it? |
What does it add? And just for 4MB boards? Any chance we can keep the same SDK for all of them? |
Wait, missed to replace eagle.app.v6.new.1024 files, now the SSDK 2.2 works for all ESP8266 boards.
If you mean features: To much to name it, so just added links below Now starting test for wifi, i2c, spi and neopixel. Any thing else to test? |
Then yes, I'd definitely be up for changing it. It'd also be nice to get the relevant files into the EspruinoBuildTools repo so we're not thrashing @tve's S3 account with Travis :) |
How to run all test from folder test? |
There's no way to run tests on the device itself though. |
Well I was thinking of some code like this to do on device testing (odt)
|
got Espruino Command-line Tool 0.1.12, but looks like this is not the one to be used for --test-all
Marks-MacBook-Pro:Espruino markbecker$ espruino --test-all --board ESP8266_4MB -p /dev/cu.usbserial -b 115200 Error: Unknown Argument '--test-all', try --help |
the
This will make ./espruino in your build folder which you can then run. |
I've been after doing actual on-device testing for some time - this issue really isn't the place to discuss that though. I started a new issue at #1490 |
Updated EspruinoBuildTools, now there are all available 2.x SDKS. Decide which to choose after testing. |
add this CFLAG to get approximately 2.5k less in size, found here
without
with
|
will be updated and extended
|
Perfect - lets definitely do that then! |
How to preapare Travis build stuff? Wanted SDK is 2.2.1 and it is uploaded as zip file to folder https://github.com/espruino/EspruinoBuildTools/tree/master/esp8266 |
@MaBecker |
How ready are we to merge this? I'd like to get a new release of Espruino out this week (ideally tomorrow). Sounds like it's unlikely we'd get all the tools put in and have it tested in the next 2 days? |
Thanks @wilberforce this was exactly what I was looking for. Ok Gordon lets cross fingers an see how travis will handle this. |
|
ESP8266: switch to SDK 2.2.1 (fix #1207)
As version 2.1 is now available since May 2017 let give it a try :)
Overview:
Code changes:
Used libraries: NET, TELNET, GRAPHICS, CRYPTO and NEOPIXEL
make statement
The result looks promising, freeHeap: 11264
The text was updated successfully, but these errors were encountered: