These are chat archives for SmingHub/Sming

28th
Oct 2015
alonewolfx2
@alonewolfx2
Oct 28 2015 07:10
@raburton how about flickering?
Richard Antony Burton
@raburton
Oct 28 2015 07:43
it's fine
give it a try
i need some feedback before i can merge to develop
alonewolfx2
@alonewolfx2
Oct 28 2015 09:37
Ok I will try when I get home
open-home-automation
@open-home-automation
Oct 28 2015 10:42
I just compiled esp-open-sdk and I get compile errors. rboot-api.c includes mem.h and in the SDK this for example defines os_free. But inside Sming this is redefined in system/include/esp_systemapi.h. And there are many others. If I remove the include of the mem.h header from rboot_api.c compilation goes fine. Should this include be removed/made conditional or should Sming rely on the existing mem.h instead of redefining the functions? Any opinions? @raburton?
Richard Antony Burton
@raburton
Oct 28 2015 11:16
The Sming header that defines those needs to be updated for sdk 1.4. Unfortunately there doesn't seem to be anyway to detect the version of the sdk to make these defines conditional. Not sure what the answer to that is.
hreintke
@hreintke
Oct 28 2015 11:54
@raburton :
There might be more/other updates necessary for supporting SDK 1.4.0
My suggestion would be investigate all these updates and define a Sming Release in which the only update is to move to SDK 1.4.0.
Anyone who still want (temporary) to stay at SDK 1.3.0 or lower should not upgrade to latest Sming.
open-home-automation
@open-home-automation
Oct 28 2015 12:45
My first experience is that the code runs way smoother with SDK 1.4.0 and the whole thing seems to use less heap space
For example loading webpages goes way faster
David
@dmarkey
Oct 28 2015 12:55
I'm using 1.4 with Sming and it works
are there specific API changes?
must be rboot specific
hreintke
@hreintke
Oct 28 2015 13:03
@open-home-automation :
Let's be clear. I am not against moving to new SDK support.
I only try to prevent that we have all kinds of SDK specific code/defines in Sming Core that makes it (more) difficult to maintain. We finally now have releases in which we have a clear distinction in what is in and what is not in.
We can use that by including support for new SDK versions and stop supporting old SDK version.
Anyone wanting to experiment with new SDK versions is free to do and has the possibility to submit a PR.
If then tested and OK, it will be merged to develop for final testing and inclusion in next release.
open-home-automation
@open-home-automation
Oct 28 2015 13:15
sounds fair
@dmarkey it is indeed rboot related, it includes mem.h and is probably the only place in Sming where that is actually done
Richard Antony Burton
@raburton
Oct 28 2015 16:04
@open-home-automation the workaround (and indeed the eventual fix) is to remove the offending function declarations from the header file
they are there for functions that aren't defined in the sdk, but from 1.4 onwards they have been defined in mem.h
and the declarations don't match due to a change at 1.4
Richard Antony Burton
@raburton
Oct 28 2015 18:06
hardware pwm is driving me crazy
after having it working, by which i mean not hanging the device, all evening it's gone back to not working again
Richard Antony Burton
@raburton
Oct 28 2015 18:27
looks like i'm back to square one, hw pwm worked for a couple of days, entirely by magic
and now it's gone again
zhivko
@zhivko
Oct 28 2015 19:57
Crazy
Can you tried with 2 devices?
alonewolfx2
@alonewolfx2
Oct 28 2015 20:34
@raburton i have a compile error in your new pr
C+ SmingCore/FileSystem.cpp
C+ SmingCore/HardwarePWM.cpp
In file included from SmingCore/HardwarePWM.cpp:19:0:
SmingCore/HardwarePWM.h:46:17: error: 'PWM_CHANNEL_NUM_MAX' was not declared in this scope
  uint8 channels[PWM_CHANNEL_NUM_MAX];
                 ^
SmingCore/HardwarePWM.cpp: In constructor 'HardwarePWM::HardwarePWM(uint8*, uint8)':
SmingCore/HardwarePWM.cpp:24:18: error: 'PWM_CHANNEL_NUM_MAX' was not declared in this scope
   uint32 io_info[PWM_CHANNEL_NUM_MAX][3]; // pin information
Richard Antony Burton
@raburton
Oct 28 2015 21:16
@zhivko yes, two very different devices, a nodemcu and a rgb led controller device
@alonewolfx2 odd, not sure where that's declared but it's obviously not missing on my system
I'll have a look
alon24
@alon24
Oct 28 2015 21:30
I just got my first NodeMcu V2 today, and I must say I was stupid to ever use anything else!!!! (for development)
you cannot imagine the joy of clicking flash, and it just flashes (no need for button pressing) - after all these months!!!
alonewolfx2
@alonewolfx2
Oct 28 2015 21:33
i am using cp2102+esp12q and i can use autoflash too without nodemcu :)
alon24
@alon24
Oct 28 2015 21:35
how do I run getFlashChipId in sming (ESP.getFlashChipId())
@alonewolfx2 but do u have the wiring with the rst to dtr or watever there
Richard Antony Burton
@raburton
Oct 28 2015 21:36
@alonewolfx2 it's declared in pwm.h, which is #included in HardwarePWM.h
alon24
@alon24
Oct 28 2015 21:36
how do i run native code (from espreifff) - I want to know the flsh type
alonewolfx2
@alonewolfx2
Oct 28 2015 21:40
@raburton weird . i have that file but eclipse has error message.
Richard Antony Burton
@raburton
Oct 28 2015 21:46
Not sure about that that then. Does your copy of the file have the define in it? It's in my for both sdk 1.3 & 1.4
alonewolfx2
@alonewolfx2
Oct 28 2015 21:52
yes its in my sdk 1.3 too
Murli Shenoy
@hmms
Oct 28 2015 21:55
@alonewolfx2 any pointers on how to use autoflash? I'm using http://jim.sh/ftx/ instead of cp2102
alonewolfx2
@alonewolfx2
Oct 28 2015 22:03
@hmms you need to dtr and rts pins
and it seems that module doesnt has rts
Richard Antony Burton
@raburton
Oct 28 2015 22:22
@alonewolfx2 you don't have another pwm.h that is getting picked up instead do you?
alonewolfx2
@alonewolfx2
Oct 28 2015 22:59
2 pwm.h. one in sdk folder one in smingcore folder
Murli Shenoy
@hmms
Oct 28 2015 23:03
ohh ok, i have the cp2102 as well, should i just connect dtr to reset and rts to the gpio2 pin?
alonewolfx2
@alonewolfx2
Oct 28 2015 23:04
yes thats it
Murli Shenoy
@hmms
Oct 28 2015 23:09
cool, will give it a try! :)