These are chat archives for SmingHub/Sming

21st
Nov 2015
crosofg
@crosofg
Nov 21 2015 16:04
the Serial output from ESP has suddenly changed.
3Et@0@CONFIgurAtION@IN`BACKGrOund
mODE@z@stAHqxzFezstzFrzABzEyI@K@sOFtHqAzFEzstzFrzaBzEyI
ADD@IFp
ADD@IFq
DHcp@sErvEr@stArtzHIpzqyrNqvxNtnqLMAsKzruunruuNruuNpLgwzqyrNqvxNtNqI
BCN@qpp
GOG@rEGIstErEd
GOCONNECtg@rEgIstErED
GOrGBG@rEGIstErED
goMOdEG@rEGIsterED
GOFreqG`rEGIstErED
50@LIstEn@pOrt@qptuw
alonewolfx2
@alonewolfx2
Nov 21 2015 16:05
@crosofg what is this output :D
crosofg
@crosofg
Nov 21 2015 16:05
characters are appering weirdly.
mode : sta(5c:cf:7f:02:33:57) + softAP(5e:cf:7f:02:33:57)
add if0
add if1
dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)
bcn 100
'/' registered
'/connect' registered
'/rgb' registered
'/mode' registered
'/freq' registered
UDP listen port 10457
thsi should havebeen t he output
thsi is from nodemcu's dev kit
David
@dmarkey
Nov 21 2015 16:06
Did you try replugging it
crosofg
@crosofg
Nov 21 2015 16:07
the jumbled output is from the esp controller from china
alonewolfx2
@alonewolfx2
Nov 21 2015 16:07
serial program ?
crosofg
@crosofg
Nov 21 2015 16:07
coolterm
i tried many times
it works fine in nodemcu's devkit and esp12
but doesnt work on custom board
all the characters are in upper case lower case jumbled...
alonewolfx2
@alonewolfx2
Nov 21 2015 16:10
so some hw thing is wrong with your custom board
crosofg
@crosofg
Nov 21 2015 16:10
what could make thsi happrn
jsut look how words have changed!1
@rEgIstErED instead of registered
alonewolfx2
@alonewolfx2
Nov 21 2015 16:12
you said same code workig fine with other board soo its not sw related right?
i saw something like that
and i fixed just re solder and clean all pin and pads on esp and board
but maybe something broken or wrong with your serial chip on custom board
crosofg
@crosofg
Nov 21 2015 16:31
but I am able to make the LEDs blink, successfully flash the esp. doesnt that mean the serial thing is workring properly @alonewolfx2
alonewolfx2
@alonewolfx2
Nov 21 2015 16:34
maybe just rx pin bad or broken
alonewolfx2
@alonewolfx2
Nov 21 2015 21:30
@raburton i have many error on compiling lastest basic rboot on windows
alonewolfx2
@alonewolfx2
Nov 21 2015 21:49
E2 /c/tools/Sming/Basic_rBoot/out/firmware/rboot.bin
make[1]: Leaving directory `/C/tools/Sming/Sming/rboot'
C+ app/application.cpp
CC /C/tools/Sming/Sming/rboot/appcode/rboot-api.c
In file included from c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:16:0:
c:/Espressif/ESP8266_SDK/include/mem.h:5:0: error: "os_free" redefined [-Werror]
 #define os_free(s)        vPortFree(s, "", 0)
 ^
In file included from c:/tools/Sming/Sming/system/include/rboot-integration.h:11:0,
                 from c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:10:
c:/tools/Sming/Sming/system/include/esp_systemapi.h:79:0: note: this is the location of the previous definition
 #define os_free     vPortFree
 ^
In file included from c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:16:0:
c:/Espressif/ESP8266_SDK/include/mem.h:6:0: error: "os_malloc" redefined [-Werror]
 #define os_malloc(s)      pvPortMalloc(s, "", 0)
 ^
In file included from c:/tools/Sming/Sming/system/include/rboot-integration.h:11:0,
                 from c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:10:
c:/tools/Sming/Sming/system/include/esp_systemapi.h:78:0: note: this is the location of the previous definition
 #define os_malloc   pvPortMalloc
 ^
In file included from c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:16:0:
c:/Espressif/ESP8266_SDK/include/mem.h:9:0: error: "os_zalloc" redefined [-Werror]
 #define os_zalloc(s)      pvPortZalloc(s, "", 0)
 ^
In file included from c:/tools/Sming/Sming/system/include/rboot-integration.h:11:0,
                 from c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:10:
c:/tools/Sming/Sming/system/include/esp_systemapi.h:80:0: note: this is the location of the previous definition
 #define os_zalloc   pvPortZalloc
 ^
c:/tools/Sming/Sming/rboot/appcode/rboot-api.c: In function 'rboot_set_config':
c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:43:2: error: too many arguments to function 'pvPortMalloc'
  buffer = (uint8*)os_malloc(SECTOR_SIZE);
  ^
In file included from c:/tools/Sming/Sming/system/include/rboot-integration.h:11:0,
                 from c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:10:
c:/tools/Sming/Sming/system/include/esp_systemapi.h:71:14: note: declared here
 extern void *pvPortMalloc(size_t xWantedSize);
              ^
c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:62:2: error: too many arguments to function 'vPortFree'
  os_free(buffer);
  ^
In file included from c:/tools/Sming/Sming/system/include/rboot-integration.h:11:0,
                 from c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:10:
c:/tools/Sming/Sming/system/include/esp_systemapi.h:74:13: note: declared here
 extern void vPortFree(void *ptr);
             ^
c:/tools/Sming/Sming/rboot/appcode/rboot-api.c: In function 'rboot_write_flash':
c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:105:2: error: too many arguments to function 'pvPortZalloc'
  buffer = (uint8 *)os_zalloc(len + status->extra_count);
  ^
In file included from c:/tools/Sming/Sming/system/include/rboot-integration.h:11:0,
                 from c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:10:
c:/tools/Sming/Sming/system/include/esp_systemapi.h:72:14: note: declared here
 extern void *pvPortZalloc(size_t);
              ^
c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:146:2: error: too many arguments to function 'vPortFree'
  os_free(buffer);
  ^
In file included from c:/tools/Sming/Sming/system/include/rboot-integration.h:11:0,
                 from c:/tools/Sming/Sming/rboot/appcode/rboot-api.c:10:
c:/tools/Sming/Sming/system/include/esp_systemapi.h:74:13: note: declared here
 extern void vPortFree(void *ptr);
             ^
cc1.exe: all warnings being treated as errors
make: *** [out/build//C/tools/Sming/Sming/rboot/appcode/rboot-api.o] Error 1

23:48:42 Build Finished (took 1s.381ms)
sdk 1.4 windows 10 x64
hreintke
@hreintke
Nov 21 2015 22:52
@alonewolfx2 :
Develop doesn't support 1.4.0.
Use SDK 1.3.0 or include #389 in your local environment