These are chat archives for SmingHub/Sming

5th
Sep 2016
zhivko
@zhivko
Sep 05 2016 00:21
OK I tried with rtos 1.3 SDK and Basic_rBoot is giving me this:
Updating...
(...)rboot_get_config
Start...
(...)(...)Fatal exception (9): 
epc1=0x401063e0
epc2=0x00000000
epc3=0x4000dea8
epcvaddr=0xfbd7f381
depc=0x00000000
rtn_add=0x40202d08
it is crashing in:
 .text          0x0000000040106394       0x62 /home/klemen/git/SmingRtosOff/sming/compiler/lib//libsming.a(Timer.o)
                0x0000000040106398                _ZN5Timer10processingEPv
 *fill*         0x00000000401063f6        0x2
zhivko
@zhivko
Sep 05 2016 07:08
frankdownunder
@frankdownunder
Sep 05 2016 09:23
@frankdownunder Its been a while since I updated my sming sources, so I did a git pull origin master,
and now I too get this same exception. The (9) is LoadStoreAlignmentCause which I have no idea about.
It seems to me that it happens when the timer fires:
void rBootHttpUpdate::start() {
timer.initializeMs(500, TimerDelegate(&rBootHttpUpdate::onTimer, this)).start();
}
Alexander V. Ribchansky
@avr39-ripe
Sep 05 2016 10:02
@zhivko @hreintke I think Sming itself or Sming+rBoot (either nonos and rtos sdk) are broken after introduction of user_rf_cal_sector.. so in your case it loads rom2 because it CANNOT load rom1.. flashinit device so there is no leftovers, and reflash your rBoot aware app with user_rf_cal_sector and device will bootloop :( So we must change something in ld script I think to get it work again
psychegr
@psychegr
Sep 05 2016 11:34
It took me 3 days to figure out what was wrong with my websockets code and it turned out to be the esp8266 not being able to receive a continuation frame. The issue is in the websocket.cpp and .H files. I was able to make it work by erasing 2 lines and adding one more in the cpp and adding one line in the header file. Now my question is, does SmingRTOS support ssl connections?
zhivko
@zhivko
Sep 05 2016 12:38
@avr39-ripe I made it yesterday bye just overwriting location of second rom at 0x2000 I think - and then rboot found out it has unvalid rom - so it loaded 1st rom instead
so this is actually fixed with this workaround... Now I got esp up running rom0, but when I issue OTA - I get exception mentioned above - it seems it crashes inside timer
@frankdownunder: Exactly - I think this is correct
@avr39-ripe: you said: " after introduction of user_rf_cal_sector" - was this introduced in latest Sming SDK 1.3.3 ?? So in: ESP8266_RTOS_SDK_1_3 ?
Alexander V. Ribchansky
@avr39-ripe
Sep 05 2016 12:41
@zhivko no, it was introducted for nonos as 1.5.2 patch and in rtos as of 1.4.1 patch i think..
zhivko
@zhivko
Sep 05 2016 12:41
I thought they would not touch 1.3.3 branch :(
BUT! SmingRTOS is 1.3.x compatible - so I took ESP8266_RTOS_SDK_1_3 from github and same mistake!
@avr39-ripe: I dont get this :(
But yes - https://github.com/espressif/ESP8266_RTOS_SDK/tree/1.3.x - and yes! 1.3.x Updated 2 months ago by Espressif Systems!
I think at that point - SmingRTOS stopped working...
why would that crash Timer functionality?
I have put some debug inside OTA libsming - but those debugf are just not appearing in console...
zhivko
@zhivko
Sep 05 2016 12:46
What is the right way to debug it (I mean write something to console) - so i could see where it is crashing?
Alexander V. Ribchansky
@avr39-ripe
Sep 05 2016 12:50
@zhivko interesting blog! will read this bit later.. :(
hreintke
@hreintke
Sep 05 2016 18:03
@zhivko :
The rfcal patch provides a flash location for the SDK to store additional information.
If that overwrites parts which are in use there will be issues.
One of the reasons I am/was hesitant to add the rfcal in smingRTOS itself instead of leaving it to the application.
zhivko
@zhivko
Sep 05 2016 18:04
OK what do you suggest then ?
Have you tried Basic_rBoot? Is it working for you ?
If you would like to reproduce this rfcal issue you need to update to latest sdk rtos 1.3.x
hreintke
@hreintke
Sep 05 2016 18:05
It was when I tried some time ago. Will do again but I have the version as in github without any rfcal patch
zhivko
@zhivko
Sep 05 2016 18:06
it is funny why it fails in Timer ?
the patch is very small - you can easily add this just for test
hreintke
@hreintke
Sep 05 2016 18:07
Need to see, but there was an update to Timer
zhivko
@zhivko
Sep 05 2016 18:07
oh,, what kind of update... so maybe it is Timer fault ?
hreintke
@hreintke
Sep 05 2016 18:10
Everything is possible, nothing to say directly without investigation
the patch can be small, but it is also an update to the SDK which.....
frankdownunder
@frankdownunder
Sep 05 2016 21:19
I dont have the rfcal patch, but I get the exception 9 - LoadStoreAlignmentCause
hreintke
@hreintke
Sep 05 2016 21:25

Just tested, probably issue with the timer update
When I used the version with latest commit : QueuedTimer trial -> it works
Adding Complete QueuedTimer -> failed

So temporary solution revert to earlier version.
I do not expect to be able to work on a fix before the weekend